Establish a TCP socket or REST session to the pick-to-light controller gateway; authenticate with the configured API key or basic credentials provided by the controller vendor
Send a light-on command for each pick location in the active wave: include the zone ID, bay address, quantity to pick, and an order reference; the controller illuminates the display at that bay
Poll or subscribe to confirmation events from the controller; when a picker presses the confirm button at a lit bay, the controller sends a pick-confirm message containing the zone, bay, quantity confirmed, and operator badge ID
Validate the confirmed quantity against the expected pick quantity; if quantities differ, send a quantity-mismatch command to relight the bay with the residual quantity and increment a short-pick counter for the order
Send a light-off command for all bays in the zone once the full order pick is confirmed; send a put-to-light command to the induction sorter divert controller to route the consolidated tote to the correct shipping lane
Record pick confirmation events with timestamp, operator badge, bay address, and actual quantity picked; feed these back to the WMS order management module to update pick task completion status
Known gotchas
Pick-to-light controllers typically use a proprietary binary or ASCII serial protocol over TCP; REST wrappers provided by gateway controllers may not support all controller firmware versions and may silently drop commands for unsupported firmware
Bay address encoding varies by vendor: some use a flat integer address while others use a hierarchical aisle-zone-bay-level tuple; sending a flat address to a hierarchical controller causes the wrong bay to illuminate with no error returned
Controller sessions are typically single-threaded per zone controller; sending concurrent light commands from multiple WCS threads to the same controller without serialization causes dropped commands or interleaved acknowledgment mismatches
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp