Home appliance online store — Online retail
One page that replaced seven reports
Every department produced its own report and the numbers disagreed. We wrote one definition per metric and moved everything onto a single source.
- Year
- 2024
- Industry
- Online retail
01Challenge
The weekly management meeting usually began by arguing about whether the numbers were right. Sales gave one figure, finance another. Neither was lying — they had simply defined "revenue" differently.
02Analysis
- 01Where the disagreement came fromThree parallel definitions of a "successful order" existed, differing in how they treated returns and cancellations.
- 02Reports nobody readOf seven weekly reports, only two ever informed a decision. The rest were produced out of habit.
- 03Data latencyData refreshed overnight, so every morning decision was made on yesterday’s picture.
03Solution architecture
01 — Solution architecture
Sources
- Storefront
- Payment gateway
- Warehouse
- Support
02 — Solution architecture
Transfer
- Scheduled ETL
- Validation
- Source health checks
03 — Solution architecture
Model
- Metric dictionary
- Aggregate tables
04 — Solution architecture
Consumption
- Management dashboard
- Ops dashboard
- Deviation alerts
04Results
- Weekly report preparationabout 6 hoursautomatic
- Definitions of "revenue"31
- Data freshnessovernightevery 15 minutes
- Reports retired7 reports2 dashboards
ToolsPostgreSQLMetabasePython ETLSlack alerts
Next step
Does your project look like this?
If any part of that story felt familiar, we can probably help.