ERP
Odoo
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Odoo SA · www.odoo.com
Compare with Microsoft Dynamics 365 Business Central → Compare with weclapp → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Odoo at a glance
- Vendor
- Odoo SA
- Headquarters
- Not stated on the vendor’s pages as of 26 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 26 Oct 2026
- Free plan
- Yes, per the vendor’s own page source, captured 26 Oct 2026
- Panel verdict
- The AI panel rates Odoo 4/5, the mean of 6 judges. Odoo is an open-source ERP from Odoo S.A. how scores are made
- As of
- Vendor pages captured 26 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Odoo is an open-source ERP from Odoo S.A. in Belgium; the bench scores it highest on finance and compliance and on production and projects, both 8 to 9: GoBD compliance is stated outright, e-invoices run via Peppol, bank feeds claim 95 per cent automatic matching, and manufacturing runs MRP, MES and PLM with finite-capacity scheduling on a Gantt chart. The weakest criterion is rollout and operations at 6 to 7, where a published 99.9 per cent uptime target and bug handling started within two business days sit beside no public information on implementation duration, a change log behind permissions or a status page. The widest splits run 6 to 8 on integration and portability and on pricing transparency. On the first, unusually strong exit terms — PostgreSQL as the data format, downloadable backups, self-hosting — meet an external API tied to the Custom plan and no public information on webhooks or a connector marketplace. On the second, the clear 19,90 € / Monat für ALLE Apps headline meets implementation and Odoo.sh hosting costs not priced publicly. Weighted totals ran 7.0 to 8.1.
Speaks for it
- GoBD compliance is stated on the accounting pages, with e-invoicing via Peppol and bank feeds auto-matching a stated 95 per cent of transactions.
- Manufacturing covers MRP, MES and PLM with finite-capacity scheduling on a Gantt chart, a tablet shop-floor app and lot traceability.
- Portability is strong: PostgreSQL as the data format, manual backups downloadable at any time, self-hosting as a stated alternative, and data returned or deleted at termination.
- Headline pricing is clear at 19,90 € / Monat für ALLE Apps, Light-Benutzer zu 7,90 €, a free single-app plan with unlimited users and renewal increases capped at up to 7 per cent per year.
- A published service level states 99.9 per cent uptime on Tier-III data centres with N+1 redundancy, with unlimited free bug tickets and handling started within two business days.
Held against it
- The pricing page ties the external API to the Custom plan only, with charges specified in writing at the conclusion of the agreement.
- No public price is shown for implementation, education or Odoo.sh hosting, and extra modules are billed monthly per 100 lines of code at a rate fixed only in writing.
- We found no public information on connections to Shopware, Amazon or eBay, or on returns with restocking and drop shipping.
- We found no public information on webhooks, a connector marketplace, a documented migration path from predecessor systems or typical implementation durations.
- EU-hosted customers on versions before Odoo 19 keep an additional backup in Canada until the fourth quarter of 2026, and the vendor-level certification shown is CSA STAR Level 1, with the ISO 27001 certificates belonging to the data-centre providers.
Best for
- You run a manufacturing operation and want MRP, MES and PLM on one platform with finite-capacity scheduling and a tablet shop-floor app.
- You want a documented exit path: PostgreSQL data format, downloadable backups, contractual self-hosting and data return or deletion at termination.
- You keep German books with GoBD stated as certified, Peppol e-invoicing and a DATEV export to your accountant.
- You want a single per-user price covering all apps, starting from a free single-app plan with unlimited users.
Avoid if
- You need to price the external API before committing — the captured pricing page ties it to the Custom plan only.
- Your data-protection rules require every backup copy to remain in the EU from day one — EU-hosted customers on versions before Odoo 19 keep an additional backup in Canada until the fourth quarter of 2026.
- You bill recurring services and expect subscriptions to generate sale orders or tasks — captured forum threads describe the subscription app creating invoices only and subscription and project not integrated in the standard product.
- You must budget the full annual cost before signing — Custom-plan charges and the per-100-lines-of-code rate for extra modules are fixed only in writing at the conclusion of the agreement.
The scores
| Criterion | Panel median |
|---|---|
| Finance, tax & compliance | 4 of 5 |
| Purchasing, inventory & order processing | 4 of 5 |
| Manufacturing, services & projects | 4.5 of 5 |
| Integration, API & data portability | 3.5 of 5 |
| Rollout, roles & operations | 3.5 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 3.5 of 5 |
Finance, tax & compliance
Show reasoningHide reasoning
How this is scored
Whether the ERP keeps books a tax adviser and an auditor accept: general and subledgers, VAT per country, GoBD-compliant posting and archiving, e-invoices sent and received (XRechnung, ZUGFeRD), payments and dunning, and a DATEV export or a documented hand-over to the accountant.
0 — No accounting at all; invoices leave as PDFs and the books are kept somewhere else by hand.
3 — Invoices and credit notes are created in the system, but there is no ledger, no stated GoBD compliance and no export the accountant can import.
5 — Invoices, open items and payments in the system with a DATEV or accounting export, VAT rates per item, dunning, and e-invoices in XRechnung or ZUGFeRD format sent to customers.
8 — Full financial accounting or a live-synchronised one: general, receivables and payables ledgers, incoming e-invoices read and matched to purchase orders, bank feeds with payment matching, OSS and reverse-charge VAT, GoBD compliance stated with a procedure documentation, and several companies in one tenant.
10 — The money side closes inside the system: an auditor's GoBD or IDW PS 880 attestation published, consolidation and intercompany postings across entities, fixed assets and cost accounting, every posting traceable to the order, goods movement and user behind it, and period close with locked periods documented.
The Managing Director
The books close inside the system: GoBD is stated as certified, e-invoices go out and come in via Peppol, bank feeds are auto-matched at a stated 95 percent, and a DATEV export demonstrably works — a captured forum thread describes an account-number-length quirk an accountant would configure around. Multi-company with intercompany transactions, lock dates, period closing, fixed assets and cost analytics are documented; we found no public auditor's attestation and no explicit XRechnung or ZUGFeRD naming. 9 10 15
The Head of Finance
Incoming bills are read by AI at a stated 98% recognition rate, bank statements import in CAMT.053 and CODA with 95% automatic matching, dunning runs by email, post and SMS, and lock dates plus monthly-to-yearly closing checks are documented. GoBD is stated as certified, multi-company with automated intercompany transactions, consolidation, fixed assets and multi-axis cost accounting sit in one subscription, and a DATEV export exists — evidenced in a support thread showing account numbers padded to eight digits where SKR03 expects four, with a settings path to adjust the length. We found no public information on a GoBD procedure documentation or a published auditor attestation, and matching of incoming invoices to purchase orders is not shown on the captured pages. 9 10 15
The Operations Lead
The money side is done properly: GoBD compliance is stated on the accounting pages, e-invoices are sent and received via Peppol, bank feeds auto-match 95 percent, dunning runs by email, post and SMS, and fixed assets, analytic cost accounting, lock dates, period closing and multi-company consolidation with intercompany transactions are all documented. A DATEV export exists — the captured forum thread shows a general-ledger export file, with an open question about account number lengths against SKR03. We found no public information on an auditor's attestation or on OSS and reverse-charge VAT, so I stop short of the top. 9 10 15
The Online Retailer
GoBD compliance is stated outright on the accounting pages, e-invoices go out via Peppol, bank feeds synchronise with a claimed 95 per cent automatic match, and fixed assets, multi-company consolidation and period closing with lock dates are all documented. A DATEV export is evidenced through a community thread about account-number lengths rather than a product page, and I found no public information naming OSS or reverse charge explicitly — cross-border tax computation is described, but for my OSS filings I would want that spelled out by name. 9 10 15
The IT Integrator
The accounting pages document a complete money loop: ledgers with reconciliation, bank feeds auto-matched at 95 percent, SEPA payments, dunning by email, post and SMS, OCR and AI capture of incoming invoices, Peppol e-invoicing, multi-company consolidation with intercompany transactions, fixed assets, analytic cost accounting and period closing with lock dates, with GoBD stated as certified and a DATEV export in real use (a forum thread reports it padding account numbers to eight digits where SKR03 expects four). No published auditor's attestation or explicit OSS and reverse-charge wording appears, which is all that keeps it from the top. 9 10 15
The Skeptic
Full books with receipts behind them are documented: bank feeds with a stated 95% automatic match, incoming invoices digitised by OCR at a claimed 98% recognition rate, dunning by email, SMS and post, SEPA collection and payment, multi-company with intercompany postings, fixed assets, analytic plans and locked periods at close. "GoBD certified" stands as two bare words — we found no public information on a procedure documentation or an auditor's attestation behind them — and the captured pages name Peppol for e-invoicing while a forum thread reports the DATEV export delivering eight-digit account numbers where SKR03 expects four. 9 10 15
Purchasing, inventory & order processing
Show reasoningHide reasoning
How this is scored
The goods chain from supplier to customer: quotes, orders and order confirmations, purchasing and goods receipt, stock per warehouse and bin, batch and serial numbers, picking and shipping, returns — and whether each step posts through to the next document and to the ledger instead of being retyped.
0 — No order or stock handling; the product is a contact list or an invoicing tool.
3 — Items with a stock count and an order list, but purchasing, goods receipt and delivery are not connected and stock is corrected by hand.
5 — Quote, order, delivery note and invoice as one document chain, purchase orders with goods receipt booking stock, and stock levels with reorder points per item.
8 — Several warehouses and storage bins, batch and serial number tracking, mobile picking and scanning, carrier and shop or marketplace connections, returns with restocking and credit note, drop shipping, and stock valuation that flows into the books.
10 — The goods chain runs and is evidenced in the system: demand-driven purchasing proposals, EDI with suppliers and customers, fulfilment and multi-channel stock allocation, best-before and recall traceability per batch from supplier to customer, and every movement attributed and dated.
The Managing Director
The goods chain is connected rather than retyped: a confirmed purchase order creates the receipt, stock only moves when the receipt is validated, and draft invoices generate automatically from sales and delivery orders. Multi-warehouse, lot and serial traceability, offline barcode picking in four strategies, carrier label integrations and valuation methods from FIFO to standard cost are documented; we found no public information on returns with restocking, drop shipping or supplier EDI. 3 4 10 11 12
The Head of Finance
The chain posts through: a confirmed purchase order creates a receipt in inventory and quantity on hand only moves when that receipt is validated, and order-line changes generate a new transfer linked to the purchase order, so nothing is retyped. Multi-warehouse stock, lot and serial traceability, offline barcode scanning with GS1, single/cluster/wave/batch picking, putaway strategies with ABC analysis, carrier label integration, and FIFO, average, LIFO and standard valuation on periodic or perpetual accounting are documented. We found no public information on EDI with suppliers and customers, drop shipping, returns with restocking and credit note, or best-before and recall traceability per batch. 3 11 12
The Operations Lead
Confirming a purchase order creates a receipt and quantity on hand moves only when that receipt is validated, with serial and lot numbers set on the goods receipt — exactly the discipline I want at the dock, and the forum confirms order-line changes generate a new linked transfer. Multi-warehouse stock with putaway and ABC strategies, offline barcode scanning including GS1, single/cluster/wave/batch picking, carrier label integration, min-max and master-schedule replenishment, and FIFO/LIFO/average/standard valuation are all documented. We found no public information on returns with restocking, drop shipping or supplier EDI. 3 4 11 12
The Online Retailer
Purchase orders book stock only when the receipt is validated, which is the right chain, and multi-warehouse stock, batch and serial traceability, offline barcode picking with cluster, wave and batch strategies, carrier label printing and valuation from FIFO to standard price are all documented. What holds it down for me: I found no public information on connections to Shopware, Amazon or eBay, nor on returns with restocking or drop shipping — precisely the multi-channel stock sync that would stop me overselling a bestseller at Christmas. 3 4 11 12
The IT Integrator
The document chain is evidenced end to end: a confirmed purchase order creates a receipt, stock moves only when that receipt is validated, lot and serial numbers are set at the receipt, and later order-line changes spawn new linked transfers. Multi-warehouse stock, putaway strategies with ABC analysis, four picking strategies on an offline GS1-capable scanner, carrier label integration, min-max and master-schedule replenishment and FIFO, LIFO, average and standard valuation are all documented. I found no public information on returns with restocking, drop shipping or marketplace connections. 3 4 11 12
The Skeptic
The chain is wired: a confirmed purchase order creates a receipt, stock moves only when the receipt is validated, picking runs single, cluster, wave or batch with offline scans of barcode, QR and GS-1, lots and serials traced in one click, multiple warehouses with putaway strategies, and valuation in FIFO, average, LIFO or standard, periodic or perpetual. Credit notes exist on both sides and carriers print the labels; we found no public information on returns with restocking, drop shipping or marketplace connections. 3 4 11 12
Manufacturing, services & projects
Show reasoningHide reasoning
How this is scored
The depth for the buyer's own business model: bills of materials, work orders and capacity planning for manufacturers; projects, time, resources and milestone billing for service firms; contracts, subscriptions and field service. A product is judged on the models it says it serves.
0 — Nothing beyond trading goods; no bills of materials, projects or service billing.
3 — A simple kit or set of items, or a project tag on invoices, but no production orders, no time recording and no planning.
5 — For at least one model a working core: bills of materials with production orders consuming stock, or projects with time recording and billing from logged hours, with the supported models named on the vendor's pages.
8 — Multi-level bills of materials with routings, work centres and capacity planning, or projects with budgets, resource planning, milestone and recurring billing, and service or maintenance contracts — with costs flowing to cost accounting.
10 — Industry depth documented for the models served: MRP runs with material and capacity planning, shop-floor data capture and quality checks, variant configuration, or full professional-services automation with utilisation, contracts and revenue recognition — each described with its limits in public documentation.
The Managing Director
Manufacturing depth is on the vendor's own pages: MRP, MES, PLM, quality, shop floor and maintenance on one platform, with finite capacity scheduling against a Gantt chart, a tablet dashboard for workers and make-or-buy sourcing options. Projects with timesheets and subscription billing are documented, and captured forum answers openly describe how the subscription and project apps are not yet integrated in the standard product. 4 5 10 14
The Head of Finance
Manufacturing depth is documented on the vendor's pages: MRP with master production schedule and min-max replenishment, finite capacity scheduling on a Gantt, a tablet shop-floor dashboard with worker feedback and quality control points, byproducts, and make/buy/subcontract sourcing, with a forum thread covering multi-step manufacturing with bills of materials and operations. For services, draft invoices generate automatically from timesheets and subscriptions, and the captured forum pages openly describe limits of the subscription-to-project flow. We found no public information on variant configuration or professional-services automation with utilisation and revenue recognition. 4 10 13 14
The Operations Lead
For my assembly line this is close to the full picture: MRP with finite-capacity scheduling on a Gantt, a master production schedule for sales-and-operations planning, byproducts on bills of materials, a tablet shop-floor app with quality control points and worker loss feedback, make-or-buy and subcontract sourcing options, and lot/serial traceability. Multi-step manufacturing with bills of materials and operations is confirmed in the forum threads, and draft invoices generate from timesheets and subscriptions for the service side. The captured forum pages themselves describe the limits of subscription-project integration in older versions, and we found no public information on variant configuration. 4 10 13 14
The Online Retailer
The manufacturing set is documented as MRP plus MES plus quality, workshop and maintenance, with finite capacity planning on a Gantt chart, a tablet shop-floor app, worker feedback and lot traceability — real depth I would never use. On the services side, subscriptions generate recurring invoices and timesheets serve as client justificatives, but the gaps I read about the subscription and project apps not being integrated come from community answers on older versions rather than product documentation. 4 13 14
The IT Integrator
For a manufacturer this is the deepest page set I have read: MRP, MES, PLM, quality, shop floor and maintenance on one platform, multi-step production with BOMs and operations, finite-capacity scheduling on a Gantt chart, real-time order simulation with component availability and cost control, tablet shop-floor dashboards with worker feedback, quality checkpoints and an IoT box for machines, plus make, buy and subcontract sourcing proposals. Projects bill from timesheets and budgets run per project through analytic accounts, but forum threads record that subscriptions create invoices only, with no orders, tasks or field-service calls generated from the subscription app. 4 13 14 10
The Skeptic
Manufacturing is the deep side: MRP, MES and PLM on one platform, finite capacity scheduling against a Gantt view, a master production schedule for sales and operations planning, byproducts, make-or-buy-or-subcontract sourcing, and a tablet shop floor with quality control points and worker feedback on losses. Services run on timesheets that generate draft invoices plus a subscription app, though captured forum threads state that in versions 14 and 15 the subscription app created invoices only, with neither sale orders nor tasks, and that subscription and project were not integrated in the standard product. We found no public information on project budgets, resource planning or work-order costs flowing into cost accounting. 4 5 10 14
Integration, API & data portability
Show reasoningHide reasoning
How this is scored
How the ERP connects and how the data gets in and out: a public API reference, webhooks, standard connectors for shops, marketplaces, banks, payroll, DATEV and BI, data import from the previous system, and a documented full export when the company leaves.
0 — No API, no import and no export beyond printing.
3 — CSV import and export of some lists, a few named integrations, but no public API documentation and no full export.
5 — A documented REST or OData API, CSV or Excel import for master data and open items, and standard connectors to common shops, banks and DATEV.
8 — A public, versioned API reference covering all main objects with webhooks, a connector marketplace, a documented migration path from named predecessor systems, and a full data export of master data, documents and postings available to the customer.
10 — Open by design and evidenced: complete API coverage with sandbox tenants and rate limits stated, open data formats or open-source code, a contractual exit with export format and timeline, and self-hosting or on-premise as a documented alternative to the vendor's cloud.
The Managing Director
A REST and XML-RPC API, CSV and Excel import, standard bank statement formats and the DATEV export are documented, and the exit story is strong: PostgreSQL as the data format, manual backups of the live database downloadable at any time, data returned or deleted at termination, and self-hosting as a documented alternative. We found no public information on webhooks, a versioned API reference or a migration path from named predecessor systems, and one captured pricing page ties the external API to a Custom plan whose price is not shown. 1 5 6 8 10 15
The Head of Finance
A RESTful and XML-RPC web-services API, CSV and Excel import, and connectors for carriers and five payment providers are documented, and portability is real: data lives in PostgreSQL, manual backups download from the control panel at any time, the source code is open with GitHub access, self-hosting is a stated option, and data is returned or deleted at the customer's choice on termination. The DATEV hand-over is evidenced only through the support forum, with the account-number length quirk. We found no public information on webhooks, a connector marketplace, a documented migration path from predecessor systems, or API rate limits and sandbox tenants, and the pricing page shows the external API as Custom-plan only. 1 6 8 10 15
The Operations Lead
There is a documented REST and XML-RPC web-services API plus CSV and Excel bulk import, a DATEV export, and portability is unusually strong: PostgreSQL as the data format, downloadable full database backups, source code access and a contractual self-hosting option with data returned or deleted at the customer's choice on termination. The pricing page ties the external API to the Custom plan only. We found no public information on webhooks, a connector marketplace, a migration path from named predecessor systems, or sandbox tenants and rate limits. 1 5 6 8 10 15
The Online Retailer
A RESTful and XML-RPC API with named language bindings, CSV and Excel import and bank statement formats like CAMT.053 and CODA are documented, and portability is unusually strong: PostgreSQL as the data format, manual backups downloadable at any time, self-hosting as a stated alternative, and data deleted or returned on termination. But I found no public information on webhooks, a versioned API reference, a connector marketplace or standard connectors to Shopware, Amazon or eBay, and the pricing page marks the external API as available in the Custom plan only, which I would need to price before relying on it. 1 5 6 8 10
The IT Integrator
The pages document REST and XML-RPC APIs with client libraries for Python, PHP, Java, C# and Ruby, CSV and Excel import, a DATEV export, plus carrier, tax and payment connectors, and portability is unusually strong: PostgreSQL as the data format, source code and GitHub access, self-hosting as a contractual option, downloadable backups and data return or deletion on exit. I found no public information on webhooks, API versioning or sandbox tenants, and the pricing page associates the external API with the Custom tariff only. 10 15 1 5 6 8
The Skeptic
Getting the data out is the strongest part: PostgreSQL with no proprietary format, manual backup downloads at any time, source code and GitHub access, self-hosting as a stated alternative, and delete-or-return of the database at termination — a real exit, in the contract. The interfaces are named as RESTful and XML-RPC with five languages, CSV and Excel import, bank statement formats and a DATEV export, but the pricing page lists the external API under the Custom plan only, and we found no public information on a public API reference, webhooks, a connector marketplace or a migration path from predecessor systems. 1 5 6 10 15
Rollout, roles & operations
Show reasoningHide reasoning
How this is scored
What it takes to go live and run the system: implementation path (self-service, vendor, partner network), onboarding and training, roles and permissions, audit log, updates and customisation that survive them, support channels and service levels, and availability.
0 — No information on implementation, roles, support or availability.
3 — A contact form and a help page, but no stated implementation path, no role model and no support terms.
5 — A described onboarding or implementation offer, user roles with permissions, a help centre with current documentation, and support channels with hours.
8 — Implementation methods with typical duration stated, a certified partner network or vendor services listed, fine-grained permissions with a change log, customisation without code that survives updates, and published service levels for support and availability.
10 — Operations are evidenced: a status page with uptime history, release notes and an update policy, a field-level audit trail, sandbox or test tenants, and support, training and implementation terms public enough to plan a go-live without a sales call.
The Managing Director
Running it is plannable: a published service level page with a 99.9 percent uptime target, Tier-III data centres with N+1 redundancy, bug handling starting within two business days, unlimited free bug tickets, a partner network, education services and backups restorable into a separate database for testing. What I could not plan from the captured pages is a stated implementation method with typical duration, and we found no public information on a field-level audit trail of changes. 6 8 17 18
The Head of Finance
Support terms are public: unlimited free tickets for bugs with handling starting within two business days, web form and phone channels with local opening hours, and a choice between a partner or Odoo SA directly; an SLA page states 99.9% uptime on Tier-III data centres with N+1 redundancy, and the yearly release policy with three covered versions and an upgrade service is documented. We found no public information on typical implementation duration, a change log or field-level audit trail of user actions, no-code customisation surviving updates, or a status page with uptime history. 6 17 18
The Operations Lead
There is a published cloud service level — 99.9 percent uptime, Tier-III data centres, N+1 redundancy — plus bug handling started within two business days, unlimited free bug tickets, an implementation route through a partner network or Odoo directly, and upgrade, education and custom development services listed. Server-side access control and administrative login controls are documented. For planning a go-live, we found no public information on a role and permission model, a change log, typical implementation duration or a status page with uptime history. 5 6 8 17 18
The Online Retailer
There is a real support structure: web form and phone channels with local opening hours, unlimited free bug tickets, handling started within two business days, automatic security updates on the cloud, and a published 99.9 per cent uptime service level in Tier-III data centres with N+1 redundancy. Implementation runs self-service or through a partner and accountant network, but I found no public information on typical go-live durations, a field-level change log behind permissions, or a status page with uptime history. 6 17 18
The IT Integrator
There is a partner network plus vendor services (upgrade, custom development, education), support by web form and phone with local opening hours, unlimited free bug tickets with handling started within two business days, and a published cloud service level with a 99.9 percent uptime target on Tier-III data centres. Access control is enforced server-side independent of the interface, with configurable password, lockout and external OIDC/OAuth authentication. I found no public information on an audit log of user actions, typical implementation durations or a status page with uptime history. 6 8 17 18
The Skeptic
Operations are partly public: a service level agreement page with a 99.9% uptime target and Tier-III data centres, bug handling started within two business days, unlimited free bug tickets, support by web form and phone, and a partner network alongside education and custom development services. What a go-live plan still needs we did not find — typical implementation duration, partner certification, a change log on permissions, no-code customisation that survives updates, or a status page with uptime history — and extra modules are billed monthly per hundred lines of code, which is where the partner meter starts running. 6 8 17 18
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where the ERP data — customers, suppliers, prices, postings, employees — is hosted, and who the subprocessors are (cloud infrastructure, email, support tooling, AI features). Independently sourced by the sovereignty pipeline; an ERP holds a company's entire commercial record, so the ownership chain counts, not only the server location.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy exists, but hosting location is unstated or non-EU and the processors behind the service are not named.
5 — EU hosting stated and an EU contracting entity, but parts of the chain (US hyperscaler, AI features, support or email tooling) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with locations, a data processing agreement offered, and an on-premise or EU-only hosting option stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, data export and deletion documented, and a certification such as ISO 27001 or BSI C5 published rather than implied.
The Managing Director
The contracting entity is Odoo S.A. in Belgium, EU-region customers are hosted on named infrastructure in France and Belgium through Google Cloud EMEA and OVH, the subprocessor list is published with standard contractual clauses applied, and self-hosting is documented. Two caveats for a European buyer: EU-hosted customers carry an additional backup in Canada until the fourth quarter of 2026, and the vendor-level certification shown is CSA STAR Level 1, with the ISO 27001 listings being datacentre certifications. 6 7 8
The Head of Finance
The contracting entity is Odoo S.A. in Belgium under Belgian law, EU-region production runs in France and Belgium on named Google Cloud EMEA and OVH infrastructure with backups in France, the Netherlands and Sweden, and the subprocessor list names Amazon Web Services, Outscale, Scaleway and FullStory with locations and purposes; standard contractual clauses are applied and self-hosting is a stated alternative. Existing EU-hosted customers keep an additional backup in Canada until the fourth quarter of 2026 per the privacy policy, and we found no public information on the ownership chain behind the Belgian entity. A CSA STAR Level 1 participation is published, and data export and deletion on exit are documented. 6 7 8
The Operations Lead
Odoo S.A. in Belgium is the contracting entity under Belgian law, EU production runs in France and Belgium on named providers (Google Cloud EMEA, OVH) with subprocessors and their purposes listed, EU standard contractual clauses are applied, the hosting region is selectable and self-hosting is a documented alternative. Deductions: EU-region customers below version 19 keep an additional backup copy in Canada until the fourth quarter of 2026, and Google Cloud EMEA and Amazon Web Services sit in the chain with a US Cloud Act exposure. We found no public information on the ownership chain or a vendor-level ISO 27001 — the ISO certificates shown are the data centres', with CSA STAR Level 1 as Odoo's own participation. 6 7 8
The Online Retailer
The contracting entity is Odoo S.A. in Belgium under Belgian law, EU-region production runs in France and Belgium on named Google Cloud EMEA and OVH infrastructure, subprocessors are listed with purposes and locations, EU standard contractual clauses are applied, and self-hosting is stated as an alternative. What holds it back: EU-hosted customers on versions before Odoo 19 keep an additional backup in Canada until the fourth quarter of 2026, trial-session recordings were processed by FullStory in US Google Cloud data centres, and I found no public information on the ownership chain or an ISO 27001 held by Odoo itself — only CSA STAR Level 1 plus data-centre certificates. 6 7 8
The IT Integrator
The contracting entity is Odoo S.A. in Belgium under Belgian law, EU-region production runs in France and Belgium on named providers (Google Cloud EMEA and OVH) with backups in France, the Netherlands and Sweden, and the subprocessor list names each provider with purpose and location, including Scaleway for mail and Outscale SecNumCloud for French e-invoice transmission; self-hosting and region choice are contractual and data is returned or deleted at termination. Two things hold it back: EU customers not yet on Odoo 19.0 keep one backup copy in Canada until the fourth quarter of 2026, and the listed ISO 27001 certificates belong to the data-centre providers while Odoo itself shows CSA STAR Level 1. 7 6 18 8
The Skeptic
Odoo S.A. sits in Belgium under Belgian law, the Europe region hosts production in France and Belgium on named Google Cloud and OVH infrastructure with the region selectable, subprocessors are listed with locations and purposes, EU standard contractual clauses bind internal transfers, and self-hosting is a stated option. We found no public information on the parent or ownership chain, Odoo's own certification shows CSA STAR Level 1 rather than a published ISO 27001 or BSI C5 for the vendor itself, and the chain touches US parents — Google Cloud EMEA for EU production, AWS for regions outside the EU, FullStory in the United States for trial recordings — while some EU-hosted customers' backups stay in Canada until a stated transition in the fourth quarter of 2026. 1 6 7 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a company can compute the real annual cost from public pages alone: price per user, module, company or transaction volume, which modules (accounting, warehouse, production, POS) cost extra, implementation and onboarding fees, minimum term, and what happens to the data on cancellation.
0 — No public prices at all; every customer is a sales call or a partner proposal.
3 — A starting price or "from" figure exists, but what is included and how it scales with users, modules or companies is unclear.
5 — Prices per edition or module are public with the main inclusions, but at least one commonly needed piece (implementation, extra companies, warehouse or production module, API use) is unpriced or "on request".
8 — Every edition and module priced publicly with its scaling rule (per user, company or volume), onboarding and implementation packages priced, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given company size and module set, with every add-on, implementation, support and hosting cost and the cancellation and data-return terms published.
The Managing Director
The headline is genuinely clear: "19,90 € / Monat für ALLE Apps", Light-Benutzer at "7,90 €", one price per user with all apps included, taxes stated as exclusive, renewal increases capped at up to 7 percent per year, a free one-app plan and cancellation with data return or deletion at the customer's choice. What I could not compute before signing: implementation and education costs, Odoo.sh hosting (stated as not included), and the Custom plan that the captured pricing page ties to the external API. 1 5 6 7
The Head of Finance
The headline model is unusually clear: "19,90 € / Monat für ALLE Apps" per user, Light users at 7,90 €, a free one-app plan with unlimited users on Odoo Online, taxes exclusive, renewal increases capped at 7% per year and 30 days' written notice against automatic renewal. The real annual cost is still not computable from public pages alone: Odoo.sh hosting costs are stated as not included with no figure, custom developments bill monthly per 100 lines of code at a rate specified in writing only at conclusion of the agreement, the Custom plan carrying the external API is unpriced, and education, upgrade and implementation services carry no public fee. 1 5 6
The Operations Lead
Unusually computable: 19,90 € per month for all apps per user, Light users at 7,90 €, a free single-app plan with unlimited users, monthly or yearly billing, taxes stated as excluded, charges rising by up to 7 percent per year on renewal with 30 days' notice, and data returned or deleted on cancellation after a three-week grace period. The gaps for budgeting: implementation and onboarding via partners, Odoo.sh hosting and the Custom plan are not priced publicly, and extra custom modules are charged per 100 lines of code with the amount only fixed in writing at contract conclusion. 1 5 6 7
The Online Retailer
Prices are refreshingly clear for a shop my size: 19,90 € / Monat für ALLE Apps on a single per-user price with no usage-based pricing, Light-Benutzer zu 7,90 €, a free single-app plan with unlimited users, taxes stated as exclusive, renewal increases capped at up to 7 per cent per year, and data deleted or returned on termination after a three-week grace. What keeps it from the top: implementation and onboarding carry no published price, Odoo.sh hosting costs are marked as not included without a figure, and extra modules are charged per 100 lines of code at a rate only specified in writing at conclusion. 1 5 6 7
The IT Integrator
Public pricing is unusually clear: 19,90 € / Monat for all apps per user, Light users at 7,90 €, a free single-app plan with unlimited users, one all-inclusive per-user price with no feature upselling or usage pricing, taxes stated as excluded, auto-renewal with 30 days' notice, a 7 percent annual increase cap, and contractual data return or deletion on exit. Implementation services and Odoo.sh hosting are not priced publicly — the page states Odoo.sh costs are not included — and extra modules bill per 100 lines of code at a rate fixed only in writing at conclusion, so the full annual cost is not computable from public pages alone. 1 5 6
The Skeptic
The subscription is unusually legible: "19,90 € / Monat für ALLE Apps", "Light-Benutzer zu 7,90 €", a free single-app plan with unlimited users, taxes stated as exclusive, a 7% cap on renewal increases and delete-or-return of data on termination. It stops where implementation starts: we found no public price for custom developments, education, upgrade services or Odoo.sh hosting — the pricing page itself marks Odoo.sh costs as "nicht inbegriffen" — the Custom plan's charges are "specified in writing at the conclusion of the Agreement", and extra modules are billed per hundred lines of code. 1 5 6 7
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 7 Report an error |
Questions about Odoo
Is Odoo European?
Yes. whats-best.ai classifies Odoo as EU-Made.
Where does Odoo store data?
Not stated on the vendor’s pages as of 26 Oct 2026.
Does Odoo have a free plan?
Yes. Odoo has a free plan, per the vendor’s page captured 26 Oct 2026.
What are the best alternatives to Odoo?
As of 29 Oct 2026, the panel rates weclapp (3.5/5), Haufe X360 (3.5/5) and JTL-Wawi (3.5/5) highest among the other 13 ERP products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is weclapp (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Odoo alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 26 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. Google Cloud EMEA Ltd is an EU contracting entity of US-headquartered Google, and the same list names Amazon Web Services, Inc. as hosting provider for regions outside the EU, alongside the French providers OVH, Outscale and Scaleway.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 60 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.odoo.com Checked 26 Oct 2026 Details →
- 2 Features page (all apps) www.odoo.com Checked 26 Oct 2026 Details →
- 3 Features page (inventory) www.odoo.com Checked 26 Oct 2026 Details →
- 4 Features page (manufacturing) www.odoo.com Checked 26 Oct 2026 Details →
- 5 Pricing page www.odoo.com Checked 26 Oct 2026 Details →
- 6 Terms naming the legal entity www.odoo.com Checked 26 Oct 2026 Details →
- 7 Privacy policy www.odoo.com Checked 26 Oct 2026 Details →
- 8 Security page www.odoo.com Checked 26 Oct 2026 Details →
- 9 Finance, tax & compliance — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 10 Finance, tax & compliance — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 11 Purchasing, inventory & order processing — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 12 Purchasing, inventory & order processing — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 13 Manufacturing, services & projects — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 14 Manufacturing, services & projects — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 15 Integration, API & data portability — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 16 Integration, API & data portability — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 17 Rollout, roles & operations — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →
- 18 Rollout, roles & operations — found from sitemap www.odoo.com Checked 26 Oct 2026 Details →