Supply Chain Snowflake Schema

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.

類型 ERD標準 Chen 1976 / Everest 1976 (crow's foot)引擎 schematex-erd更新時間 2026/9/24

需求

“A supply chain snowflake schema: FactShipment linked to Date, Product, Warehouse, and Carrier; normalize Product through Category to Department and Warehouse through City to Region.”

接著試試Add a customer dimension to shipmentsAdd a carrier service-level table

這張圖裡有什麼

看懂背後的決策。

01Shipment grain

Store one row per shipment.

02Product hierarchy

Separate category and department.

03Warehouse geography

Normalize warehouse location through city and region.

Use this when shipment measures need consistent product and location rollups.

瀏覽所有 ERD 範本 →

常見問題

What does FactShipment measure?

It records shipment units and freight cost at the shipment grain.

Why use a carrier dimension?

It enables shipment measures to be grouped by carrier.

Where is warehouse geography stored?

Warehouse links to City, which links to Region.