Salta al contenuto principale

Where Did $90 Billion in Inventory Just Go? A Small Retailer's Guide to Booking Shrinkage Correctly

9 minuti di letturaMike ThriftMike Thrift
Where Did $90 Billion in Inventory Just Go? A Small Retailer's Guide to Booking Shrinkage Correctly

Walk into the back office of almost any small retail shop and ask the owner one question: "What's your shrink rate?" Most will shrug. A few will guess. Almost none will have a real number, because most small retailers only discover inventory shrinkage the way you discover a leaky pipe — after the damage is already done, usually at year-end when the physical count doesn't match the books and nobody can say why.

That gap isn't a rounding error. U.S. retailers lost somewhere between $90 billion and $112 billion to inventory shrink in the most recent reporting cycle, according to industry loss-prevention benchmarks — and the retail sector's average shrink rate now sits around 1.6% of sales. For a shop doing $800,000 a year in revenue, that's roughly $12,800 in inventory that simply vanished. Not returned. Not refunded. Gone, and often never recorded as anything more specific than "cost of goods sold ran a little high this quarter."

Here's the part that should really bother small business owners: most of that loss is preventable, and almost all of it is trackable — if you're willing to treat shrinkage as a line item instead of a mystery.

What "Shrinkage" Actually Means (And Why the Term Undersells It)

Inventory shrinkage is the difference between what your books say you should have on the shelf and what's actually there when you count it. It sounds clinical, almost accidental — like inventory just "shrank" on its own. In reality, shrink is an umbrella term for several very different problems, each with a different fix:

  • Shoplifting — external theft by customers. Self-checkout lanes show a shrink rate around 3.5%, compared to roughly 0.2% at staffed registers, which tells you something about where the exposure concentrates.
  • Employee theft — internal theft, including outright stealing and "sweethearting" (giving friends unauthorized discounts or free items by manipulating the point-of-sale system). Employee theft accounts for close to 29% of total shrink and averages around $1,890 per incident when caught.
  • Organized retail crime — professional theft rings targeting resellable, high-value merchandise, responsible for roughly 10% of shrink industry-wide.
  • Administrative and operational errors — pricing mistakes, mis-shipped goods, receiving errors, damaged stock never written off, and cycle-count discrepancies. This bucket alone accounts for around 20% of shrink, and it's the category small retailers are most likely to be able to fix immediately, because it's not a crime — it's a process gap.
  • Vendor fraud — short shipments, invoice discrepancies, and billing for goods that never arrived.

Add it up and roughly 70–75% of total shrink traces back to causes a small business can actually influence with better process, not just better cameras. That reframes the whole problem: shrinkage isn't primarily a security issue, it's a bookkeeping and operations issue wearing a security issue's clothes.

The Real Mistake: Burying Shrink Inside COGS

Here's where most small retailers go wrong, and it has nothing to do with theft prevention. It's an accounting habit.

When the year-end physical count comes up short, the easiest thing to do is quietly adjust the inventory asset account and let the difference flow into Cost of Goods Sold. Technically that's not wrong — shrinkage is a cost of doing business, and it does belong somewhere in COGS territory. But when you dump it into the same COGS bucket as your actual product costs, you lose the ability to see it. Gross margin looks a little softer than it should, you can't tell if the problem is pricing, purchasing, or theft, and — critically — you have no data trail to act on next year.

The fix is a simple structural change: give shrinkage its own account.

Instead of this:

Debit: Cost of Goods Sold          $500
Credit: Inventory Asset                    $500

Do this:

Debit: Inventory Shrinkage Expense $500
Credit: Inventory Asset                    $500

Both entries reduce your inventory asset by the same amount. The difference is that the second one shows up as its own line on your income statement (or at minimum, its own tagged account you can report on separately), so at any point you can pull a report and see: how much did we lose to shrink this quarter, and is it going up or down?

A few rules of thumb for applying this correctly:

  1. Record shrinkage in the period it's discovered, not when you suspect it happened. If a cycle count in March reveals a discrepancy, that adjustment belongs in March's books, matched against March's revenue.
  2. Distinguish a write-down from a write-off. If damaged or obsolete inventory still has some resale value (discount rack, liquidation sale), write it down to that lower value rather than to zero. If it's genuinely worthless — spoiled, destroyed, unsellable — write it off completely.
  3. Set a materiality threshold. A $40 discrepancy from a miscounted box of pens doesn't need forensic investigation. A $4,000 discrepancy in a single SKU does. Decide in advance what dollar or percentage threshold triggers a deeper look, so you're not treating every variance as equally urgent.
  4. Tag it by cause when you can. Even a rough split — "known damage," "suspected theft," "count error" — turns your shrinkage account from a single number into a diagnostic tool.

