Forecasting vs Demand Planning: What They Are, How They Differ & How They Work Together

What Is Forecasting?

Forecasting is the quantitative process of using historical demand data — time series of shipments, sales, or consumption — and mathematical models to project future demand over a planning horizon. It is a statistical discipline, concerned with pattern recognition: detecting and extrapolating trends, seasonal cycles, and underlying signals from noisy data.

Forecasting is systematic and reproducible: given the same data and the same model, two people running the same algorithm will produce the same output. This repeatability is its strength — and also its limitation. A statistical model knows only what the historical data can tell it. It cannot anticipate a product discontinuation, a competitor recall, a promotional campaign, or a market disruption that has not happened before.

The role of the statistical forecast

In a mature demand planning process, the statistical forecast is the starting point — not the finished product. It provides the evidence-based baseline that commercial and market intelligence is layered on top of. Its role is to remove the unconscious biases that come from purely judgemental forecasting: the salesperson who always under-forecasts to ensure they beat target; the marketing team that over-forecasts promotional uplift; the operations manager who over-forecasts to guarantee supply availability.

What forecasting does not do

• It does not incorporate promotional plans, pricing changes, or new product launches unless these are modelled explicitly as causal variables
• It does not resolve conflicts between what sales wants, what operations can supply, and what finance expects
• It does not produce a plan — it produces a number. A plan requires decisions, owners, and accountability
• It does not improve supply chain performance by itself — only when it is acted upon through a formal demand planning process

What Is Demand Planning?

Demand planning is the end-to-end business process through which an organisation arrives at a single, credible forecast of future demand — the consensus demand plan — and translates it into supply chain instructions. It encompasses data collection, statistical modeling, commercial review, cross-functional consensus building, and handoff to supply planning.

Demand planning is as much an organisational process as it is an analytical one. Its output — the consensus demand plan — is meaningful only because every function has committed to it. An accurate forecast that no one acts on has no value. A somewhat imprecise forecast that everyone plans from produces better supply chain outcomes than a theoretically perfect forecast that sales, operations, and finance each override independently.

Demand planning scope

Key Differences: Forecast vs Demand Planning

The Demand Planning Process

A mature demand planning process follows a structured monthly cycle, aligned with the broader S&OP rhythm. Each step has defined inputs, responsible parties, and outputs.

Step 1: Data Collection and Cleansing

Before any forecasting model can run, demand history must be cleansed. Raw shipment history contains events that should not be extrapolated — promotional spikes, one-off bulk orders, stockout-impacted periods where actual demand was higher than recorded shipments, prior forecast errors propagated through the supply chain. Demand history cleaning is one of the highest-value activities in demand planning and one of the most consistently under-invested.

• Remove or adjust promotional events (flag known promotions; adjust the baseline)
• Identify and correct for stockout-impacted periods (demand was censored by supply unavailability)
• Manage new product introductions and end-of-life transitions thoughtfully — do not extrapolate launch ramp or phase-out decline as steady state
• Correct for master data changes: pack size changes, unit-of-measure reclassifications, customer realignments

Step 2: Statistical Baseline Generation

The cleansed demand history is fed into the forecasting engine to generate a statistical baseline. The choice of statistical method should be driven by the demand pattern actually present in the data:

