Barcode scanning at order locations for order completion will now allow for scanning 1D and 2D barcodes, as well as QR codes. You can apply this to any order type and multiple barcodes for single orders are allowed. It is part of the Proof of Delivery form, including Custom POD.

Barcode scanning is available on Trial, Pro, and Custom Plans.

How to enable

Driver applications will need to be updated to the iPhone version 2.16.7 or above or Android 2.16.5 version. If you use Custom Forms, please reach out to Support for assistance in using the two together.

Optional: In the Mobile App Configuration (Administration > Mobile Apps > Configuration) the Administrator can adjust the workflow in case of exceptions or issues, such as missing items (barcodes), unexpected barcodes, unscannable barcodes, or the collection of unplanned barcodes.

Settings can be changed to either disallow unexpected barcodes, manually enter, or scan a new one. Settings can also be adjusted to require a photo when a barcode is non-scannable. Drivers can also mark a barcode as ‘item missing’ to support partial deliveries. Enabling the collection of unplanned barcodes is also possible.

How to use

You can set pre-attached values to an order, either manually, during import, or through API order insert. You just need to define the barcode’s values, though you are still able to use barcode scanning with unplanned barcodes. To do that, enable the collection of unplanned barcodes as explained in the previous section.

Our system supports a variety of barcodes, including 1D and 2D barcodes, QR codes, etc. OptimoRoute’s barcode scanning capabilities can support various types of barcodes, such as: 1D barcodes like UPC-A, UPC-E, EAN, Code 39, Code 93, Code 128, Interleaved 2 of 5, ITF-14, Codabar and others, as well as 2D barcodes like QR, Data Matrix, PDF417, Aztec and others.

Manually: Use the ‘Barcodes’ section in the Add/Edit Order window.

Import: Have a separate column in the spreadsheet titled ‘Barcodes’ and use the dedicated field ‘Barcodes’ when mapping. In an Excel file, multiple barcodes can be entered for a single order by separating them with a comma. For CSV, use the double quotes when using multiple barcodes for a single order.

API insert: Barcodes are pre-attached to an order when using the call ‘Create Order’ or Create or Update Orders.’ ‘OrderData’ will send single or multiple barcode object key-values in an array.

Displaying barcodes attached to orders

Two new columns are now available for display in the Orders data grid: one indicating whether a barcode is attached to an order, and another showing the actual values of the barcodes.

How to scan

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 included for the actual scanning. For orders with multiple barcodes, the drivers are able to batch scan all the barcodes at once or to scan each one individually.

While scanning, the screen will display a scanning frame and provides feedback on the scan results. If there is an issue with the scan, there is a ‘Scan issue’ dialogue that can be used.

A photo requirement for an unscannable item will depend on the workflow the Administrator set up in Mobile App > Configuration.

If an unexpected barcode is found, the driver has the option to scan a new barcode or enter the value manually.

Barcode collection is a separate section in the ‘Proof of Delivery’ form, dedicated to attaching new, unexpected barcodes to an order.

Monitoring the barcode scans 

In the web-app: The Live and Analytics tabs will show collected barcodes in the Proof of Delivery data. It will show expected barcodes, photos taken of barcodes, and exception statuses. As a dispatcher, you will be able to see icons showing a barcode exception in the Live and Analytics Plan History screens. The Analytics Planned vs Actual report will also include an option to show a flag for a POD barcode exception.