Volume 13, Chapter 3
Shrinkage and Waste
Definition
Imagine a recurring small fabric shortfall gets quietly blamed on theft, an uncomfortable, unconfirmed suspicion that damages trust before anyone actually investigates. A closer look at the cutting process reveals the real cause: an outdated cutting technique leaves more waste than a newer method the team simply hadn't adopted yet. Nobody stole anything. The fix was training, not security, and it resolved the shortfall completely while clearing suspicion that was never warranted in the first place.
is inventory that disappears without a legitimate business reason, theft, unrecorded damage, or counting errors. Waste is inventory legitimately consumed or discarded as a normal part of production, offcuts, spoilage, defects. They look similar on a stock count (less than expected), but they need completely different responses.
If a stock count comes up short, the first question is: was this shrinkage or waste? Waste is an efficiency problem, solved by Volume 02's systems thinking and Volume 14's quality control. Shrinkage is a control problem, solved by Volume 11's internal controls. Treating one as the other wastes the fix.
Telling Them Apart
| Shrinkage | Waste | |
|---|---|---|
| Cause | Theft, unrecorded damage, counting/paperwork errors | Offcuts, spoilage, defective output, normal process loss |
| Is it expected? | No, it represents a control failure | Some level is normal and even planned for |
| Fix | Internal controls, segregation, access, counting discipline | Systems and quality improvements, better process, better training |
| Warning sign | A pattern with no production explanation | A rate that's higher than the documented, expected level |
Waste can be traced to a specific, documented cause. Shrinkage can't. If you can point to exactly where the missing inventory went (offcuts, a defect log), it's waste. If you can't, it's shrinkage, and it deserves a control review, not a shrug.
Setting an Acceptable Waste Rate
Waste isn't eliminated, it's measured and bounded. A documented, expected waste rate (e.g., "fabric waste should not exceed 8% of material used") turns "some waste happens" into a checkable KPI (a set number to measure against), anything meaningfully above that rate becomes worth investigating, exactly like Volume 07's budget-vs-actual discipline.
Example Story: The Shortage That Was Neither
Here's the full version of the fabric-shortfall story from the start of this chapter.
A recurring small fabric shortfall at MANIAC MINDZ was initially assumed to be theft, an uncomfortable, unconfirmed suspicion that damaged trust before any real investigation. A closer look at the cutting process revealed the true cause: an outdated pattern-cutting method left more waste than a newer technique the team hadn't yet adopted. The fix was a training update (Volume 06, Chapter 8), not a security measure, and it resolved the shortfall completely, while also clearing suspicion that had never actually been warranted.
Across Industries
| Business | Shrinkage Risk | Waste Consideration |
|---|---|---|
| Golden Crust Bakery | Unrecorded staff consumption of product | Unsold, unsellable end-of-day bread |
| Rapid Auto Works | Small tools going missing over time | Parts damaged during a difficult repair |
| Precision Print & Press | Unaccounted paper stock | Misprints and test runs |
Common Mistakes
As the example story shows, jumping to shrinkage without investigating can damage trust unnecessarily when the real cause is a process problem.
Without a baseline, there's no way to tell normal waste from a genuine, worsening problem.
"Some waste always happens" is true, but the rate is rarely fixed, better technique and training usually lower it over time.
Quiz Yourself
Practice Exercise
For your highest-shrinkage-risk inventory item, document an expected waste rate based on your actual process. Track actual loss against it for one month, and investigate any shortfall you can't explain.
Quick Summary
Quick Summary
- Shrinkage (unexplained loss) needs internal controls; waste (explained, process-related loss) needs systems and training improvements.
- The test: can the loss be traced to a specific cause? If yes, it's waste; if no, it's shrinkage.
- Set a documented, expected waste rate so deviations become checkable, not guessed at.
- Don't assume theft before investigating, the real cause is often a fixable process issue.