Plan and API boundary
Confirm external API entitlement and the supported interface for the installed Odoo version.
ERP coexistenceImplementation-scoped
Connect Odoo to governed AI operating workflows
Keep selected Odoo apps as systems of record while Soberan coordinates planning, exceptions, customer conversations, and approved actions.
A Soberan–Odoo integration is scoped by Odoo version, hosting model, pricing plan, installed apps, custom modules, companies, and the workflow to automate. Typical models include contacts, products, warehouses, stock, sales orders, purchase orders, invoices, and payments. Odoo 19 introduces the JSON-2 API; older deployments may use legacy RPC interfaces. External API access, authentication, model methods, permissions, and write actions are confirmed before implementation.
01
Typical Odoo model mapping
Use the real database model and access rules—not a generic field list—as the integration contract.ObjectSourceDestinationPurpose
ContactOdoo res.partnerCustomer or supplier context
Resolve identity across CRM, sales, purchasing, service, and finance.
Product and stockOdoo product / stock modelsPlanning context
Align variants, units, warehouses, routes, availability, and replenishment.
Sales and purchase documentsOdoo sale.order / purchase.orderOperating workflow
Coordinate demand, supply, commitments, suppliers, and exceptions.
Invoice or approved actionSoberanAuthorized Odoo model
Return only the permitted status, activity, or transaction.
02
A practical Odoo coexistence workflow
- 01
Choose one outcome
Start with replenishment, order exceptions, supplier follow-up, customer service, or receivables.
- 02
Inventory the Odoo database
Confirm version, Online/Odoo.sh/on-premise hosting, plan, companies, apps, Studio changes, custom modules, and record rules.
- 03
Map models and permissions
Document model names, fields, methods, companies, currencies, units, access rights, and external IDs.
- 04
Activate governed writeback
Enable approved methods gradually with idempotency, thresholds, audit evidence, reconciliation, and rollback.
03
Odoo integration controls
Record rules and companies
Respect user permissions, allowed companies, fiscal positions, currencies, and company context.
Custom-module contract
Inventory Studio fields, overrides, automations, third-party apps, and custom methods before integration.
Idempotency and reconciliation
Use external IDs, duplicate checks, timestamps, exception logs, and source-to-target reconciliation.
04
Odoo integration checklist
- Odoo version, plan, hosting, database, companies, and environments
- JSON-2 or supported legacy interface, API key, user, and access rights
- Installed apps, Studio changes, custom modules, third-party apps, and overrides
- Models, fields, methods, external IDs, currencies, units, and ownership
- Approvals, retries, reconciliation, monitoring, audit evidence, and rollback
05
Best fit
- Teams retaining Odoo CRM, Sales, Inventory, Purchase, Accounting, or Manufacturing apps
- Businesses adding governed agent workflows without rebuilding their Odoo database
- Operations connecting Odoo records to WhatsApp, voice, suppliers, commerce channels, or external systems
Frequently asked questions
Does Soberan replace Odoo?
It can coexist with selected Odoo apps for a scoped workflow. Replacement is a separate decision based on localization, accounting, custom modules, ecommerce, manufacturing, and historical data.
Which Odoo API does the integration use?
For Odoo 19, JSON-2 is the current external API. Older supported deployments may use JSON-RPC or XML-RPC while their migration path is planned. The exact interface is confirmed from the installed version and plan.
Does every Odoo plan include external API access?
No. Odoo documents external API access as a Custom-plan capability. Plan entitlement is verified before integration scope is committed.
Can Soberan work with custom Odoo modules?
Often yes, after custom models, fields, methods, access rules, dependencies, and upgrade ownership are inventoried and tested.