Inventory Stress Testing for Mid-Market Manufacturers
How to run a useful inventory stress test without a full planning team — the four scenarios that matter most, and how to read the burn-down curve before it forces a customer call.
Why mid-market needs this now
Stress testing has historically lived in enterprise S&OP teams with full-time planning analysts. That's no longer where the risk is. Mid-market manufacturers run leaner inventory, depend on fewer suppliers per part, and have less margin to absorb a missed week. They need stress testing the most — but in a form that doesn't require a planning org to run.
What an inventory stress test actually is
An inventory stress test asks one question, applied across your top SKUs: if a specific disruption hits this part right now, when does our cover run out? The output is a burn-down curve over time, not a static days-of-cover number.
The reason a curve matters is that days-of-cover hides the shape of the problem. Two SKUs with the same 28-day cover behave very differently if one has steady demand and one has a customer commitment landing in week three.
The four scenarios that matter
You don't need twenty scenarios. You need four that map to disruptions you've actually seen:
- 1Single supplier outage — your primary supplier for this part is offline for 4 weeks.
- 2Lane disruption — the route this part travels on is delayed by 2 weeks.
- 3Demand surge — a customer pulls forward 30% of next quarter's demand into the next 30 days.
- 4Quality hold — a recent batch is held pending re-qualification, removing 3 weeks of usable inventory.
The minimum inputs you need
To run a credible stress test you need only six inputs per SKU:
- On-hand inventory at the consuming plant.
- In-transit inventory and its expected receipt dates.
- Average daily demand over the trailing 60 days.
- Confirmed customer commitments by week for the next 90 days.
- Primary supplier lead time, in calendar days.
- Qualified backup lead time — or the cost of expedite if no backup exists.
If any of these inputs is missing for an SKU, that SKU itself is an audit finding before the stress test can produce useful output. Visibility gaps have to close first.
Reading the burn-down curve
For each scenario, the curve plots projected on-hand cover over time, given the simulated disruption. The three things to read on the curve are:
- The first day projected on-hand crosses safety stock.
- The first day projected on-hand crosses zero — the stockout date.
- Whether any customer commitment lands between those two dates — that's the specific shipment that breaks.
The narrative output of the test is one line per SKU: "In a single-supplier outage scenario, SKU 21340-A stocks out on day 18, which lands inside the customer commitment for Acme on day 16."That sentence is what gets a procurement team to act.
Thresholds that trigger action
Define action thresholds before you run the test, so the result drives a decision and not a debate:
- Stockout inside 14 days under any scenario → expedite or activate backup supplier this week.
- Stockout inside 30 days under two or more scenarios → open a sourcing review for this part.
- Stockout inside 60 days under the supplier-outage scenario → re-qualify a backup or build buffer.
Common traps and how to avoid them
- Averaging away spikes. Use trailing 60-day demand and known commitments — averaging hides the customer call that actually triggers the stockout.
- Trusting the backup that hasn't shipped. Score backup lead time only if the backup has shipped a qualified part inside 12 months.
- Stress testing only A-class SKUs. A B-class part with a single source and a long lead time can stop a finished good as fast as an A-class part. Score by criticality, not revenue.
- Producing a report nobody acts on. If the test isn't tied to a defined action threshold, the test is theatre.
Operating cadence
Run the four scenarios on the top 50 SKUs every two weeks. Run them on the full critical SKU list monthly. Re-run any specific SKU on demand when a disruption signal hits its supplier or its lane. That cadence is enough for most mid-market operations to stop being surprised.
Run this audit against your real supplier list.
Bring a BOM, supplier list, or even a flat CSV — ChainsSignal returns a first dependency map and the top exposures within a working day.