Feature pipeline
dbt models over sales, promotions, price changes, stockouts and calendar effects. Stockouts are masked rather than read as zero demand, or the model learns to under-forecast the SKUs that matter most.
SKU-level forecasts delivered where purchase orders are written, with published back-tests.
Reference engagements illustrate how Elicon would approach a project of this kind — the problem, the architecture and the decisions. They are examples, not accounts of past client work.
THE SITUATION
A retailer that forecasts demand by putting last year's sales next to a gut-feel column. The engagement builds a SKU-level forecasting pipeline with hierarchical reconciliation, delivers reorder suggestions into the warehouse system where buyers already work, and publishes back-tests so the team knows when to trust it.
Manual forecasting causes stockouts at peaks and write-downs in lulls.
APPROACH
ARCHITECTURE
dbt models over sales, promotions, price changes, stockouts and calendar effects. Stockouts are masked rather than read as zero demand, or the model learns to under-forecast the SKUs that matter most.
A statistical baseline for seasonal, well-behaved SKUs and a neural model for the intermittent long tail, selected per SKU by back-tested accuracy.
Reorder suggestions written into the warehouse system with the forecast, confidence interval and reasoning attached. Buyers accept, edit or reject where they already work.
DECISIONS
Zero sales during a stockout is censored data, not low demand — the most common way retail forecasting quietly fails.
TRADE-OFFLess usable history for the SKUs that stock out most.
Periods of one-off behaviour teach a model patterns that will not recur.
TRADE-OFFGaps in history and weaker long-horizon seasonality for some categories, documented so nobody rediscovers it as a bug.
Adoption is a delivery problem. A better forecast that lives somewhere buyers don't go changes nothing.
TRADE-OFFIntegration is fiddlier than a standalone app.
STACK
Work of this shape usually runs as AI Product Launch →
SIMILAR PROBLEM?
One conversation with an engineer is usually enough to tell whether this is a few weeks of work, a few months, or something you shouldn't build at all.
Talk to an engineer →