Search and Find for Shipments

Modified on Tue, 9 Jul, 2024 at 4:20 PM


Overview:


This article covers using the Search and Find feature in the Xemelgo app, including searching for shipments by Order Number or Tag Number, establishing RFID device connections, and interpreting proximity feedback for locating assets efficiently.


Instructions:


To use the search and find feature, tap Search and Find under the Looking for something? section of the Shipments user interface.


Next, use the text field to search for a shipment. 


Users can enter either the Order Number or Tag Number.


Once you have entered the Order Number or Tag Number, tap Return.


Then tap on the shipment you were searching for.


Next, the Xemelgo app will automatically establish a connection to the RFID handheld device you are using. 


Note: If the RFID handheld device you are attempting to use has not been onboarded to the Xemelgo app before, please consult the Onboarding an RFID Device section of the Xemelgo knowledge base.


Then, the RFID handheld reader will provide proximity feedback to help you locate the asset you are searching for. 


To begin this process, press and hold the trigger on the reader to scan.


When the order is nearby, the screen indicator will turn Green, and the RFID handheld reader will emit a rapid audible alert. Conversely, if the order is barely in proximity, the screen indicator will turn Red, and the RFID handheld reader will emit a subdued audible alert. In cases where the order is out of range, the indicator will display Nothing Detected


If you need to change the shipment you are searching for, tap Change.

Note: To learn more about utilizing Search and Find, view our comprehensive Instructional Video.










Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article