Forecast Range

Forecast Risk

A Forecast Is a Range of Risk, Not a Single Number

Retail forecasts often arrive with a false sense of certainty.

A system says next month’s sales will be $842,000. A category plan says demand will be 4,700 units. A store forecast says 312 pieces of a seasonal item will sell over the next six weeks.

The numbers look exact, so the decision process often becomes exact too. If the forecast says 4,700 units, the buying conversation becomes, “How do we make sure we have 4,700 units available?”

But the forecast isn’t a promise. It’s the centre of a possibility.

That distinction matters because retail decisions aren’t made in a world where one demand number comes true. Weather shifts. Promotions overperform. Competitors react. Deliveries slip. Stores execute unevenly. Customers simply behave differently from what the model expected.

A point forecast is still useful. It gives you a reference point. The mistake is treating that reference point as though it contains the whole risk.

A stronger way to think is this:

The point forecast tells you where demand may centre. The range tells you what the decision has to survive.

If expected demand is 4,700 units, a useful planning conversation is not finished until you ask what happens if demand is materially lower or higher.

Maybe a plausible range is 4,000 to 5,500 units. The exact width depends on the item, history, volatility, seasonality, promotion, lead time and life cycle.

The point is not to apply an arbitrary plus-or-minus percentage. It’s to expose uncertainty before you commit inventory against it.

Once you think this way, forecasting stops being only a prediction problem and becomes a decision-risk problem.

  • What is the downside if we are wrong low?
  • What is the downside if we are wrong high?
  • Which error is more expensive?
  • Which error is easier to correct?
  • Which part of the decision is reversible, and which part locks us in?

Those questions often matter more than whether expected demand is 4,700 or 4,760.

Consider a retailer planning a spring outerwear buy.

The forecast for one jacket is 1,000 units. The simplest response is to buy around 1,000 units, perhaps with a little safety stock.

But suppose the merchant and planner agree that 800 to 1,250 units is a more credible planning range because spring weather is volatile, the product has limited history, and a planned campaign could create upside.

Now the decision changes.

If they buy 1,000 units and demand lands at 800, they have 200 units of excess stock, potentially creating markdown exposure and weaker margin.

If demand reaches 1,250, they miss 250 units of potential sales unless they can replenish.

At first glance, those look like equal misses. They aren’t.

Suppose the vendor can replenish within ten days, but leftover outerwear becomes difficult to sell once warm weather arrives.

Overbuy risk may be more damaging because the underbuy can be corrected while the overbuy becomes progressively harder to recover from.

The same forecast range could therefore support a more conservative initial buy, perhaps 850 or 900 units, combined with a reorder trigger if early sell-through confirms stronger demand.

The forecast didn’t become more accurate. The decision became more intelligent.

Better forecasting is valuable, but better decisions do not require pretending uncertainty has disappeared.

Sometimes the bigger improvement comes from designing the inventory decision around uncertainty rather than squeezing more apparent precision from the forecast.

A useful mental model is to separate three things:

Expected demand. Plausible demand range. Cost of being wrong.

The expected demand gives you the middle. The range gives you the uncertainty. The cost of being wrong tells you how aggressively to act.

If you only use the middle, you’re missing two-thirds of the decision.

This is why two products with the same expected demand may deserve different decisions.

A basic replenishable item with weekly deliveries and little loss of value if stock carries forward can tolerate forecast error better than a fashion colour tied to a six-week trend window with an eight-week replenishment lead time.

The forecast might be 500 units for both. The number is the same. The risk structure is not.

This leads to a repeatable rule:

Forecast uncertainty matters most when the decision is hard to reverse.

That’s why range thinking becomes more valuable as lead times lengthen, seasonal windows shorten, products become more fashion-sensitive, promotions become more aggressive, or inventory becomes more perishable financially or physically.

You don’t need a sophisticated probabilistic model to use this idea well.

A practical planning discussion can begin with three cases: a lower-demand case that would not surprise you, a central case you currently consider most likely, and a higher-demand case that would also not surprise you.

“Would not surprise you” is a useful test because it keeps the range grounded. You’re not imagining every theoretical outcome. You’re defining a credible operating envelope for the decision.

Then ask what happens to inventory, sales, margin and flexibility in each case.

