Leak 22 · Inventory & Working Capital - Excess safety stock
Safety stock set once, by feel, for every item. It protects against a stockout that stopped being likely years ago and ties up cash doing it.
Diagnostic note. Symptoms, the records to bring, and a practical first check with your team.
What is it?
Safety stock should reflect how variable demand and lead time are for each item. In practice it is often a fixed number of weeks applied to everything, or a number set after one bad stockout and never revisited. The result is too much stock on stable items and, often, too little on volatile ones.
- Family
- Inventory & Working Capital
- Primary owner
- Inventory Manager
- Secondary owners
- Purchasing Manager, CFO
- Primary impact
- Working capital
- Typical data source
- ERP replenishment settings, demand and lead-time history
- Detection difficulty
- 30-day measurability
Ask yourself
Are safety stock levels calculated from demand variability and lead time, or set by hand and rarely changed?
Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.
What does it look like?
Look for these patterns, then use the check below to trace the issue in your own records.
- The same safety stock rule for all items regardless of demand pattern.
- Stable, high-volume items with months of buffer.
- Settings last reviewed at the ERP implementation.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| Item safety stock and reorder point settings |
| Monthly demand history for 24 months |
| Supplier lead time actuals |
| Service level target, if defined |
The initial check
Start with a small sample. Ask the person who owns the records to gather the exports and agreements, then work through these steps together.
- 1Export your top 200 items by inventory value with safety stock settings and 24 months of monthly demand.
- 2For each, compare safety stock to one month of average demand.
- 3Sum the value of safety stock above one month on items whose monthly demand varies by less than 25%.
Excess safety stock value = Σ (safety stock − justified buffer) × unit cost, for low-variability items
Then ask one question: Who set these levels, and what were they protecting against?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Excess safety stock value × carrying cost rate, net of any stockout cost avoided
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No periodic review of replenishment parameters.
- Data
- Demand variability and lead-time actuals are not calculated.
- Technology
- The ERP’s replenishment settings are static fields, not calculated from history.
What should we do?
Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.
Level 1
Visibility
A report of safety stock value versus demand variability by item.
Level 2
Policy
Service level targets by item class, and a quarterly parameter review.
Level 3
Calculation
Safety stock calculated from demand and lead-time variability and written back to the ERP for review.
Where AI helps
- Forecasting demand for items with seasonality or customer-specific patterns that a simple average misses.
Where AI probably doesn’t
Standard safety stock math handles most items. Use it before anything more elaborate.
Before you call it a leak
- Cutting safety stock on the wrong items causes stockouts on high-value SKUs. Do it class by class, and measure fill rate as you go.
Think this might be happening in your business?
Turn the finding into a next step.
If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.
Related leaks
- Leak 20 · InventorySlow-moving inventoryStock that turns once every three years ties up cash, takes space, and eventually becomes dead. The ERP already knows which items. Nobody has asked it.
- Leak 23 · InventoryStockouts on high-value SKUsThe fast, high-margin item is out again. The customer buys elsewhere, and the sale is never recorded because it never happened.
- Leak 25 · InventoryPoor inventory transfer decisionsStock shipped between branches to cover a shortage, then shipped back when the shortage is over. Freight both ways, and no one is counting.
Let’s start with one thing.
Give your team more time for the work that needs them.
Show us the quoting, order-entry, or follow-up work that keeps piling up. We’ll map it with you and find a practical place to start.
Start with a free workflow conversation with Alex.