Skip to Main Content
Locus Robotics Ideas Portal
Status Will not implement
Created by Sam Moore
Created on Apr 20, 2022

Multi-SKU Putaway Tote ID Validation & Single Confirmation

The associate would scan the put location with a scanner to validate, then the put screen would ask for a scan to validate the tote ID, the associate would scan the tote ID. The put screen would then display the total quantity to be confirmed for all the SKUs in that tote - the put screen could display an arrow or "next page" button to view all the different SKU details e.g. UPC, item description, picture etc. The use would then put all the items from the tote into the put location, and confirm. The bot would then move to the next put location of the mission (for any other remaining totes)

Problem/opportunity trying to be solved

Locus doesn't support tote ID validation at the point of the put task, and also requires multiple confirmation screens for putting away multiple SKUs to a single put location. DHL require these features to ensure that the correct tote is being put away at the correct put location, but also that all of the multi-SKU contents can be confirmed with a single confirmation.

Quantify the problem/opportunity

Tote ID validation for putaway will ensure a level of accuracy for our customers using Locus for putaway. Having a single confirmation screen that concatenates the quantities for multiple SKUs if they are going to the same location will be a good option for customers that would like to streamline the put process for multi-SKU locations, and aren't too concerned about the quantity of the individual SKUs.

What is the root cause of the problem/opportunity

DHL Adidas have communicated that these functionalities are a hard requirement for go-live, as their current putaway process follows the approach of putting all the contents of a single tote to a single put location. The totes are filled with multiple SKUs, and DHL fear that the inefficiency of having to confirm the qty of each SKU (and use multiple put screens), will affect their business case.

Customer need date Jul 11, 2022
Urgent request Yes
Report Tag Deployment
  • Attach files
  • Admin
    Dan Coote
    Apr 25, 2022

    Sam I'll meet with you to work through the detail of this request to make sure we have it fully understand and see if there is a work around available.