Demand sensing

Definition

Demand sensing is a short-horizon forecast that refines the plan a few days to a few weeks out by reading the freshest signals available: point-of-sale data, orders, promotions, weather, online activity. It does not replace the baseline forecast; it is its reactive extension, the layer that keeps the plan glued to reality between two planning cycles.

Why it matters

The forecast that reads the present.

Classical forecasting looks far ahead and leans on history: it sets the frame weeks or months out. But between two planning cycles real demand moves, sometimes sharply, and history says nothing about what just happened. Demand sensing fills exactly that gap: it refines the forecast over the very short horizon, the next few days to the next few weeks, by reading the most recent signals.

Its raw material is not the distant past but the immediate present: point-of-sale sales, open orders and their changes, live promotions, weather, online activity. Where the baseline forecast assumes tomorrow resembles the past, sensing assumes the very short term resembles what just occurred. It weights recent observations heavily and reacts fast, whereas statistical forecasting, by design, reacts slowly to stay stable.

The stakes are concrete: over the short horizon, a sharper forecast translates directly into fewer stockouts, less overstock and a steadier plan sent to the factory and to suppliers. This is where service level and tied-up capital are decided. Sensing does not replace the baseline forecast; it is its reactive extension, the layer that keeps the plan aligned with reality between two revisions.

Business impact

The gains reported by vendors and practitioners are real but very uneven across products. On volatile categories that are sensitive to promotions, weather or fads, the reduction in short-term forecast error can reach 20 to 50%, alongside an inventory drop often cited around 15 to 25% and a clear cut in stockouts. On stable, slow-moving references the gain is marginal: deploying sensing there costs more than it returns.

The expert lesson fits in one sentence: demand sensing refines a forecast, it does not create one. Without a solid baseline it amplifies noise instead of correcting it, a point the trade press underlined in early 2026. And where most projects are won or lost is not the model but the quality and freshness of the data: a late or mismatched sales feed feeds the model errors. Sensing is first a data effort, then an algorithm effort.

The mechanism

Fresh signals, fused then weighted.

Demand sensing always follows the same logic: capture recent, relevant signals, clean them and align them to the right grain, then correct the baseline forecast more strongly the nearer the horizon.

It all starts with capture. The system continuously ingests heterogeneous feeds: point-of-sale transactions at the reference and store level, orders and backlog, planned promotions, weather forecasts, online signals. These feeds arrive in different formats, grains and frequencies. The most decisive and most underrated step is their harmonisation: normalise, match each signal to the right reference and location, correct latencies, strip noise. Sloppy harmonisation dooms everything that follows.

Next comes the transformation into predictive features. A temperature spike matters only for certain categories and seasons; a promotion produces an acceleration then a fall-back; a disruption elsewhere shifts demand. Sensing encodes these effects into usable factors, such as weather-sensitivity indices or promotional uplift coefficients by store cluster, that the model can weight.

The core of the setup is a model built for responsiveness, not stability: state-space models, Bayesian updates, gradient boosting, local pattern matching. All share the same principle: give far more weight to recent observations and causal signals than to old data. The result is a forecast that self-corrects as information arrives, delivered at the fine grain where execution needs it. The schematic shows this fusion: several real-time signals converge to bend the baseline forecast over the short window alone.

Store POSOrdersWeatherPromotionsfusion0 to 8 wksnow
Baseline forecastSensing-correctedReal-time signals

Figure 1. Demand sensing fuses recent signals (POS, orders, weather, promotions) to correct the baseline forecast over the short horizon, where the gap costs most. Beyond the short window, the correction fades. Illustrative schematic.

ŷt+h = ŷbaset+h × ( 1 + Σk βk · sk(t) )
The refined forecast ŷt+h starts from the baseline forecast ŷbase, from consensus or the statistical model, and applies a multiplicative correction built from recent normalised signals sk(t): POS sales deviation, open orders, promotions, weather, web activity. Each βk is a learned sensitivity, how much a given signal moves demand. Two properties do all the work: recent observations weigh far more than old ones, and the correction fades as the horizon h lengthens, because today’s signal only informs the very short term. Sensing corrects a forecast; it never builds one from scratch.

The traps

Three demand-sensing errors.

The same causes recur in projects that disappoint: a sensing layer set on a fragile baseline, mismanaged responsiveness, a polished model starved of data.

01

Sensing without a solid baseline

Demand sensing corrects an existing forecast; it does not create one. Wired onto a fragile or biased baseline, it merely amplifies its errors while refreshing them faster. The correct sequence is a sound baseline first, only then the sensing layer. Reversing the order turns a precision tool into a noise amplifier.

02

Mistaking responsiveness for over-reaction

A fresh signal is not always a true signal. Reacting to every wobble in sales means taking noise for information and injecting instability into the plan, up to an internal bullwhip effect. Useful sensing tells a genuine regime change from mere randomness: it reacts fast, but not to everything.

03

Polishing the model, neglecting the data

The temptation is to perfect the algorithm and under-invest in the feeds that nourish it. The opposite is what works. A complete, on-time, correctly matched sales feed beats the most sophisticated model starved of late data. Most failures sit in integration, not in the science.

The rollout

Four steps to useful sensing.

Deploying demand sensing follows a progression where order matters as much as content.

Secure the baseline forecast

First make sure the baseline is sound, free of systematic bias and measured cleanly. Sensing sits on top of it; it only makes sense once that foundation is verified. A check of baseline bias and error precedes any signal wiring.

Wire and harden the signals

Identify the signals with real predictive value over the short horizon, then invest in their integration: frequency, latency, matching to the right grain, cleansing. This is where performance is won or lost, in the data far more than in the algorithm.

Target the references that deserve it

Focus sensing on volatile, promotional or event-sensitive categories, where the gain is real. Spare stable, slow-moving references, where the effort does not pay back. Sensing is a scalpel, not a uniform treatment.

Link to short-term execution

Flow the corrected signal automatically into replenishment, distribution and execution, and measure the real uplift against the baseline with a Forecast Value Added logic. Sensing that does not change decisions is just one more dashboard.

Neighboring concepts

Read next.

Demand sensing extends the baseline forecast into the very short term and feeds execution directly.

From knowledge to action

Does your plan still match today’s demand?

Between baseline forecast, real-time signals and execution, demand sensing is only worth as much as the data it runs on. Our Planning, Forecasting & S&OP file connects your forecasts to the signals that matter.