Groups running several legal entities on one Odoo database hit a recurring wall the moment stock has to move between companies. Odoo core handles internal transfers cleanly inside a single company, but a delivery from Company A to Company B is not one stock move — it is a sale/purchase pair or a manual double entry someone has to remember to reconcile. Teams create a delivery order in the source company, then hand-key a matching receipt in the destination company, re-typing quantities, lots, serials and costs, and hope the two sides agree at month-end. Valuation drifts, in-transit stock is invisible, and inter-company reconciliation becomes a spreadsheet exercise. A typical off-the-shelf apps.odoo.com module tends to cover one narrow flavour of this and rarely matches your chart of accounts, costing method, or approval rules.

This is what we build to order: a Multi-Company Inventory Transfer module that treats a cross-company movement as a single, governed transaction. At the ORM layer we add a transfer document model (models.Model) that, on confirmation, orchestrates the paired stock.picking records in the source and destination companies and links them with stored relational fields so each side always knows its counterpart. Quantities, stock.lot/serial numbers, packages, and unit cost are carried across via @api.depends computes and create()/write() overrides, so the receiving company inherits the same traceability and valuation basis instead of a re-keyed guess. An optional in-transit location and a two-step (send/receive) flow make goods that have left one company but not yet arrived at the other fully visible on both stock ledgers.

Because this rides on Odoo's own multi-company plumbing, we wire it to your real structure: res.company boundaries, per-company warehouses and operation types, and — where the entities also transact financially — the inter-company journal/pricing rules so a stock transfer can optionally raise the matching internal invoice or leave accounting untouched, per your policy. Access is locked down with ir.model.access.csv plus record rules scoped by company_ids/company_id so a user only ever sees transfers their companies are party to; automated actions or scheduled jobs can auto-confirm receipts or flag stuck in-transit lines. The UI is delivered as standard form/list/kanban views (XML, with OWL where an interaction warrants it) and a QWeb transfer note/report for the warehouse floor, and everything is reachable over the XML-RPC/JSON-RPC API for external systems. We build against your target release — Odoo 17.0, 18.0, or 19.0 — and account for Community vs Enterprise differences (for example, native inter-company rules and some valuation features differ by edition), so the module behaves correctly on the exact stack you run.

Delivery is build-to-order. We start with a short scoping call to confirm which companies, warehouses, costing method (standard/FIFO/AVCO), lot/serial requirements, whether accounting entries are in or out of scope, and your target Odoo version and edition. You approve a fixed quote and scope, we build and unit-test on a staging copy of your database, run UAT with your team, then install to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, depending on complexity and how many entities and integrations are in play. Pricing starts from $249 (indicative, single-company base scope); additional companies, inter-company accounting/invoicing, multi-warehouse and in-transit routing, and data migration volume increase the quoted scope.