Blind Stock Counts: Why Showing the Expected Quantity Ruins Your Count
A blind count hides the expected quantity so counters record what they find, not what the screen says. Why it matters, when to use it, how to run one.
Here is an uncomfortable question about your last stock count: how much of it was counting, and how much was confirming?
If the screen showed Expected: 100 while someone counted the shelf, you don’t fully know. That’s the problem a blind stock count solves — it hides the expected quantity so the person counting records what they actually find, not what the system suggested they should find.
It costs nothing, it’s a checkbox, and it’s the single change that most improves the quality of inventory data in a small store.
What a blind count is
In a normal (open) count, the counter sees the system’s expected quantity next to each product and types what they counted. In a blind count, that expected number is hidden. The counter enters a figure with nothing to compare it against; the variance is calculated afterwards, by the system, out of their sight.
That’s the whole mechanic. Everything interesting about it is what happens in the counter’s head.
The bias you’re removing
Nobody sets out to fake a count. What happens is subtler and much more common.
When a number is on screen before you start, it stops being a record and becomes a hypothesis. Counting turns into checking whether the hypothesis is right. And checking behaves differently from counting in three specific ways:
- You stop early. Counting a bin of small items, you reach 97, 98… the screen says 100, and the remaining ambiguity resolves upward. Not dishonestly — the brain treats “close to the expected value” as “the expected value”.
- You don’t recount. If your count matches, you move on. If it doesn’t, you count again. So mismatches get scrutiny and matches don’t, which systematically pushes results toward the system number.
- You resolve ambiguity in the system’s favour. Is that opened box a unit or not? Does the damaged one count? With a target on screen, those judgement calls land wherever they need to land.
None of this requires a bad employee. It happens to owners counting their own stock, which is worth remembering before you decide you don’t need blind counts because you trust your team.
What an open count actually measures
Here’s the part that makes blind counting more than a nice-to-have.
Suppose you run an open count and it comes back with almost no variance. What have you learned? Two explanations fit that result equally well:
- Your stock records are accurate.
- Your counters confirmed the numbers on screen.
An open count cannot distinguish between them. A clean result is exactly what you’d expect in both cases, which means the result carries no information. You’ve spent a day counting and learned nothing you didn’t assume at the start.
A blind count is an independent measurement. When it comes back clean, that’s a real finding.
When a blind count matters most
- Anyone other than you is counting. Not because of suspicion — because you can’t audit a judgement call you didn’t watch.
- The count has consequences attached. A loss investigation, a year-end figure that goes to an accountant, anything connected to someone’s performance. The moment a count can produce a bad outcome for the counter, an on-screen “correct answer” is an invitation.
- High-value lines. The items where a two-unit discrepancy is worth investigating are exactly the items where you need the count to be independent.
- You suspect something and want to know. If you already believe stock is walking out, an open count will very politely tell you it isn’t.
The cost: blind counts are slower, and that’s the point
Be honest with yourself about the trade-off. A blind count takes longer, and it produces more variances to review — some of which are real discrepancies and some of which are ordinary counting errors that an open count would have silently absorbed.
That extra review work isn’t waste. It’s the information an open count was hiding from you. But it does mean you need a rule for what happens next, and you need it before you start:
Decide your recount threshold in advance. For example: any variance over 5 units, or over €50 in value, gets a second count by a different person.
Write it down. The reason to fix the threshold beforehand is that “recount the ones that look wrong” reintroduces exactly the bias you just removed — one level up, at the supervisor. If you only recount results you dislike, you’ll converge on the system’s numbers again, just more slowly.
When not to bother
Blind counting is not a moral obligation. Skip it when:
- You’re checking a delivery against a packing note. You’re verifying a specific document, not measuring your stock position — the expected number is the point.
- You’re doing a five-item spot check on something you’re about to reorder, on your own, and speed matters more than rigour.
For anything that ends up in a report, count blind.
How to run a blind count in WooCommerce
In Stocktake for WooCommerce, blind count is a per-session toggle set when you create the session — Blind count (hide expected qty). It’s included in the free version.
Once the session is running, the count screen shows the product and an input, and no expected figure anywhere. Scanning still works exactly the same way: a recognised barcode counts the item on the spot, scanning again adds on top. The counter simply never sees what the system thought.
The variance appears when you finish and open the review — expected against counted, with the differences and their value, all calculated after the counting stopped. From there it’s the same as any other count: review, investigate the outliers, then apply.
A practical sequence for a store with staff:
- Create the session with blind count on, scoped to one section.
- Whoever is counting works through it without ever seeing wp-admin’s product screens.
- You open the review, apply your recount threshold, and send the outliers back for a second count — by someone else if you can.
- Apply the adjustment once you believe the numbers.
Making the result stick
One blind count tells you where you are. Two tell you which direction you’re going, and that’s the number worth managing. Export the count sheet each time and compare the variance value between sessions — if it’s shrinking after you changed a receiving process, the change worked.
If you want the whole workflow rather than just this one setting, the full stocktake guide walks through snapshot, count, review and apply from start to finish.
Blind count FAQ
What is a blind stock count?
A count where the system’s expected quantity is hidden from whoever is counting. They enter what they find with nothing to compare it against, and the variance is calculated afterwards. The alternative, an open count, shows the expected figure next to each product.
Does blind counting mean I do not trust my staff?
No. The bias it removes is not dishonesty, it is the ordinary human tendency to treat a number on screen as the answer and the count as a confirmation. It happens to owners counting their own stock just as reliably as it happens to anyone else.
Is a blind count slower?
Yes, and it produces more variances to review, some of which are ordinary counting errors rather than real discrepancies. That extra review work is the information an open count was hiding from you, but you should budget for it.
Should I recount every variance?
Set a threshold before you start — for example any variance over five units or over a set value gets a second count, ideally by a different person. Deciding what to recount after you have seen the results reintroduces exactly the bias you removed, one level up.
Is blind count available in the free version of Stocktake?
Yes. It is a per-session toggle set when you create the stocktake, and it is included in the free plugin on WordPress.org.
When should I not use a blind count?
When you are checking a delivery against a packing note, because there the expected number is the whole point of the exercise. Also for very small solo spot checks where speed matters more than rigour. For anything that ends up in a report, count blind.