Counting: The Habit That Makes Everything Else Possible

You can't book what you don't measure, and this is where most small retailers fall down before the accounting even comes into play. If your only inventory count happens once a year — often rushed, often after-hours, often the thing everyone dreads — you're not managing shrink, you're documenting it after the fact.

Physical inventory counts (counting everything, typically once or twice a year) are still necessary for year-end reporting and tax purposes. But they're a blunt instrument: by the time you find a discrepancy, it could have been building for eleven months, and you have no way to know when it happened or why.

Cycle counting — counting a subset of inventory on a rolling schedule throughout the year — is the practice that actually catches problems while they're still small and traceable. A practical approach for a small shop:

  • Rank your SKUs by value or velocity (the classic "ABC" split): your top 20% of items by revenue or turnover get counted monthly, your middle tier quarterly, and your slow-movers once or twice a year.
  • Keep counts small. Ten to twenty SKUs a week is enough to build a real pattern without turning it into a part-time job.
  • Compare every cycle count against the book quantity immediately, not at month-end. A discrepancy you investigate the same week is solvable; one you investigate three months later is a guess.
  • Log every discrepancy somewhere durable — even a simple spreadsheet with date, SKU, expected quantity, actual quantity, and suspected cause — before it gets adjusted in the books. That log is what turns "we lost some inventory" into "we lose the most inventory in category X, in the two weeks after we run a promotion," which is an insight you can actually act on.

This is exactly the kind of record-keeping that plain-text, version-controlled bookkeeping is built for. When your shrinkage entries live in a plain-text ledger, every adjustment is timestamped, attributable, and diffable — you can literally see the history of every inventory correction you've ever made, which account it hit, and when. That's a very different experience from digging through a black-box software's audit log trying to reconstruct what happened six months ago. Beancount.io gives you exactly that kind of transparent record for every inventory adjustment, alongside the rest of your books.

Where to Actually Focus, Given Limited Time and Budget

Small retailers don't have loss-prevention departments. You have maybe a few hours a month to spend on this. Here's where that time returns the most:

Fix self-checkout exposure first, if you have it. The gap between self-checkout shrink (roughly 3.5%) and staffed-lane shrink (roughly 0.2%) is enormous. If you run self-checkout, even lightweight measures — visible camera coverage, random receipt checks, weight-verification at checkout — close a disproportionate amount of the gap relative to the effort.

Address administrative errors before you address theft. It's tempting to focus on theft because it feels like the "real" problem, but the roughly 20% of shrink caused by pricing errors, receiving mistakes, and count discrepancies is the easiest to fix and the least emotionally loaded. Standardizing your receiving process — checking every shipment against the packing slip before it goes on the shelf — closes a surprising amount of the gap on its own.

Take employee theft seriously but proportionately. Sweethearting and register manipulation are hard to catch without deliberately looking for the pattern: unusual voids, unusual discount rates from a specific employee, unusual return volume tied to one register. Most point-of-sale systems can generate an exception report for these patterns — if yours can, review it monthly. This doesn't require accusing anyone; it just requires knowing the numbers.

Don't skip the paper trail on vendor shipments. A short shipment that never gets flagged looks identical, in your books, to shrink that happened on your own shelves. Reconciling receiving records against invoices closes that blind spot without any loss-prevention technology at all.

The Bottom Line

Shrinkage isn't a line item you write off once a year and forget. It's an ongoing signal about where your operation is leaking money — and like any signal, it's only useful if you're actually recording it in a way you can look back at. A retailer who books shrink into a dedicated account and counts inventory on a rolling cycle has a dashboard. A retailer who buries it in COGS and counts once a year has a surprise.

Keep Your Inventory Losses Visible, Not Buried

If shrinkage is hiding somewhere in your cost of goods sold right now, you're not alone — it's the default, not the exception. Beancount.io's plain-text accounting makes it straightforward to give inventory shrinkage its own tracked account, so every adjustment is transparent, version-controlled, and easy to audit later instead of disappearing into a single COGS number. Get started for free and see exactly where your inventory dollars are going.

Condividi questo articolo