Inventory Shrinkage: Why Your Stock Count Never Matches the System
Shrinkage is the difference between the inventory your records say you have and what a physical count actually finds. It's rarely one single cause — it's usually a mix of theft, damage, administrative errors, and supplier discrepancies, each contributing a small piece to a total that adds up faster than most businesses expect.
Retail shrinkage typically runs between 1.5% and 2% of annual revenue — on a business doing $2M a year, that's $30,000–$40,000 disappearing without a clear line item to explain it.
Origins: from "inventory loss" to a tracked discipline
Shrinkage wasn't formally measured at industry scale until retail trade groups began coordinated benchmarking in the early 1990s, most notably the National Retail Security Survey, first fielded in 1991. Before that, loss was often absorbed silently into cost of goods sold with no dedicated line item — the survey era is what turned "some stock just goes missing" into a tracked, budgeted, and actively managed percentage.
Where it actually comes from
Shrinkage splits roughly into four buckets: theft (external or internal), damage during handling or storage, administrative errors (miscounts, mis-entered receiving quantities), and vendor fraud (paying for quantities that were never actually delivered). Most businesses assume theft dominates, but administrative error is often just as large a contributor.
Shrinkage in dollars
Shrinkage $ = Recorded inventory value − Physical count value
Expressing it as a rate — shrinkage $ ÷ total revenue — is what makes it comparable across periods and against industry benchmarks.
Why it hides so well
A single miscounted receipt or one damaged case doesn't move the needle. It's only when you compare a full physical count against system records, SKU by SKU, that the pattern becomes visible — which is exactly why businesses that only count once a year are usually the most surprised by the total.
Running a Shrinkage Audit
A shrinkage audit is a physical count run specifically to isolate loss, rather than just to true up general stock levels. It follows the same mechanics as a standard inventory audit, with a few things done deliberately:
- Compare the physical count against system records SKU by SKU, not just as a total dollar variance
- Separate the variance into the four causes — theft, damage, admin error, vendor fraud — instead of lumping it all into one "shrinkage" line
- Cross-check receiving records against purchase orders for the same period, since vendor discrepancies are easy to miss in a general count
- Flag categories or zones where the variance is concentrated, rather than only looking at the company-wide rate
Run this way, the audit tells you not just how much shrinkage happened, but where to actually point a fix.
A typical breakdown
Industry surveys generally attribute shrinkage to four sources in roughly this proportion, though it varies significantly by retail category:
| Cause | Typical share | Primary fix |
|---|---|---|
| Internal theft | ~35% | Access controls, separation of duties |
| External theft | ~30% | Physical security, high-value item placement |
| Administrative error | ~20% | Cycle counts, receiving verification |
| Vendor fraud | ~15% | Line-by-line PO matching |
Warning signs you have a shrinkage problem
- Physical counts consistently come in lower than the system, and not on the same SKUs each time
- Certain categories — small, high-value, easy-to-conceal items — are disproportionately short
- Receiving records rarely get double-checked against what was physically delivered
- Nobody can say what last year's shrinkage rate was, because nobody's tracked it as its own number
Shrinkage doesn't announce itself — it just quietly erodes margin until a physical count forces the gap into the open.
Cutting it down
The fix depends on the source: cycle counts catch administrative errors early, matching receiving quantities against purchase orders line by line catches vendor discrepancies, and basic access controls on high-value or easily concealed items address a meaningful share of theft. None of these require expensive security systems to start.
Prioritizing by value: shrinkage × ABC tier
Not every SKU needs the same level of loss-prevention attention. Cross-referencing shrinkage risk with ABC tier tells you where controls actually pay off: a small, high-value A-tier item is worth locking behind glass or tagging with an alarm; a bulky, low-value C-tier item usually isn't, even if it "walks off" occasionally.
Where to start
Waiting for an annual count means a full year of undetected discrepancies before you know there's a problem.
A quick count-and-check at receiving catches vendor shortages before they're buried in the system.
A rising trend in one category tells you exactly where to focus, instead of guessing across the whole catalog.
Limitations to keep in mind
- A single rate hides which SKUs — a healthy overall shrinkage percentage can still mask one category bleeding badly
- It's seasonal — theft and admin error both tend to spike around peak-season staffing and volume
- A perpetual system alone doesn't stop shrinkage — it only tracks recorded transactions, so theft and damage that never get logged are invisible until a physical count happens
Key takeaways
Shrinkage comes from theft, damage, admin errors, and vendor discrepancies combined — not just theft. A shrinkage audit that separates the variance by cause, run alongside regular cycle counts, catches most of it before an annual audit forces an unpleasant surprise.
See also
- Inventory audit checklist
- ABC analysis
- Perpetual vs periodic inventory
- National Retail Security Survey
Want to see this with your own company's data?
Upload your spreadsheet and get the analysis in seconds, for free.
