This article will go over how Double Scan Prevention works for Fulfillment Checkout in TREEZ
LucidIDs allow for unit-level-tracking with a unique identifying QR code printed on the label of each product. Preventing the ability to scan the same LucidID multiple times into the same order, or into separate orders simultaneously, helps to reduce inventory discrepancies and increases the accuracy of the sales data.
Fulfillment Checkout
When using LucidIDs at POS checkout with Double Scan Prevention turned on, you will notice some changes to how the fulfillment flow operates. When opening a fulfillment order that contains a product associated with a LucidID, it will look like this:
You will need to scan the LucidID of the product you are associating with this order. Upon scanning the LucidID, and the number of LucidIDs scanned match the allocated quantity of that product, you will see the screen change to look like this:
Note: If you click on "EDIT ORDER", this will remove the LucidID from the order and it will need to be scanned in again.
Fulfilled LucidIDs status will carry on to SellTreez checkout:
Note: Clicking on "Save Current Sale" will remove the LucidIDs from the transaction, even if the line item stays. LucidIDs will need to be scanned again before checkout.
Pushing Back a Fulfilled Order
Pushing back a fulfilled order from “PACKED & READY” to “IN PROGRESS” will retain the LucidID associations. Ensure that the same unit that was scanned in to the order originally is still the unit that will be given to the customer. This can by done by scanning the LucidID in the cart and seeing this error message pop up:
This will let you know that the unit you scanned is already associated with this order. If scanning the unit makes the quantity increase, delete the line item with the trashcan button and scan the unit(s) in again to ensure the correct LucidIDs are associated with the order.
Important Note
Historical LucidIDs that were sold and returned for any reason will not be sellable and the retailer will not be able to check them out.
-
Why?
Before this update, we were not detecting when a LucidID was removed from an order.
-
How to fix?
The retailers can mark the LucidIDs as "unsold" using the steps in this article: LucidRetail Mobile: Mark LucidID as Not Sold
Comments
0 comments
Please sign in to leave a comment.