After creating your Virtual Manifest in the LucidRetail mobile app and having assigned the correct Package UIDs, LucidRetail LITE will now automatically import the CaseIDs to the matching Package IDs in your POS/Inventory system.
NOTE: Package UID in LucidRetail is the same as Package ID in Dutchie and State Tracking ID in Treez. For states with a track-and-trace system, this is usually the Transfer Tag (Transfer Regulator UID).
You can create your virtual manifest before or after you receive your products in your POS/Inventory system. For instructions on creating a virtual manifest, please see the steps here: Received Inventory Scanning: Creating a Virtual Manifest
IMPORTANT: CaseIDs will not start to automatically import to the inventory records for at least 10 minutes after the virtual manifest has been created in order to give time to review and make any necessary changes to the virtual manifest. It can take up to 20 minutes for the CaseIDs to be automatically imported.
If you need to edit your virtual manifest, you can follow the steps here:
- Received Inventory Scanning: Viewing and Adjusting a Virtual Manifest on the LucidRetail Mobile App
- Received Inventory Scanning: Viewing and Adjusting a Virtual Manifest on the LucidRetail Web Portal
While reviewing your virtual manifest, you will either need to assign the Package UID to your CaseIDs or verify the pre-assigned Package UIDs are correct.
If a CaseID does not have a Package UID assigned to it, you will see a button to assign the Package UID:
IMPORTANT: Any CaseIDs without the Package UID assigned will not be automatically associated.
Here is what the virtual manifest looks like when the Package UIDs are assigned:
When the CaseIDs are imported, you will see this called out in your inventory views:
Dutchie:
Treez:
For the first 24 hours after a CaseID has been automatically associated, when you click on the inventory record you will see this message pop up:
This will let you know the number of CaseIDs that were associated with this inventory record where the Package ID and Package UID match.
Troubleshooting Steps
You can view your CaseID Auto Import Logs on the LucidRetail web console: retail.lucidgreen.io
Here you can see the status of the auto imports:
If an auto import was not successful, you will see this in the Status column:
To see why this failed, click on the UUID of the log:
Here you will see the reason it failed and the option to try again if the alert has been handled:
Important Notes and Reminders
- 0-Click CaseID Import: LucidRetail LITE will automatically bring CaseIDs into your POS/inventory system if you've already created a Virtual Manifest in the LucidRetail mobile app.
- Package ID Match: Just so you know, the Package UID in LucidRetail is the same thing as the Package ID in your system (and often your Transfer Tag if you're in a state with track-and-trace).
- Virtual Manifest First: You can create that Virtual Manifest before or after your products actually arrive in your inventory.
- Wait a Bit: Give it at least 10 minutes after making the Virtual Manifest for those CaseIDs to start auto-importing. This gives you time to double-check everything. CaseIDs will be automatically associated with between 10 and 20 minutes after the Virtual Manifest has been completed.
- Need to Edit? You can adjust your Virtual Manifest on either the LucidRetail mobile app or the web portal. Links to instructions are in the original document.
- UID is Key: Every CaseID needs a Package UID assigned to it. If it doesn't, it won't auto-import. There are buttons in the manifest to help with this.
- Inventory View: When the CaseIDs do get imported, you'll see it noted in your inventory views (there are specific examples for Dutchie and Treez systems).
- Info Pop-up: For the first day after a CaseID is auto-associated, you'll get a pop-up telling you how many CaseIDs were linked with a matching Package ID/UID.
- Troubleshooting: If something goes wrong with the auto-import, you can check the logs on the LucidRetail web console at retail.lucidgreen.io.
- Error Details: If an import failed, the log will show you why and give you a chance to retry if needed.
Comments
0 comments
Please sign in to leave a comment.