An unopened item returns to stock; a damaged item goes to a marked hold area with a photo and reason.
When this method works well—and when it does not
Works well when
- Ecommerce and service-parts returns
- Multiple disposition outcomes
- Condition or serial verification
- Meaningful recovered-value opportunity
Usually a poor fit when
- Simple reusable-container return
- Regulated or hazardous returns requiring specialized compliance
- Very low-value goods better handled by a fixed policy
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.
- 1Open box
- 2Decide from memory
- 3Create pile
- 4Research later
- 1Identify return
- 2Inspect by rule
- 3Choose disposition
- 4Route physically
- 5Close financially
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
Identify order, item, reason, and ownership
- 02
Use a finite decision tree for condition and disposition
- 03
Physically separate sellable, repair, vendor, scrap, and investigation
- 04
Require evidence for overrides
- 05
Age unresolved work by reason and value
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
Set value-based service levels and authority limits.
Separate reinventory capacity from complex problems.
Use visual standards, sample calibration, and check.
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 identify dynamic triage and disposition locations and present task-specific instructions.
See how Voodoo worksWhen to choose something else
The difficult part is policy and evidence; lights cannot decide product condition or financial ownership.
Read how recommendations are made