E-commerce & Retail
One GMV. Peak-week blast radius before standup.
Shopify (or your storefront), Fivetran, dbt, and Airflow on one graph, so marketing and finance report the same GMV.
Peak season turns small pipeline issues into revenue surprises. Marketing and finance report different GMV because attribution lives in spreadsheets and DAG failures go unnoticed until Monday standup.
Company Brain links storefront ingest, fct_orders, and exec dashboards in one graph. Promo math is named. Oversell is an exception with an owner. The agent sees the real order.
This page is for merch, growth, ops, and finance who have to survive the next peak on the same number.
Company Brain is order, inventory, and margin on one grain. SKU, order, and customer share IDs. Promo math is named. The agent sees the real order.
Marketing and finance stop bringing two GMV books. Peak failures surface before standup. CX does not invent a shipment the warehouse cannot see.
Attribution lives in the graph, not a seasonal spreadsheet.
Inventory and ads should not discover fill issues after the window.
Channel mix experiments stop fighting over which GMV is real. Name the stacking rules.
ATP, reserve, and in-transit sit on the SKU. Oversell is an exception with an owner.
Chat sits on Company Brain. No second story in Zendesk.
If Finance remaps channels every month, the grain is wrong.
No rip-and-replace. Metadata only.
Stacking, exclusions, and channel rules live in the graph. The Friday spreadsheet retires.
Replay and re-verify with lineage.
New channels inherit SKU, order, and customer. Then they may claim GMV.
The sector playbook plus two articles before the next peak.
One GMV. Peak-week blast radius before standup.