In a multi-site Odoo deployment, every internal user with inventory rights can see every warehouse and every stock location by default. A picker in your Dubai branch can pull quants from the Karachi warehouse; a branch storekeeper can select the wrong source location on a delivery; and inventory reports mix numbers across sites that should never be cross-visible. Odoo core gives you stock.warehouse and stock.location records and a few multi-company sharing rules, but it has no concept of "this user may only operate within these warehouses." Once you have more than one physical site — or franchisees, 3PL partners, and branch teams sharing one database — that missing access boundary becomes a daily source of mis-picks, wrong-location stock moves, and data leakage.

We build a made-to-order module that adds a genuine per-user warehouse and location restriction layer. Technically, it introduces a many2many between res.users and stock.warehouse (and, where you need finer control, stock.location) declared in a __manifest__.py that depends on stock. Enforcement is done the right way — through ir.rule record rules against stock.warehouse, stock.location, stock.picking, stock.move, and stock.quant, evaluated with user.id in the domain so the restriction holds on the ORM, in every list/kanban/form view, in reports, and over the XML-RPC/JSON-RPC API alike (not just hidden in the UI, which a smart user can bypass). Default warehouse assignment on operations, source/destination location domains, and the warehouse selector on stock.picking and sale.order are constrained to the user's allowed set via @api.onchange/@api.depends computes and domain filters. Because it is record-rule based, it composes cleanly with your existing multi-company setup and Odoo's security groups rather than fighting them.

The behavior is configured to your reality: a warehouse-manager group that sees a defined subset, an admin group that bypasses the restriction, optional read-only vs. read-write distinction per site, and sensible defaults so a restricted user's new transfers and orders pre-fill their home warehouse. We ship it as installable source you own, tested on your actual location tree so the record-rule domains match how your stock.location hierarchy is really structured — Community or Enterprise, on Odoo 17.0, 18.0, or 19.0.

Because this is build-to-order, delivery is typically 2-4 weeks from confirmed scope: we run a short scoping call, agree the exact restriction matrix and edge cases, build on a staging copy of your database, run UAT with your users, then install to production with a rollback plan. Pricing starts from $249 (indicative, single-company base scope); multi-company enforcement, per-location (not just per-warehouse) granularity, restrictions extended to purchase/manufacturing/POS documents, and data migration of existing user-warehouse mappings increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.