Inventory shrinkage is the gap between what your records say you have and what is actually on your shelves. For the average Shopify merchant it silently erases 1–3% of revenue every year — and most never know it is happening.
Your inventory records show 200 units. You count the shelf. There are 183.
The missing 17 units did not sell. They did not get returned. They simply vanished — and with them, the revenue they would have generated and the cost you already paid to acquire them.
This is inventory shrinkage. It is one of the most underestimated financial drains in retail and ecommerce, and most Shopify merchants have no idea how much it is costing them.
Inventory shrinkage is the difference between your recorded inventory value and the actual physical inventory value, expressed as a percentage of total inventory.
Shrinkage Rate = ((Recorded Inventory − Physical Count) ÷ Recorded Inventory) × 100
If your system records £50,000 of inventory and a physical count finds £48,500, your shrinkage rate is:
((50,000 − 48,500) ÷ 50,000) × 100 = 3.0%
At 3%, a store doing £500,000 in annual revenue is losing approximately £15,000 per year to shrinkage — a number that would appear as lost margin with no obvious explanation.
Shrinkage is not just a cost. It causes phantom stock — your system believes you have units that do not exist, leading to oversells, failed fulfilment, and customer complaints. The operational damage often exceeds the direct financial loss.
Return fraud is particularly damaging because it creates phantom stock: inventory levels increase on return, but the returned item is unsellable — so you show stock that cannot actually be fulfilled.
Internal theft is harder to detect than external theft because the people who could notice it are often the people committing it.
Unlike theft, administrative shrinkage is not malicious. But it is just as financially damaging. A warehouse team that consistently counts 100 units as 102 or 98 creates compounding discrepancies over hundreds of shipments.
Supplier errors account for roughly 6% of shrinkage. Small on a percentage basis, but significant in absolute value on large purchase orders.
To calculate shrinkage accurately, you need two numbers:
1. Book inventory value: The total inventory value your system reports, calculated at cost price.
2. Physical inventory value: The total value of inventory actually counted, calculated at the same cost price.
The gap between them, expressed as a percentage of book value, is your shrinkage rate.
For ongoing monitoring, calculate shrinkage: - Per SKU: Identifies which specific products are most affected - Per location: Identifies whether shrinkage is concentrated in a specific warehouse, store, or fulfilment partner - Per time period: Identifies whether shrinkage is getting better or worse over time
A single store-level shrinkage figure tells you there is a problem. SKU-level and location-level data tells you where the problem is.
The reported shrinkage rate is only as accurate as your physical counts. Most merchants:
Count infrequently. An annual stock count means shrinkage accumulates for 12 months before it is detected. By that point, the source is almost impossible to identify, and the financial damage is done.
Count inaccurately. A rushed stock count — often done by staff who have other responsibilities — introduces new counting errors that can partially mask genuine shrinkage or create artificial shrinkage that does not exist.
Do not count at all for some SKUs. Many merchants do full counts on high-value products and spot-checks on low-value ones. Shrinkage in the uncounted SKUs is invisible until a customer order cannot be fulfilled.
Annual stock counts are compliance exercises, not shrinkage control. By the time you find the problem in an annual count, months of phantom stock have already been causing oversells, refunds, and customer complaints. The count confirmed damage that was already done.
Instead of one annual stock count, count a rotating subset of your inventory continuously throughout the year. Divide your SKUs into groups and count one group each week — so every SKU gets counted 4–6 times per year.
Cycle counting detects shrinkage earlier, requires less disruption than shutting down for a full count, and produces more accurate data because counts are smaller and more focused.
Prioritise your cycle count schedule by ABC class: Count Class A SKUs (your top revenue drivers) monthly. Count Class B quarterly. Count Class C semi-annually.
Count every inbound shipment against the purchase order before signing off receipt. Do not trust the supplier's packing slip — count the units physically.
A simple rule: no inventory update until the physical count matches (or is recorded as a discrepancy against) the PO. This eliminates supplier short-ship errors and creates an immediate record of any discrepancy for follow-up.
Every returned item should be: 1. Inspected immediately on receipt 2. Classified as resellable, damaged, or unsellable 3. Added back to inventory only if genuinely resellable 4. Written off if unsellable — never logged as sellable stock
The most common source of phantom stock from returns is skipping step 2–4: logging the return, incrementing inventory automatically, and never physically inspecting whether the item is actually fit to resell.
When a stock count reveals a discrepancy — even a small one — investigate it before the next count. Who handled that product? When? What was the receiving process? Is the discrepancy consistent with a specific SKU, location, or time period?
Uninvestigated discrepancies normalise shrinkage. Investigated discrepancies identify root causes that can be fixed.
Every manual adjustment to inventory should be logged with a reason code: damaged goods, supplier short-ship, customer return write-off, cycle count correction. Over time, these logs reveal patterns — which suppliers short-ship most often, which SKUs have the most damage write-offs, which time periods see the most adjustments.
Pattern data converts shrinkage from a monthly loss into a manageable, addressable operational problem.
Shrinkage and phantom stock are two sides of the same problem. Shrinkage creates phantom stock (your system shows units that do not exist), and phantom stock causes the customer-facing failures — oversells, failed fulfilment, incorrect availability displays — that shrinkage ultimately produces.
Reducing shrinkage is not just a financial exercise. It is what keeps your inventory records accurate enough to run your business on.
Inventory shrinkage is inevitable at some level — but 1–3% annual revenue loss is not. Most shrinkage is preventable with the right processes.
Calculate your current shrinkage rate. If you do not know it, your first priority is a full stock count. Move to cycle counting for ongoing detection. Verify every inbound shipment. Tighten your returns inspection process. Log every adjustment with a reason code.
Merchants who treat shrinkage as a background noise accept a permanent, unnecessary cost. Merchants who measure it, investigate it, and act on it consistently bring it below 0.5% — and keep it there.
CoreCaptain detects phantom stock, sync errors, and inventory discrepancies automatically. 14-day free trial, no credit card required.
Start Free Trial