• Stable products: Simple or weighted exponential smoothing (SES/WES) or Simple Exponential Smoothing with dampening
• Trending products: Double exponential smoothing (Holt's method) or Trend-adjusted exponential smoothing
• Seasonal products: Holt-Winters (Triple Exponential Smoothing) or seasonal decomposition models
• Intermittent / lumpy demand: Croston's method or Syntetos-Boylan approximation — never apply standard exponential smoothing to intermittent demand
• Causal relationships available: Regression with causal variables (e.g., economic indicators, weather, pricing elasticity)

For full method explanations, see the Demand Forecasting Guide.

Step 3: Commercial and Market Intelligence Overlays

The statistical baseline is presented to commercial stakeholders — sales, marketing, key account managers, product managers — for review and adjustment. Commercial overlays should be specific, quantified, and assumption-documented:

• Promotional plans: Expected volume uplift by SKU in the promotional period, with source (historical promotional lift data, customer commitment)
• New product introductions: Launch ramp forecast, target distribution, analogous product benchmarks
• End-of-life and range changes: Wind-down curve; substitution rates to successor SKUs
• Customer-specific intelligence: Known large orders, customer inventory positions, contract renewals, lost accounts
• Market intelligence: Competitor activity, economic indicators, channel inventory levels

Step 4: Consensus Demand Review

The demand review brings together demand planning, sales, marketing, and finance to review the working demand plan, resolve disagreements, and agree on a consensus. Key discipline points:

• Start from the statistical baseline, not from last year's actuals or intuition. The baseline is the objective starting point; deviations must be justified
• Every adjustment must have a documented assumption — not "sales thinks it will be higher" but "promotion XYZ, historically +25% uplift, confirmed by key account manager"
• The output is an unconstrained consensus demand plan — it reflects what customers want, not what supply can deliver (that reconciliation happens in S&OP supply review)
• Disagreements between functions that cannot be resolved at the demand review are escalated to the pre-S&OP or executive S&OP meeting

Step 5: Handoff to Supply Planning

The approved consensus demand plan is released to supply planning to drive constrained supply plan generation, safety stock target setting, purchase order creation, and production scheduling. The quality of the supply plan is bounded by the quality of the demand plan — a biased or inaccurate demand plan propagates through the entire supply chain, generating excess inventory, stockouts, or both simultaneously.

Step 6: Performance Review and Calibration

Every planning cycle must close with a review of forecast accuracy from the prior cycle. No improvement in demand planning is possible without systematic measurement of forecast error. Accountability for forecast accuracy drives behaviours — documented assumptions enable learning; unmeasured forecasts drift.

Forecasting Methods Overview

See the Demand Forecasting Guide for worked examples and full method explanations.

Demand Sensing

Demand sensing is a technique that dramatically improves near-term forecast accuracy by replacing projected demand with actual real-demand signals as close to execution as possible. Rather than running a monthly forecast cycle and leaving the short-horizon plan unchanged until the next cycle, demand sensing continuously updates the 1–4 week demand signal based on high-frequency data.

Demand sensing data sources

• Point-of-Sale (POS) data: Daily sell-out from retail customers — far more leading than weekly shipment orders, which lag actual consumer demand
• Daily order patterns: Actual customer order intake as an early indicator of period demand
• Inventory positions: Customer inventory levels (when shared via VMI or collaborative programmes) — detecting depletion rates that signal incoming replenishment orders
• External signals: Weather data (relevant for cold & flu products, outdoor categories, seasonal foods), financial market data, web search trends, social listening

Demand sensing vs Statistical Forecasting

Demand Planning KPIs

Measuring demand planning performance is essential for continuous improvement. The key metrics address both the accuracy dimensions of the forecast and the process health indicators.

The Bias vs MAPE Priority

Bias is more operationally damaging than high MAPE. A forecast with high MAPE but no systematic bias generates random overshoots and undershoots — the supply chain copes with safety stock. A biased forecast consistently pulls inventory in the wrong direction: a persistent positive bias (over-forecast) builds excess stock and eventually triggers write-offs; a persistent negative bias (under-forecast) generates chronic stockouts and lost revenue. Bias must be identified and corrected at the source — usually a commercial team that over-promises or a sales team that sand-bags.

Common Mistakes in Forecasting and Demand Planning

1. Confusing the statistical forecast with the demand plan

Treating the system-generated statistical number as "the forecast" and skipping the commercial review, assumption documentation, and consensus process is the most pervasive failure. The statistical model is a tool; the demand plan is a business decision.

2. Forecasting at the wrong level of aggregation

Statistical models are typically more accurate at higher aggregation levels (product family, region) than at SKU-location level. A good demand planning architecture forecasts at the statistically optimal level, then disaggregates to SKU-location using historical mix ratios. Running independent statistical models at SKU-location level for thousands of items generates massive aggregate bias and poor accuracy.

3. Not cleaning demand history

A promotional spike, a one-off bulk order, or a stockout-impacted period left in the demand history will corrupt the statistical model. A forecast that extrapolates an anomalous event as baseline demand is wrong before it has calculated a single number.

4. Allowing sales to over-adjust without accountability

Sales teams have access to commercial intelligence the statistical model lacks — but they also carry motivational biases. FVA analysis frequently shows that sales adjustments degrade forecast accuracy on average, even when individual adjustments are directionally correct. The solution is not removing sales from the process but creating accountability: every adjustment is documented with an assumption, and FVA is tracked by adjuster.

5. Not managing new products and end-of-life

Statistical models cannot forecast a product that has no history. New product forecasting requires analogous product benchmarks, launch curve frameworks, and commercial input. End-of-life requires explicit phase-out curves — not just dropping the item from the forecast and hoping inventory arrives at zero simultaneously with last sales.

6. Treating forecast accuracy as an IT problem

When forecast accuracy is poor, organisations often respond by buying a better forecasting system. In most cases, the root cause is not algorithmic — it is process: insufficient demand history cleaning, no commercial review, no assumption documentation, no accountability. Better algorithms on bad inputs produce bad outputs. Process discipline precedes system investment.

Frequently Asked Questions

Related Resources