CRM
Odoo CRM
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Odoo SA · www.odoo.com
Compare with Zoho CRM → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Odoo CRM, from Belgian vendor Odoo S.A., scores highest on sovereignty, where marks cluster at 7-8: European production hosting in France and Belgium, a published subprocessor list, EU Standard Contractual Clauses, and self-service database deletion and full-backup export. Data portability follows at 6-8, held down for some judges by the External API sitting in the Custom plan, for which we found no public price. Pricing transparency lands at 4-5: the One App Free tier at € 0 with unlimited users and no credit card required is public, and a worked example totals €4,776.00 / year for all apps at 20 users, but we found no public information on per-seat figures for the Standard and Custom plans, and the discount is valid 12 months for initial users ordered. The sales pipeline is weakest, clustered at 3: a Kanban pipeline with quotations and a probable-revenue view is evidenced, while a captured forum answer reports recurring subscriptions do not come back in the sales forecast and revenues are booked as lump sums. Scores sit in narrow ranges, and no disagreements were flagged.
Speaks for it
- A complete database backup is self-service from the control panel at any time.
- European production hosting in France and Belgium, a published subprocessor list, and EU Standard Contractual Clauses.
- A One App Free tier at € 0 with unlimited users and no credit card required.
- CSV import runs a Validate step before committing.
- Incoming email is added to the pipeline automatically, with Email, Live chat, SMS and VoIP channels listed.
Held against it
- The External API sits in the Custom plan, for which we found no public price.
- Recurring subscriptions do not come back in the sales forecast, and revenues are booked as lump sums.
- Only admin-level users in the Administration / Settings group can create automated actions.
- EU-hosted customers other than new customers on Odoo 19.0 or later keep an additional Canada-based backup until the transition completes (ETA Q4 2026).
- Personal data can persist in backups for up to 12 months after a deletion request.
Best for
- You want a free start with one app at € 0, unlimited users, and no credit card required.
- You need a built-in exit path — on-demand full-database backup and self-service deletion rather than a support-ticket process.
- Your procurement requires a European vendor with EU production hosting and a published subprocessor list.
- Your sales process is stage-based deal tracking with quotations rather than subscription revenue forecasting.
Avoid if
- Your revenue is subscription-based and your finance team needs it reflected in the sales forecast.
- You need API access for your integration stack without entering a Custom-plan sales conversation.
- Your sellers, rather than admins, need to build automation rules.
- Your data-deletion policy cannot tolerate personal data persisting in backups for up to 12 months.
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
Contacts, companies and their relations exist and custom fields even survive export and import, but tying a person to their company mid-import means juggling External IDs and a three-part procedure, and I found no public information on dedupe or merge tooling. As a one-person shop I can live with these objects, but nobody should need pseudo-foreign-keys to load an address book on a Tuesday afternoon. 1 4 5
The Data Protection Officer
The standard objects exist with persons linked to companies via import, custom fields on contacts, multi-company support, and record visibility governed by sales access-right groups — but the captured forum threads show linking people to employers on import is an External ID procedure that changed between versions and needed three parts in Odoo 13. We found no public information on duplicate detection or merge tooling, and unchecked duplicates in a database of other people's personal data is a records-hygiene problem before it is a sales one. 1 4 5 6
The Sales Ops Lead
The standard three objects exist with real relations — persons link to companies at import via external identifiers, multi-company is supported, and pipeline visibility is genuinely permissioned through sales access-right groups. Custom fields are evidenced only as a code-level exercise, and I found no public information on deduplication or required-field enforcement, so hygiene rests on manual discipline. 1 4 5 6
The RevOps Integrator
Contacts, companies and opportunities exist with person-to-company relations kept through External ID mapping during import, custom fields on contacts, and access groups that gate which records each salesperson sees — workable, though linking people to companies on import needs a multi-step procedure and custom fields sit behind a technical features toggle. We found no public information on deduplication or merge tooling. 4 5 6
The Migrator
Relations between people and companies are real — the import path links contacts to companies via external identifiers — and custom fields exist on contacts, but the evidence shows custom fields arriving via code and a three-part import procedure to keep contacts with their companies. We found no public information on deduplication or merge tooling, which is exactly the silence that bites during a migration. Visibility of pipeline records is governed by sales access-right groups, which is record-level rather than field-level. 1 4 5 6
The Skeptic
Contacts, companies and opportunities exist and relate to one another, but linking a person to a company through CSV import is described in the vendor's own forum as a multi-pass procedure built on External IDs and an "Is a Company" flag — a workaround where a hygiene tool should be. Custom fields on contacts are evidenced, though the discussion points to a code-based method, and visibility of records runs through access-right groups rather than field-level control. We found no public information on deduplication, merge tooling or field-level history. 4 5 6 7
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
The kanban with drag-and-drop stages is there and quotations feed a probable-revenue view, but I found no public information on required fields per stage, a custom report builder or quota tracking, and a captured forum thread notes monthly subscriptions don't come back in the sales forecast with revenues booked as lump sums. Good enough for my pipeline; nothing here a finance department signs off on. 1 7
The Data Protection Officer
The captured pages show a Kanban pipeline you drag opportunities across, quotations, and insight into planned or probable revenue — while a forum capture reports that recurring subscriptions do not come back in the sales forecast and revenues are booked as lump sums. We found no public information on required fields per stage, win/loss capture, quota tracking or custom reporting, so nothing here evidences a process a finance department would sign. 1 7
The Sales Ops Lead
Kanban stages with drag-and-drop and a probable-revenue view are all the captured product page shows, and the one forecast discussion I found states that monthly subscriptions do not come back in the sales forecast and revenues are booked as lump sums, which is not what a finance department can accept. I found no public information on required fields per stage, quota tracking or forecast snapshots. 1 6 7
The RevOps Integrator
The pipeline is a Kanban of opportunities by stage with quotations and a planned or probable revenue view, and sales access groups control visibility of other users' records. Captured forum answers describe revenues booked as lump sums and monthly subscriptions that do not reappear in the sales forecast; we found no public information on stage requirements, win/loss capture, quota tracking or a custom report builder. 1 6 7
The Migrator
The pipeline is a Kanban of opportunities by stage with quotations and a 'planned or probable revenue' view, and record visibility is controlled through sales access-right groups. The captured forum pages document forecasting pain — revenues booked as 'lump sums' and monthly subscriptions that do not come back in the sales forecast — and we found no public information on stage requirements, win/loss capture or a custom report builder. 1 6 7
The Skeptic
What is evidenced is a Kanban pipeline with drag-and-drop stages, quotations and "probable revenue" insight, with record visibility governed by sales access-right groups. The only forecasting discussion we found reports that recurring subscriptions do not come back in the sales forecast and that revenues are booked as lump sums — not reporting a finance department would sign. We found no public information on required fields per stage, a report builder, quota tracking or forecast snapshots. 1 6 7
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
Automation is real — lead creation, team assignment, scheduled activities — but the captured pages show record-level rules where the create trigger was folded into a catch-all on-save trigger with a creation-date workaround, and creating automated actions is admin-only. I found no public information on multi-step sequences, branching or delays, so this reads as if-this-then-that with friction, not a workflow engine. 1 8 9
The Data Protection Officer
Automation is real but thin and gated: lead creation, team assignment and scheduled activities are advertised, and the captures describe record-triggered automation rules — yet only users in the Administration/Settings group can create automated actions, and a forum capture shows the create-time trigger deprecated in favor of an On Save trigger whose official workaround is firing on the creation date. We found no public information on branching, delays or multi-step sequences. 1 8 9
The Sales Ops Lead
Automation rules act on records for lead creation, team assignment and scheduled activities, but the captured help threads show automated actions are restricted to admin-level users and even a create-only trigger needs a workaround through an on-save rule. I found no public information on branching, multi-step sequences or per-step logging. 1 8 9
The RevOps Integrator
Automation rules handle lead creation, team assignment and scheduled activities with an On Save trigger covering create and update, though create-only rules rely on the official workaround of triggering on the creation date field and only the Administration / Settings group can build automated actions. We found no public information on multi-step sequences, branching or sequence analytics. 1 8 9
The Migrator
Automation exists — lead creation, team assignment, scheduled activities, AI lead scoring — with rules firing on 'On Save' triggers, but creating automated actions is restricted to Administration/Settings admin users, and create-only triggers are deprecated in favor of an official workaround selecting creation date as the trigger field. We found no public information on multi-step sequences with delays or branching. 1 8 9
The Skeptic
Automated lead creation, team assignment and scheduled activities are real, but creating automated actions is restricted to admin-level users in the Administration / Settings group, and the create-versus-update distinction was deprecated into an "On Save" trigger whose official workaround is selecting the creation date as the trigger field. We found no public information on multi-step sequences, branching, delays or error handling. 1 8 9
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
Incoming email lands on the pipeline automatically, email, live chat, SMS and VoIP are listed, and there's an XML-RPC channel external tools can feed — but the External API sits in the Custom plan, and I found no public information on two-way calendar sync, webhooks or a native app directory. Holding the API behind a sales conversation is exactly the kind of enterprise-tier hostage-taking I refuse to pay for. 1 2 13
The Data Protection Officer
The captured pages list Email, Live chat, SMS and VoIP as channels with incoming mail added to the pipeline automatically, plus an XML-RPC API for external tools — while the pricing capture lists External API among the Custom plan's features, so what API access other tiers include is not shown. We found no public information on two-way calendar sync, webhooks, OAuth applications or a native integration directory. 1 2 10 13
The Sales Ops Lead
Incoming mail lands in the pipeline automatically and email, live chat, SMS and VoIP are the named channels, but the external API is listed as a feature of the Custom plan and the only protocol the captured help threads document is the older XML-RPC channel. I found no public information on two-way calendar sync, webhooks or OAuth apps. 1 2 10 13
The RevOps Integrator
Incoming email is added to the pipeline automatically and Email, Live chat, SMS and VoIP channels are listed, but the captured pricing places the External API in the Custom plan alongside Odoo Studio and Multi-Company, and the documented route for external tools is an XML-RPC channel. We found no public information on two-way calendar sync, webhooks or native connectors for the revenue stack — an API behind the top tier is a closed door for anyone building a stack. 1 2 10 13
The Migrator
Incoming emails land in the pipeline automatically, and the channel list covers email, live chat, SMS and VoIP. But the external API is named as a feature of the Custom plan, and the API evidence in the captured pages is a legacy XML-RPC channel. We found no public information on two-way calendar sync, webhooks, OAuth apps or documented API limits. 1 2 13
The Skeptic
Email, live chat, SMS and VoIP channels with incoming mail auto-attached to the pipeline are evidenced, as is an external XML-RPC API discussed in the forums — but the pricing page lists the External API among the Custom plan's features, so a buyer below that tier is looking at an unpriced plan for their integration path. We found no public information on calendar sync, webhooks, OAuth applications or API rate limits. 1 2 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
A Belgian company with a published address and VAT number, Europe-region production hosting in France and Belgium, a named subprocessor list built on OVH and Outscale, Standard Contractual Clauses, and self-service database deletion — this is a serious European file. It stops short of the top because EU-hosted customers still carry a Canada-based backup copy until late 2026, personal data can persist in backups up to 12 months after a deletion request, and free-trial session recording ran through a US service (currently inactive). 3
The Data Protection Officer
The captured privacy page shows a Belgian entity with EU-region production in France and Belgium on French infrastructure (OVH, Outscale, Scaleway, including SecNumCloud), a published subprocessor list naming each processor and purpose, and self-service database deletion — a serious European posture. I hold it below the top of the range because EU-hosted customers still carry a Canada-based backup until a transition dated Q4 2026, personal data can persist in backups for up to 12 months after deletion, and Clearbit is used to retrieve business info on visitors coming from EU companies, an open-web enrichment practice I do not sign off. We found no public information on a published data processing agreement or on consent-management fields, and the US processors named (FullStory for trial recordings in Google Cloud US, AWS) are both marked currently inactive. 3
The Sales Ops Lead
A Belgian entity with EU production hosting, a published subprocessor list dominated by French hosts, and self-service deletion and full-backup controls sit near the top of the anchor curve. Residual exposure is named and narrow — Clearbit enrichment for visitors from EU companies, Stripe and PayPal for payments, and an additional Canada-based backup for existing EU customers until the stated 2026 transition — which is honest but real. 3
The RevOps Integrator
A Belgian entity hosts EU customers in France and Belgium on OVH, publishes a subprocessor list naming EU hosts (OVH, Outscale SecNumCloud, Scaleway) alongside US processors such as Stripe, PayPal, CloudFlare and Clearbit that appear scoped to payments, website caching and prospection, and offers self-service database deletion with a three-week grace period. Data can persist in backups up to 12 months after deletion, EU customers on versions before Odoo 19.0 keep a Canada-based backup until the transition completes, and we found no public information on a standalone DPA. 3
The Migrator
The vendor is Odoo S.A., Chaussée de Namur 40, Grand Rosière, Belgium, with European production hosting in France and Belgium, EU Standard Contractual Clauses for subsidiary access, and a published subprocessor list where US exposure — payment processors, Cloudflare caching, Clearbit prospection — is named rather than buried. Deletion of the entire database is self-service from the control panel with a three-week grace period before destruction. Residual caveats are stated on the vendor's own page: personal data can remain in backups for up to 12 months, and EU customers' backups include an additional Canada copy until a transition dated Q4 2026. 3
The Skeptic
A Belgian entity, EU production hosting in France and Belgium, a published subprocessor list anchored on OVH, Outscale and Scaleway, EU Standard Contractual Clauses and self-service whole-database deletion put this near the top of the class. The fine print still costs: EU-hosted customers carry a Canada-based backup until Q4 2026, deleted personal data can persist in backups for up to 12 months, AWS and FullStory — trial recordings formerly processed in the United States — remain authorized subprocessors "for potential future use" though currently inactive, and Do Not Track signals are explicitly unsupported. 3
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
A complete database backup is self-serve from the control panel for transfer or archiving, CSV import and export work the same way across the whole suite with a validate step before committing, and it's open core, so the data model is not a black box. I found no public information on dedupe during import, and with the External API living in the Custom plan a scripted exit could cost more conversation than the backup route. 3 12 13
The Data Protection Officer
Getting out is self-serve: a complete database backup from the control panel, CSV export from list views across nearly all data, and CSV import with a Validate step that acts as a dry run before committing. The captured forum threads show contact-to-company linking on import requires External ID workarounds, we found no public information on dedupe at import, and after deletion personal data can remain in backups for up to 12 months — an exit that still leaves copies behind. 3 4 12
The Sales Ops Lead
A complete database backup is self-service from the control panel, and cancellation destroys the database after a three-week grace period — exit is engineered, not a support ticket. CSV import carries a validate-before-commit step and links contacts to companies during import, though I found no public information on deduplication at import time. 3 4 12
The RevOps Integrator
Exit is close to a feature here: a complete database backup is downloadable at any time from the control panel, CSV import across objects includes a Validate step before commit, a migration service is offered, and the same import/export mechanics apply across the suite. We found no public information on dedupe during import or contractual data-return terms, and import must first be switched on in General Settings. 3 4 12 13
The Migrator
This is the part I check first, and it holds: a complete database backup is exportable self-service from the control panel at any time for transfer or archiving, database deletion is self-service, and CSV import carries a validate step before committing — a poor man's dry-run, but a dry-run. What keeps it down: no public information on dedupe during import, linking contacts to companies needs a multi-part import procedure, and the external API is a Custom-plan feature, so a scripted exit runs through a sales conversation. 3 2 4 12
The Skeptic
Exit is stronger than most: a complete database backup is self-service from the control panel at any time, CSV import and export run across the suite with a validate-before-import step, and the open-core licensing means the software itself is not the cage. What holds it back: we found no public information on export formats or deduplication on import, the migration service is sold rather than included, and the pricing page parks the External API inside the unpriced Custom plan. 3 2 10 12 13
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
The honesty is real at the bottom: one app free forever with unlimited users, no credit card, instant access, and a public calculator that printed a €4,776.00 per year total for 20 users on all apps, with the discount's 12-month validity and the Odoo.sh hosting exclusion stated in plain sight. But the Custom plan where Studio, Multi-Company and the External API live carries no number, and the captured pages don't state VAT treatment or per-seat figures for the paid plans, so I can't compute my own renewal from what's public. 1 2
The Data Protection Officer
The captures show a One App Free plan at € 0 with unlimited users, an all-apps single fee for the Standard and Custom plans, and a worked example totalling €4,776.00 / year for 20 users — but not the per-seat rate behind it, the billing-period split or VAT treatment, and the discount is valid for 12 months for initial users ordered, which obscures the renewal invoice. Odoo.sh hosting cost is stated as not included and the Custom plan carries no numbers in the captures, and we found no public information on usage metering for the optional in-app purchase services. 1 2
The Sales Ops Lead
The free tier with unlimited users is real, and the captured pricing page shows a total of €4,776.00 / year for 20 users with all apps, but the Custom plan — home to Odoo Studio, multi-company and the external API — carries no price there, Odoo.sh hosting is stated as not included, and the discount valid 12 months for initial users ordered makes renewal math hard to compute. Billing period and VAT treatment are not stated on the captured pages. 1 2
The RevOps Integrator
A One App Free tier at € 0 with unlimited users, a savings calculation for 20 users, and a discount stated as valid for 12 months for initial users ordered give a partial picture, but we found no public information on per-seat rates for the Standard and Custom plans, the billing period or VAT treatment. The External API sits in the Custom plan with unanswered questions routed to Account Managers, and Odoo.sh hosting cost is stated as not included. 1 2
The Migrator
The entry point is genuinely public — 'One App Free' at € 0 with unlimited users, no credit card required — and a published worked example totals €4,776.00 / year for all apps at 20 users, with discount terms disclosed as valid 12 months for initial users ordered. But Odoo Studio, Multi-Company and the External API are listed under the unpriced Custom plan, and we found no public information on the Standard plan's per-seat price, its billing-period split or VAT treatment. 1 2
The Skeptic
A genuine free tier — "One App Free € 0", one app, unlimited users — plus a public savings calculator are on the table, but we found no public information on the Standard or Custom per-user price, the monthly/annual split or VAT treatment; the Custom tier is by definition a sales conversation. The renewal maths is the real story: the discount "is valid for 12 months, for initial users ordered", Odoo.sh hosting costs are "not included", and Odoo Studio, Multi-Company and the External API all sit in the Custom plan. 1 2
European sovereignty — proven facts
0 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 | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 Sep 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, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 11 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
- 5 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
- 3 support 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 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor product page www.odoo.com Checked 15 Sep 2026 Details →
- 2 Vendor pricing page www.odoo.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 3 Privacy policy www.odoo.com Checked 15 Sep 2026 Details →
- 4 Contact & data model — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 5 Contact & data model — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 6 Pipeline & forecasting — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 7 Pipeline & forecasting — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 8 Automation & workflows — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 9 Automation & workflows — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 11 Integrations & API — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 12 Import, export & exit — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
- 13 Import, export & exit — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →