Metabase Odoo Integration
Open-source BI on top of Odoo.
Metabase is the pragmatic choice when you want dashboards and self-service questions on Odoo data without a licence per viewer. It sits on the Postgres database, which is exactly why it should point at a read replica rather than at production. The value comes from curating models first: a handful of clean, documented queries that people build on, instead of forty raw tables that only a developer can interpret.
What syncs between Metabase and Odoo
- โ Read-only access to Odoo tables: Odoo to Metabase, one-way. Nothing is ever written back.
- โ Curated models: saved queries that hide the ERP schema and expose business-shaped tables.
- โ Dashboards and questions: built on those models rather than on raw tables.
- โ Scheduled subscriptions: dashboards sent by email on a schedule so numbers reach people who never log in.
- โ Alerts: triggered when a metric crosses a threshold you define.
- โ Permission groups: mapped so each team sees only its own data.
How we implement it
- 1 Read replica
Stand up a replica and point Metabase at it. Analysts running unbounded queries against production is a well-known way to slow an ERP.
- 2 Schema orientation
Document the tables that matter and the traps: archived records, company scoping, state fields and relation tables that surprise newcomers.
- 3 Curated models
Build the core models first: sales, invoices, stock, projects. Everyone else builds on those instead of writing the same joins again.
- 4 Dashboards per audience
One dashboard per role, answering the questions that role actually asks, rather than one dashboard with forty cards.
- 5 Permissions
Group-level access so data is scoped by company, country or team, matching the access people have in Odoo.
- 6 Subscriptions and handover
Schedule the email subscriptions, then train two or three internal people so the tool survives without us.
Services that cover this work
Odoo Customization
Custom modules built to match your exact workflow.
Odoo Integration
Connect Odoo with your stack and third-party APIs.
Odoo Consultancy
Expert advice on architecture, licensing, and strategy.
Metabase and Odoo: common questions
Will it slow down Odoo?
Not if it reads a replica, which is how we set it up. Pointing BI at the production database is the usual cause of the reports and the ERP both getting slower at month end.
Do users need SQL?
No. Once curated models exist, most questions are built by clicking. SQL stays available for analysts who want it, which keeps both audiences served.
How does it compare with Odoo reporting?
Odoo reporting is better inside a workflow, where you act on the record. Metabase is better for cross-module dashboards, trends and anything that needs data from outside Odoo.
Can numbers be emailed automatically?
Yes. Dashboard subscriptions go out on a schedule, and alerts fire when a metric crosses a threshold. That is how the people who never log in still get the figures.
What about archived records?
Odoo hides archived records in the interface but they remain in the tables, so models filter on the active flag explicitly. Missing that is the most common source of BI figures that disagree with Odoo.
Other analytics integrations
Need a connector that is not on the list?
Custom REST, GraphQL, webhook, EDI and flat-file integrations, built with retry, idempotency and audit logging so a failed message is visible instead of lost.