The short answer
A material shortage is what happens when the floor reaches for a part and it is not there. The instinct is to blame purchasing, but the cause almost always sits one step earlier, in planning: the requirement was calculated wrongly, or too late to act on. Preventing shortages is about knowing the exact quantity you are genuinely short of, in time.
Four mechanisms do that job together: net against stock and open supply so you plan the real shortfall, not the whole demand; run a reorder-level dashboard as a continuous safety net between cycles; set the planning parameters on each item — lead time, reorder level, order interval, procurement method — so the system knows when to act; and reserve stock to a plan so two plans do not double-allocate the same inventory. This guide works through each, grounded in how production planning software runs it.
Net requirement, not gross demand
Every shortage-prevention strategy rests on one calculation. For each item, at each BOM level, the requirement to act on is:
Gross demand is exploded through the BOM down to sub-assemblies, components and raw materials, and each level is netted against what you already hold and what is already coming. Whatever remains short becomes a suggestion — a purchase requisition to buy, or a work order to make in-house.
Purchasing on gross demand fails in two directions at once: buy the full quantity when stock or open orders already cover part of it and you pile up excess; ignore open supply and you cannot see a genuine shortage until it runs out. Netting removes both — you buy exactly the shortfall, in time.
| Approach | What it orders | Result |
|---|---|---|
| Order on gross demand | The full BOM quantity, ignoring stock and open orders | Excess + shortage Cash tied up, still runs out of untracked parts |
| Net vs stock only | Gross minus on-hand, but not open POs/WOs | Over-orders Re-buys what is already on order |
| Net vs stock + open supply | Only the genuine shortfall after everything already coming | Right quantity Buys the gap, no more, no less |
| Net + reorder dashboard | The shortfall, plus a live trigger between runs | Right qty, in time Drifts caught before they bite |
Planning parameters — when to act
Netting tells you how much is short; the parameters on the item master tell you when to act — the difference between a suggestion with room to breathe and one too late to place an order.
Lead time
The single most important parameter — how long replenishment actually takes, supplier lead time for a bought-out part or manufacturing lead time for what you make. If the run does not offset by it, it suggests ordering on the day you need the material. Real, measured lead times raise the requisition early enough to matter.
Reorder level and order interval
The reorder level is the threshold below which replenishment triggers; the order interval governs how often you place, batching to a weekly or monthly rhythm rather than a requisition per movement. Set them per item — a fast-moving fastener and a long-lead casting need very different rhythms.
Procurement method
Whether an item is bought, made in-house, or sent out decides which suggestion the plan raises — a purchase requisition, an in-house work order, or an outsourced one — routing the shortfall to the team who can clear it. Set it wrong and a shortage surfaces in the wrong queue, or not at all.
The last step keeps the loop honest: as purchase requisitions become POs, that open-PO quantity feeds back as open supply into the next run — automatic when planning, purchasing and inventory share one database, so the plan never re-orders what it already asked for.
The reorder-level dashboard as safety net
A formal MRP run is periodic, but consumption moves every day — an item can net out fine at the last run and be short a week later. The reorder-level dashboard catches those drifts: it runs continuously, independent of the planning cycle, listing every item whose free stock has fallen below its reorder level and suggesting a purchase requisition for each. It is the auto-PR safety net between runs, and a WhatsApp, email or SMS alert can fire the moment an item crosses its reorder point, so you are warned with lead time to spare.
- Continuous, not periodic — it watches free stock against reorder points every day, not only when a plan is rebuilt.
- Suggests, does not just warn — each below-reorder item carries a suggested PR, so the buyer acts in one click.
- Independent of the run — it protects the gap between cycles, where most surprise shortages are born.
- Alertable — a reorder breach can push a notification, so the buyer need not keep the dashboard open.
Stock reservation and double-allocation
Netting alone will not prevent this one. Two plans run against the same warehouse and both net against the same 400 units of a shared component, so both assume those units are theirs — until whichever draws first leaves the other empty. This is double-allocation, a shortage the numbers swore did not exist.
Stock reservation closes the hole. Reserved stock is committed to its plan and removed from the free pool the next run can see, so the second plan nets against what is genuinely available. A stock-reservation report makes it transparent — everyone sees which inventory belongs to which plan — so stores does not issue against a promise already spoken for.
Where a shortage actually came from
A mixed make-to-order shop kept losing a day here and there to a shared bracket that was "in stock" until it wasn't, while a low-value long-lead seal quietly ran out because purchasing bought to demand. The fix was not a bigger buffer — it was netting against open supply so redundant bracket orders stopped, putting the seal's real lead time on the item master so its reorder fired earlier, and reserving stock to each order so two jobs stopped drawing the same brackets. Three fixable gaps in the calculation, not bad luck.
Still firefighting shortages a bin at a time?
We can run your own BOMs and stock through a netted MRP calculation and show you the real shortfall, the reorder cockpit and stock reservation — in 30 minutes, on your own data.
The root dependency — BOM and stock accuracy
Every mechanism above still produces shortages if two things underneath are wrong: the bill of materials and the live stock figure. A mistyped reference, a stale BOM that never absorbed an engineering change, a quantity-per off by one — each silently skews the gross requirement, so the plan confidently asks for the wrong thing.
Live stock is the twin dependency: if the recorded balance drifts from the physical shelf, netting subtracts a number that does not exist. This is why the strongest prevention comes from a system where planning, inventory and production read the same stock and BOM tables. Keep the BOM current and stock honest — capturing consumption by barcode and machine-data capture rather than end-of-day memory — and the math finally has something true to work on.
Safety stock vs reorder level
These two get used interchangeably and are not the same. Safety stock is the buffer you hold to absorb variability — a late supplier, a demand spike, a rejected batch; it answers how much cushion to keep. The reorder level is the trigger: when free stock falls to it, replenishment is raised; it answers when to act to protect that buffer.
Set safety stock from how variable an item's demand and supply are — a reliable local supplier needs little, a single-source import with lumpy demand needs more. Then set the reorder level to cover expected demand across the lead time plus that safety stock, so replenishment lands while the cushion is still in hand rather than after you have eaten into it.
Festivals, OSL and India-specific realities
Two realities sit on top of the standard approach for Indian manufacturers. The first is seasonal and festival demand: order books swell ahead of Diwali, the wedding season, or a fiscal-year-end push, and a shortage that is a nuisance in a quiet month becomes a lost order in peak. The defence is forward planning — pull the spike into the sales plan early so netting offsets it by the full lead time, and raise reorder levels on the items that ride the season.
The second is outsourced (OSL) job-work. A large share of Indian components go out for processing — plating, heat treatment, machining — and each carries its own lead time that is a shortage source: a delayed job-worker starves the next operation as surely as a missing raw material. The component plan splits the netted make requirement into in-house semi-finished and outsourced lines. On compliance, job-work material is reported through ITC-04 under GST and the movement must reconcile with what the plan sent; a system that tracks OSL work orders gives you that trail, but the return is a compliance task — confirm it with your CA rather than treat any planning report as tax advice. Indicative INR pricing is on the pricing page.
How Fast Planning prevents shortages
Fast Planning Software — built by Improsys in Pune under the Fast Technology brand, cloud or on-premise — runs every mechanism in this guide from one planning run, because planning, inventory and production read the same item master, BOM and stock tables: no interface, no reconciliation between plan and shelf.
Downstream, work orders lay out on a DayPilot Gantt board by priority, the machine loading report shows where capacity is short, and plan-vs-actual and OEE dashboards close the loop — but it all starts with a netting run that knows what you need from what you already have.
Frequently asked questions
How do you prevent material shortages in manufacturing?
You prevent material shortages by planning against net requirement, not gross demand. Explode each finished good's demand through the BOM, then subtract stock on hand, open purchase orders, open work orders and reserved stock to find what is genuinely short — and raise a purchase requisition or work order only for that. Around the planning run, a live reorder-level dashboard watches free stock against each item's reorder point and suggests replenishment between runs, planning parameters on the item master (lead time, reorder level, order interval) set when to act, and stock reservation stops two plans double-allocating the same inventory. Accurate BOMs and live stock underpin all of it.
What is netting in MRP?
Netting is the core MRP calculation that turns gross demand into a real buy-or-make requirement. For each item the formula is Net requirement = Gross demand − Stock on hand − Open supply, where open supply is open purchase orders plus open work orders plus stock already reserved to another plan. Whatever is still short after netting becomes a suggestion: a purchase requisition for bought-out items and raw material, or a work order for items made in-house. Netting is what prevents you from buying material you already have on the shelf or already have on order, which is how gross-based purchasing creates both shortages and excess at the same time.
What is the difference between safety stock and reorder level?
Safety stock is the buffer you deliberately hold to absorb variability — a late supplier, a demand spike, a rejected batch. The reorder level is the trigger point: when free stock falls to it, the system raises a replenishment suggestion. The reorder level is usually set to cover expected demand across the replenishment lead time plus the safety stock, so that by the time new material lands you have drawn down to roughly the safety buffer, not to zero. Safety stock answers how much cushion to keep; reorder level answers when to act to protect it.
How does a reorder-level dashboard prevent shortages?
A reorder-level dashboard is a continuous safety net that runs between formal planning cycles. It lists every item whose free stock has fallen below its reorder level and suggests a purchase requisition for each, so replenishment is triggered by the threshold rather than by the next MRP run. That matters because demand and consumption move every day: an item can be fine at the last run and short a week later. The dashboard catches those drifts as they happen, giving the buyer lead time to act before the shortage reaches the shop floor and stops a work order.
Why does purchasing on gross demand cause both shortages and excess?
Purchasing on gross demand ignores what you already have and already have coming. Buying the full gross quantity when stock or open orders already cover part of it piles up excess and ties cash in inventory. But the same blindness cuts the other way: without netting against open supply you cannot see that an item is genuinely short until it runs out, and without a reorder trigger between runs a fast-moving part slips through. Netting against stock and open supply, plus a live reorder level, is what removes both failure modes — you buy exactly the shortfall, no more and no less, and you buy it in time.