All ideas

Clients are often in the dark as to the status of messages flowing between the systems. This would give them the ability to check message statuses. It gives them more immediate information, and will reduce customer service cases.

A manual process is currently used to configure LP-to-bin location mappings where CS provides SW Eng with a spreadsheet of mappings for SW Eng to upload & update Locus accordingly. CS is also reliant on SW Eng to confirm when the udpates have ...

Print multiple fields on a label at each pick stop.

Will be able to scan 1 bar code and derive the upc code only, and scan the same barcode again to derive the lot number.

In order to utilize the robots in the best possible way and to meet the Rhenus requirements regarding prioritization its necessary that the LOCUS System is able to distribute the tasks across different task types (putaway|B2B|B2C). Logic in princi...

Industry-Specific Barcodes - Continue building catalog of barcode support Flex data capture - Rising needs for capturing flexible fields (e.g., IMEI, Country of Origin, etc) Lot, Serial, Expiration, & Other Capture/Validation

LV2

Hospital, tote full, different pack locations, etc... Generally useful feature across customer base. 1st implementation of Multiple drop-offs - Hospital and Drop off ONLY. 1st drop is at hospital, 2nd and final is at drop-off.

It currently takes ~1 hr per 10K sq ft to map a Locus area with a bot and up to 5 business days to process the map before it is ready to be put into production. Even if map is only expanded by 20%, may be necessary to remap the entire floor and no...

Be able to select which custom fields would be added into the pick detail report.