Shrinkage is inventory that disappears between purchase and sale — through theft, spoilage, damage, or administrative error — expressed as a percentage of revenue or inventory value, and representing a direct, compounding distortion to every procurement calculation that depends on accurate inventory records.
Quick answers
What is shrinkage? Shrinkage is the gap between what your system says you have and what you actually have on the shelf. It has four causes: external theft (shoplifting), internal theft (employee), spoilage and damage (breakage, expiration), and administrative error (mis-scans, receiving mistakes, wrong counts). Every unit of shrinkage inflates your apparent demand, causing your procurement system to reorder based on sales that never happened.
What's a normal shrinkage rate? Retail average: 1.4% of revenue. Grocery: 2–3%. Restaurant food cost: 4–10%. If you have never measured shrinkage, assume you are at or above the industry average — operators who don't measure it are the ones most affected by it.
How does shrinkage affect procurement? Your POS records a sale, or your system records a receipt. When inventory vanishes between those events, the system interprets the gap as sales. Demand appears higher than it is. Safety stock is sized for phantom demand. Reorder points trigger early. You carry more inventory than you need, which increases carrying cost, which increases the next round of shrinkage through spoilage. It compounds.
How do you detect shrinkage? Cycle counts. Compare physical count to system quantity. The difference, aggregated across all items and periods, is your shrinkage rate. Without regular cycle counts, shrinkage is invisible until annual physical inventory — by which point twelve months of procurement math have been contaminated.
The formula
shrinkage rate (%) = (recorded inventory − physical inventory) / recorded inventory × 100
or equivalently:
shrinkage ($) = COGS_recorded − COGS_actual
annual shrinkage rate = shrinkage ($) / total revenue × 100
Shrinkage by source and industry
| Source | Retail avg | Grocery | Restaurant |
|---|---|---|---|
| External theft | 37% of total | 15% | 5% |
| Internal theft | 29% | 20% | 25% |
| Spoilage/damage | 12% | 45% | 55% |
| Administrative error | 22% | 20% | 15% |
| Total shrinkage rate | 1.4% of revenue | 2–3% | 4–10% of food cost |
In perishable businesses, spoilage dominates. In general retail, theft and admin errors dominate. The remedies are different: spoilage requires FEFO rotation and tighter ordering; theft requires physical controls; admin error requires process discipline at receiving and POS.
Worked example
A grocery store does $40,000/week in revenue with a 2.5% shrinkage rate.
- Weekly shrinkage: $40,000 × 0.025 = $1,000/week
- Annual shrinkage: $1,000 × 52 = $52,000/year
- Demand distortion: If average item cost is $4, shrinkage destroys ~250 units/week. The procurement system sees those 250 units as demand and reorders them. Over a year, the store procures $52,000 of inventory to replace goods that were never sold — inflating average inventory and carrying cost by the same amount.
- Compound effect on safety stock: The phantom demand raises σ (demand standard deviation). At a 95% service level with z = 1.65, an artificially inflated σ adds unnecessary buffer across every SKU. If shrinkage inflates σ by 10%, safety stock across the catalog is ~10% higher than optimal — thousands of dollars in excess inventory earning zero margin.
Why most operators get shrinkage wrong
- Treating it as a cost of doing business. "We budget 2% for shrinkage" is not a strategy. Measuring shrinkage by source reveals which portion is preventable and which is structural. Administrative error — the largest controllable component — is fixable with process changes at receiving.
- Only counting it at year-end. Annual physical inventory reveals shrinkage twelve months too late. Monthly or weekly cycle counts on high-value items catch discrepancies while the root cause is still diagnosable.
- Ignoring the demand signal contamination. Shrinkage is not just a P&L line item. It is a data quality problem. Every unit that vanishes without a corresponding sale corrupts the demand signal your entire procurement stack depends on — consumption rate, forecast accuracy, reorder timing.
- Not connecting shrinkage to decay rate. For perishable items, shrinkage and decay are intertwined. An item with a high decay rate and no FEFO discipline will generate spoilage shrinkage that looks like demand variability in the data. The fix is shelf-life-aware ordering, not bigger safety stock.
How LineNow handles shrinkage
- Flags inventory discrepancies when cycle count results are entered, calculating the shrinkage rate per item and per category automatically.
- Adjusts demand signals by separating verified sales (POS-confirmed) from inventory decrements that lack a corresponding sale event, so the consumption rate reflects actual customer demand rather than demand-plus-shrinkage.
- Tracks shrinkage trends over time by item, category, and location, surfacing items where shrinkage is accelerating or exceeds the category benchmark.
- Connects shrinkage to procurement impact — showing the dollar value of excess inventory carried due to demand signal inflation, so operators can quantify the ROI of shrinkage reduction efforts.
- Recommends count frequency based on item value and shrinkage history: high-value items with rising shrinkage get flagged for weekly counts; stable items stay on a monthly or quarterly cadence.
- Reports shrinkage as a percentage of revenue and COGS in the dashboard, broken out by category, so operators can benchmark against industry averages and track improvement quarter over quarter.
The net effect: shrinkage stops being an invisible line item absorbed at year-end and becomes a measured, managed metric with a direct connection to procurement accuracy.