The Demand Planning Process: 7 Steps for Manufacturers
The demand planning process steps for manufacturers: 7 concrete stages from data cleanup to consensus and measurement, with the owners and KPIs for each.
The demand planning process steps below are the exact sequence I ran monthly at a $250M manufacturer with 4,200 SKUs across 11 locations. Not a textbook diagram — the working version, with the owners, the inputs, and the places it actually breaks. If you run these seven steps with discipline, you produce one signed demand number every month that supply, inventory, and finance can build off. Skip a step and you get the usual chaos: three competing numbers, a quarter-end inventory surprise, and a planner who can't tell you why the forecast missed.
Each step has an owner and a deadline. Demand planning fails when it's everyone's job, which means it's no one's. Assign names.
Step 1: Clean and segment the data
Before any math, fix the inputs. Pull 24-36 months of shipment or order history and scrub it:
- De-stockout the history. Past stockouts mean you sold what you had, not what customers wanted. Flag those periods and correct them, or your forecast inherits your old supply failures.
- Strip one-time events. A 2024 emergency buy from a customer who left isn't a pattern.
- Segment with ABC/XYZ. ABC by revenue, XYZ by demand variability. Your A/X items (high value, stable) get tight statistical forecasting. Your C/Z items (low value, lumpy) get simple rules, not babysitting.
Most teams skip this and forecast on dirty history. Garbage in, expensive out. Owner: demand planner. Deadline: day 2.
Step 2: Generate the statistical baseline
Now run the math. Match the model to the demand profile — there is no single best method:
| Demand profile | Model that fits |
|---|---|
| Stable, seasonal (A/X) | Exponential smoothing (Holt-Winters), ARIMA |
| Trending | Holt's linear / damped trend |
| Intermittent, lumpy (C/Z) | Croston's method, SBA |
| Rich external signal | ML / AI forecasting (gradient boosting, etc.) |
Let the system pick best-fit per SKU against a holdout period. Don't hand-tune 4,200 SKUs. Hand-tune the 200 that drive 80% of revenue. Owner: planning analyst. Deadline: week 1.
Step 3: Run the demand review with sales and marketing
This is where the forecast becomes a plan. Get sales, marketing, and the planner in a room (or a shared model) and layer in what the math can't see:
- Promotions and price changes on the calendar
- Known account wins and losses
- New product launches and the SKUs they'll cannibalize
- Channel and customer shifts
The planner's job here is to bias-correct sales optimism. Track each rep's historical bias and discount accordingly. If sales has been 18% high for six quarters, their input gets a haircut. Owner: demand planner. Deadline: week 2.
Step 4: Build the consensus number
Reconcile the statistical baseline and the sales intelligence into one number. Document every override and why — "+2,000 units, Q3 Costco promo, confirmed PO." The override log is gold later, because it tells you whether your adjustments help or hurt accuracy.
The rule: no orphan numbers. There is one demand plan, by SKU, by location, by time bucket. Not a sales number and a planning number. One. Owner: demand planner, arbitrated by S&OP lead. Deadline: week 2.
Step 5: Reconcile against supply and finance
A demand plan you can't build or fund isn't a plan, it's a wish.
- Supply review: can the plant and suppliers actually deliver this mix? Where it can't, the constraint goes back to demand for re-prioritization.
- Finance review: does the plan roll up to the revenue and margin the P&L needs? If there's a gap to target, name it now — don't let it surface in the board meeting.
This is the S&OP handshake. The demand plan, the supply plan, and the financial plan are the same plan in three views. Owner: S&OP lead. Deadline: week 3.
Step 6: Commit in executive S&OP
Leadership signs the number. This is a decision meeting, not a status update. The agenda is exceptions and trade-offs only:
- SKUs where demand and supply can't reconcile — what do we serve, what do we let slip?
- The gap to the financial plan and what closes it
- Risk items and the scenarios around them
When the executive team commits, the number is locked for the period. Everyone downstream executes off it. No re-litigating in week 2. Owner: GM / VP Supply Chain. Deadline: week 4.
Step 7: Measure, then close the loop
The step everyone skips. Compare the committed plan to actuals and dissect the misses:
- Forecast accuracy / WMAPE, weighted by revenue
- Bias — chronic over or under is your most fixable problem
- Plan attainment — did the decision hold, or did execution drift?
- Forecast value add — did human overrides beat the naive statistical baseline? If your overrides make accuracy worse, stop making them.
Feed every lesson back into step 1. Demand planning is a loop, not a line. The teams that compound are the ones who run the post-mortem every single month. Owner: demand planner. Deadline: week 1 of next cycle.
The cadence at a glance
| Week | Steps | Output |
|---|---|---|
| Week 1 | Data clean, statistical baseline, prior-month measure | Clean forecast + last cycle's accuracy |
| Week 2 | Demand review, consensus number | One reconciled demand plan |
| Week 3 | Supply + finance reconciliation | Buildable, fundable plan |
| Week 4 | Executive S&OP commit | Signed, locked number |
The whole thing runs in four weeks and resets. The discipline beats the sophistication every time — a simple process run religiously crushes a fancy model run sporadically.
See your process graded against this
We'll map your current process against these seven steps, flag exactly which one is leaking accuracy, and run a stranded-inventory teardown on your actuals so you can see the dollar cost of the gap. It's free, and it takes one quarter of your shipment and inventory data. Book a 30-minute call and we'll show you which step is costing you the most cash.
Let's see what's worth building first.
A 15-minute call: tell me where your AI or planning is stuck, and I'll tell you the one thing worth building first — and whether it's worth doing at all.