Integration Service
Odoobravo: Connecting Odoo & Openbravo
A microservices integration layer that lets Odoo and Openbravo run side by side, sharing data instead of competing for it.
Many businesses end up running both platforms at once, Openbravo on the retail or point-of-sale side, Odoo for back-office finance, HR, or manufacturing, often after a merger, an acquisition, or simply because each system was chosen for a different part of the business. Rather than forcing a costly migration to one platform, Odoobravo keeps both systems in place and connects them with a dedicated integration layer.
How it works
A set of independent microservices, each responsible for one data domain, sits between the two platforms and keeps them in sync.
Sync services
Independent microservices handle one data domain each, products, customers, orders, inventory, or invoices, calling each platform's native REST APIs rather than touching either database directly.
Message queue
Changes in one system are queued as events and delivered to the other, so a burst of activity, like a busy sales day, doesn't overwhelm either platform or cause records to be missed.
Mapping & reconciliation
A mapping layer translates each platform's field names, units, and currencies into the other's format, with scheduled reconciliation checks that flag records that fall out of sync.
What typically gets connected
Products & inventory
Stock levels and product catalogs kept consistent between Openbravo's retail/POS side and Odoo's operational or manufacturing side, so neither platform oversells or shows stale stock.
Sales & orders
Orders captured in one platform, for example POS sales in Openbravo, flow through to Odoo for fulfillment, accounting, or reporting, without double entry.
Customers & partners
A single customer record shared across both systems, so support, sales, and finance teams aren't working from two different versions of the truth.
Financial data
Invoices, payments, and journal entries reconciled between platforms so finance can close the books without manually merging exports from two systems.
Why a microservices approach
- No rip-and-replace: both platforms keep running as-is, so teams already trained on Openbravo or Odoo don't need to relearn a new system.
- Independent scaling: each sync service can be scaled, updated, or restarted on its own without taking the whole integration down.
- Easier troubleshooting: when something goes wrong, it's isolated to one data domain, inventory sync issues don't affect customer or invoice sync.
- Room to grow: new services can be added later, a new sales channel, a third platform, a reporting layer, without redesigning the whole integration.
Running both Odoo and Openbravo?
We can map out what needs to sync between your two platforms and design an integration layer that fits.
Talk to Us