Locus Robotics Ideas Portal
Instead of a return being processed and assign to a bin location for putaway by a locus bot it is assign to a bin and an active order is pulled from the order pool and assign to that bin. Then locus goes out to complete the order once that bin is assigned to the bot.
|
Problem/opportunity trying to be solved
Right now we putaway a return into an active pick location. The thought here is to reduce return handling by creating an active pick based on an active order in the order pool. Instead of returns being a put job the returns bin becomes an incomplete pick job that can be assigned to the Locus bot. This could reduce touches and inventory space taken up by returns. |
|
|
Quantify the problem/opportunity
Returns are typically a huge loss to most retailers and every touch of a return item is money lost. |
|
|
What is the root cause of the problem/opportunity
Locus return handling requires multiple touches for returns where some G2P systems can reduce the touches and easily prioritize the pick of that return. |
|
| Customer need date | Apr 30, 2024 |
| Urgent request | No |
We will not pursue this at this time. Very complicated feature. We can revisit if we see a lot of commercial benefit to developing it.
Dylan - Do we know how often a returned item has an open order for it?