Engineering an Azure Data Layer for Odoo Analytics Without Changing the ERP

One thing I have learned from working on ERP-driven data projects is that the ERP is rarely the place where you want to solve every analytics problem.

We saw this firsthand in a manufacturing engagement where Odoo was being used across finance, inventory, procurement, and manufacturing, but reporting still involved substantial manual extraction and Excel-based consolidation.

The interesting engineering question wasn't “How do we replace the ERP?” It was:

“How do we build a reliable analytical layer around it without changing the transactional system?”

That shaped the architecture.

We used Odoo APIs and Azure Data Factory for ingestion, landing the data in Azure Data Lake Storage Gen2.

From there, the data was organized into Bronze, Silver, and Gold layers:

Bronze: Source-aligned Odoo data was retained with minimal transformation.

Silver: Data was cleansed, standardized, and prepared across finance, inventory, procurement, and manufacturing domains.

Gold: Analytics-ready data was prepared for downstream reporting and consumption.

Azure Databricks with Spark handled transformation and KPI standardization, while Synapse/SQL layers provided structured analytical models for reporting. Power BI datasets consumed the prepared data, with Row-Level Security applied for role-based access.

Why did this separation matter for the project?

The important architectural boundary was:

Odoo → transactional operations

Azure data platform → ingestion, storage, transformation, standardization

Power BI → analytical consumption

That separation meant the reporting layer did not have to repeatedly extract and reshape data directly from the ERP. It also gave us a dedicated place to handle historical data and standardize information across business domains before it reached the reporting layer.

What changed?

The implementation automated 15+ Odoo-based reports and provided governed Power BI dashboards to 60+ business users. More importantly, teams moved away from repeated ERP extraction and spreadsheet consolidation toward a reusable analytical data layer.

For our team, the bigger takeaway was that ERP modernization does not necessarily mean modifying the ERP.

For teams building Azure data platforms around ERP systems, how are you drawing the boundary between API ingestion, historical storage, transformation, and analytical modeling?