Odoo Implementation Plan Saudi Arabia 2027: 90 Days, Week by Week

This is a typical 90-day plan for a Saudi SME of 10 to 30 users on standard Odoo (Sales, Purchase, Inventory, Accounting, perhaps one Point of Sale) with little custom code. It is a plan, not a promise: decisions, data and scope set the pace. Eight weeks to build, go-live on the 1st of a month, four weeks of follow-up.

Copy these lines into a spreadsheet and split them into columns on the | character:

• Week | Goal | Who | Deliverable
• 1 | Scope and apps | Owner, partner | Signed one-page scope
• 2 | Map processes to standard Odoo | Key users, partner | Gap list with a decision for each gap
• 3 | Clean accounts and contacts | Accountant, key users | Mapped accounts; contacts with VAT number and address
• 4 | Products, opening balances, ZATCA readiness | Key users, accountant | Product file with taxes; cut-off date; Fatoora access confirmed
• 5 | Configure company, VAT and journals | Partner, accountant | Test invoices accepted in Sandbox
• 6 | Workflows, minimal customization | Partner, key users | Invoice layout approved; journals onboarded in Simulation
• 7 | End-to-end tests in Simulation | Key users | Signed test scripts
• 8 | Arabic training, parallel run, go/no-go | All users, owner | Users trained; figures matched; written go decision
• 9 | Go-live on the 1st | Owner, accountant, partner | Opening balances posted; journals onboarded in Production
• 10 | Daily follow-up | Key users, partner | Issue log; ZATCA rejections cleared
• 11 | Reports and handover | Owner, key users | Weekly reports from Odoo; old system read-only
• 12 | First month-end close | Accountant, partner | Month closed; VAT checked; next-phase backlog

A worked calendar: week 1 starts on Sunday 8 November 2026 and week 8 ends on Thursday 31 December. The cut-off is 1 January 2027, the new financial year for a December year-end company, and staff work in Odoo from Sunday 3 January. Week 12 starts on Sunday 24 January, and the January close itself runs into the first working days of February, still inside the 90 days. All of this lands ahead of ZATCA's 1 February 2027 date for Wave 25. Book your accountant early: December is their year-end too.

Three roles carry the project, and each needs a named person in week 1:

• Owner or general manager: signs the scope, decides within two working days, chairs a 30-minute weekly review and gives the final go/no-go.
• Key users: one per department, such as sales, warehouse and accounts, with part of each week freed from daily work. They map processes, clean data and test, then train colleagues.
• Partner: a project manager and functional consultant who configure Odoo, run the ZATCA onboarding and keep the gap list honest. Your accountant or tax adviser signs off the chart of accounts, taxes and opening balances.

The week 1 scope fits on one page: users per department, apps, companies and branches, POS counters, integrations, the reports the owner reads every week, and the target go-live month.

Weeks 3 and 4 are for data, loaded in the order Odoo's accounting guide sets, because invoices rely on products and contacts:

• Chart of accounts: rename and recode Odoo's Saudi accounts to match yours; never delete standard accounts, which Odoo uses as defaults.
• Products: category, unit, cost and the right sales tax: standard 15%, zero-rated or exempt.
• Customers and suppliers: VAT number, identification scheme and number such as the CR, and the full national address with district, building number and plot identification.
• Opening balances: the trial balance at the cut-off date, updated once the old year is closed, open invoices and bills at the amount still due, and a physical stock count.

Run Odoo's four checks before posting. Example: receivables of SAR 845,000 in the old books must equal open invoices of SAR 872,500 minus credit notes of SAR 27,500. Download the templates and press Test before every import in Odoo's import tool. Our guide to migrating from Excel covers clearing accounts and Saudi data checks in depth.

Saudi VAT has been 15% since 1 July 2020, according to ZATCA's VAT page (in Arabic). Odoo's Saudi localization installs a Saudi chart of accounts with 15%, zero-rated and exempt taxes, so week 5 is about checking them with your accountant, not building them. A SAR 20,000 B2B invoice carries SAR 3,000 of VAT: SAR 23,000 in total.

E-invoicing is the part that depends on ZATCA's systems. As of November 2026, ZATCA's Fatoora portal user manual and Odoo's Saudi Arabia documentation give these steps:

