Is Odoo Free in Saudi Arabia? Odoo Community vs Enterprise and ZATCA

Yes, Odoo can be free in Saudi Arabia, and free goes further than most buyers expect. Odoo Community, the open-source edition, carries the LGPLv3 licence, and so do the Saudi modules that connect it to ZATCA's FATOORA platform for Phase 2 e-invoicing. A Community database can send tax invoices for clearance and report simplified ones without paying Odoo anything.

Community runs only on a server you control, never on Odoo Online or Odoo.sh. Enterprise adds Odoo's proprietary apps under a subscription licence that ends when you stop paying, so there is no perpetual licence to buy.

On 17 October 2026, Odoo's pricing page for Saudi visitors showed these Enterprise prices per user per month, billed yearly:

• Standard: US$16.90, about SAR 63 at the 3.75 peg, or US$13.50 (about SAR 51) for the first 12 months for the users in your first order. All apps, hosted on Odoo Online.
• Custom: US$32.00, about SAR 120, or US$25.50 in the first year. Needed for Odoo.sh or your own server, Studio and agentic AI, multi-company, and any outside system that calls Odoo's API, such as an external online store or a legacy system. Odoo.sh hosting is billed on top.

Billed monthly, the two plans were US$21.10 and US$40.00. Prices vary by country and change, and Odoo's fees exclude taxes, so check the official page before you budget.

The other no-fee route is Odoo's One App Free plan: one hosted Enterprise app, plus the apps it depends on, for unlimited users.

Some vendor guides still claim Odoo's ZATCA integration needs Enterprise. The source code says otherwise. In the public Community repository, on both 19.0 and 20.0, these modules carry the LGPL-3 licence:

• l10n_sa: the Saudi chart of accounts, 15% VAT, the Arabic and English invoice layout and the Phase 1 QR code.
• l10n_sa_edi: Phase 2 integration that talks to ZATCA's FATOORA platform directly in Sandbox, Simulation and Production modes, sending B2B tax invoices for clearance and reporting simplified ones.
• l10n_sa_pos and l10n_sa_edi_pos: simplified invoices from Point of Sale.
• Withholding tax on vendor payments: l10n_sa_withholding_tax on 19.0, built into l10n_sa on 20.0.

Onboarding is identical in both editions: set the ZATCA API mode in Settings, then click Onboard on each sales journal's ZATCA tab with a 6-digit OTP from the FATOORA portal, valid for 60 minutes. In Community these menus sit under Invoicing, not Accounting. After the first Production invoice, there is no way back to Sandbox or Simulation.

What Community lacks is the reporting around it. The l10n_sa_reports module is not in the Community repository, so there is no Tax Return screen, and you feel that at every month-end.

The timing matters. ZATCA's Wave 25 covers taxpayers whose VAT-subject revenue exceeded SAR 187,500 in any year from 2022 to 2025, with an integration deadline of 1 February 2027; ZATCA notifies those in scope.

Follow one month at a VAT-registered trading company in Riyadh and you see exactly where the editions part:

• Sales and POS: identical. Tax invoices go for clearance, simplified invoices are reported and the QR code prints in both editions.
• VAT and Withholding returns: l10n_sa ships both return definitions and their tax grids, but only Enterprise displays them, on the Tax Return screen with drill-down to each entry. On Community, give your accountant Show Full Accounting Features (visible in developer mode), open Journal Items, group them by Tax Grid for the period and copy each grid's total into the return on ZATCA's portal. The OCA's account_tax_balance module (AGPL-3) adds per-tax totals for a date range.
• Bank reconciliation: Enterprise Accounting. On Community, you add an OCA module or reconcile outside Odoo.
• Payroll: Odoo's Saudi payroll, with GOSI contributions and end-of-service, builds on the Enterprise Payroll app. Community has Employees and Time Off, but no payslips.
• Month-end stock count: Inventory is in Community, but the Barcode app for scanning counts and pickings is Enterprise.

For contracting and facility-management firms the list grows: Field Service, Helpdesk, Planning, Sign, Documents and Approvals are Enterprise. So are the Android and iOS store apps, while Community installs on a phone's home screen as a progressive web app (PWA), which Odoo's documentation recommends anyway.

What the source code shows: account_reports, hr_payroll, stock_barcode, industry_fsm and web_studio do not exist in the Community codebase on 19.0 or 20.0. These are not hidden settings, so there is nothing to switch on.

For 10 full users billed yearly, at the 17 October 2026 prices above, before VAT and if prices hold:

• Standard: SAR 6,075 in year one at the promotion, then SAR 7,605 a year, about SAR 21,300 over three years, including Odoo Online hosting, upgrades and support.
• Custom: SAR 11,475 in year one, then SAR 14,400 a year, about SAR 40,300 over three years, plus Odoo.sh or your own server.
• Community: no licence fees. That saving funds the lines below, which become your job.

The Community lines that are specific to Saudi Arabia:

• Hosting: a server in the Kingdom or with a cloud provider, backups, monitoring and security patches, and a named person responsible, without whom your FATOORA integration is at risk.
• ZATCA rule changes: fixes land in Odoo's public code, but you pull, test and deploy them yourself, on supported versions only; Odoo 17's standard support ended in September 2026. Some arrive only with a new version: Odoo 20 rejects a Building Number or Secondary Number that is not exactly four digits, including Arabic-Indic digits like ١٢٣٤ from some Arabic keyboards, so clean contact addresses before upgrading.
• Upgrades: Odoo's upgrade service comes with Enterprise. On Community, each major version is a project you fund.
• Support: Odoo's pricing page lists email support in English, French, Spanish or Dutch. Arabic help comes from your partner, in either edition.

If those lines cost less than the licence saving, Community is cheaper. Ask any partner to quote them in days, not as a lump sum.

Three Saudi questions settle most edition decisions:

• Your ZATCA wave: in Wave 25 with no in-house Odoo skills, Standard on Odoo Online is the shortest route to 1 February 2027: no server, the Tax Return screen, bank reconciliation, and upgrades handled by Odoo. Community fits only if a developer or long-term partner already runs your server.
• Your commercial registrations: Odoo's Saudi guide sets up extra CRs under one VAT number as branches, each with its own CRN, using the parent's sales journal or its own onboarded one. Separate legal entities need multi-company, which on Enterprise means Custom; ask Odoo in writing whether your branches count as companies for pricing.
• Where the data must live: Odoo's Middle East cloud region may run in Saudi Arabia or India, and backups are replicated to Europe and Canada with no choice of region. If all data, backups included, must stay in the Kingdom, you need your own server: Community, or Enterprise on Custom.

If all you need is ZATCA-compliant invoicing, with no stock, sales or projects, ask Odoo to confirm that One App Free with Invoicing covers Saudi e-invoicing, or compare a dedicated e-invoicing product, before paying for a full ERP.

For a first-year estimate for your users and apps, including implementation and data migration, try the pricing calculator on our Pricing page. METCH, an official Odoo partner based in Riyadh, offers a free consultation in Arabic or English: we map your branches and sales journals to FATOORA onboarding before 1 February 2027 and tell you which edition fits.