Forecast (Demand Planning)
A forecast (demand planning) is a data-driven prediction of a company’s future sales – usually per item, channel and period – that serves as the basis for procurement, production, inventory disposition and financial planning.
A forecast (demand planning) is the systematic, data-driven prediction of future sales – that is, which quantities of an item or product group are expected to sell in a given period, channel and market. It translates historical sales data, trends and additional knowledge into a planned figure that purchasing, production, inventory disposition and financial planning use as a shared expectation.
The forecast answers the central steering question „How much will we likely sell?“ and thereby makes plannable the business decisions that would otherwise rest on gut feeling: How much stock must be procured, which capacities are needed, how high will expected revenue be? Good demand planning simultaneously reduces two expensive risks – stockouts with lost revenue on the one hand, and excess stock with tied-up capital on the other.
At a glance
- Prediction of future sales per item, channel and period
- Basis: historical sales data plus trends, seasonality and additional knowledge
- Steers procurement, production, inventory and revenue planning
- Goal: fewer stockouts and excess stock, higher service level
- In the ERP usually calculable automatically from transaction data
How does a forecast work?
The starting point of any demand planning is the historical transaction data – completed sales, orders and consumption over a sufficiently long period. From this time series a forecasting method derives the expected future by recognising recurring patterns: a base trend, seasonal curves and random fluctuations. The result is a planned value per item and period, usually supplemented by a range or margin of variation.
A rough distinction is drawn between quantitative and qualitative methods. Quantitative techniques compute purely on the numbers – from simple moving averages through exponential smoothing to seasonal models and machine-learning approaches. Qualitative methods bring in human additional knowledge, such as sales assessments, planned promotions, market entries or competitor moves. In practice the combination is strongest: the statistical model provides the baseline, and the departments correct it where history does not explain the future.
Components of a demand plan
A forecast is typically composed of several components: the base value from the time-series analysis, a seasonal and trend share, planned special events such as campaigns or price changes, and manual adjustments by the planners. The right granularity is crucial – too fine (each item per day) makes the forecast unstable, too coarse (only total revenue per year) loses its steering value. Common practice is planning per item or product group at weekly or monthly level.
Measuring forecast accuracy
A forecast is only as good as its subsequent review. To measure hit rate, metrics such as the forecast error, the MAPE (mean absolute percentage error) or the bias, which reveals a systematic over- or under-estimation, are used. Anyone who regularly compares planned and actual values recognises which items are easy to plan and where the model needs sharpening – a cycle of forecast, reconciliation and correction.
Why the forecast (demand planning) matters
The forecast is the bridge between past and future and thus the pacemaker of many downstream processes. Without reliable demand planning, purchasing procures reactively, production plans imprecisely and finance estimates revenue flying blind. With it, a shared numerical basis emerges that all areas align to.
The economic lever lies in inventory: too little stock leads to shortages, inability to deliver and lost revenue; too much ties up capital, occupies warehouse space and risks scrapping or write-downs. The forecast helps size the safety stock and order quantities so that the service level stays high without tying up capital unnecessarily. In production it steers capacity and material planning, in sales it forms the basis for revenue and commission targets. In this way demand planning connects operational disposition and strategic financial planning.
Forecast in the ERP system
A merchandise management or ERP system holds exactly the data that demand planning needs: sales history, item master, open orders and stock. That is why the forecast is well placed there – many systems calculate it automatically from the transaction data and present it in dashboards and reports. From the planned value, order proposals, minimum and reorder levels as well as disposition parameters are then derived directly.
Technically, the range spans from simple reorder-point logic to integrated requirements planning. In systems with material requirements planning, the demand forecast feeds into the MRP calculation as primary demand, which generates procurement and production proposals from it. For deeper analyses, the data often moves into a data warehouse or business intelligence tool that processes larger data volumes, multiple channels and more complex models. Data quality remains decisive: only cleansed, complete sales data delivers a reliable forecast.
Rolling planning
Instead of drawing up a rigid plan once a year, many businesses work with a rolling forecast: the planning horizon is shifted forward by one period at fixed intervals – monthly, for example – and updated with the latest actual figures. This keeps demand planning always current and responsive to demand changes, rather than chasing an outdated annual figure.
Distinction: forecast vs. budget and requirements planning
Forecast, budget and requirements planning are often confused but mean different things. A budget is a target – the desired, usually year-start fixed nominal figure. A forecast, by contrast, is the current expectation of how sales will actually develop; it is continuously updated and may well deviate from the budget. Put simply: the budget says what you want to achieve, the forecast what you will likely achieve.
Requirements planning (demand planning in the narrower sense) goes one step further than the pure sales forecast. The sales forecast predicts sales in the market; requirements planning translates this into the concrete material demand across bills of materials and lead times – that is, what, when and in which quantity must be procured or manufactured. The forecast is thus the input, requirements planning the downstream procedure. Also related is the XYZ analysis, which classifies items by the predictability of their demand and thereby shows where a statistical forecast works reliably at all.
Limits and practice in the DACH mid-market
Every forecast is an assumption about the future and therefore prone to error – the question is not whether it deviates, but how strongly. Structural breaks such as new products without history, supply shortages, price shocks or exceptional events can hardly be derived from past data and must be planned in manually. Excessive detail also does harm: anyone forecasting every small item to the day creates false precision and a lot of maintenance effort.
In the DACH mid-market, practice ranges from the spreadsheet to integrated planning in the ERP. Common pitfalls are uncleansed histories – such as promotion spikes not flagged as special cases, or shortages that mask true demand. A pragmatic path has proven itself: a statistical baseline forecast in the system, supplemented by the market knowledge of sales, combined with differentiated control by value (ABC) and predictability (XYZ). This way, the planning effort concentrates on the items where it has the greatest leverage on service level and tied-up capital.
Example
Rolling forecast at an online retailer
A mid-sized e-commerce retailer sells household goods through its own shop and several marketplaces. Until now, purchasing reordered from experience – with the result that seasonal items were regularly sold out in summer, while slow movers clogged the warehouse. The company introduces a monthly rolling forecast in the ERP that calculates trend and seasonality from 24 months of sales history per item and channel.
Sales adds planned campaigns and a marketplace relaunch manually. From the planned value, the system automatically generates order proposals and adjusts the reorder levels seasonally. After two quarters, the stockout rate of the A-items falls significantly, while the average stock level of the slow-moving items goes down – tied-up capital drops without service level suffering.
Frequently asked questions
Matching ERP systems
Related services
Questions about Forecast (Demand Planning) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.