Stocktake Checklist: Count What You Have, Not What the System Says You Have

The quick version: a stocktake is the only instrument that measures the gap between what your shelves hold and what your system claims — and that gap is where the margin goes. Run it blind, count what's expensive first, recount before you adjust, and never move a number without a reason code attached. The count doesn't have to stop the business; the best ones almost never do.

Why the gap is where the margin goes

The system says 14 bags of house coffee; the shelf holds 12. Nothing dramatic happened — a delivery that was never counted, two sold off-system, one broken and binned without a note, a case received as 12 but entered as 10. Each one is a rounding error. Summed over a year across everything the business touches, that gap is a second payroll — paid to nobody.

Most small businesses know the number only once a year, at the annual count, when it arrives as a shrug: "shrinkage, call it 2%." The 2% isn't a weather condition. It's an invoice. Every dollar of it went somewhere specific — out the door unpaid, into the bin unrecorded, or into someone's pocket — and the only way to make it speak is to measure it while the trail is warm, not twelve months later.

The five-step stocktake ritual

1. Count blind. The counter never sees the system number first. Print count sheets without quantities, or hide the on-hand column entirely. A counter who knows the system says 12 will find 12 — the mind finishes the count from memory and the audit becomes a copy-paste of the claim. Blind counting is the whole discipline; every other rule is scaffolding for it.
2. Freeze the floor, or count in zones. A small business that can close for two hours closes and counts everything at once. A business that can't stop counts one zone at a time on a rolling calendar — stockroom this week, fridges next week, front-of-house the week after — and accepts that the total is stitched, not simultaneous. What it may never do is count a zone mid-delivery: receiving and counting the same shelves in the same hour manufactures variances out of thin air.
3. Count value-first. The top 20 items by value get counted every cycle, to the unit, by two different people on different shifts. The cheap and ambiguous stuff gets tolerance bands: nobody recounts a $3 item to resolve an 11-cent variance. Perfect counting is for the SKUs where a single error is a wage; band counting is for the SKUs where the recount costs more than the gap.
4. Recount before you adjust. Every variance above its band gets a second pair of hands before the system moves — different person, different shift, blind again. Half of all variances die at this step: the first count was wrong, and no adjustment was ever needed. The rule costs ten minutes and prevents the most expensive kind of accounting: fixing the books to match a bad count.
5. Adjust with a reason code, or not at all. The variance line carries a why — receiving error, spoilage, breakage, comping, theft-suspected, data entry, supplier short. A number without a reason is a decision postponed, and a postponed decision is a pattern that gets to repeat all year. The monthly close checklist reads these codes like a doctor reads symptoms; feed it guesses and it prescribes guesses.

The rules that make the count honest

• The system number is a claim, not a fact. It is the residue of every uncounted delivery, every unlogged breakage, every typo since the last count. The shelf is the fact. The count exists to make the claim match the fact — not the reverse.
• Count units you sell, not units you filed. The system holds coffee in kilos, the shelf holds bags, the invoice holds cases. Decide the counting unit per SKU, write it on the sheet, and convert in exactly one place. Unit-of-measure mismatch is the quietest variance factory in small business: perfectly correct counts producing perfectly wrong numbers.
• Variance gets a threshold and a band. ±2% on the $500 line gets investigated same day; ±10% on the $3 line gets noted and released. Bands are not laziness — they are where the counting effort goes instead, and they are written down so the counter isn't making judgment calls at 9pm.
• Shrinkage is a story, not a subtotal. Every unexplained dollar gets a hypothesis and a fix within the month: the back door propped during deliveries, the comped round nobody logged, the case counted as units. A hypothesis you can't test in a month isn't a hypothesis — it's an excuse with a schedule.
• The count feeds the close. Results land in the monthly close as adjusted COGS, not as a memo. The delivery receiving checklist is the upstream half of the same system: a docket counted at the door is a variance that never gets born.

The five traps

• The annual-only stocktake. Twelve months of drift measured at once, with every trail cold. Whatever it finds, it can only bill to the whole year — and by the time it's found, the habit that caused it has done 364 more repetitions.
• Counting from memory. "I know we have 12" is the sound of a blind count dying. Memory is the system's Advocate in the room; the count exists to outvote it.
• The tidy-up adjustment. The gap rounded to zero, the books balanced, the cause never named. A tidy-up adjustment is not an accounting entry — it's an alibi, renewed every count.
• Counting in sales units, adjusting in purchase units. The count says "3 bottles"; the system adjusts "3 cases"; the variance announces itself next count as 33 bottles. One counting unit per SKU, printed on the sheet, forever.
• The pre-announced count. Everyone knows stocktake is Friday, so Thursday night is unusually tidy. Surprise spot counts on the top-20-by-value SKUs are the honest version — cheap, frequent, and impossible to rehearse for. Shrinkage hides in the calendar gaps between announced counts.

Cycle counts for businesses that can't stop

• ABC the shelf. A items (top ~20% of SKUs carrying ~80% of value) count weekly or fortnightly; B items monthly; C items quarterly with bands. The A list is small — twenty SKUs is an hour with a competent counter and a blind sheet.
• The daily ten-minute count. Top five value items, every trading day, before open. It keeps two counters calibrated and it catches the big leaks while they're still small.
• Tie the count to receiving. Every docket from the receiving ritual becomes tomorrow's count sheet input. Where the two disciplines touch, variances get caught in days instead of quarters — and the receiving error and the shelf error stop blaming each other.
• Surprise one zone a month. Unannounced, top-value zone, thirty minutes. Not a punishment — a calibration check on both the stock and the process. The month it finds nothing is a good month twice over.

Worked example: the bottle shop's $6,200 answer

A suburban bottle shop replaced its annual count with a rolling weekly zone count — three zones, blind sheets, recount before adjust, reason codes on every line. In week three, the spirits zone showed the same variance two weeks running: three bottles of the same $105 whisky, entering nowhere in the system. The reason codes pointed one direction, a camera angle confirmed it, and the leak closed in a fortnight — roughly $6,200 a year, found by an hour a week that had previously been spent on nothing.

The shop up the road does the annual count every January and budgets 2% for shrinkage, because that's what it has always been. It isn't a budget. It's a leak with a subscription. The difference between the two shops is not honesty or effort — it's that one measures the gap while the trail is warm and the other measures it when the trail is a year cold.

From the HIVE80lab kit

Every page ships with a kit block — the paid tools behind the free advice:

• The First 30 Minutes — free incident quick-start checklist
• Ops Starter Kit — incident response for small teams — $14
• Ops Starter Kit Vol. 2 — advanced incident response & communications — $27
• Ops Mega Bundle — all 5 kits in one download — $49

Related: the delivery receiving checklist is the upstream half of the same ledger — the docket counted at the door is a variance that never gets born; the monthly close checklist is where the reason-coded adjustments land as real COGS; the vendor escalation ladder is the path when the reason code keeps reading "supplier short"; and the asset inventory checklist is the same discipline pointed at the things that don't walk out the door as sales.