Shrinkage & Loss Prevention

Measure the gap between what you should have and what you do, then close the sources of loss.

4 lessons 35 min 5-question assessment 75% to pass

What you’ll learn

Define shrinkage and its main causes

Calculate a shrinkage rate

Apply controls that reduce loss

Investigate discrepancies by reason

Lesson 1 of 4 Reading 8 min

What shrinkage is

Shrinkage is the difference between the stock your records say you should have and the stock you actually count. It is inventory that has gone missing somewhere between receiving and sale.

It matters because shrinkage is pure lost margin — goods you paid for but will never sell. Unlike a markdown, you get nothing back; the cost falls straight through to the bottom line.

If your books say 500 units but a count finds 470, that 30-unit gap is shrinkage. At a cost of KES 800 each, that is KES 24,000 vanished with no sale behind it. Across a year and many SKUs, unnoticed shrinkage can quietly eat more profit than a bad month of slow sales.

Key takeaways

Shrinkage is the gap between recorded and counted stock.
It is inventory gone missing before sale.
It is pure lost margin with nothing recovered.
Example: a 30-unit gap at KES 800 each is KES 24,000 lost.

Lesson 2 of 4 Reading 9 min

Main causes

Shrinkage has a few usual sources: theft (external or internal), administrative error (miscounts, mis-keyed receipts), supplier short-shipments, and damage or spoilage. Most loss is a mix, not one villain.

Knowing the causes matters because the fix differs by source — a camera stops theft but not a data-entry error, and tighter receiving stops short-shipments but not spoilage. You cannot fix what you have not named.

A branch losing KES 24,000 a month might find half is mis-keyed receiving (an admin fix), a quarter is unrecorded breakage (a process fix), and a quarter is genuine theft (a security fix). Splitting the loss by cause turns a scary lump sum into three solvable problems.

Key takeaways

Causes: theft, admin error, short-shipments, damage.
Most loss is a mix, not a single villain.
Each cause needs a different fix.
Example: KES 24,000 may split across admin, breakage, and theft.

Lesson 3 of 4 Practice 9 min

Measuring the rate

The shrinkage rate is loss value divided by sales (or stock) over a period, as a percentage. It turns raw missing units into a number you can track and compare across branches and months.

Measuring matters because "we lose some stock" is not actionable, but "shrinkage is 2.5% versus a 1% target" is. A rate tells you whether a control is working and which branch needs attention.

If a branch sells KES 4,000,000 and loses KES 100,000 to shrinkage, that is a 2.5% rate. If the company target is 1%, this branch is losing KES 60,000 a month more than it should — a clear, ranked signal to investigate that branch first rather than spreading effort evenly.

Key takeaways

Shrinkage rate = loss ÷ sales (or stock), as a percentage.
It turns missing units into a trackable number.
Rates let you compare branches and months.
Example: KES 100,000 loss on KES 4M sales = a 2.5% rate.

Lesson 4 of 4 Reading 9 min

Controls that cut loss

Controls fall into prevention and detection: tight receiving checks, restricted access to high-value stock, scanning instead of manual entry, recorded reasons for every write-off, and regular cycle counts that catch loss early.

Controls matter because shrinkage compounds when unwatched — the longer a leak runs undetected, the more it costs. Frequent counts and recorded reasons turn a year-end shock into a weekly catch.

Cycle-counting high-value A-items weekly might catch a recurring 5-unit gap on KES 8,000 phones within days — KES 40,000 found early instead of KES 480,000 at year end. Pair that with scanned receiving (no mis-keys) and a locked aisle for top SKUs, and the same branch can pull its 2.5% rate back toward the 1% target.

Key takeaways

Controls are prevention plus detection.
Tight receiving, restricted access, scanning, recorded reasons, cycle counts.
Unwatched shrinkage compounds over time.
Example: weekly A-item counts catch a KES 40,000 gap early, not a KES 480,000 one.

| AWRA OpsHub

Shrinkage & Loss Prevention

What you’ll learn

Course content

What shrinkage is

Main causes

Measuring the rate

Controls that cut loss

Finished the material?

More in this path

Inventory Foundations

Warehouse & Locations

Units of Measure & Conversions

Need a quick answer while you read?

AwraIQ