Ask most retailers where their shrinkage comes from and you will hear a shrug, a percentage, and a story about “the usual suspects”. Treated as a mystery, shrinkage stays a mystery. Treated as a workflow — a series of steps that produce loss and can therefore be measured and managed — it becomes something you can actually work down.
Shrinkage is not one event, it is a chain
The word “shrinkage” flattens a lot of very different things into a single scary number. In practice, that number is the sum of several ongoing processes: theft by customers, theft by staff, supplier and delivery discrepancies, admin and pricing errors, damages and write-offs, and stock that was never received correctly in the first place. Each of these has its own trail. Lump them together and you can only react. Separate them and you can see where the loss is being manufactured.
The useful mental shift is this: every unit of shrinkage was created by a moment in a process that either failed or was exploited. A missed goods-receiving check. A refund with no product back on the shelf. A count done in a hurry. A void that nobody questioned. None of these are random. They are the visible end of a workflow that ran without a control.
Why “mystery” thinking keeps loss high
When loss is framed as unknowable, three bad habits follow. First, teams wait for the annual or half-yearly count to “discover” the damage — by which point the trail is cold and the cause is unrecoverable. Second, everyone blames the most visible channel, usually external theft, because it is the one with cameras pointed at it. Third, action becomes emotional rather than procedural: a crackdown, a suspicion, a memo, and then a slow return to normal.
None of that reduces loss durably, because none of it touches the step where the loss was created. You cannot manage what you only meet once a year as a surprise.
Map the workflow, then instrument it
Managing shrinkage as a workflow starts by writing down the actual journey of stock through a branch and marking every point where it can leak:
- Receiving: Is delivered quantity checked against the order and captured accurately, or signed for on trust?
- Storage and replenishment: Is high-risk stock controlled, and does the shop floor match the system?
- Point of sale: Are voids, refunds, discounts, and no-sales visible and reviewed, or invisible until month-end?
- Counts: Are cycle counts frequent enough to localise a variance to a week and a person, or so rare that any variance is untraceable?
- Disposal and damages: Are write-offs recorded with a reason, or used as a bin for anything that does not reconcile?
Once the map exists, each leak point gets a control and a signal. A control is the check that should prevent loss. A signal is the data that tells you whether the check is happening and working. A receiving control without a receiving report is just a good intention.
Close the loop: from number to action
The workflow only pays off when a variance leads somewhere. A count that shows a gap should not end in a spreadsheet cell; it should open a question, and where the pattern warrants it, a case. That is the difference between recording loss and reducing it. This is where structured stock counts and shrinkage tracking earn their keep — not because counting is clever, but because a count tied to the surrounding process turns a symptom into a lead you can follow.
Follow enough leads and patterns appear: one branch with recurring receiving gaps, one till with an unusual refund rate, one product line that only ever shrinks on late shifts. Patterns are the whole point. A single missing item is noise; a repeated leak at the same step is a workflow defect you can fix once and benefit from everywhere.
Make it routine, not heroic
Retailers who get shrinkage down rarely do it with a dramatic intervention. They do it by making the boring parts consistent: counts on a rhythm, exceptions reviewed weekly, receiving discipline enforced, and every unexplained variance owned by a named person until it is explained or escalated. It is unglamorous, and it works precisely because loss is unglamorous too — it accumulates one uncontrolled step at a time.
Key takeaway
Shrinkage is not a fog that descends on your business; it is the output of specific, repeatable steps that failed. Map those steps, put a control and a signal on each, and make sure every variance leads to a question rather than a shrug. Manage the workflow and the number follows.
If you are trying to move from reacting to shrinkage once a year to managing it as an ongoing process, a good next step is simply to map your own stock journey and mark the leak points — most teams find two or three obvious ones they can tighten this quarter. We are happy to share how other multi-branch retailers structure that review if it helps.