• Week 4: confirm who logs in to the Fatoora portal with the company's ZATCA credentials (TIN or registered email, and password). Complete the company record: a name of up to 63 characters, the full address, CR, VAT number and SAR as currency. Missing fields cause rejection at onboarding.
• Week 5: Sandbox, a shared test environment, with test invoices.
• Weeks 6 and 7: Simulation, on a duplicate of your database. Generate one OTP per sales journal in the Fatoora Simulation portal and enter each in Odoo within one hour. Simulation invoices are not legally valid, so test freely.
• Week 9: Production. Generate one OTP per sales journal in the Fatoora portal, the POS invoices journal included, and onboard each before the first live invoice.

Behind each OTP, Odoo obtains a compliance CSID (cryptographic stamp identifier) from ZATCA, passes ZATCA's compliance checks, then obtains a production CSID. Once an invoice reaches ZATCA in Production, Odoo cannot switch back to Simulation.

In Production, ZATCA clears each B2B tax invoice before you share it, and simplified B2C invoices must be reported to ZATCA no later than 24 hours after issue. Invoices must be in Arabic, so enable the Gulf Cooperation Council Format for bilingual documents. Wave 25, per ZATCA's announcement, covers VAT-subject revenue above SAR 187,500 in any year from 2022 to 2025.

Configure before you customize. For each gap from week 2, ask in order: can a standard setting do it, can we change the process, is it worth code? Write the answer and its cost on the gap list. A Saudi example: Arabic-English invoices are a setting, not development.

Training happens in week 8, in Arabic, by role, in the Simulation copy with your own products and customers:

• Each user picks Arabic under My profile, as Odoo's language guide shows, so the screens match the training.
• Cashiers: opening and closing a session, returns, internet outages. Sales: quotation to invoice. Warehouse: receipts, deliveries, counts. Accounts: bills, payments, bank reconciliation, the VAT report.
• The partner trains key users first; key users then train colleagues, each role with a one-page Arabic sheet of its five daily tasks.

The parallel run, also in week 8: key users enter one real week of transactions in the old system and the Odoo test copy, then compare sales, stock, receivables and VAT. Invoices still come from one system only.

The go/no-go meeting, on the last Thursday before the 1st, checks five things: test scripts signed, users trained, opening balances reconciled, Fatoora access ready, and the owner's written yes. If anything is missing, move to the next month's 1st; never go live mid-month. Odoo prefers the end of a financial year or tax period and advises against switching mid-period, because one VAT return would mix two systems. Quarterly VAT filers, those with annual taxable supplies up to SAR 40 million per ZATCA's VAT page (in Arabic), should pick a month that starts a quarter.

The first 30 days after go-live:

• Daily: read ZATCA's reply on every invoice (green accepted, yellow with warnings, red rejected) and fix the cause before it repeats on the next invoice.
• Weekly: a 30-minute review of the issue log with the owner.
• Day 30: the first month-end close in Odoo, VAT figures checked, and a short backlog for the next phase.

Most delays come from the business side, not the software. Eight common risks, and how to avoid each:

• No written scope, so new apps join mid-project. Fix: a signed one-page scope; anything new waits for the next phase.
• Slow decisions while the owner is away. Fix: one named decision-maker and a fixed weekly review.
• Key users with no time, so testing slips behind daily work. Fix: free part of their week from week 1.
• Late, messy data: duplicate customers, missing VAT numbers and addresses. Fix: start cleanup in week 3, in spreadsheets.
• Customizing before trying standard Odoo. Fix: a gap list with the cost of each change and the owner's approval.
• ZATCA onboarding left to go-live week: nobody has the Fatoora login, or the company record is incomplete. Fix: Sandbox and Simulation done by the end of week 7.
• Opening balances counted twice. Fix: clearing accounts and Odoo's four checks, rehearsed in the test copy.
• Going live mid-period or in peak season, such as Ramadan, Eid or White Friday. Fix: the 1st of a quiet month, ideally the start of a VAT period.

What drives the cost:

• Users, and whether you need Odoo's Standard or Custom plan.
• Apps and processes in scope, and how far they differ from standard Odoo.
• Data volume and how clean it is.
• Customizations and integrations with other systems.
• Sales journals, branches and POS counters to onboard with ZATCA.
• Training groups, and hosting.

On Odoo's paid plans, Studio, a second company or an External API connector moves every user to the Custom plan; our Odoo price guide for Saudi Arabia shows the per-user figures in SAR.

METCH, an official Odoo partner in Saudi Arabia, can turn this template into a dated plan for your company.