New guide: assessing organisational readiness for Microsoft 365 Copilot. Read the guide

Multi-Entity Retail Group ยท Retail and Consumer

A single reporting model for a multi-entity retail group

Several operating entities moved from separate extracts to one governed semantic model with owned definitions.

18 February 2026 Retail and Consumer

Technologies

  • Microsoft Fabric
  • Power BI
  • Azure Data Factory
  • Microsoft Purview
  • Microsoft Azure

Outcome themes

  • Agreed definitions
  • Traceable figures
  • Less manual preparation

Client context

A retail group operates several entities acquired at different times, each with its own point-of-sale and finance systems. Group reporting is assembled monthly by consolidating extracts, and management meetings begin by reconciling differences between entity figures.

The challenge

Each entity defines core measures slightly differently, and the differences are legitimate in local context. A single definition imposed centrally would be inaccurate for local operations. The group needs comparable figures without invalidating local reporting, and needs to trace any figure back to source.

Objectives

  • Comparable group figures without invalidating local reporting
  • Named owners and written definitions for core measures
  • Lineage from any published figure back to source
  • Reduced manual effort in monthly pack preparation
  • Row-level security aligned to entity and role

The solution

Core measures are defined at group level with named owners and written definitions, and entity-specific variants are modelled explicitly rather than hidden. Source data lands in Microsoft Fabric through a medallion structure, with conformed dimensions built at the silver layer. One shared semantic model serves group and entity reporting, with row-level security aligned to entity and role. Lineage is published through Microsoft Purview so any figure can be traced. Definition changes follow a change process with dependent report identification.

Architecture

  • Microsoft Fabric lakehouse with bronze, silver and gold layers
  • Azure Data Factory pipelines for entity source ingestion on agreed schedules
  • Conformed dimensions for product, location, calendar and customer at the silver layer
  • Shared Power BI semantic model with row-level security by entity and role
  • Microsoft Purview for catalogue, lineage and definition documentation
  • Change process for measure definitions with dependency analysis before release

Delivery approach

How the work ran

  1. Define

    Workshops with entity and group finance to agree measures, owners and legitimate variants.

    Measure catalogue Ownership register Variant analysis
  2. Architect

    Lakehouse structure, ingestion patterns, conformed dimensions and security model.

    Data architecture Security model Ingestion design
  3. Build

    Pipelines, conformed dimensions, semantic model and certified reports built iteratively by subject area.

    Pipelines Semantic model Certified reports
  4. Validate

    Reconciliation against existing entity reporting, with differences explained rather than adjusted away.

    Reconciliation evidence Difference log Sign-off
  5. Operate

    Definition change process, capacity governance and usage-based report retirement.

    Change process Capacity plan Usage reporting

Outcomes

What changed

Agreed definitions with owners

Each core measure has a written definition and a named business owner.

Traceable figures

Published figures can be traced to source through documented lineage.

Less manual preparation

Monthly packs are generated from the model rather than assembled from extracts.

Local reporting preserved

Legitimate entity variants are modelled explicitly instead of being overridden.

Lessons learned

What we would tell the next organisation

Every engagement produces something worth carrying forward. These are the points that mattered most in this one.

  • Reconciliation differences should be explained, not adjusted. The explanation is where the definition work actually happens.
  • Fabric capacity governance needs to exist before month-end contention makes it urgent.
  • Entities accept group definitions when their local variants remain visible and supported.

More customer stories

Next step

Start with the problem, not the platform

The first conversation is about what is not working today. Product selection comes later, and sometimes the answer is that you do not need a new one.

Talk to an expert Solutions