A scheduled supply cart delivers two labeled containers every 30 minutes and removes the empty ones.
When this method works well—and when it does not
Works well when
- Manufacturing supermarkets
- Kanban, milk-run, or call-driven supply
- Reusable containers
- High consequence of line-side shortages
Usually a poor fit when
- Unpredictable engineer-to-order material with no standard location
- Bulk raw-material systems requiring specialized handling
- No clear production consumption signal
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.
- 1Visual shortage
- 2Expedite
- 3Overdeliver
- 4Clutter line
- 1Consumption signal
- 2Create route
- 3Pick container
- 4Deliver point of use
- 5Confirm exchange
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
Define consumption and replenishment signals
- 02
Size container and loop quantity
- 03
Build routes around service interval and handling constraints
- 04
Confirm source, point of use, and container status
- 05
Escalate shortage risk before line impact
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
Check signal delay, loop quantity, route interval, and inventory accuracy.
Treat containers as controlled circulating assets.
Correct signal duplication and maximum presentation quantity.
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
Dynamic light-directed supermarkets and point-of-use displays can guide route picks and deliveries.
See how Voodoo worksWhen to choose something else
Voodoo cannot repair an undefined consumption signal or undersized kanban loop.
Read how recommendations are made