Supply chain Data engAnalyticsML retailmarketplace Working capital −14%

Demand forecast + reorder

4 people · 7 months Data engineer · Forecasting specialist · Analytics engineer · Me — architecture and delivery
the engagement client data — not shown
heard
"We are out of stock on the things that sell and sitting on a warehouse of the things that do not."
real problem

Forecasting was a spreadsheet of last year plus a growth factor. Reorder points were static, so service level and stock cover were both wrong in opposite directions across the range.

system built

A hierarchical forecast at SKU-location-week with reconciliation up to category, a reorder policy that takes lead-time variance seriously, and a weekly run that writes suggested purchase orders for the planners to approve.

what broke

Promotions were not in the feature set, so the forecast missed every uplift. The promo calendar became a first-class input and a data dependency the business had to own.

the open rebuild same architecture · public data
dataset

M5 Forecasting — Accuracy (Walmart, 42k series)

what the rebuild covers

Hierarchical forecast with reconciliation, plus the inventory policy simulator that turns forecast error into a working-capital number.

artifacts
NotebookCodeDatasetWrite-upDemo
Open the code Open notebook