Keep source ownership visible
Map Odoo customers, products, taxes, journals, branches, and document identities into an explicit integration contract.
Decision guide · Odoo teams
Keep Odoo as the business workflow. Add a Saudi invoice boundary you can explain.
Odoo can remain the source workflow while your team decides where Saudi invoice mapping, credentials, submission state, corrections, evidence, and production responsibility should live. Fatoorah API is a bounded integration option, not a claim of a turnkey Odoo connector.
Built for
The team that must operate the integration.
Odoo implementers, localization teams, ERP partners, finance advisers, and businesses extending Odoo for Saudi operations.
Avoid a hidden connector assumption
Start from a representative mapping proof and document what is supported, missing, or requires customer confirmation.
Give support a real trail
Connect the Odoo reference to request identity, invoice artifacts, lifecycle state, webhook delivery, and evidence.
Implementation path
From source operation to an inspectable result.
Inventory the Odoo model
Identify company, VAT, branch, journal, partner, product, tax, line, document, and correction fields that matter to the invoice path.
Submit a redacted mapping sample
Use field names and structure without raw customer values, then review missing fields and tax assumptions before implementation.
Build one sandbox transaction
Create a representative standard or simplified flow with stable identity, artifacts, request logs, and a known recovery path.
Agree the operating boundary
Define who owns corrections, credentials, retries, reconciliation, customer support, and the separate external production gate.
Questions
Decide with the boundary visible.
Availability and external prerequisites stay explicit throughout evaluation.
Does this page promise a ready-made Odoo module?+
No. It describes an integration decision and mapping path. Any connector, module, or implementation scope must be verified separately.
Can Odoo remain the source of truth?+
Yes, if the integration contract assigns the source fields, document identity, correction responsibility, and reconciliation boundary explicitly.
Can we send real ZATCA traffic from the sandbox?+
No. The current sandbox is synthetic and production traffic is disabled until external prerequisites are independently verified.
Continue with a real next step