Master data
Customers, vendors and materials flowing from SAP into Odoo as the authoritative source, with changes travelling one way to avoid divergence.
There are two honest reasons to connect Odoo to SAP, and they lead to different projects. One is coexistence: SAP stays as the group system and Odoo runs a subsidiary, a plant or a business line. The other is migration: Odoo is where you are going, and the connection is temporary scaffolding.
Mixing them up is expensive. A coexistence design assumes SAP is permanent; a migration design assumes the opposite. We ask which one you are doing before quoting anything.
Businesses running Odoo with OdooBots
Odoo SAP integration either lets the two systems coexist with a defined master-data boundary, or carries a staged migration from SAP to Odoo. In coexistence, SAP typically owns customer, vendor and material master data and the consolidated ledger, while Odoo runs the operations of a unit — orders, stock, production, invoicing — and posts summarised results back. In migration, data moves in planned waves with a reconciliation at each step.
SAP integration cost is driven almost entirely by what your SAP team can expose and how quickly they can act. The Odoo side is rarely the constraint, and a project plan that assumes otherwise will slip.
Six things move between SAP and Odoo, and which of them apply depends on whether you are coexisting or migrating.
Customers, vendors and materials flowing from SAP into Odoo as the authoritative source, with changes travelling one way to avoid divergence.
Orders raised in Odoo for the unit it runs, with references carried so an SAP enquiry can find the Odoo transaction behind it.
Stock levels and movements for the plants or warehouses Odoo manages, reported back at the level the group actually needs.
Summarised journal entries posted to the group ledger rather than every transaction, which is nearly always what finance wants.
Manufacturing orders, consumption and output in Odoo, with the material and cost effect reported into SAP.
Where the goal is to leave SAP, data moving in planned waves — master, open items, balances — each reconciled before the next.
In a coexistence design, master data arrives from SAP overnight and Odoo runs the unit’s day: quotations, orders, picking, production, invoicing. At period end a summarised set of journal entries goes back to the group ledger, with references that let a group accountant trace a figure to the Odoo transaction behind it.
In a migration design, the same connection runs in reverse and temporarily: data moves out of SAP in waves, each reconciled against SAP’s own reports before the next wave starts, until the connection is switched off.
These are the decisions that are cheap to make now and painful to reverse once two systems have been exchanging records for a month.
Which project you are actually doing. The designs are different and choosing late is the most expensive mistake available.
Which system owns customers, vendors and materials, and whether anything may be created in Odoo at all.
IDoc, BAPI, OData or a middleware already in place. This is a question for your SAP team and it sets the timeline.
Transaction-level or summarised postings to the group ledger. Summarised is usually right and has to be agreed with group finance.
How Odoo accounts map to the group chart, including cost centres and profit centres.
How the two systems are proven to agree each period, and who signs that off.
SAP-side changes need SAP people. Agreeing availability up front is what keeps the plan realistic.
We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a different tool, or tell you the connector will not reach.
We work to the interfaces your SAP team exposes. We do not develop in SAP, and we will not pretend the timeline is ours to control.
What you may extract and how often can be limited by your SAP licence. That is a commercial question to settle early.
Most SAP interfaces are batch by nature. A design that assumes instant synchronisation usually has to be reworked.
Consolidation, IFRS treatment and statutory group reporting stay in SAP. Odoo feeds them; it does not replace them.
B1 is a different product from ECC or S/4HANA, with different interfaces. The approach is assessed per product, not per vendor name.
A migration that pauses halfway leaves two systems of record indefinitely, which is the worst outcome of all. The wave plan exists to prevent it.
Connecting SAP to Odoo is less about the connector than about agreeing what is true where, and what happens when a record will not go through.
Understand whether this is coexistence or migration, which SAP product and version you run, what interfaces are available, and who on the SAP side can act.
Agree the master data boundary, posting granularity, chart of accounts mapping and the reconciliation method with group finance before anything is built.
Connect SAP to Odoo using the standard connector where one fits, and build only what the connector genuinely cannot reach. See Odoo customization.
Your records, in a test database, including the awkward ones — the cancelled order, the partial refund, the product that exists on one side only.
A queue for failed records with a named owner and an alert, because an integration nobody watches diverges quietly and the divergence is found at audit.
Cutover with a reconciliation on both sides, then hypercare, then ongoing support and AMC.
We do not publish one integration price, because the same connector costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.
We ask whether you are coexisting or migrating before anything else, and we are honest that the SAP side sets the pace. A plan that assumes our team controls the timeline is a plan that slips, and we would rather say so at the quotation stage.
Product capabilities stated on this page are documented by Odoo. The mapping advice, failure handling and limitations come from our own integrations.
Tell us whether SAP is staying or going, and which SAP product you run. Those two answers decide the whole approach, and the diagnosis call is free.