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.

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.