When you run more than one company inside a single Odoo database, stock genuinely moving between them creates a reconciliation headache. A warehouse operator confirms a delivery from Company A, but nothing lands in Company B until someone manually keys in a matching receipt — and the two picks drift out of sync, valuations diverge, and month-end inventory never quite ties out. Odoo's native inter-company rules can mirror sales and purchase documents between companies, but out of the box they do not reliably create a fully-linked, valuation-correct counterpart stock.picking for every warehouse transfer, especially when you are moving stock without a customer invoice or across different warehouses, operation types, and unit-of-measure setups. Teams end up bridging that gap with spreadsheets and double data-entry.

ECOSIRE builds a made-to-order Odoo module that closes this loop. When a validated outgoing transfer is detected in the source company, the module creates the matching counterpart document in the destination company — a receipt against your delivery, or a delivery against your receipt — with the correct partner company, warehouse, operation type, source/destination locations, products, quantities, lots/serials and unit of measure carried across. Technically it hangs off stock.picking/stock.move state transitions (an @api.depends-driven flag plus a server action or base.automation rule), runs the counterpart creation with sudo() in the target company's context so multi-company record rules are respected, and stores a bidirectional link between the two pickings (a custom Many2one on each side) so the pair is always traceable. We add ir.model.access.csv entries and record rules so users only see documents for companies they belong to, plus configurable per-company-pair settings (which warehouse and operation type to post into, whether to auto-validate or leave the counterpart in draft for review, and how to map locations).

The build is grounded in the way your business actually operates. During scoping we map each company pair, your warehouse and location topology, whether you need lot/serial and expiry propagation, landed-cost or inter-company price handling, and whether counterpart documents should auto-confirm or wait for a receiving check. We wire optional QWeb transfer notes, an audit log of every generated pair, and — where you integrate external systems — expose the linkage over the standard XML-RPC/JSON-RPC API so a WMS or middleware can read both sides. The module is delivered as a clean, upgrade-safe addon in its own __manifest__.py, targeting your exact Odoo series (17.0, 18.0 or 19.0) and respecting Community vs Enterprise differences in the inventory app.

Delivery is build-to-order: after a short scoping call we confirm the company-pair matrix and behaviour rules, then build, test on a staging copy of your database, run UAT with your team, and deploy to production — typically one working week from confirmed scope. You receive the full source, documentation, a training session and a post-go-live support window. Pricing starts from $999 (indicative, single-company-pair base scope); additional company pairs, lot/serial and landed-cost propagation, multi-warehouse mapping, and integration with external WMS or middleware increase the quoted scope.