The purchase order says 48 cases, but the receiver sees only the item number and independently counts 46.
When this method works well—and when it does not
Works well when
- High consequence quantity errors
- Suppliers with recurring short/over shipments
- Countable cases or individual units
- Systems that can conceal expected quantity but retain purchase order identity
Usually a poor fit when
- Sealed pallets accepted by pallet-ID label
- Items that require weigh-counting or specialized measurement
- Very low-risk receipts where double handling costs more than discrepancies
Show exactly what happens at each step
Write down actions that someone can see or confirm: what the worker does, what moves, who owns the next step, and what happens if something goes wrong.
- 1See expected quantity
- 2Glance at freight
- 3Accept expected
- 4Discover later
- 1Identify item
- 2Count blind
- 3Record actual
- 4Reveal variance
- 5Recount or resolve
Get these basics right before adding technology
- One named person owns the process, and everyone agrees what one task includes
- Current time, accuracy, problem, and volume numbers collected using written rules
- One named person corrects product and location information
- A written backup method and a clear path for getting help
If workers cannot reliably identify the item, order, or location, correct that problem before expecting new guidance equipment to improve accuracy.
Step-by-step procedure
- 01
Keep item identity visible while hiding expected quantity
- 02
Require the first count before revealing the variance
- 03
Use a second counter or alternate method for large variances
- 04
Record the reason code and supplier evidence immediately
- 05
Track false variances caused by unit-of-measure errors
Information the process must track
For each task, decide what item or order is being worked, where it comes from, where it goes, how much is expected, how the worker confirms completion, what happens when something goes wrong, and which system records the final result.
Technical notes for the warehouse software or IT team
Use one unique task ID. Re-sending the same message should not create a duplicate move or pick. Keep a way to compare records and repair differences when messages are delayed, repeated, or missed.
Decide what workers should do when something goes wrong
Rotate assignments and sample independent recounts.
Show the counting unit explicitly without showing expected quantity.
Set risk-based thresholds and approval rules.
Numbers to watch
Before the test starts, write down what is counted, what it is divided by, when the clock starts and stops, what is excluded, and where the data comes from. Keep those rules the same through the test.
Test it on a small scale before a full rollout
Trial steps
- Choose one realistic area, shift, and order mix
- Watch the current method long enough to include normal work and a busy period
- Test the new method using exactly the same measurement rules
- Review every problem and worker workaround before expanding the change
What must be true before rollout
- The target output is maintained for one full, realistic shift
- Accuracy and problem recovery meet the written target
- New workers can follow the process without unwritten tips from experienced workers
- The backup method works, and the team can return cleanly to the normal process
Voodoo is one possible way to guide the work—not the answer to every problem.
Where it may help
Displays can show item, unit of measure, and disposition without exposing expected quantity, then switch to variance resolution.
See how Voodoo worksWhen to choose something else
The method is a counting-control choice; Voodoo is unnecessary when the warehouse management system (WMS) and scanner already present a clean blind-count screen.
Read how recommendations are made