On this page
Companies in Bahrain and Saudi Arabia usually spend their first Odoo conversations on the edition: Community or Enterprise, which apps, which version. It is the wrong place to start. The same Odoo, installed by two different partners, produces two different systems: one that closes the month in a day and passes a ZATCA audit, and one that the finance team quietly abandons for spreadsheets. The partner decides the outcome. This guide gives you a way to tell them apart before you sign: what an official partner is and how to verify it, ten questions to ask, the answers that should worry you, and how we answer them ourselves.
Why the partner matters more than the edition
Odoo’s own editions page puts it plainly: Community is the core on which Enterprise is built, and you can switch at any time. The edition is a reversible decision. The partner’s decisions are not: how your chart of accounts is structured, how your products and customers are migrated, which processes are configured and which are coded, where your database lives, and who holds the keys. Each of those is expensive to undo a year later. Choosing the partner is the real procurement decision; the edition follows from what your business needs.
What “official Odoo Partner” means, and how to check it
Odoo runs a partner programme and publishes every partner in a public directory at odoo.com/partners. You can filter it by country, Bahrain and Saudi Arabia included, and by grade: the directory shows Ready, Silver and Gold. Each partner card also shows a count of references, which are implementations the partner has declared, and of certified experts, broken down by Odoo version. Three things follow from that.
- If a company calls itself an Odoo partner and does not appear in the directory, it is not one. Ask for the link to its partner page and open it yourself.
- The grade reflects the partner’s commercial volume with Odoo and its certified staff. It is a useful signal, not a verdict: a Ready partner with the right Gulf references can be a better fit than a Gold partner whose references are all abroad.
- Certifications are per version. A partner certified on an old version and not on the current one has probably not implemented the current one yet.
Ten questions to ask before you sign
1. What have you delivered in Bahrain and Saudi Arabia, specifically?
Ask for Gulf projects, not a global list. In Bahrain the test is VAT: the NBR’s tax invoice fields, the VAT return, Arabic and English on the same invoice. In Saudi Arabia it is ZATCA e-invoicing: phase 1 (generation) has applied since 4 December 2021 and phase 2 (integration with the Fatoora platform) since 1 January 2023, in waves. A partner who has connected a company to Fatoora can tell you how the onboarding went, what ZATCA rejected and why. One who has not will describe the documentation. Our guide to Odoo for VAT and e-invoicing in Bahrain and Saudi Arabia lists what a compliant setup contains; use it as a checklist for their answers.
2. Who will actually do the work, and where do they sit?
Many proposals are sold by one company and delivered by another: a sales office in the Gulf, developers subcontracted elsewhere. That is not wrong in itself, but you should know it. Ask for the names of the functional consultant and the lead developer, whether they are employees, which time zone they work in, and who you call when something breaks at 9 a.m. on a Sunday. A team that cannot name its people before the contract will not be easier to reach after it.
3. Fixed scope or time and materials, and what happens when the scope changes?
Both models work when they are honest. A fixed-scope offer needs a written scope precise enough to be checked: which apps, which flows, which reports, which integrations, how many users trained. Time and materials needs a budget ceiling and a weekly report of hours against it. In either case, ask how a change request is priced and approved, and who decides whether a request is a change or a bug. The answer tells you how the invoices will look in month four.
4. How will my data be migrated, and who cleans it?
Data migration is where Gulf projects most often slip: customer records in two scripts, products with Arabic and English names, open invoices with VAT already declared, opening balances that must reconcile with the last return filed. Ask for the migration plan as a document: which objects, from which source, how many trial loads before the real one, who validates each load, and what is left behind on purpose. “We will import your Excel files” is not a plan.
5. What will be custom code, and what does it cost at the next upgrade?
Every custom module is a future bill. Odoo’s upgrade documentation is explicit: a database cannot be upgraded until a version of its custom modules exists for the target version, and it is the responsibility of the maintainer of the custom module to make it compatible. Upgrading the standard database is free for Enterprise subscribers; adapting your custom code is not. So ask the partner to list what it intends to customize, why configuration or a standard app does not cover it, and what it will charge to carry that code to the next version. A partner that minimizes custom code is protecting your budget three years out.
6. Where will the database be hosted, and who controls it?
Odoo offers three hosting models: Odoo Online, Odoo’s own SaaS, hosted in a region you choose among the Americas, Europe or Asia, and which does not accept non-standard apps; Odoo.sh, Odoo’s cloud platform for databases with custom modules; and on-premise, on your own servers or a cloud provider of your choice. The right answer depends on your customizations, your data-residency requirements and your IT team. Whatever the model, insist that the subscription, the hosting account and the domain are in your company’s name, with your own administrator access, and that you can take a full backup whenever you want.
7. How will my team be trained, and what is handed over?
Ask what training is included, for whom, in which language, and whether it happens on your data or on a demo. Ask what documents you receive at go-live: the configuration record, the user procedures in Arabic and English where needed, the list of custom modules with their source code, the integration credentials. A handover you cannot read is not a handover.
8. What does support look like after go-live?
Get the support offer in writing: hours and days of coverage, the languages spoken, the channel, the response time by severity, what is included in the monthly fee and what is billed. Ask who answers a ZATCA rejection on a Thursday afternoon, and whether security patches and minor Odoo updates are applied for you. Ask how the partner handles Odoo’s upgrade cycle, since Odoo Online in particular requires major upgrades every two years.
9. Which references can I call?
Not a logo wall: two or three companies of your size, in your country, that went live in the last two years, with a name and a phone number. Ask them three things: did the project finish on the agreed scope, how long did the first VAT return take after go-live, and would they choose the same partner again. The directory’s reference count tells you a partner has clients; a phone call tells you whether they are happy.
10. If we part ways, what do I keep?
Read the exit clause before the pricing page. You should own the database, the backups, the custom modules’ source code and the documentation, and be able to move to another partner or to Odoo directly without a penalty. Ask what happens to your data at the end of the contract and how long it takes to receive a complete export. A partner who hesitates here is planning on lock-in.
Red flags
- A proposal with a price and no written scope, or a scope written in Odoo’s marketing vocabulary rather than your processes.
- No partner page on odoo.com, or a grade claimed that the directory does not show.
- Everything is “standard Odoo” until the workshop, when everything becomes a custom module.
- The hosting, the subscription or the domain would be registered in the partner’s name.
- No Gulf reference you are allowed to call.
- Arabic is “handled by the translation module”, with no one on the team who reads the invoices.
- The go-live date is promised before anyone has looked at your data.
A one-page comparison grid
Put every shortlisted partner in the same grid and score what you can verify. Price belongs on the grid, but only once the first seven rows are filled.
| Criterion | What “good” looks like | How to verify |
|---|---|---|
| Partner status | Listed on odoo.com/partners with a current-version certification | Open the partner page yourself |
| Gulf localization | Named Bahrain VAT and ZATCA phase 2 projects | Ask what ZATCA rejected and how it was fixed |
| Team | Named consultant and developer, employees, Gulf working hours | Meet them before signing |
| Scope and change control | Written scope, priced change process, named decision-maker | Read the proposal, not the deck |
| Migration | Documented plan with trial loads and validation owners | Ask for the plan as a file |
| Custom code | Short list, each item justified, upgrade cost stated | Compare with your process list |
| Hosting and ownership | Your name on subscription, hosting and domain; backups on demand | Check the order form |
| Training, support, exit | Written offer with hours, languages, response times and exit terms | Ask for the support contract draft |
Frequently asked questions
Is a Gold partner always the best choice?
No. The grade reflects commercial volume with Odoo and certified staff. It says nothing about experience in your country, your industry or your size. Use the grade to confirm a partner is real and active, then judge it on Gulf references, the named team and the written scope.
Can a partner outside Bahrain or Saudi Arabia implement Odoo for us?
Yes, and many do, provided the team has done Bahrain VAT or ZATCA phase 2 before, works in your hours, and can come on site for the workshops that need it. Ask where the people are, not where the company is registered.
Should we choose the partner before or after the edition?
Before. A good partner will recommend the edition from your processes and show you what each one costs over three years. A partner that leads with an edition is selling a licence, not a project.
How many partners should we shortlist?
Three is enough to compare and few enough to take each one seriously. Give all three the same process list and the same data sample, and score them on the same grid.
What if the partner wants to host our database in its own account?
Decline. The subscription, the hosting and the domain belong in your company’s name, with the partner as an administrator you can remove. That single clause protects you more than any penalty.
How do we check ZATCA experience without being experts ourselves?
Ask for a walkthrough of one real onboarding: the sandbox run, the production OTP, the first cleared invoice, the first rejection and its fix. A partner who has done it can show you the screens. One who has not will show you the slides.
How Azinove answers these questions
Azinove W.L.L is the group’s Bahrain company, based in Isa Town (CR 190436-1), and an official Odoo Partner; the group has delivered more than 45 projects. The team sits in Bahrain and in Strasbourg, France, so you get Gulf working hours and European engineering on the same project. We implement Odoo for companies in Bahrain and serve Riyadh and the rest of Saudi Arabia remotely from Bahrain, with on-site sessions on request; we have no office in the Kingdom and say so. Every proposal carries a written scope, a named consultant and developer, a migration plan, the list of custom modules with the reason for each, and an exit clause under which the database, the code and the documentation are yours. Send us your process list and we will answer the ten questions in writing, starting with a 30-minute call.
Sources
- Odoo — Implementation partners directory, filtered by country and grade (read on 21 October 2026) — https://www.odoo.com/partners
- Odoo — Compare editions: Community and Enterprise (read on 21 October 2026) — https://www.odoo.com/page/editions
- Odoo — Documentation 19.0: Upgrade, including the responsibility for custom modules (read on 21 October 2026) — https://www.odoo.com/documentation/19.0/administration/upgrade.html
- Odoo — Documentation 19.0: Hosting (Odoo Online, Odoo.sh, on-premise) and regions (read on 21 October 2026) — https://www.odoo.com/documentation/19.0/administration/hosting.html
- ZATCA — E-invoicing: introduction, phase 1 (generation) and phase 2 (integration) (read on 21 October 2026) — https://zatca.gov.sa/en/E-Invoicing/Introduction/Pages/What-is-e-invoicing.aspx

