AI Agent for Unit Demand Planning
A demand plan is only useful if somebody checks it afterwards. This agent projects units by item and location from drivers you can name, distinguishes a genuine shift from noise, and reports how accurate its previous projection turned out to be.
What is an AI demand forecasting agent?
An AI demand forecasting agent is a governed software worker that projects unit demand at item and location level. It decomposes each projection into named, quantified drivers, tests apparent demand changes against historic variability before acting on them, and reports the accuracy of the previous cycle attributed by driver so the process can improve.
What it does
What it is not
Nobody ever checks whether the last one was right
Demand planning runs on a cadence and almost never on a feedback loop. A number is produced, the business plans against it, reality diverges, and the next cycle starts from a fresh number rather than from an understanding of which assumption was wrong. Accuracy is discussed in aggregate, where the errors cancel out and teach nothing.
Accuracy is never measured per driver
The plan missed by nine percent and nobody can say whether it was seasonality, a promotion or a price move.
Noise is read as signal
Three weeks of unusual orders trigger a plan change that reverses the following month at considerable cost.
Aggregation hides the error
A national forecast is close while every region it is made of is wrong in a different direction.
Assumptions live in a modeller’s head
The plan embeds a view about a customer or a season that nobody else can see or challenge.
A projection with its assumptions and its track record
Drivers
Say What The Number Assumes
Named, quantified, challengeable.
Each projection decomposes into the drivers behind it — baseline trend, seasonality, a promotion, a price change, a known customer commitment — with the contribution of each stated, so a planner argues with an assumption rather than with a total.
- Projection decomposed by contributing driver
- Each driver quantified, not merely listed
- Known commitments separated from statistical base
- Drivers with no supporting data marked as judgement
By driver
Stability
Tell A Shift From A Wobble
Before the plan chases it.
A change in recent orders is tested against the historic variability of that item and location before it moves the projection, so a genuine level shift is acted on and three unusual weeks are reported as within normal range.
Shift or noise
Accountability
How Wrong Was The Last One
Reported with every new run.
Each cycle opens by measuring the previous projection against what actually shipped, broken down by driver so the error is attributable, which is the only mechanism by which a forecasting process gets better rather than merely continuing.
By driver
How the AI Demand Forecasting Agent runs a task
- STEP 01
Score the last cycle first
Before producing anything new the previous projection is compared with what actually shipped, and the error is attributed across the drivers that were used, because a cycle that starts from a blank sheet learns nothing.
Accuracy measurementError attribution - STEP 02
Establish the statistical base
A baseline is built from shipment history at the grain the plan is made on, with one-off events excluded and marked rather than smoothed, so the base reflects underlying demand rather than the last unusual quarter.
Baseline constructionOutlier exclusion - STEP 03
Layer the known drivers
Seasonality, planned promotions, price moves and committed customer orders are applied as separate named adjustments with their contributions quantified, which is what makes the resulting number arguable.
Driver layeringContribution split - STEP 04
Test what changed
Any movement against the previous projection is checked against the variability of that item and location, and reported as a level shift, a trend break or within normal range, so the plan does not chase noise.
Change testingVariability comparison - STEP 05
Hand over for consensus
The statistical projection and any commercial overlay are presented separately for the demand review, and the number the business commits to is theirs rather than the model’s.
Consensus packOverlay separation
Systems the AI Demand Forecasting Agent connects to
Demand history
Projection
Inputs, outputs and runtime
- Ingests
- Shipment and order historyPromotion and price calendarCommitted customer ordersPlanning grain and horizonPrior cycle projections
- Produces
- Unit projection by item and locationDriver decompositionSignal versus noise assessmentPrior accuracy by driverConsensus review pack
- Triggered by
- Planning cycleApparent demand shiftNew product introduction
- Human oversight
- The demand review commits the plan
- Models
- Open-weight LLMs you host — Llama, Qwen or Mistral class
- Typical latency
- Minutes across a full item catalogue
- Deployment
- On-premise or sovereign cloud with egress control
- Data residency
- Demand and customer data stay internal
Where the Demand Forecasting Agent pays back
Cycle Demand Planning
Produce the unit projection by item and location with the contribution of each driver stated.
Forecast Accuracy Review
Measure the prior cycle against actual shipments and attribute the error to specific drivers.
Signal Versus Noise Testing
Test an apparent demand change against historic variability before the plan responds to it.
Promotion Impact Estimation
Project the uplift a planned promotion implies using comparable past events rather than a flat multiplier.
New Product Projection
Build an opening projection from comparable items where the product itself has no history.
Consensus Preparation
Prepare the demand review with the statistical base and the commercial overlay shown separately.
AI Demand Forecasting Agent vs chatbots and SaaS copilots
Most demand planning processes measure their own accuracy once a quarter, in aggregate, at a level where regional errors in opposite directions cancel and the number looks respectable.
| Generic chatbot | SaaS copilot | VDF AI | |
|---|---|---|---|
| Grain | Whatever you paste | Aggregate series | Item and location |
| Assumptions | Implicit | Model parameters | Named drivers, quantified |
| Recent change | Extrapolated | Extrapolated | Tested against variability |
| Prior accuracy | Not measured | Aggregate score | Attributed by driver |
| Commercial overlay | Merged in | Merged in | Shown separately |
| Commits the plan | Not applicable | Publishes | Never — the review commits |
| Where demand data sits | Pasted | Vendor cloud | Inside your own network |
Governance and controls
A demand plan drives purchasing, production and headcount, so the thing that matters for control is whether the assumptions behind it were visible to the people committing against it.
Drivers stated per projection
No number without its assumptions
Judgement marked as judgement
Unsupported drivers labelled as such
Prior accuracy always reported
Each cycle opens with the last error
Read-only source systems
Shipment history is never altered
Overlay kept separate
Commercial views not merged into base
Plan committed by people
The consensus number is a decision
Evidence it leaves behind
What changes after rollout
Who runs the AI Demand Forecasting Agent
Demand planner
Opens the cycle knowing which driver was wrong last time and by how much, which turns the review from a negotiation about a number into a discussion about a specific assumption that can be corrected.
Supply planning manager
Can tell whether a jump in the projection reflects a confirmed level shift or three unusual weeks, which is the difference between a justified production change and an expensive reversal next month.
Commercial director
Sees the statistical base and the commercial overlay separately, so the question of whether the sales view is being optimistic is answerable rather than embedded in a single agreed figure.
Questions about the AI Demand Forecasting Agent
What is an AI demand forecasting agent?
It is an agent that projects unit demand by item and location: decomposing each projection into named drivers with their contributions, testing apparent changes against historic variability before acting on them, and measuring the prior cycle against what actually shipped.
How is an AI demand forecasting agent different from a generic chatbot?
A chatbot can describe forecasting methods. This agent runs against your own shipment history, states which driver produced each part of the number, and opens every cycle by reporting how wrong the last one was.
Can an AI demand forecasting agent run on-premise on shipment and order data?
Yes. A demand plan exposes customer concentration, planned promotions and expected volumes well before any of it is commercial knowledge, so it stays on infrastructure you control.
What does an AI demand forecasting agent produce, and in what format?
A unit projection by item and location, decomposed by driver with contributions quantified, a signal-versus-noise assessment on each change, and a prior-cycle accuracy report attributed by driver.
Where does an AI demand forecasting agent fit in a governed AI programme?
It projects; the business commits. The consensus plan is a management decision, the stock position that follows belongs to the inventory optimization agent, and financial planning to the FP&A agent.
How does this differ from the AI FP&A Agent?
Units against money, and a different buyer. This agent projects how many of an item will ship from a given location, which drives purchasing, production and stock. The FP&A agent plans financially — revenue, cost, headcount, scenarios — and typically consumes a demand plan as one of its driver assumptions rather than producing one. A demand planner and an FP&A manager are different people with different systems.
Why report prior accuracy at all?
Because without it a forecasting process cannot improve, only continue. Aggregate accuracy measured quarterly is close to useless — errors in opposite directions cancel, and the number that results tells nobody which assumption to change. Attributing error to the specific driver that caused it is the only version of the measurement that changes behaviour, and it is uncomfortable enough that it rarely happens unless something does it automatically.
Can it forecast items with no history?
It builds a projection from comparable items and any committed orders, and labels the whole thing as an analogue-based estimate rather than presenting it at the same confidence as a line with three years of data. New product forecasting is genuinely hard and mostly a commercial judgement; what the agent contributes is a defensible starting point and an explicit statement of how little the data supports it.
How does it handle promotions?
As a named driver with its uplift estimated from comparable past events for that item and channel, rather than as a flat percentage applied across the board. Where a promotion has no close comparable the uplift is flagged as judgement. The contribution is kept separate from the baseline throughout so that when the promotion ends, the plan returns to the base rather than carrying the uplift forward.
Does it feed the inventory agent automatically?
The projection is available to it, and that pairing is the normal deployment — but the handover is deliberate rather than automatic. A stock proposal built on an uncommitted projection inherits every one of its assumptions invisibly. Running both with the demand plan committed first means a planner can see whether a replenishment is driven by real demand movement or by a forecast nobody has yet agreed.
See which assumption was wrong last cycle
See the AI Demand Forecasting Agent project unit demand and score its own prior run.