What an Odoo implementation costs in Qatar

6 payment rails have no Odoo connector we would put in production

Each one is an API build with its own tests: authorization, capture, refund and a deliberate failure in sandbox, repeated once in production with a small live amount, then settlement mapped to the ledger so the bank reconciliation clears. Price them one at a time. This is where a checkout budget doubles quietly.

• Fawran. Fawran is Qatar Central Bank's instant payment service and it now reaches local e-commerce checkouts through QPay, where the buyer pays from a mobile number or alias instead of a card. Merchants have to register for Fawran separately, and Doha Bank was the participating bank when it went live on QPay.
• Noqoody. Noqoody holds a QCB payment service provider licence and accepts NAPS, Himyan and GCCNET beside Visa, Mastercard, Apple Pay, Google Pay and Samsung Pay, with payment links and subscription billing. Nothing on the Odoo apps store connects to it, so this one is an API build.
• Doha Bank Internet Payment Gateway. Doha Bank runs its own merchant gateway covering domestic card schemes and bank transfers, with its Doha Pay wallet and QR payments, and it is the bank named for Fawran acceptance through QPay. Relevant when the client already banks there and wants one relationship.
• Ooredoo Money. Ooredoo Money is one of the most used mobile wallets in Qatar and also sells a merchant gateway with QR and mobile payments. There is no Odoo payment connector for it, only an unrelated Ooredoo SMS module, so plan on an API build.

8 payment rails need a paid connector

The connector licence sits outside our fee and is quoted separately by whoever sells it. Our side is configuration, the four-test cycle per provider, and the reconciliation mapping. Budget for keeping each one current across Odoo upgrades, because a connector that stops at your next version is a cost you meet later.

5 carriers have no Odoo connector

Rating, label printing, tracking and cash on delivery reconciliation are four separate pieces of work with four separate failure modes, and we quote them separately. Carrier test credentials rarely carry your negotiated rates, so the account and the rate card get validated before the connector is written.

• Qatar Post. Qatar Post runs the domestic tiers Qatar Standard, Qatar Express and Qatar Post Premium, the outbound Global Standard, Global Express and Global Priority, plus e-commerce fulfilment and Makan-E. There is no Odoo connector, so rates and labels are manual or an API build.
• Posta Plus. Posta Plus is a Kuwait headquartered courier whose GCC coverage includes Qatar, selling express, e-commerce fulfilment, last mile and customs clearance. No Odoo connector exists on the apps store, so this is an API build.
• Snoonu. Snoonu is the Qatari delivery platform that runs its own last mile logistics across food, grocery, e-commerce and services, and it is named as a local specialist competing with the global integrators. Nothing connects it to Odoo, so a merchant handover would be an API build.
• Milaha. Milaha is the Qatari maritime and logistics group named among the operators in the local courier and parcel market, and it is who a Qatari distributor uses for inbound sea and land freight rather than parcels. Freight bookings sit outside Odoo's carrier connectors.

3 carriers sit behind a paid connector

Cheaper than a build and not free. The licence is quoted separately, and our work is the account setup, the rate check against your contract, and the label and tracking test on real shipments.

Cash on delivery is in the flow

Cash on delivery touches the order, the stock move and the cash reconciliation at once. The courier holds your money for days and remits in batches, so someone has to match remittances back to orders and chase the gaps. That is a reporting and reconciliation build, not a checkbox, and it needs an owner in finance before go-live.

Payroll is built here, not switched on

No payroll localization module appears in our Qatar module list, so every contribution, ceiling, deduction and statutory file becomes a salary rule, a bank file or a report that we write and test. Add at least one parallel run against your current system, reconciled line by line, before anyone switches.

• Payroll. Qatar is not in Odoo's payroll localization list. GRSIA contributions for Qatari nationals, end of service gratuity accrual and the WPS Salary Information File all need paid apps store modules or a custom build.

5 items Odoo does not cover for Qatar

This is the honest part of a quote. Each line below is scoped, priced and agreed as a build before the project starts, rather than discovered halfway through and raised as a change request.

• Everything past the chart of accounts. There is no Qatar tax engine to configure because there is no VAT, but withholding tax at 5%, the 16th-of-month remittance and the monthly Dhareeba WHT statement are all custom.
• Contract notification tracking: catching every signed contract and reporting it in Dhareeba within 30 days, with a QAR 10,000 penalty for each miss.
• E-invoicing. No Odoo module exists because no Qatar specification exists. Any vendor selling you a Qatar e-invoicing module today is selling you a guess.
• Arabic financial statements for the tax return, which means bilingual account names and Arabic report layouts, not a one-off translation.
• Dhareeba has no Odoo integration. Filing stays manual unless you build an export.

14 statutory items to configure, test and hand over

Tax, accounting and payroll items on our own Qatar list. Each one becomes a configuration, a test document and a number your accountant checks independently before sign-off. Individually cheap, collectively the reason a localization is a work package rather than a setting.

Documents in more than one language

A second language on printed documents is not a translation pass at the end. Account names, product names, report layouts and every customer-facing template carry it, and someone on your side has to own the wording. Budget review time from a native speaker, and expect the layout work to be re-checked after it.

• l10n_gcc_invoice adds Arabic as a secondary language on invoices, credit notes, debit notes, vendor bills and refund bills, which is what you need for bilingual documents.
• Arabic financial statements for the tax return, which means bilingual account names and Arabic report layouts, not a one-off translation.

28 open questions in our own Qatar notes

Where our research did not reach a primary source, we mark it open rather than pricing a guess. Those questions get closed in discovery against your entity, your documents and your advisor, which is exactly why a fixed price comes after discovery and not before it.

2 official Odoo modules cover part of this market

Configuration and testing, not development. Anything on this list is install, configure and verify work that sits inside the tier price rather than beside it.

What you get without a build

Printed as checked. Where a requirement is met by something below, the work is proving it against your documents, not writing it.

• A Qatar chart of accounts. The l10n_qa manifest describes itself as the base module to manage the accounting chart for Qatar and lists exactly one activated feature: chart of accounts.
• l10n_qa auto-installs with the Accounting app when the company country is Qatar, and pulls in l10n_gcc_invoice.
• l10n_gcc_invoice adds Arabic as a secondary language on invoices, credit notes, debit notes, vendor bills and refund bills, which is what you need for bilingual documents.
• QAR is configured with 2 decimal places in Odoo core, so no currency rounding work is needed.

4 payment providers ship with Odoo

Configured before anyone buys anything. Starting from what already ships is the cheapest checkout you can have, and it keeps the number of things that break after an upgrade down.

3 carriers ship with Odoo

Rating, labels and tracking without a connector purchase or an API build. If your volume can move to one of these, that is a real saving on build and on support.

1 item has a community module

Install and test rather than build, then budget a little for keeping it current across upgrades. Cheaper than a build, and not free.

No live authority integration to build here, on this evidence

Where documents are exchanged or filed rather than cleared in the moment, e-invoicing is a format and archive job instead of a live integration, which is the cheaper end of this work. It also moves. Schemes get mandated with lead time, so we get the invoice data right now rather than retrofitting it under a deadline later.

• Nobody yet. The draft law gives the GTA power to require e-invoicing for named taxpayers and transaction types, but those categories have not been published. Do not plan a build against a scope that does not exist.