AI Forecasting Engine
Ensemble AI that picks the right model for every SKU
Demand OS evaluates dozens of statistical and ML model classes per SKU, selects the best-performing method automatically, and logs every choice with its accuracy score.
Book a Demo30+
Model classes evaluated per SKU before selection
Source: Perimattic product benchmark
Week 1
When planners see production-ready model-selected forecasts
Source: Perimattic implementation benchmark
How does demand planning AI software select the right forecasting model?
Demand OS evaluates each SKU against dozens of statistical, machine learning, and specialized model classes — including ARIMA, ETS, Holt-Winters, gradient boosting, and Croston's method for intermittent demand — and selects whichever produces the lowest error on held-out historical data. The selection and its accuracy score are logged for every SKU, so planners can inspect exactly why a given model was chosen. Models are re-evaluated on a configurable schedule, with out-of-cycle retraining triggered if accuracy degrades. The result is forecasting accuracy tuned per SKU instead of one method forced across an entire catalog.
The Problem
Why one model for every SKU always fails
The Capability
How the forecasting engine selects and explains every model
Benchmark Results
What forecasting teams see in the first quarter
20–50%
Reduction in forecast error vs statistical baseline across SKU portfolio
Source: McKinsey & Company
9%
Average reduction in manual override rate when planners can inspect model reasoning
Source: Perimattic product benchmark
34pts
Accuracy improvement on seasonal SKUs when moved from generic to per-SKU model selection
Source: Perimattic customer benchmark
In Practice
A food manufacturer cuts forecast error by 34 points on seasonal SKUs
The Situation
A food and beverage manufacturer with 2,400 SKUs was running a single exponential smoothing model across the entire catalog. Seasonal ranges, promotional products, and slow-moving long-tail items were all treated identically. Forecast accuracy on seasonal SKUs was 58% — well below the 75% planning target. The team was manually overriding 30% of all SKUs every Monday.
What Demand OS Did
The AI Forecasting Engine evaluated each of the 2,400 SKUs independently, testing ARIMA, ETS, Holt-Winters, gradient boosting, and Croston's method. Seasonal SKUs were assigned ETS or Holt-Winters based on historical pattern scoring. Promotional SKUs received gradient boosting models trained on event history. Slow-moving long-tail items were assigned Croston's method. All model selections were logged with accuracy scores visible to planners.
The Outcome
Forecast accuracy on seasonal SKUs improved to 92% in the first quarter — a 34-point improvement. The manual override rate dropped from 30% to 8%. The planning team stopped spending Monday mornings correcting the baseline and started reviewing the exception queue instead.
Explore more Demand OS capabilities
Demand OS for Manufacturing
BOM-level disaggregation and intermittent spare-parts demand handling.
Learn moreDemand OS for Retail
Seasonal forecasting, promotional lift modeling, and store-level replenishment.
Learn moreDemand OS vs Blue Yonder
Faster implementation and explainable AI, compared to Blue Yonder's 12–24 month rollouts.
Learn moreCompare AI forecasting approaches across leading vendors in our guide to the 5 best AI-powered demand forecasting tools.
Frequently Asked Questions
AI forecasting questions answered
How does Demand OS decide which model to use for each SKU?+
How does the engine handle new products with no historical data?+
Can planners override model selections?+
How often are models retrained?+
Does the engine handle intermittent demand on spare parts and MRO items?+
Get Started
Ready to plan with confidence?
Talk to a demand planning specialist and see the AI forecasting engine live on your own SKUs. You leave with accuracy benchmarks, a scoped pilot plan, and published pricing — all in one call.