Intermittent Demand
Intermittent demand series contain many zero observations and occasional positive demand. They are common in spare parts, slow-moving inventory, maintenance events, and low-frequency service requests. Ordinary forecasting methods struggle because the timing of nonzero events and their sizes are both uncertain.
Why ordinary methods struggle
Moving averages and smooth regression models often predict small positive values in every period. This can look reasonable under squared error but fail operationally if decisions require stock availability for rare bursts. Percentage errors such as MAPE are unstable or undefined when actual demand is zero.
Zeros can mean no demand, no exposure, stockout, missing measurement, or not-yet-launched status. These meanings must be separated before modeling.
Croston-style methods
Croston’s method decomposes intermittent demand into two processes:
- The size of nonzero demand.
- The interval between nonzero demand events.
The forecast is based on estimated nonzero size divided by estimated interval. Bias-adjusted variants modify the original estimator because it can overforecast under some demand processes.
Croston-style methods are useful baselines for slow-moving items, but they usually do not use rich covariates or metadata.
Worked example
Take a 10-period series with demand in only three periods:
The nonzero sizes are and the intervals between successive demand events (counting from the series start) are . Croston smooths each stream separately; using simple means for illustration,
The per-period rate matches the long-run average ( units over periods), but the decomposition is the point: Croston represents demand as “about 4 units every 3.3 periods,” so it updates correctly when either the typical size or the arrival frequency changes. A moving average would instead predict a small positive value in every period, including the many periods where the true demand is zero. The Syntetos-Boylan variant multiplies by to remove the known upward bias, giving at smoothing constant .
Aggregate-disaggregate methods
Aggregate-disaggregate approaches such as ADIDA aggregate demand to a coarser frequency, forecast the aggregated series, and disaggregate the forecast back to the required frequency. Aggregation reduces sparsity and can make patterns more stable, but disaggregation introduces assumptions about within-period allocation.
Evaluation
Intermittent demand often requires WAPE, MASE, aggregated errors, range-normalized errors, or business-weighted metrics. Metric denominator behavior must be explicit. Bias should be monitored because systematic overforecasting can inflate inventory, while underforecasting can reduce service levels.
Practical guidance
- Diagnose whether zeros are true demand zeros, missing observations, no exposure, or stockouts.
- Use seasonal naive, Croston-style, and aggregate-disaggregate baselines.
- Avoid MAPE when zeros are common.
- Evaluate over meaningful aggregation windows as well as point timestamps.
- Use category-level or metadata-based fallback for cold-start sparse items.
Common failure modes
- Treating all zeros as equivalent.
- Optimizing RMSE and producing small positive forecasts every period.
- Using pointwise percentage metrics with zero actuals.
- Ignoring stockout censoring.
- Evaluating only high-volume items and missing sparse-series behavior.
Connections
Intermittent demand is a special case of demand forecasting where zeros are structural. It often needs statistical forecasting methods designed for sparse counts, cold-start forecasting fallbacks, and metrics from forecast-error metrics.
References
- Hyndman & Athanasopoulos, FPP3: Time series of counts
- Nixtla StatsForecast intermittent-demand model index
Nav