The gap master planning fills
A supply chain has decisions operating at three very different time horizons. At the long-term end, network design decides where plants, warehouses and distribution centres should physically sit, and what capacity they should have — decisions that lock in for years because they involve buildings, leases and equipment. At the short-term end, day-to-day scheduling decides which specific order gets picked, which truck it goes on, and which shift on the factory floor produces it today. Between those two sits a gap: given the network we already have, and the demand plan we have agreed for the coming months, how much should each part of the network actually produce, procure, hold and ship?
That is the decision situation master planning exists to solve. It typically runs on a rolling horizon of somewhere between 3 and 18 months, re-planned regularly (often monthly) as new information — actual sales, updated forecasts, supplier lead-time changes — comes in. It sits below strategic network design (which it treats as fixed, at least for the horizon in question) and above detailed scheduling (which it constrains but does not dictate down to the individual order).
The decision: how much, where, and how to move it
At its core, master planning answers a deceptively simple question across an entire network at once: given the demand plan, how much should each plant produce or each distribution centre procure, in each period, and how should product flow between locations, so that demand is met at the lowest achievable total cost without breaching any capacity constraint? "Total cost" here is not just production or purchase cost — it includes holding stock, transporting between locations, and, where relevant, the cost of ramping production up or down.
Typical objectives that master planning balances against each other include minimising total network cost, hitting agreed customer service targets (not running out of stock in a region because volume was allocated elsewhere), and — in manufacturing settings — smoothing production or workforce levels over time rather than swinging wildly between overtime and idle capacity from one month to the next. These objectives often pull in different directions: the cheapest plan on paper might starve one region of stock, so master planning is as much about finding an acceptable trade-off as it is about finding the mathematically cheapest answer.
Capacity itself is rarely a single hard number. Production capacity can often flex, at a cost, through overtime, an extra shift, or a subcontractor — master planning has to weigh whether paying for that flex is cheaper than the consequence of not meeting demand in that period. Transport and warehousing capacity behave the same way: a distribution centre can absorb a short-term surge by paying for overflow storage, and a carrier lane can absorb extra volume at a premium rate during a peak. Part of what makes master planning genuinely valuable, rather than just an arithmetic exercise, is surfacing exactly where and when these trade-offs need to be made — early enough that the business has time to act on them, rather than discovering a shortfall the week it was due to ship.
Why aggregate, and how the roll-up and cascade work
Master planning deliberately works at an aggregate level — product families rather than individual SKUs, regions rather than individual customers or stores — for the same reason demand planning does: aggregated numbers are more stable, more forecastable, and computationally far more manageable than trying to jointly optimise every SKU-location-period combination at once, which for any real network runs into an unmanageable number of combinations. Planning a "furniture" family's total volume across a region is a tractable, meaningful decision; planning the exact quantity of every individual chair colour and finish for every single store, three months out, is not just harder — it is usually not even a decision worth making that far in advance, because it will change many times before it matters.
This is why master planning relies on a two-way translation between detail and aggregate. Detailed demand at SKU and location level is first rolled up into planning-friendly groups — product families, regional totals — where the aggregate plan is calculated. That aggregate plan is then cascaded back down, or disaggregated, into detailed, executable numbers (specific SKUs, specific locations, specific weeks) using historical or planned splits, close to when those numbers are actually needed for execution. The aggregate plan is the stable skeleton; the disaggregated detail is filled in progressively, and with more confidence, as the horizon gets shorter.
The choice of how to group products into families is itself a judgement call, not a mechanical exercise. A useful family groups items that behave similarly — similar demand pattern, similar production process or supplier, similar transport profile — so that an aggregate decision about the family translates sensibly down to its members. Group dissimilar items together purely because they happen to sit in the same accounting category, and the aggregate plan can look perfectly balanced while individual members are badly over- or under-supplied once disaggregated. Getting this grouping right is one of the quieter but more consequential design decisions behind a master planning process, and it usually needs revisiting as a product range evolves.
Rolling horizon and the frozen zone
Because demand forecasts, supplier conditions and internal capacity all keep changing, master planning is never done once and left alone — it is replanned on a rolling basis, typically monthly, with each new run extending the horizon out by another period and refreshing all the numbers in between with the latest information. A plan drawn up in January for the next 12 months is not meant to survive unchanged until December; it is meant to be re-run in February with 11 months (plus one new month) of updated data.
If every replan could freely rewrite every period, though, operations would never be able to commit to anything — a purchase order confirmed last week could be silently reshuffled by this week's replan. To prevent this, mature master planning processes deliberately "freeze" the near-term portion of the plan (commonly the next one to a few periods) so that operational commitments already made — orders placed, production already scheduled — are protected from being overwritten by every new planning run. Only the portion of the plan beyond the frozen zone is genuinely open to revision. This frozen-zone discipline is what allows a rolling plan to stay responsive further out while still being stable and trustworthy close in — the same tension between responsiveness and stability that shows up in the bullwhip effect, where over-eager replanning amplifies noise instead of damping it.
How master planning relates to S&OP
It is easy to conflate master planning with Sales and Operations Planning (S&OP), but they are different layers of the same picture. S&OP is the cross-functional business process — the recurring meeting cadence where sales, operations, finance and supply chain leaders come together, review the demand plan against the supply plan, resolve conflicts (not enough capacity to meet the sales team's number; too much inventory sitting in one region), and formally sign off on one agreed plan for the business to execute against.
Master planning is the quantitative engine that produces the supply-side numbers those S&OP meetings actually review. Without a master plan, an S&OP meeting would be reviewing opinions rather than a calculated, capacity-aware allocation of production, procurement and inventory across the network. Without S&OP, a master plan would be a purely technical output with no cross-functional sign-off — accurate in isolation, perhaps, but never actually reconciled against the commercial reality sales and finance are seeing. The two need each other: S&OP is the governance and decision-making forum, master planning is the numbers it governs.
The South African angle: committing container volume months before the order exists
Consider a South African distributor running three regional distribution centres, sourcing the bulk of its range from a single Asian supplier via ocean freight. Four months out, this business has to decide, at an aggregate level, roughly how much container volume to commit for the coming quarter and how to provisionally split that volume across its three DCs — long before individual customer orders exist to justify the exact numbers, the same up-front commitment discussed from a buying perspective in our festive-season import planning guide. Commit too little container capacity and the business risks a stock-out it cannot fix quickly, given ocean transit and customs-clearance lead times; commit too much, tied up in a specific regional split, and it risks sitting on excess stock in one DC while another runs short.
This is master planning in its purest form: an aggregate, forward-looking decision (total container volume, rough regional allocation) made under real capacity and lead-time constraints, based on the demand plan rather than firm orders, with the detailed SKU-and-store allocation only finalised much closer to actual arrival. The distributor's master plan does not need to know yet exactly which SKUs go on which container — it needs to know how much total volume and shelf space to reserve, region by region, so that when real orders do start to firm up, there is enough supply in roughly the right place to fill them.
Frequently asked questions
How is master planning different from network design?
Network design is a long-term, infrequent decision about where plants and distribution centres should physically exist and what capacity they should have — it takes the network's structure as something to be built. Master planning takes that structure as a given, fixed input, and works out, month to month, how much to actually produce, procure and move through the network already in place.
Why doesn't master planning just plan at the individual SKU and store level directly?
Planning every SKU at every location for every period several months out is both computationally unmanageable and largely pointless, because detailed demand at that level is volatile and will change many times before it matters. Aggregating into product families and regions produces a more stable, forecastable plan, which is then cascaded down into detail only as the horizon gets closer and the numbers become more certain.
What does "freezing" part of the plan mean, and why bother?
Freezing means locking the near-term portion of a rolling plan so that commitments already made — orders placed, production already scheduled — are not silently rewritten every time the plan is re-run. Without a frozen zone, operations could never trust a plan long enough to act on it, because it might change again next week.
Is master planning the same thing as S&OP?
No. S&OP is the cross-functional business process and meeting cadence where sales, finance and operations review and approve a plan. Master planning is the quantitative, capacity-aware supply plan that S&OP reviews — the numbers behind the meeting, not the meeting itself.