When businesses operate multiple entities across jurisdictions, shareholders, or data boundaries, consolidating everything into a single Odoo can be impossible. For one high-volume customer, we built an inter-Odoo bridge between two instances (v16 and v18), using only Odoo Studio and APIs. The result? Seamless stock syncing, shared sales flows, and synchronized chat messages and attachments—all without touching core code.
Introduction: The Case for Multi-Odoo Integration
Odoo is famously modular and multi-company ready—but sometimes, running all entities on a single instance isn’t viable. Legal barriers, traffic limitations, or shareholder concerns may require each branch to have its own database. The consequence? Teams exchanging PDFs and Excel sheets, wasting time on double input and manual updates.
We encountered this challenge with one of our customers managing large-scale goods movement between branches. They needed real-time visibility, but without merging ERPs.
Syncing Stock Across Instances
We solved the problem using API-based syncing between the “factory” (Odoo 16) and “buyer” (Odoo 18) systems. At scheduled intervals, the factory instance exports its stock availability to a custom table on the buyer's side—ensuring low bandwidth usage and no performance bottlenecks.
From there, the replenishment team simply ticks the products they need and confirms the selection. This triggers the creation of a draft packing list *automatically* in the factory's Odoo—removing all need for external communication.
Orders, Packing Lists, and Confirmations—All Synced
We didn’t stop at stock: sales orders, purchase orders, and packing lists all flow between systems.
The buyer creates a purchase order → it's mirrored as a sales order in the factory instance. A confirmation/rejection flow is added to the chatter (buttons), and responses trigger corresponding actions remotely.
The same applies to logistics: once the factory completes a packing list and scans goods into the container, all details are automatically transferred to the buyer instance—ready for reception.
Shared Communication & Attachments: Unified History
To align teams across both sides, we also synchronized chatter messages and document attachments. If a buyer comments on a PO or uploads a revised drawing, it immediately appears on the corresponding document in the factory instance, and vice versa.
This removes the need to forward emails or screenshots, letting teams collaborate with a shared document history as if they were on the same system.
Conclusion: When Two Odoos Work as One
Sometimes, you can’t consolidate—but that doesn’t mean you can’t integrate. By combining the power of Odoo Studio, a bit of API logic, and real operational insight, we helped our customer eliminate manual workflows between systems and speed up their operations.
If you have similar challenges—multiple entities, isolated systems, or cross-company coordination—there’s a smarter, more connected way forward.
Need to bridge two Odoo systems?
Let's make your operations smoother and smarter—contact Majorbird for a demo of our inter-Odoo sync solution today.