Once the orders have their barcodes and the configuration is done, then your drivers can start scanning barcodes using their driver app. In this article, we will explain how drivers can perform barcode scanning, and how the dispatcher can monitor this.
| Who can use this feature | |
| Available for Pro and Custom plans | |
| All users | |
| All regions | |
Accepted barcode types
OptimoRoute's barcode scanning capabilities can support various types of formats.
| Type | Supported versions |
|---|---|
| 1D Barcodes |
|
| 2D Barcodes |
|
Scanning from driver app
Once you have barcode scanning set up for proof of delivery, your drivers will be able to scan in their driver apps. When drivers are completing an order in the driver app, the "Proof of Delivery" form will show them the expected barcodes to be scanned, with functions for the actual scanning. This scanning function seamlessly scans any barcode type (1D, 2D, QR, etc.). There is an option to either batch scan all the barcodes in quick succession or to scan each one individually.
To scan barcodes from the driver app:
- Open the driver app and click "Start service" on an order
- Click "Complete"
- Make sure the order status is toggled to "Completed"
- In the section called "Barcode", click on an individual barcode to scan a specific one or click "Tap to scan barcodes" to scan all in any order. If you have "Barcode Collection" enabled, you can click this section to scan barcodes that haven't been attached to the order.
- A successful scan will automatically validate and register the barcode. See the next section of this article "Scan results" to learn more.
Scan results
While scanning, the screen displays the scanning frame and provides visual and auditory feedback on the scan results. Also, a flashlight can be activated from within the screen.
If there are any scanning issues, a scan issue dialog is available for resolution.
Successful scan
A successful scan will automatically validate and register the result with a green check mark. No further action is needed by the driver.
Unsuccessful scan
An unsuccessful scan will show in red and alert you to a potential issue. If there's a problem with scanning, the driver can report a "Scan issue".
To report a scan issue:
- Click on "Scan issue" in the bottom left of the scanning screen
- Choose from the available options. The available options depend on how you configured the driver app in the administration settings.
- Follow the instructions for reporting the scan issue.
Scan issues will show with a yellow warning sign and will be apparent to the dispatcher upon reporting.
Possible issues include:
Can’t find item
One issue that can be encountered is when the item associated to the barcode is missing. This option can be enabled in the driver app configuration settings.
Barcode not scannable
Another issue that can be encountered is when a barcode cannot be scanned because it is damaged or the phone just isn’t reading it. Whether a photo is required for a non-scannable barcode depends on the workflow set up by the administrator.
Unexpected barcodes
Another issue that can be encountered is when the driver encounters a barcode that is not originally part of the order and therefore “unexpected”. If an unexpected barcode is encountered, the driver can either scan a new barcode to register or enter its value manually to continue.
It is possible to enable the collection of barcodes that haven't been attached to an order without it being logged as a scan issue.
Barcode collection is a separate section in the "Proof of Delivery" form, dedicated to attaching new, unexpected barcodes to an order. This can be configured in your administration settings.
Monitoring barcode scans
To see the results of barcode scans, you can do this in a few ways:
- In the “Live” tab under the “Proof of Delivery” column
- In the “Analytics” tab under “Plan History” under the “Proof of Delivery” column
- In the “Analytics” tab under “Planned vs. Actual” under the “POD exceptions” column
- In the order detail window under “Proof of Delivery” for an individual order
- From the API (see documentation)
Proof of delivery column
On the "Live" screen and analytics "Plan History" screen, the "Proof of Delivery" column will indicate whether barcode scanning has occurred, along with any exception statuses in the case of scanning issues.
Exceptions alert the dispatcher of any scan issues that happened during proof of delivery. The proof of delivery exceptions are indicated by warning icons in order grids. Hover over the yellow warning symbol to see the issues.
The "POD exceptions" button in the "Live" screen and analytics "Plan History" screen will filter orders to show only the ones with any scanning exception happening.
Order detail window
Once an order has been completed, the order detail will show proof of delivery details. This shows more details on expected barcodes and scanned barcodes, any exception statuses, and any photos of the barcodes taken.
Planned vs. Actual Report
Also, in the analytics report "Planned vs. Actual", a new column titled "POD exceptions" is now available to indicate any scanning exceptions.