Notes

AI supply chain planning: a better forecast is only the start

Turn a demand forecast into a decision about stock, capacity and delivery. A worked example and interactive comparison show what AI planning needs beyond accuracy.

The forecast says next month's demand will reach 1,000 units. Sales wants to promise delivery. Production can make 600. There are another 200 in stock.

Someone has to decide what to do about the gap.

A better forecast helps. It still doesn't tell you whether to book overtime, buy from another supplier or accept some late deliveries. That depends on the costs, the constraints and what you have promised customers.

This is where AI supply chain planning needs to prove its value: helping people choose a workable response, then checking whether it worked.

PwC's September 29 article, From plans to decisions, argues for planning that responds to changing conditions, with clear limits on what AI can do. The direction makes sense. The practical test is what happens to one order, one capacity decision and one customer promise.

Let's work through that test.

First, count the demand once

Our fictional manufacturer has a forecast of 1,000 units for next month. Customers have already placed orders for 600 of those units. All figures refer to the same product, customer group and delivery month.

Adding the forecast and the orders would produce demand of 1,600 units. But the forecast already includes the orders. The remaining demand still to arrive is 400.

Orders belong inside the forecast Fictional example: adding 1000 forecast units and 600 confirmed units would overstate demand as 1600. Consuming the orders leaves 600 confirmed units and 400 units still expected, totalling 1000. Orders belong inside the forecast Adding both: 1,600 units 1,000 forecast600 orders Counted twice Counted once: 1,000 units 600 ordered400 Still to be ordered
Fictional example. The 600 confirmed units are part of the 1,000-unit forecast. They leave 400 units of forecast demand still to be ordered, not another 1,000.

This is called forecast consumption: actual orders replace the matching part of the forecast. Oracle's planning documentation explains the process and its timing rules.

The matching matters. An order for a different month or customer may not belong inside this forecast. And if confirmed orders exceed the forecast, the plan must still cover those orders. Subtracting everything from everything would create a different mistake.

Foreviq, the demand-forecasting project I'm working on, connects sales history with open orders and nets the orders against the forecast. That is a useful connection before anyone decides how much to make.

Data quality can sound abstract until a mismatch creates a production requirement. In PwC's 2026 operations survey, 87% of respondents said poor data quality had affected the value of digital initiatives. The survey covered 767 operations and supply chain leaders at US organisations with annual revenue of at least $100 million. It describes their reported experience.

For this decision, the first checks are quite specific: the right product, the right month, orders counted once, and stock that is actually available.

A forecast range changes the capacity question

After correcting the demand, we still have 1,000 expected units against 800 available: 200 in stock and 600 from regular production. That leaves a 200-unit gap at the central forecast.

But 1,000 is an estimate. For this example, let's also examine demand of 800 and 1,200 units. Those are fictional scenarios, with no probabilities assigned.

At 800, regular production is enough. At 1,200, filling the central forecast's gap would still leave 200 units short.

That is why a point forecast needs context. A prediction interval describes uncertainty around future demand under a forecasting model; it is not a promise that demand will stay inside its bounds. Forecasting: Principles and Practice explains the distinction.

Foreviq includes an 80% planning range alongside its forecasts. Our fictional scenarios below let us inspect what happens when demand comes in lower or higher than planned.

The question is now clearer: how much extra capacity is worth committing to before we know the demand?

Compare the response, not just the forecast

Assume materials, staffing and supplier capacity are available for these three options, with all units ready by the same delivery deadline:

Plan for next month Units available Assumed additional commitment
Keep regular production 800 None
Add 200 units through overtime 1,000 €300 setup plus €2 premium per extra unit: €700
Buy 400 additional units externally 1,200 €4 premium per extra unit plus €100 extra freight: €1,700

The outside supplier meets the same quality requirement. Overtime and external purchasing are alternatives, not combined. These are fixed commitments made before demand is known; extra units are not cancelled when demand comes in lower.

To compare them, assume €8 of late-delivery cost for each unit we cannot supply on time, and €2 to carry each leftover unit into the next month. All these costs are fictional inputs.

We compare premiums, late-delivery costs and one month's carrying costs. Ordinary unit costs, sales revenue and stock purchases sit outside this model. Leftover stock remains usable next month, so we charge its carrying cost rather than write off its value.

At demand of 1,000 units, regular production leaves 200 late units, costing €1,600. Overtime costs €700 and covers demand. External purchasing costs €1,700 plus €400 to carry its 200 leftover units, giving €2,100.

Overtime has the lowest cost in this comparison. Now change the demand.

One month · one product · fictional inputs

What would you commit to?

A change in demand can change which plan costs least.

6001,400 units
4001,000 units

Every plan starts with 200 units in stock. Overtime adds a fixed 200 units; external purchasing adds a fixed 400.

Lowest modelled costAdd overtime€700
Extra commitmentLate deliveryCarrying stock

Additional cost (€), on a shared scale. Hover, tap or focus a plan to inspect its cost breakdown.

Add overtime

€700 commitment + €0 late delivery + €0 carrying stock = €700

Assumptions, calculations and all values

All quantities refer to one product and one delivery month. The 600 confirmed orders in the story sit inside forecast demand; they are not added again. Demand cannot fall below those orders in this control. Regular output is the quantity available before the deadline, not a long-run capacity rating.

