Voodoo RoboticsWarehouseWorkflow Lab
Voodoo Robotics Start diagnostic
For warehouse managers and their WMS or IT team

Make sure the computer task and the physical warehouse task stay in agreement.

Decide which system owns each warehouse decision—often the warehouse management system (WMS) or enterprise resource planning system (ERP). Floor guidance shows the worker what to do, confirms the result, and gives problems a safe next step.

Four-step flow · Plain example · Technical checklist includedNot sure about a term? Open the plain-English glossary
01

Create the work

The agreed owning system—often the WMS or ERP—decides which item, order, or move should happen.

02

Send one clear task

The guidance system receives the item, quantity, source, destination, and a unique task number.

03

Guide the worker

The worker sees the next action and confirms completion or reports a problem.

04

Confirm the result

The main system updates only after it receives and checks the completion message.

Example: one putaway task

The WMS sends: “Move pallet P104 from receiving to B-03-02.” The worker scans the pallet, follows the display, scans B-03-02, and confirms. The WMS then changes the pallet’s location. If the destination is blocked, the worker selects a reason and the task goes to a named person for reassignment.

Information every task should include

  • A unique task number
  • The order, work, pallet, tote, or other thing being handled
  • Where it comes from and where it goes
  • The product, quantity, and unit such as each, case, or pallet
  • Priority and what should happen if the task is cancelled
  • The confirmations and problem reasons workers are allowed to use

Questions to answer before testing

  • If no answer comes back, which system sends the task again?
  • If the same completion arrives twice, how is a duplicate move prevented?
  • Can two answers arrive in the wrong order?
  • What can workers safely do when the network or server is down?
  • How will offline work be added later without posting it twice?
  • How much delay can the floor tolerate before workers must stop or switch methods?
Technical notes for software and integration teams

Give every business task and message a stable unique ID. Processing the same message twice should have the same effect as processing it once; software teams call this idempotency.

Record sent, received, accepted, completed, failed, cancelled, and timed-out events. Keep a reconciliation process that compares both systems and repairs differences after delays or outages.

Agree on retry ownership, timeout values, out-of-order messages, offline rules, units of measure, time zones, security, monitoring, and the maximum acceptable response delay before the test begins.

Voodoo integration information

Send work to Voodoo displays and receive confirmations without replacing the main warehouse system.

The developer pages explain Voodoo’s application programming interface (API) and its completion messages for technical teams.

API documentation Completion-message documentation