ForecastingInventoryD2CFMCGDemand PlanningIndiaOperations

Why Forecasting Failure Leads to Inventory Disaster

Bad forecasts do not just produce wrong inventory numbers. They produce the cash traps, the stockouts, the dead stock write-offs, and the missed seasonal windows that determine whether a brand has the working capital to keep growing or runs into a wall it did not see coming.

Aditya Sharma

Author

23-04-2026
9 min read
Why Forecasting Failure Leads to Inventory Disaster

Demand forecasting is the most consequential and least invested analytical function in most Indian D2C and FMCG businesses. It is consequential because every production, procurement, and cash flow decision downstream depends on the accuracy of the demand estimate. It is under-invested because the consequences of bad forecasts arrive 6 to 12 weeks after the forecast is made long enough after the decision that the causal connection between the forecast error and the inventory crisis is rarely made explicit. The founder who ordered too much inventory for a seasonal peak because the forecast was optimistic experiences the cash crunch when the overstock sits unsold for three months after the season ends not as a forecasting failure, but as an inventory problem, a cash flow problem, or a sales shortfall. The diagnosis that would prevent the recurrence the forecast methodology was wrong is never reached because the problem was diagnosed at the symptom level rather than the root cause level.

01

The Three Most Common Forecasting Failures

Failure 1: Using last period's sales as next period's forecast

The simplest and most common forecasting method is extrapolation from the most recent period if the brand sold 800 units last month, the forecast for next month is 800 units with a growth adjustment. This method ignores trend direction changes (a SKU decelerating from 40% month-over-month growth to 15% growth will be significantly over-forecast by an extrapolation model), seasonal patterns (last month's sales in March do not predict April's sales for a product with summer seasonality), and channel mix shifts (the same total volume can be distributed very differently across channels with very different margin and fulfilment implications). The production decision made on this forecast will be wrong in ways that compound: the wrong total quantity, at the wrong channel mix, at the wrong timing.

Failure 2: Conflating primary sales with consumer demand

For brands with distribution through trade channels, the sales figure in the OMS or ERP represents shipments to distributors and retailers not sales to end consumers. When the distribution pipeline is filling (as it does during new product launches or market expansion), primary sales overstate true consumer demand. When the pipeline is draining (as it does when distributors reduce inventory ahead of a new packaging launch or due to cash flow constraints), primary sales understate consumer demand. Forecasting from primary sales in either situation produces a forecast that is structurally wrong and the production decisions based on it will be wrong by the same magnitude.

Failure 3: Ignoring the forecast horizon vs lead time relationship

The forecast horizon how far ahead the forecast is made must be at least as long as the production and distribution lead time for the forecast to be useful. A brand with a 45-day production lead time needs a demand forecast that is accurate 45 days out. Most demand planning models are most accurate in the short term (next 7 to 14 days) and least accurate at longer horizons. The specific planning failure: making production decisions based on a 60-day forecast that has wide confidence intervals, treating the point estimate as if it were precise, and placing production runs that are sized for the point estimate rather than for the uncertainty range around it.

02

Building a Forecasting System That Reduces Inventory Disasters

A reliable demand forecasting system for a D2C or FMCG brand at ₹30 to ₹2 crore monthly revenue does not require machine learning or a data science team. It requires three components applied consistently. A rolling velocity baseline: the trailing 21-day weighted average of daily sell-through units by SKU by channel, with higher weight on more recent days, updated weekly. This baseline captures the current demand trend without over-weighting the most recent day's variance. A seasonality adjustment layer: for each SKU, a set of monthly or weekly demand indices derived from the last two years of sell-through history that adjusts the rolling baseline for known seasonal patterns. A product without sufficient history uses category-level seasonality indices as a proxy.A forecast confidence range rather than a point estimate: rather than forecasting 840 units for next month, the forecast produces a range of 720 to 960 units with a 75% confidence level. Production decisions are made against this range the production run is sized for the 60th percentile of the range (not the optimistic end) with explicit safety stock calculated to protect against the difference between the 60th and 90th percentile. This approach produces production runs that are slightly more conservative than pure optimism but significantly less likely to result in both overstock and stockout the twin costs that bad point-estimate forecasting generates alternately.

03

The Forecast Accuracy Tracking That Prevents Recurrence

  • Calculate forecast accuracy monthly for every SKU: (1 - |actual units sold - forecast units| / forecast units) × 100 = forecast accuracy percentage
  • Track MAPE (Mean Absolute Percentage Error) by SKU category categories with consistently high MAPE require either a different forecasting methodology or a higher safety stock buffer to compensate for forecast uncertainty
  • Review the three largest forecast errors each month and identify the root cause: was it a demand signal that was not in the model (new competitor, viral social content), a supply event that distorted the sales pattern, or a model assumption that was structurally wrong?
  • Adjust the safety stock formula for high-MAPE SKUs a SKU with 35% average MAPE requires 35% more safety stock than a SKU with 10% MAPE to achieve the same service level target