Choosing an Odoo Partner in Saudi Arabia: ZATCA Proof, Quotes, Ownership

On 11 October 2026 the directory at odoo.com/partners listed 197 official partners in Saudi Arabia: 21 Gold, 54 Silver and 122 Ready. The level badge is the first thing a company in Riyadh, Jeddah or Dammam sees, and it measures less than it seems to. Odoo sets each level from three criteria and reviews it every quarter:

• Ready: 10 net new Enterprise users sold in the last 12 months and 1 certified employee, with no retention minimum.
• Silver: 75 users, 3 certified employees and at least 70% customer retention.
• Gold: 300 users, 6 certified employees and at least 80% retention.

Certified employees only count if they are certified on one of the last three Odoo versions, now 18, 19 and 20. Net new users add new customers and upsells, then subtract downsells and churn; renewals do not count. Retention is the share of Enterprise customers won in the last three years that are still active. None of the three criteria measures the quality of delivered projects.

So 122 of the 197, about 62%, hold a level that needs only 10 net new users a year and one certified employee, while each Gold firm has to sell 300. That tells you who sells licences at volume, not who has taken a Dammam contractor through ZATCA clearance.

Certifications belong to named individuals and cannot pass to a colleague. Ask whether the certified consultants on your project are based in the Kingdom or deliver from abroad, and who will be on site at go-live.

Start with the partner's profile on odoo.com/partners, which shows its level, certified experts by version, references by industry and typical project size. Standard support for Odoo 17 ended in September 2026, and on 11 October 2026 Odoo listed no Odoo 20 certification exam, so look for experts certified on 18 or 19. Then ask for references that match your business:

• A Riyadh retail chain needs Point of Sale references, a Jeddah wholesaler needs multi-warehouse and credit-control work, and a Dammam contractor needs project costing and progress billing.
• Speak to one or two of the partner's customers in your sector, and if you plan 60 users across three branches, ask about its largest project.

The sharper test in Saudi Arabia is ZATCA Phase 2. Odoo's localization handles it with l10n_sa_edi, which clears B2B tax invoices and reports simplified invoices to FATOORA, and l10n_sa_edi_pos for Point of Sale. Ask the partner to walk you through a client it took live:

• How it onboarded each sales journal. In Odoo each sales journal is onboarded separately, with a one-time code generated in the taxpayer's FATOORA portal.
• How it tested in ZATCA's simulation environment on a copy of the database before production, a switch Odoo says cannot be reversed once an invoice is submitted.
• What happens when ZATCA rejects a B2B invoice at clearance.
• A printed Arabic and English invoice with its QR code.

If payroll will run in Odoo, ask for a similar example of GOSI and end-of-service settings.

Ask each shortlisted partner for a milestone plan with named deliverables. A Saudi plan should cover:

• Company VAT, commercial registration and address data, complete enough to pass ZATCA onboarding, and your branches.
• The chart of accounts, 15% VAT and withholding taxes from the Saudi localization.
• ZATCA onboarding of each sales journal, simulation first, then production.
• A check of the bilingual invoice and its QR code.
• A cut-over date set against your VAT return period (monthly if annual taxable supplies exceed SAR 40 million, otherwise quarterly) and away from month-end.
• Training by role, in Arabic and English.

Odoo's implementation methodology runs from ROI analysis and kick-off through go-live to a second deployment and a progress report, and argues hard for standard-first. It estimates that custom development creates technical debt of about 25% of its cost every year, that project complexity grows exponentially, not linearly, as customisations are added, and that when development deferred until after go-live is reviewed at the second deployment, typically half of it turns out to be unnecessary. These are Odoo's estimates, but two consequences are certain: custom modules cannot run on Odoo Online, so they need the Custom plan with Odoo.sh or on-premise hosting, and a database cannot be upgraded until its custom modules are ported.

The localization already ships with 15% VAT preconfigured, a withholding-tax module and ZATCA integration. When a partner proposes custom code for e-invoicing or the bilingual invoice layout, ask for a written note of what the standard module lacks in your case.

Quotes vary widely, so ask for amounts in SAR with 15% VAT shown separately and compare the structure, not only the total. The partner's own invoices should be ZATCA-compliant tax invoices. A fixed fee protects you only if the scope is written in detail, with a change-request process and rates for extra work. Time and material suits evolving work, provided you get a rate card, an estimate per phase and regular timesheets.

Two checks are specific to the Kingdom:

• If the implementer invoices from abroad, ask your tax adviser about withholding tax on the fee and the VAT reverse charge.
• Ask for each branch's journal onboarding and each Point of Sale register as separate lines.

List what sits outside the service fee:

• The Odoo Enterprise subscription. The listed discount lasts 12 months for the initial users ordered, and renewals below list price can rise by up to 7% a year.
• Odoo.sh hosting for custom code, priced by workers, storage and staging, licence excluded.
• In-app purchase credits for SMS, lead generation, contact autocomplete and AI scanning of vendor bills and expenses.
• Custom code maintenance: Odoo charges a monthly fee per 100 lines of code for modules you choose to cover, porting at upgrade included, and subcontracts that work to your partner, who quotes for the rest.
• Support. A B2B tax invoice must be cleared before it reaches the buyer, and Odoo's included support is closed on Sundays, so put a same-day, Arabic-language response time for clearance errors in the partner's terms.

Settle ownership before signing. On Odoo Online the database administrator can download a backup from the database manager (very large databases need a request to Odoo Support); on Odoo.sh, keep the GitHub repository in your company's organisation. Odoo's subscription agreement does not grant you copyright in modules a partner writes for you, so make sure your contract assigns it to you or grants a licence that survives the relationship. You can switch partner with 30 days' written notice to Odoo, and the partnership agreement bars partners from blocking your Enterprise licence without Odoo's written authorisation.

FATOORA access is a key only you, the taxpayer, hold. To onboard each journal, your partner needs a one-time code that you generate in your FATOORA portal, not your ZATCA portal login. Keep that login, the Odoo subscription and the main admin account under the legal entity on your commercial registration.

Walk away unless the partner commits to:

• Custom code, e-invoicing included, only where standard Odoo falls short and the gap is in writing
• A written scope, deliverables and acceptance criteria before work starts
• The admin account, subscription and repository in your company's name
• A one-time code from you for each journal, never your ZATCA portal password
• Test and copied databases connected to ZATCA simulation only, never to production

METCH is an official Odoo partner in Saudi Arabia, based in Riyadh. Send our team your branch list and any quote you hold, and in a free consultation we will mark which lines Odoo's standard Saudi localization already covers.