This is where the range becomes more than a forecasting exercise. A forecast range only becomes useful when paired with response options.

Without response options, the range merely describes uncertainty. With response options, it becomes a decision tool.

So retailers should stop asking only, “What do we think demand will be?” They should also ask, “What can we still do if demand is different?”

Can we reorder? Transfer stock between stores? Delay receipts? Redirect inventory to e-commerce? Accelerate marketing? Carry the item forward? Exit without severe markdown pain?

The more options you have, the less damaging uncertainty becomes. The fewer options you have, the more carefully you need to position the initial commitment.

That gives you a simple diagnostic for almost any forecast-driven inventory decision. Look at the lower and upper ends of the plausible range and ask:

If demand lands here, what hurts?

If demand lands here, what can we still change?

Those two questions expose the real decision faster than debating whether the forecast should be 3 percent higher or lower.

Teams sometimes say, “We need a better forecast before we decide.” Sometimes they do. But sometimes what they really need is to understand the asymmetry of the risk.

If being 20 percent over forecast creates heavy markdown exposure while being 20 percent under can be corrected with fast replenishment, the decision should reflect that asymmetry even if the forecast itself does not improve.

Likewise, if stockouts during a short seasonal peak would create a major lost-sales problem and there is no replenishment path, a retailer may deliberately accept more downside inventory risk to protect the upside.

Range thinking does not automatically make you conservative.

It makes you explicit about which risk you are choosing.

A forecast should not tell the retailer what will happen. It should help the retailer prepare for what could plausibly happen and decide which errors are acceptable.

So when a forecast lands on your desk as one clean number, don’t ask only, “Do we believe it?”

Ask what range around it is plausible, what happens at each end, which miss is more expensive, and what you can still change after demand reveals itself.

Then make the inventory decision that can survive the range, not just match the midpoint.

The strongest forecast isn’t the one that looks most precise. It’s the one that helps you make a decision that remains sensible when reality refuses to hit the number exactly.

AI Diagnosis

AI Prompt

Analyze this retail forecast or inventory decision using the principle that a forecast is a range of risk, not a single number: [Paste or describe your forecast, product, inventory situation, lead time, replenishment options, seasonality, promotion, or other facts you know. Example: “We forecast 1,000 units of a spring jacket over six weeks. Initial order must be placed now. Replenishment takes 10 days. The item becomes difficult to sell once warm weather arrives. We have limited sales history, and a marketing campaign could increase demand.”] Turn the information into a practical risk-aware inventory decision. Identify the expected-demand case, then establish a plausible lower-demand and higher-demand case using only evidence in my input; if there isn’t enough evidence to justify numeric boundaries, use clearly labelled qualitative scenarios rather than inventing numbers. For each case, explain what would happen to inventory, lost-sales exposure, markdown or margin risk, and operational flexibility. Then compare the cost of being wrong on the low side with the cost of being wrong on the high side, identify which risk appears more damaging and explain why. Show which parts of the decision are reversible and which become difficult to correct, including options such as replenishment, transfers, delayed receipts, e-commerce allocation, marketing changes, carrying inventory forward, or markdowns when relevant. Finish with a specific recommended decision approach for the initial inventory commitment, any sensible trigger for changing course as actual demand becomes visible, and a concise decision rule I can reuse. Clearly label any conclusions that are reasonable inferences rather than facts, and don’t invent sales history, probabilities, costs, margins, demand ranges, or capabilities I haven’t provided.

AI Output

The 1,000-unit forecast is useful as a planning centre, but the decision shouldn’t be “Do we buy 1,000?” The better question is: How much inventory should we commit before we know which demand path we’re actually on?

The information you’ve provided points to an important asymmetry.

Excess inventory becomes increasingly difficult to recover from as warm weather arrives, while at least some upside demand can potentially be recovered through a 10-day replenishment cycle.

That makes the two forecast errors economically different.

Risk range

