whats-best.ai
Search Sign in

CRM

Odoo CRM

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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 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 Solo Seller

Weighted verdict

Runs their pipeline between customer calls and pays with their own card. Optimizes for a CRM that is set up in an afternoon, priced honestly at 1-5 seats, and never asks them to configure an object model. Rejects seat minimums and features held hostage in enterprise tiers.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Solo Seller

Contact & data model

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.

Report an error

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

Report an error

Pipeline & forecasting

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.

Report an error

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

Report an error

Automation & workflows

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.

Report an error

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

Report an error

Integrations & API

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.

Report an error

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

Report an error

European sovereignty

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.

Report an error

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

Report an error

Import, export & exit

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.

Report an error

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

Report an error

Pricing transparency

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.

Report an error

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

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.

Do you know more about Odoo CRM? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor product page www.odoo.com Checked 15 Sep 2026 Details →
  2. 2 Vendor pricing page www.odoo.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
  3. 3 Privacy policy www.odoo.com Checked 15 Sep 2026 Details →
  4. 4 Contact & data model — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  5. 5 Contact & data model — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  6. 6 Pipeline & forecasting — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  7. 7 Pipeline & forecasting — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  8. 8 Automation & workflows — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  9. 9 Automation & workflows — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  10. 10 Integrations & API — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  11. 11 Integrations & API — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  12. 12 Import, export & exit — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →
  13. 13 Import, export & exit — found from sitemap www.odoo.com Checked 1 Oct 2026 Details →