Choosing an Odoo Partner in Jordan: Shortlist, JoFotara Tests, Dinar Quotes

On 11 October 2026, Odoo's directory at odoo.com/partners listed 28 partners in Jordan: 3 Gold, 6 Silver and 19 Ready. Odoo reviews levels every quarter. Ready needs 10 net new Enterprise users sold over the last 12 months, one certified employee and no minimum retention; Silver needs 75 users, three certified employees and 70% retention; Gold needs 300 users, six certified employees and 80% retention. Certified employees count only if certified on one of the last three Odoo versions.

What that distribution means for your shortlist:

• A Gold-only shortlist is three firms. Gold signals sales volume and a larger certified bench, which matters most for a rollout across Amman, Zarqa and Irbid, but no level criterion measures project quality.
• 19 of the 28 are Ready, a level that needs only one certified employee. Ask a Ready firm how many certified people it actually has, and whether they would all work on your project.
• Certifications belong to people, and a partner must tell Odoo when a certified employee joins or leaves, so confirm at signing that they are still on the team.

With 28 names, you can open every profile in an hour. For each, note its certified experts on v18 or v19 (Odoo Learn had no Odoo 20 exam yet), whether its references are Jordanian companies or clients abroad, and its average project size against your own user count. Then test the shortlist on what levels never cover: JoFotara, a Qualified Industrial Zone (QIZ) exporter's dollar invoicing and an NGO's donor reports.

Much of what a Jordanian company needs is standard. Odoo's Jordanian localization installs the chart of accounts, taxes and tax report, with the 16% general sales tax, exempt sales and 0% export tax preconfigured. A separate module sends invoices in UBL format to JoFotara, the e-invoicing system of the Income and Sales Tax Department (ISTD), for real-time validation and adds the returned QR code to the PDF. A partner who wants to build its own JoFotara connector must explain what the standard module misses.

Test one is JoFotara. Ask the partner to show or explain:

• an invoice at 16%, a 0% export invoice, an invoice with an exempt line, and a credit note whose reason fits ISTD rules
• who will obtain the client ID, secret key and activity number (income source sequence) from your JoFotara account, and which taxpayer type it will set
• how it will test submission before go-live, whether any trial invoices would reach the live system, and who will watch the JoFotara state and error fields afterwards

Test two is the fils. The dinar has three decimals, so invoice totals, tax amounts and the tax report must agree to the fils. Odoo's own documentation notes that it stores JOD amounts to three decimals while ISTD expects nine, so differences below one fils can appear; ask how the partner will handle them. For QIZ exporters invoicing in US dollars, ask how dinar amounts will be posted: the dinar is pegged to the dollar, but each USD invoice still needs a JOD rate.

Ask each shortlisted partner for a reference in your own sector, then ask to speak to that customer directly. A reference page on odoo.com shows that a project exists; only the customer can tell you how it went. What to probe depends on your sector:

• Trading and import. If you are a distributor with warehouses in Amman and Zarqa and a showroom in Irbid, ask how the partner would staff a project across three sites, how it handles stock transfers between them, and how customs duties and freight reach product cost through landed costs.
• QIZ exporters. Ask for a manufacturer that invoices in US dollars and reports in dinars, and check that its 0% export invoices reach JoFotara and that dollar receipts reconcile with the dinar ledger.
• NGOs. Ask how the partner would report per donor or grant, for example with one analytic account per grant, and how it limited access to beneficiary records.

On the reference call, ask three things. Did the partner deliver what the written scope set out, and how were change requests priced? Do invoices reach JoFotara without manual workarounds? Are the people who did the work still with the partner?

If a partner's average project is a handful of users and yours is several times larger, ask what it would change for a project of your size. A partner whose references are mostly outside Jordan is not ruled out, but ask who on its team has taken a company live on JoFotara.

Odoo lets partners set their own service fees and takes no share of them, so compare quotes on the written scope, not the headline total. Ask for separate lines in dinars, to three decimals, each stating whether it includes the 16% general sales tax:

• implementation services, by phase
• the Odoo subscription, billed under Odoo's terms; if Odoo prices it in US dollars, ask for the list price, the dinar equivalent and the exchange rate used (partners earn a commission from Odoo on licences they sell)
• Odoo.sh hosting, if needed, priced separately from the licence
• In-App Purchase credits, such as SMS or AI scanning of vendor bills
• maintenance of custom code, which Odoo's pricing page lists as not included in its plans
• on-site days outside Amman, such as in Zarqa or Irbid

Ask too whether the partner invoices you from Jordan or from abroad; if from abroad, ask your accountant how the general sales tax applies to the imported service.

Check the plan. Studio, a second company or custom modules all require the Custom plan, so a group that wants its Amman trading company and its QIZ factory in one database will not fit the Standard plan. Odoo's discount lasts 12 months for the initial users ordered, so ask what renewal will cost.

Support after go-live deserves its own clause: the monthly fee in dinars and the hours it includes, the response time when a JoFotara submission fails, and cover on Sundays, a working day in Jordan.

On Odoo Online, the database manager lets you download a backup at any time; on Odoo.sh, keep the GitHub repository in your company's organisation. Odoo's subscription agreement lets you switch partner, or work directly with Odoo, with 30 days' written notice, and its partnership agreement bars partners from restricting your licence without Odoo's written authorisation.

Decide three things before you sign:

• Custom code. Odoo's subscription agreement does not say who owns modules a partner writes for you, so agree in writing on ownership or a perpetual licence, with the source code delivered.
• Groups. If an Amman trading company and a QIZ factory share one database, decide which legal entity holds the subscription and the main administrator login.
• NGOs. Keep donor-related attachments and the audit trail in the database you own, and use Odoo's access rights to limit which partner staff see beneficiary records.

Walk away if a partner:

• offers to build its own JoFotara connector without explaining what the standard module lacks
• cannot show invoice and tax totals that reconcile to the fils
• puts several legal entities in one database on the Standard plan
• proposes a new project on Odoo 17, whose standard support ended in September 2026, with no clear reason
• registers the database, repository or subscription in its own name

METCH is an official Odoo partner serving Jordan. For a free consultation, send us a quote you hold in dinars, and we will mark which lines are standard Odoo, which are custom work and what is missing.