Stream Odoo Sales, Inventory, Accounting & CRM into Power BI — live or scheduled — with secure token auth and multi-company support. One-time license from $399.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Stream Odoo Sales, Inventory, Accounting & CRM into Power BI — live or scheduled — with secure token auth and multi-company support.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Your Microsoft stack runs on Power BI, but your operational truth lives in Odoo — and copy-pasting exports into spreadsheets is not analytics. The Power BI Connector for Odoo closes that gap. It is a purpose-built, build-to-order Odoo module that ECOSIRE designs, develops, installs, and supports so your data team can pull Odoo data straight into Power BI Desktop and the Power BI Service, on a live connection or a scheduled refresh, without brittle CSV pipelines or a shadow ETL stack.
Live (DirectQuery-style) data pulls from Odoo into Power BI for near-real-time operational dashboards
Scheduled refresh via the Power BI Service, with on-premises data gateway support when Odoo is not publicly exposed
Pre-mapped Sales dataset: sale orders, order lines, margins, salesperson and product performance with joins pre-built
Pre-mapped Inventory dataset: on-hand quantities, stock valuation, and stock moves per warehouse and location
Pre-mapped Accounting dataset: invoices, payments, aged receivables/payables, and journal entries
Pre-mapped CRM dataset: leads/opportunities, pipeline stage, expected revenue, and win-rate metrics
This is not an off-the-shelf apps.odoo.com download. After purchase, ECOSIRE builds the connector against your actual database — your models, your custom fields, your access rules — and hands you a clean, upgradeable Odoo app plus everything needed to run it in production. Under the hood it is a proper Odoo module: a token-authenticated read endpoint layered over Odoo's JSON-RPC/XML-RPC API, backed by dedicated data-access models, hardened by ir.model.access.csv and record rules so Power BI only ever sees the records a service account is permitted to read. Because it respects Odoo's own ORM and security layer, multi-company boundaries and record-level rules that already exist in your Odoo apply automatically to every query Power BI makes.
Out of the gate you get pre-mapped datasets for the domains your executives actually ask about — Sales (orders, order lines, margins, salesperson performance), Inventory (on-hand quantities, valuation, stock moves), Accounting (invoices, payments, aged receivables/payables, journal entries), and CRM (pipeline, stage, expected revenue, win rate). Each dataset arrives with the joins, currency handling, and Odoo-to-Power BI field typing already done, so a Power BI author can drop a table onto a canvas and build a report in minutes instead of reverse-engineering Odoo's schema. Need more than the standard four domains? Custom model and field selection lets ECOSIRE expose any model in your database — including your bespoke modules and studio fields — as a first-class Power BI table.
Refresh works the way Power BI expects. Use DirectQuery-style live pulls for near-real-time operational dashboards, or configure the Power BI Service scheduled refresh (and an on-premises data gateway where your Odoo isn't publicly reachable) for heavier historical models that don't need to be second-fresh. Multi-company and multi-currency are first-class: figures come through with company scoping intact and currency fields carried so you can convert or slice by company in Power BI without guessing which res.company a row belongs to.
The connector is compatible with Odoo 17, 18, and 19 and works on both Community and Enterprise editions — ECOSIRE targets your specific version's __manifest__.py, ORM, and API surface so nothing breaks on your next Odoo upgrade. Security is treated as a feature, not an afterthought: connections authenticate with rotatable API tokens scoped to a dedicated, least-privilege service user, tokens are stored hashed, every pull is auditable, and no analyst ever needs a real Odoo login or database credentials. The result is a governed, IT-approved bridge between your ERP and your BI platform — one that your data team owns, ECOSIRE supports, and Microsoft's tooling treats as a native source.
Standardizing all reporting on Microsoft Power BI and needs Odoo to behave like a governed, first-class data source — not a manual export. Wants pre-mapped datasets, scheduled refresh, and a connection IT will actually approve.
Lives in aged-receivables, margin, and inventory-valuation dashboards. Needs Odoo Accounting, Sales, and Inventory numbers in Power BI daily, correctly scoped by company and currency, without waiting on someone to email a spreadsheet.
Owns database security and the upgrade path. Wants BI access via a least-privilege token and service user — never real logins — with record rules and multi-company boundaries enforced by Odoo itself, and a module that survives the next Odoo upgrade.
Builds the actual reports and is tired of reverse-engineering Odoo's schema. Wants clean, correctly-typed tables with joins already done so they can go from blank canvas to published dashboard the same day.
Buy the license on ecosire.com and download the Power BI Connector for Odoo module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Power BI Connector for Odoo, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Time to first dashboard | 2–4 weeks to a built, installed connector with pre-mapped Sales/Inventory/Accounting/CRM datasets and a starter .pbix | Months of in-house ETL/API work before the first reliable dashboard | Fast to install, but generic mappings mean weeks of your own remodeling to fit your schema | |
| Pre-mapped Odoo datasets | ||||
| Live and scheduled refresh into Power BI | Both live (DirectQuery-style) and Power BI Service scheduled refresh, with gateway support | Whatever you build and maintain yourself | Usually scheduled only; live pulls often limited or unsupported | |
| Security via record rules & least-privilege token | ||||
| Multi-company & multi-currency handling | ||||
| Custom models & Studio fields exposed to Power BI | ||||
| Odoo 17/18/19 + Community & Enterprise upgrade-safety | Version-targeted, manifest-clean, upgrade-friendly module across all three | Breaks on upgrade unless you re-engineer it each time | Depends on the vendor keeping pace with each Odoo release | |
| Ongoing support & ownership | Included support window + optional maintenance; you own the source code | You own it and you alone maintain it — the whole burden is internal | Vendor support varies; you rarely get or control the source |
This is a build-to-order module, not an instant download. After purchase, ECOSIRE runs a short discovery call to confirm your Odoo version (17/18/19), edition, hosting, and which models and custom fields you need. We then build and test the connector, install it on your staging instance first, validate the datasets against your data, and promote to production. Typical lead time is 2–4 weeks depending on how many custom models you want mapped. You get progress checkpoints along the way, and final handover includes installation, the starter .pbix template, documentation, and a training session.
Every build includes a post-deployment support window for bug fixes, connection issues, and questions from your BI team. During that window we also cover version-compatibility adjustments — for example, if a field changes or you move between Odoo 17, 18, and 19. Because the module respects Odoo's ORM and __manifest__.py conventions, it is upgrade-friendly by design. After the initial window, ongoing support and enhancement (new datasets, new models, added companies) is available through a support/maintenance agreement so you are never left with an unmaintained connector.
It works with both. The connector is built on Odoo's standard ORM, JSON-RPC/XML-RPC API, and security layer (ir.model.access.csv and record rules), all of which exist in Community as well as Enterprise. ECOSIRE targets your specific edition and version so the module installs cleanly whichever you run.
No. Power BI connects using a rotatable API token bound to a dedicated, least-privilege service user — not a real employee login or raw database credentials. That user's access is governed by Odoo's own ir.model.access.csv and record rules, so any multi-company boundary or record-level restriction you already enforce in Odoo automatically applies to every Power BI query. Tokens are stored hashed, can be rotated on demand, and pulls are audit-logged so IT can see what was queried and when.
Both. You can configure live DirectQuery-style pulls for operational dashboards that need to be current to the minute, and scheduled refresh in the Power BI Service for larger historical models. When your Odoo instance isn't publicly reachable, we set up the connection to work through an on-premises data gateway so scheduled refresh still runs securely.
Yes. Beyond the pre-mapped Sales, Inventory, Accounting, and CRM datasets, custom model and field selection lets ECOSIRE expose any model in your database — including bespoke modules and Studio-added fields — as a first-class Power BI table, with the correct field typing and joins built in during the engagement.
Stream Odoo Sales, Inventory, Accounting & CRM into Power BI — live or scheduled — with secure token auth and multi-company support.