Scenario What it means Inventory consequence Main risk Flexibility
Lower-demand case Demand develops below the 1,000-unit expectation An order built around the full forecast could leave meaningful residual stock Markdown pressure, weaker realized margin, end-of-season inventory Low. Time works against you because the jacket becomes harder to sell as temperatures rise
Expected-demand case Demand develops broadly in line with the 1,000-unit forecast Inventory needs to support roughly 1,000 units over six weeks Either excess stock or missed sales if timing is wrong Moderate. Replenishment provides some ability to adjust
Higher-demand case The campaign performs strongly or underlying demand is better than expected An overly conservative initial commitment could create temporary shortages Lost sales and possible missed momentum from the campaign Higher than in the downside case because 10-day replenishment may allow additional stock to arrive

I wouldn’t assign numeric boundaries to the low and high cases from the information available.

Limited sales history tells us uncertainty is meaningful, but it doesn’t tell us whether a credible range is 900 to 1,100, 750 to 1,300, or something else.

That uncertainty itself should influence the decision.

Which mistake is harder to recover from?

Inference: The downside error appears more difficult to correct.

Suppose you commit heavily to the 1,000-unit forecast and demand disappoints. As the six-week period progresses, your choices deteriorate.

You can promote harder or markdown the jackets, but you can’t extend spring indefinitely. Inventory that looked reasonable in week one may become a liability in week five.

By contrast, if demand runs above plan, the 10-day replenishment time gives you at least some possibility of responding. You may temporarily lose sales, but the error isn’t necessarily permanent.

That creates the key decision principle:

When underbuying can be corrected faster than overbuying can be cleared, don’t treat the forecast as the initial order quantity.

The marketing campaign complicates this slightly. It creates genuine upside risk. You don’t want such a small initial commitment that strong campaign response immediately produces stockouts.

But the campaign doesn’t eliminate the downside risk. In fact, because its effect is uncertain and sales history is limited, it increases the argument for maintaining flexibility rather than making one large irreversible bet.

Recommended decision approach

I wouldn’t recommend committing the entire 1,000-unit forecast upfront based on the information given.

Inference: A staged inventory commitment is more appropriate.

Place an initial order that provides meaningful coverage of expected early demand while deliberately keeping part of the forecast uncommitted.

Then use actual demand during the first part of the six-week window to decide whether to release additional inventory.

I can’t responsibly specify whether the initial buy should be 700, 800, 900 units or another quantity because we don’t have the information needed to justify that number.

In particular, we’d want to know supplier availability, minimum order quantities, when replenishment stops being viable, campaign timing, expected sales distribution across the six weeks, and whether excess inventory has any useful carry-forward value.

But the shape of the decision is clear:

Commit less before demand is visible. Commit more when demand earns it.

The 10-day lead time should then become part of the control mechanism rather than simply a supply-chain fact.

Instead of waiting until inventory is almost depleted, monitor the jacket’s sales pace against remaining inventory and ask:

If the current demand rate continues, will we have enough stock to cover demand through the next replenishment arrival?

If the answer is approaching no, that becomes the signal to reorder.

You should also interpret early sales in context. Strong opening demand during the marketing campaign doesn’t automatically mean six-week demand will remain equally strong.

You’d want to distinguish between a temporary campaign spike and evidence that the underlying demand level is genuinely higher than expected.

Similarly, weak first-week sales shouldn’t automatically trigger discounting. They’re information. They tell you not to deepen the inventory commitment until there’s stronger evidence.

That is one of the advantages of staging the buy. Early sales become evidence used to improve the next inventory decision rather than merely a scorecard showing whether the original forecast was right.

Some decisions here are relatively reversible. Additional inventory can potentially be ordered. Marketing can potentially be adjusted.

Inventory might be redirected between stores or channels if those capabilities exist.

Other decisions become increasingly irreversible. A large initial purchase can’t easily be undone. A jacket arriving too late in spring loses selling opportunity.

Excess seasonal inventory becomes progressively more dependent on markdown.

So I’d frame this decision around option value. Keeping part of the purchase uncommitted preserves your ability to respond to what customers actually do.

The working rule would be:

Forecast 1,000 units, but don’t automatically buy 1,000 units. Make the first commitment large enough to serve credible early demand, small enough to protect against seasonal downside, and use the 10-day replenishment window to let actual demand determine the rest.

The deeper lesson is that you’re not trying to prove whether the 1,000-unit forecast is right. You’re designing an inventory decision that still works reasonably well when it’s wrong.