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 Sales Ops Lead

Weighted verdict

Owns the forecast a 40-seat team lives by. Optimizes for pipeline discipline: stage hygiene, required fields, routing, quota and forecast reporting the CFO will accept. Rejects freeform pipelines that cannot enforce a process and reporting that stops at a dashboard screenshot.

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

Scored by The Sales Ops Lead

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

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

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

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

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

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

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

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 →