Skip to main content
Back to Projects
CompleteFlagship project

Azure Retail Data Pipeline

A 300K-order Azure pipeline from Data Factory and Azure SQL to Power BI

Azure Data FactoryAzure SQLPythonSQLPower BIDAXETL / ELT
300K
Orders
50K
Customers
10K
Products
4
Analytical Views

Project overview

The pipeline covers 50,000 customers, 10,000 products, 300,000 orders, 100 stores, 200 suppliers, 30 categories, and 50 promotions. It uses Python and SQL for transformation, Azure Data Factory for orchestration, Azure SQL for relational modeling and analytical views, and Power BI for revenue, order volume, average order value, margin, store, and customer reporting.

The problem

Large retail datasets become useful only when ingestion, relational modeling, analytical logic, and reporting are connected into a repeatable pipeline.

The approach

Built a cloud flow from structured source data through Azure Data Factory and Azure SQL into reusable analytical views and Power BI reporting.

Implemented systems

  • Structured ingestion and transformation across customers, products, orders, stores, suppliers, categories, and promotions
  • Azure Data Factory orchestration feeding a relational Azure SQL Database design
  • Analytical views: vSalesByMonth, vTopProducts, vCustomerCohorts, and vStorePerformance
  • Power BI KPIs for revenue, order volume, average order value, margin, stores, and customer trends
  • Python, pandas, SQLAlchemy, and SQL across validation, transformation, loading, and analysis

System flow

A simplified view of the major system boundaries
  1. Source Data
    Retail
  2. Azure Data Factory
    Orchestrate
  3. Azure SQL
    Model
  4. Analytical Views
    Semantic
  5. Power BI
    Decisions

Architecture

01.Source data: customers, products, orders, stores, suppliers, categories, and promotions
02.Orchestration: Azure Data Factory manages ingestion and movement
03.Transformation: Python, pandas, SQLAlchemy, and SQL prepare and validate data
04.Storage: Azure SQL Database provides the relational analytics model
05.Semantic layer: vSalesByMonth, vTopProducts, vCustomerCohorts, and vStorePerformance
06.Reporting: Power BI and DAX deliver KPIs and interactive analysis

Engineering challenges

1

Maintaining relationships and load order across high-volume retail entities

2

Designing views for recurring KPI reporting and deeper analysis

3

Keeping orchestration, transformation, storage, and BI responsibilities separated

Current state

  • The pipeline covers ingestion, transformation, relational storage, analytical views, and visualization
  • The modeled dataset includes 300,000 orders, 50,000 customers, and 10,000 products
  • Power BI surfaces commercial, store, product, and customer performance measures

Continue exploring