Each option commits its entire additional quantity before demand is known. Materials, labour and supplier availability are assumed. Regular production is unchanged across the three plans at any chosen input; leftover units remain usable next month. No safety-stock target is imposed.

  • Stock: 200 units.
  • Overtime: 200 extra units, €300 setup plus €2 premium per extra unit = €700.
  • External purchasing: 400 extra units at €4 premium each plus €100 extra freight = €1,700.
  • Late-delivery cost: €8 per unit not available by the deadline.
  • Carrying cost: €2 per leftover unit for one month.

Available = stock + regular output + extra units. Late units = max(0, demand − available). Leftover units = max(0, available − demand). Additional cost = commitment + late units × €8 + leftover units × €2.

Current scenario: 1,000 demand units, 600 regular units
PlanAvailable unitsLate unitsLeftover unitsCommitmentLate costCarry costTotal
Regular production8002000€0€1,600€0€1,600
Add overtime1,00000€700€0€0€700
Buy externally1,2000200€1,700€0€400€2,100

This is a comparison of selected additional costs, not total company cost, profit or cash spend. It excludes ordinary unit costs, sales revenue, acquisition value of stock, quality losses, cancellation rights and wider service effects. Stock retains its value. We assign no probabilities to demand scenarios, so these are not expected costs. A lowest-cost highlight does not grant approval or recommend a real production plan.

Original illustrative model for this note. The order-netting principle and forecast uncertainty are described by the linked sources; the example's costs are assumptions.

Fictional one-month comparison. Change demand or regular output to inspect the trade-offs. The highlighted plan has the lowest modelled additional cost at those inputs, not a proven best plan for a real business.

With the original 600-unit regular output, demand of 800 favours regular production. At 1,200, external purchasing has the lowest modelled cost. The same forecast range contains three different answers.

Choosing a plan before demand arrives also means judging how likely those scenarios are. The comparison shows what would change the choice: overtime beats regular production above 910 units; external purchasing beats overtime above 1,140. At each boundary, the two plans tie.

Those thresholds are useful questions for the team. How credible is demand above 1,140? Can we wait for more orders before committing? Would the supplier still have capacity then?

This connects to the procurement savings example: compare the cost of meeting the requirement, including what happens after the purchase order. A lower price or a faster recommendation is only part of that decision.

The arithmetic here fits in a spreadsheet. AI can help a team notice changed demand, gather relevant inputs and prepare a comparison. It should make the underlying calculation easier to inspect.

A research community vision statement on AI in supply chains separates prediction from choosing actions and discusses language models as interfaces to planning tools. The assistant, forecast and capacity calculation have different jobs. Connecting them does not remove the need to check the result.

Make approval worth doing

Suppose AI recommends overtime. “Approve” should mean the planner can see the 200-unit gap, the €700 commitment, the alternatives and the assumptions that made overtime look sensible.

Showing a confident paragraph is not enough. Neither is putting a person in front of a button when they cannot inspect what will change.

For this example, the approval record could be short:

What the reviewer needs What this decision should show
The demand assumption 1,000 units, including 600 already ordered; forecast version and issue date
The supply assumption 200 usable units in stock, 600 regular units and confirmed capacity for 200 overtime units
The comparison €700 for overtime versus €1,600 or €2,100 in the central scenario; results at lower and higher demand
The authority AI prepares the proposal; the operations manager approves the overtime commitment
The point of no return Approval and cancellation deadlines, with a new review if demand or capacity changes before commitment

Foreviq separates draft, review and approved plans. Its assistant can propose a forecast but cannot publish it without a person. Committing to overtime is a separate decision with its own owner.

The previous note on AI and human control asked what authority we give a system. In planning, that becomes very concrete: who may commit spend, change a delivery promise or choose which customer waits?

These choices need named owners even when the calculations are automated.

Check the result without rewriting the decision

After the month ends, compare the approved assumptions with what happened: demand, units delivered on time, extra spend and leftover stock. Keep the original forecast and plan so the comparison survives later updates.

If demand turns out to be 800, our overtime plan looks unnecessary after the fact. That alone does not prove the original decision was careless. We made it with uncertainty. Review whether the information was reasonable, then check whether the forecasts and cost assumptions improve across several decisions.

Vrolen connects to this part of the problem. It lets teams compare possible changes through guided what-if analysis and simulation, then check whether a change produced the expected result.

Forecast error still matters. The MAPE and WAPE note shows why different accuracy measures can point to different winners. Put those measures beside delivery performance, stock and additional cost. Otherwise a better forecast score can hide a worse operational result.

For a first AI planning pilot, choose one recurring decision and follow it through this whole process. Agree what counts as an improvement before the pilot starts. Record the assumptions, compare the alternatives, set the approval boundary and review the outcome.

The useful test is simple: when the forecast changes, can the team explain what it will do differently, why, and how it will know whether that choice worked?

Sources

The manufacturer, quantities, options and costs are fictional. The original worked example's assumptions and calculations are available beside the visual.

NextCan AI take over? What the singularity debate gets wrong

Test the change before committing

Vrolen’s private pilot helps operations teams compare proposed changes and check whether the expected improvement held. Bring the capacity assumptions behind your planning decision.

Abolfazl Shirkavand