Supply Planning vs Demand Planning
Demand planning asks what will sell. Supply planning asks what that costs in cash, capacity and lead time. How to build the second one, step by step, and what it catches that a forecast alone never will.
Most brands get reasonably good at demand planning first. It is the visible half: a number per SKU, a chart, a conversation with sales. Supply planning is the half that decides whether the number can be met — and most brands meet it for the first time on a Friday afternoon when a supplier says the minimum order is twice what the forecast justifies and the container leaves on Monday.
What is supply planning?
Supply planning is deciding what to make or buy, how much, and by when, so a forecast can actually be served. It starts from the demand plan and tests it against everything that decides whether units exist on a date: lead time, minimum order quantity, case pack, capacity, shelf life, and the cash the order commits.
| Demand planning | Supply planning | |
|---|---|---|
| The question | What will we sell? | How do those units exist in time, and what does that cost? |
| Main input | Sales history, promotions, retail commitments | The demand plan, plus supplier and capacity constraints |
| Output | Units per SKU per period | Dated purchase orders and production runs |
| Fails by | Forecasting the wrong number | Forecasting the right number and not being able to buy it |
| Owned by | Whoever knows the channels | Whoever talks to suppliers and watches the bank balance |
The distinction matters because the two failure modes need different fixes. A demand-planning failure is corrected with better history, a better method or a known event nobody entered. A supply-planning failure is corrected with an earlier order date, a different supplier, or a decision to hold more stock — and no improvement to the forecast touches it.
How does supply planning differ from demand planning?
The sharpest difference is that a demand plan has one answer per SKU per period and a supply plan has to satisfy several constraints at once, some of which contradict each other.
- The forecast is continuous; the buy is lumpy. Demand arrives a few units at a time. Supply arrives in case packs, pallets and containers, so the quantity you can order is rarely the quantity you need.
- Supply has a deadline the forecast does not. A forecast can be revised the day before the period. An order that had to be placed ten weeks ago cannot.
- Supply is a cash decision. The forecast is free. Acting on it moves money out well before revenue comes back, which is why a supply plan that ignores cash timing gets overruled.
- Constraints interact. A minimum order quantity that solves a supplier problem creates a warehouse problem, and a shelf-life limit can make the economically sensible buy the wrong one.
What does a supply plan actually contain?
One dated line per thing to be ordered or made, and the constraint that shaped it:
| Field | Why it is there |
|---|---|
| SKU or component | The level you place an order at, not the level you report at |
| Quantity | After netting, and after the supplier's case pack and minimum |
| Supplier or co-packer | Different lead times, different reliability, different minimums |
| Order-by date | Required arrival date minus lead time. The field that gets missed |
| Expected arrival | Used to check cover between now and then |
| Cash committed | Quantity times unit cost, dated at the order, not the sale |
Everything above is derivable from the forecast plus your own purchase order history. None of it needs a new system to exist; it needs to exist somewhere other than in someone's head.
How do you build a supply plan, step by step?
1. Start from a demand plan at the right level
Pull the forecast in units at SKU × channel, over a horizon longer than your longest lead time. What demand forecasting is covers producing that number; the only thing supply planning needs from it is that the horizon reaches past the lead time. A forecast that stops before your supplier's lead time cannot support a single order.
2. Net it against what you already own
Subtract what is on hand, what is already on order, and what is committed to someone else — a retail purchase order, a subscription run, a wholesale allocation. What is left is the genuine requirement. Most double-buying in small CPG comes from skipping the "committed" term.
3. Work backwards from the arrival date
For each requirement, take the date you need the units and subtract the lead time to get the order-by date. Use your own measured lead time from past receipts rather than the quoted one; they are different numbers, and lead time is the input most commonly taken on trust.
4. Apply the supplier's constraints
Round up to the case pack. Respect the minimum order quantity. Combine SKUs that ship from the same supplier into one order where that clears a minimum you would otherwise miss. What MOQ means, and when to eat a bigger buy is the decision underneath this step, and it is a carrying-cost decision rather than a unit-cost one.
5. Check capacity and cash
A plan that clears every supplier constraint can still fail on your co-packer's schedule or your bank balance. Lay the order-by dates against production slots and against expected cash, and move what has to move. Doing this now is cheaper than doing it after the deposit.
6. Add the buffer, then re-check cover
Safety stock sized from your own demand and lead-time variability raises each requirement, and the reorder point is what turns the plan into a trigger you can act on between planning cycles.
7. Re-run it on the cadence you order on
A supply plan is stale the moment a supplier confirms a different date. Re-run it weekly if you order weekly, and treat every change as an input to the next demand plan rather than as an exception.
What breaks a supply plan?
Quoted lead times
The most common single cause. A supplier quotes an average and you plan as though it were a guarantee. Measure the spread of your own receipts and plan against the spread.
Commitments nobody entered
Stock that is physically present and already promised is the quietest way to over-sell. If retail allocations and wholesale commitments live in someone's inbox, the plan will count them as available.
Components, not finished goods
If you make anything, the constraint is usually a component with a longer lead time than the product. Forecasting finished goods and buying components off the same numbers understates what has to be ordered and when.
Treating retail like a run rate
A retail launch order is a one-off; the replenishment behind it is the run rate. Planning supply as though the launch quantity repeats every period is how brands end up long on a SKU immediately after a good win.
Where Planster fits, and where it doesn't
Planster builds one demand forecast across DTC, Amazon, retail and wholesale from data pulled out of 150+ systems, then nets it against what is on hand, on order and already committed and turns what remains into a reorder point, an order quantity and an order-by date per SKU. That netting step is the supply plan, and it is the engine the rest of the product runs on. On top of it, Master Plan prices a scenario — a bigger buy, an earlier order, a second supplier — before you commit to it, and the overnight run brings you a ranked list each morning with the purchase orders already drafted. You open Planster, change what you want changed, and approve. Nothing reaches a supplier until you do. Flat $1,000/month, for consumable CPG brands between $10M and $50M.
Where it does not help: it is not a manufacturing execution system and it does not schedule a production line hour by hour. If your constraint is machine sequencing rather than what to order and when, this is the wrong tool. And if you have a handful of SKUs, one supplier and one channel, the seven steps above are genuinely a spreadsheet job — automating them will not be what changes your results. See pricing for the whole number on one page.