All ideas

We want Locus to develop a safeguard to keep us from accepting messages for pre-processor with the toteid field missing.

The host will send the Locus system a request to relocate stock items. The WMS will create work that consists of two separate steps: Picking and Putaway. The pick task is executed in the same manner as a customer order pick. The pick user will not...

Currently, customers can only access Locus Admin from a single Admin iPad that needs to be specifically configured for that customer site. This requires additional time & effort for Locus to configure each iPad and the Admin iPad is not delive...

What they confirm is that we have build in the totevalidation (scan of handling unit) as part of the barcode verification interface. SAP is saving the first and the last barcode. And because the last barcode now is the handling unit, the parsing o...

A new branch/screen flow that allows the users to accumulate part picks towards a total quantity. I have suggested from the quantity down step, but it could also be a new button or sub menu elsewhere.

The user scans a carton onto the bot. the contents of the carton are unknown. A the conclusion of the bot being loaded with the cartons with content to be putaway, the Putaway message for the Tote ID is sent to the WMS. The WMS recognises the Tote...

and a check bot by each custowner to be able to select multiple custowners at a time.

Deliver Next Generation LocusBot to deliver additional value to our customers

We want to develop a way to capture more data points to calculate every aspect of an associates PICK. See 'Problem/opportunity trying to be solved'

Allow for the ability to add in a background image, thinking of the Pretty Map from FA, to the Task Map in Locus Hub.