The receiver scans purchase order 4102, counts 12 cases, photographs one crushed case, and places that case in the damage area.
When this method works well—and when it does not
Works well when
- Mixed purchase orders and inbound carriers
- Operations where damage or lot/serial control matters
- Facilities with dock congestion or long dock-to-stock time
- Teams that release inventory before discrepancies are resolved
Usually a poor fit when
- Pure cross-dock flow with reliable advance shipment data
- Full-pallet receipts already controlled by mature advance shipping notice and pallet-ID label processes
- Tiny inbound volume where a simple signed checklist is sufficient
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.
- 1Unload
- 2Find paperwork
- 3Count
- 4Ask supervisor
- 5Stage
- 6Enter later
- 1Identify receipt
- 2Inspect by rule
- 3Capture discrepancy
- 4Direct disposition
- 5Release inventory
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
Create the receipt identity before material leaves the door
- 02
Separate count, condition, identity, and compliance checks
- 03
Route clean receipts and problems to visibly different destinations
- 04
Post inventory only when the defined release event occurs
- 05
Measure dock wait time and problem age separately
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
Quarantine to a named owner; do not create anonymous available inventory.
Capture expected, received, damaged, and accepted quantities as separate facts.
Prioritize by production/customer impact and add an explicit written response-time limit.
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
Wireless displays can label temporary receiving, inspection, and disposition lanes and present the current task at changing dock positions.
See how Voodoo worksWhen to choose something else
Lights do not replace supplier discipline, dimensional inspection, or a reliable receiving record.
Read how recommendations are made