Locus Robotics Ideas Portal
Thoughts from the customer:
The picker to press a button on the device to send an information-only message (location, SKU, task ID, required quantity) to the Troubleshoot team.
This action should not create a final short pick in the system.
This action should not change any quantities.
|
Problem/opportunity trying to be solved
Pickers are not allowed to short pick. With an LN upgrade we can disable this which is good, but still they need to pass on this information to Inventory to first investigate the location and if necessary perform the short pick. Or what happens regularly is that bots are getting to locations faster than replenishments are completed. There are several reasons Inventory needs to investigate a location. Their struggle is they currently have the picker walk over to Inventory notifying them on what to check which is taking up quite some time. |
|
|
Quantify the problem/opportunity
When we are looking at shirt picks or other troubleshooting activities, they estimate it's happening 7-10 times per day. But if we include the bots already at the pick location before the replenishments is done, we are talking 30x per day on average |
|
|
What is the root cause of the problem/opportunity
Customer also has WMS challenges and is sometimes releasing orders while the they need the replenishment to be done. So often it might seem a short pick that could be avoided by skipping the pick and return when the replenishment is done. I'm checking what their WMS can do to only release orders after the replen is done. |
|
| Customer need date | Apr 1, 2026 |
| Urgent request | No |
| Report Tag | CSM |
