Power BI & CPG reporting examples
Go beyond the graph.
Find the next decision.
Explore a genuine public Power BI report, then work through four CPG reporting scenarios that connect sales, assortment, inventory and costs.
An actual Power BI experience
Explore the public report.
The existing owner-approved demonstration runs in Microsoft Power BI. Use its available filters and report controls to explore the actual report.
CPG Dashboards / public Power BI report
Load the interactive report from Microsoft, or open it in a separate tab. Loading sends a request to Microsoft.
Genuine public Power BI report. Open the full report in a new tab · External-content privacy
An interactive reporting walkthrough
Four decisions.
The same connected data.
These interactive HTML examples use fictional Grove Beverage data. They demonstrate reporting logic and business decisions; they are not Power BI reports or client results.
Period: 4 illustrative weeksComparable prior 4 weeks · Snapshot data
| Account | Current cases | Prior cases | Change |
|---|---|---|---|
| 64 | 60 | +4 | |
| 32 | 32 | +0 | |
| 24 | 24 | +0 | |
| 56 | 48 | +8 | |
| 40 | 40 | +0 | |
| 20 | 20 | +0 |
Is demand changing, or is ordering changing?
Compare depletion patterns by account and product, then check stock and shipment timing. Depletions are not consumer POS; this velocity uses active accounts and four weeks, not store-level selling weeks.
Source joins, definitions and limits
One agreed grain
Sales and eligibility: account × SKU. Stock and shipments: region × SKU. Costs: SKU. Measures preserve each grain; stock is never duplicated across account rows.
A clear definition
Depletion velocity = cases ÷ (active accounts × 4 weeks). CanBuy = eligible account-SKU pair with zero current-period cases. Cover = available cases ÷ average weekly depletions.
Traceable, not automatic
Source and canonical identifiers are explicit. Ambiguous matches need review. In real delivery, refresh dates, coverage, reconciliation and exception ownership are visible alongside the model.
Take the model into Power BI
A synthetic starter dataset, with the measures explained.
Download CSV tables, a relationship guide and example DAX. Build the four report pages in Power BI Desktop using the same illustrative data. This is a starter kit, not a finished PBIX report.
One business. Many sources.
Different files.
One trusted business view.
Distributor depletions, retailer sales, authorized assortment, inventory and cost files each tell part of the story. The value comes from connecting them without losing what each number means.
Distributor & retailDepletions, POS and account activity
Assortment & account listsWhich account can buy which SKU
ERP & inventoryShipments, on-hand and allocations
Costs & tradeProduct cost, discounts and freight
A shared reporting model
- Normalize dates, units and file formats.
- Match account and SKU identifiers.
- Reconcile totals; isolate unmatched records.
- Agree measures, freshness and ownership.
Where is velocity changing?
Which eligible accounts are not buying?
Is stock available for the next sale?
What remains after trade and freight?
RIVER MKT 101 + RM-MARIETTA
One account: River Market — Marietta / A101
CIT-12OZ-12 + GRV-CIT
One SKU: CIT12 / 480 units = 40 twelve-unit cases
Fictional identifiers. A new or ambiguous match goes to an exceptions review; it is never silently guessed. Shipment and depletion facts remain separate to avoid double counting.
Sources may include authorized KeHE, UNFI, VIP, retailer, direct-sales or ERP exports. Formats, licensing, permissions and available integrations are assessed individually; no universal connector or real-time refresh is assumed.
Your data. Your decisions.
What would one trusted view unlock?
Start with your sources and the decisions your team needs to make.