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

Ability to induct order without scanning container ID, and assigning container ID at pick

The user would press a button on the induction screen to assign an order to that bot, then assign a position. This would be repeated until the required number of orders is inducted. They would then hit "Done" and "Go" and the bot would travel to the first pick. The system would send a form of the TOTEINDUCT message with a blank ToteId field. At pick, the associate would scan the product and then scan a carton ID (which would come off a role of carton IDs the associate carries with them) to assign. The system would then send a PICK message which includes the ToteId field, and the WMS would assign the carton ID from that message instead of the TOTEINDUCT.

Problem/opportunity trying to be solved

The customer has a singles picking flow, where they pick single line, single unit orders onto a bot. They would like to be able to induct 12 singles orders onto a bot, but not use a tote/carton to pick into, instead picking straight onto the bot. They want to then assign a carton ID (from a tape roll) at the point of pick - they would scan the single order, then scan a carton ID to assign, and place on the bot.

Quantify the problem/opportunity

This would allow Locus to support customers who have a limitation on their packing process whereby each single pick needs to each be assigned a unique carton ID

What is the root cause of the problem/opportunity

The customer has stated that assigning a batch of singles orders to one carton ID would introduce too many steps in their packing process, whereby they would have to scan the carton ID and then scan the product SKU to pack out each single order. Currently as each single order has its own carton ID (all orders are picked in shoeboxes), then its a 1:1 assignment.

Customer need date Mar 28, 2022
Urgent request No
  • Attach files
  • Admin
    Dan Coote
    Feb 4, 2022

    Upon discussing this with Sam, the customer has changed the request. Sam is sending through a different request - I am moving this to will not implement.

  • Guest
    Feb 4, 2022

    Thanks Dan, Do you have a date of the review so we can adjust the action date accordingly and give the customer some indication of a result? Thanks

  • Admin
    Dan Coote
    Feb 2, 2022

    Andy, there was a pending review to look at this with our engineering teams. I have asked for an update so you can advise the customer accordingly, will let you know once received.

  • Admin
    Dan Coote
    Jan 17, 2022

    Sam, please have a look at this idea submitted by Erik Pichette - is this effectively the same ask? - LSA-I-47