Shrink is not just theft. It's receiving mistakes, mis-tags, no-notes comps, and bad handoffs. Here's a small-business loss prevention system you can run weekly using POS roles, inventory adjustments, exception reports, and simple habits that do not ruin the customer experience.

Shrink is one of those words that sounds abstract until you do the math.

If your gross margin is 40% and you lose 2% of sales to shrink, that is not a 2% problem. That is a "we just donated 5% of our gross profit" problem. And in many small businesses, that 5% is the difference between feeling in control and feeling like the business is constantly squeezing you.

Here is the honest take from an operator point of view: shrink is rarely one thing. It is a bundle of small failures that stack up:

  • Receiving counts are off
  • Returns are processed with sloppy reasons
  • Discounts get used as a social lubricant
  • Inventory adjustments happen with no notes
  • Cash handling rules drift over time
  • Sometimes, yes: theft

The solution is not to become paranoid. The solution is to build a system where mistakes are visible early, and where the same few exceptions do not repeat forever.

This post outlines a practical loss prevention system for small teams. It is designed for real life: busy shifts, part-time staff, and owners who cannot spend two hours a day auditing reports.

The mindset shift: shrink is a workflow, not a villain

When teams talk about shrink, it often becomes a moral conversation. That is emotionally satisfying and operationally useless.

A better question is: Where can an item leave the building without leaving a reliable record?

Those gaps are your shrink multipliers. Fixing one gap can reduce loss from multiple causes at once.

Step 1: Lock down the three high-risk actions

In most POS systems (and in most stores), three actions create a disproportionate amount of mess:

  • Inventory adjustments (especially negative adjustments)
  • Discounts / comps
  • Refunds / voids

Your goal is not to prevent them. Your goal is to make them accountable.

Rules that work for small teams

  • Adjustments require a reason. Not optional. Not "misc". If your system supports notes, require notes.
  • Discounts have named types. "Damaged", "Late order", "Customer recovery", "Employee meal". Give the team safe lanes.
  • Refunds require an itemized reason. Size issue, defect, wrong item, delivery late, duplicate charge, etc.

As a team, you are building a vocabulary. Your reports are only as good as your vocabulary.

Step 2: Create a weekly 20-minute audit (the owner version)

This is the audit you can actually sustain. Pick one day a week. Put it on your calendar. Do it when you are not in the middle of a rush.

A. The exception list

Pull these reports for the week:

  • All refunds
  • All voids
  • All discounts over a threshold (example: over 15% or over $10)
  • All inventory adjustments (especially negative)
  • Cash drawer over/short per shift (if you handle cash)

You are not reading every transaction. You are looking for patterns:

  • Same employee repeatedly doing the same exception
  • Same item repeatedly refunded or discounted
  • Same shift (Friday close) always over/short
  • Adjustments with blank notes

If you find a pattern, do not jump to blame. Ask: what is the broken process?

B. The top 10 shrink candidates

Pick your top 10 items by sales and top 10 items by value. Then look at on-hand counts versus what you would expect based on sales and receiving. You are looking for "fast drift" items:

  • Small, easy to pocket
  • Frequently handled (impulse items)
  • Frequently mis-scanned (similar UPCs)
  • Frequently damaged (fragile)

These become your cycle count targets for the next week.

Step 3: Fix the upstream causes (where most shrink is born)

A. Receiving: the silent killer

Most stores lose more money from sloppy receiving than from dramatic theft. The fix is a short receiving checklist:

  • Count the shipment (do not trust the invoice)
  • Scan to confirm the right SKU
  • Log discrepancies immediately
  • Do not shelve until the count is recorded

Engineer perspective: treat receiving like data ingestion. Garbage in, garbage out. If you ingest wrong counts, you will spend the rest of the month arguing with your own numbers.

B. Returns: make the reason useful

Returns are valuable operational data. If you track reasons consistently, you can spot:

  • Quality issues (same defect)
  • Training issues (wrong item selected)
  • Catalog issues (confusing names, wrong photos)

That is shrink prevention disguised as customer service.

Step 4: The culture piece (without being weird)

Loss prevention fails when it becomes accusatory. Good teams do it like safety checks: normal, expected, and emotionally neutral.

What works:

  • Tell the team why: "We audit so we can keep hours stable and prices fair."
  • Praise good notes and clean shifts
  • Fix system issues fast so the team believes the process matters

Using M&M POS to make shrink visible

A loss prevention system needs two things: permissions (who can do what) and visibility (what happened, when, and why).

If you want a POS foundation that supports operational discipline, start with M&M POS. Set up roles so high-risk actions are restricted, then run weekly exception reviews so patterns show up early. If you are ready to build the system, download M&M POS and start with the three actions: adjustments, discounts, and refunds.

One-page weekly checklist

  • Review exceptions: refunds, voids, big discounts, adjustments
  • Pick 10 SKUs to cycle count (fast drift)
  • Spot-check receiving on one recent shipment
  • Coach one repeated pattern (process fix, not blame)
  • Update one rule or note template to reduce ambiguity

Done consistently, this is how shrink stops feeling like a mystery and starts feeling like a manageable operational metric.