When the catalogue lives inside an ERP rather than a standalone ecommerce platform, AI content integration is a different project. The product record is not just a listing — it is tied to procurement, inventory, and pricing logic that the content layer has to respect. Odoo and SAP handle that differently enough that the integration path changes.
Odoo: fast to wire, model-friendly
Odoo's product model is open and its API (XML-RPC / JSON-RPC) is straightforward to script against. For most Odoo installs we can read and write `product.template` fields directly, which means generated descriptions, translated variants, and category tagging can be pushed back into the ERP without a middleware layer. A typical Odoo catalogue integration is live in 10 to 15 days — on the fast end of the range we cover in our integration timeline post.
The tradeoff: Odoo installs vary a lot from client to client. Custom modules and non-standard fields are common, so the discovery phase matters more than the build phase.
SAP: slower to wire, harder to break
SAP catalogues (S/4HANA or ECC) are usually governed by stricter change-control — product master data changes often go through approval workflows, and direct field writes are rarely allowed. The realistic integration pattern is to generate content in a staging layer (a database, a DAM, or a PIM sitting in front of SAP) and let the existing SAP governance process pull it in, rather than writing to SAP directly. That adds a step, but it also means the integration does not require touching SAP's change-control rules — which is usually the actual blocker, not the technology.
SAP integrations typically run 20 to 30 days, weighted toward discovery and stakeholder sign-off rather than the AI pipeline itself.
What does not change
Regardless of ERP, the content generation and translation layer is the same model-agnostic pipeline we described in our post on model choice. The ERP only determines how content gets read in and written back — it does not change how it is generated.
The question we ask first is never "which AI model" — it is "who owns write access to the product master, and what has to approve a change." That answer determines the entire integration shape.
If your catalogue sits in a different ERP — Microsoft Dynamics, NetSuite, a custom system — the same principle applies: map who owns the write path before scoping the AI layer.