Supply chain snowflake schema
This supply chain snowflake schema stores shipment measures in FactShipment. Each shipment links to a date, product, warehouse and carrier, then records units shipped and freight cost. Product rolls into category and department. Warehouse rolls into city and region. Those normalized hierarchies let operations teams analyse volume and cost by product department, carrier or warehouse region while maintaining common hierarchy values in one place. It is a useful pattern when logistics reporting combines transactional shipment data with shared master-data structures. It supports common rollups even when warehouse and product master data are maintained by different operational teams. Shared dimensions also improve comparisons across sites, carriers and product portfolios over time.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Shipment reporting
Key decisions
- Shipment grain: Store one row per shipment.
- Product hierarchy: Separate category and department.
- Warehouse geography: Normalize warehouse location through city and region.
When to reuse this
Use this when shipment measures need consistent product and location rollups.
Frequently asked questions
What does FactShipment measure?
Why use a carrier dimension?
Where is warehouse geography stored?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.