Last updated: 2025-09-02

Customising the scan list in Opter Driver

Applies to Opter Driver for iOS and Opter Driver Labs for Android.

In this Price item

The scan list is the view displayed when a driver has scanned the parcel. It is possible to set which fields are displayed in the scan list and which information should be displayed for each package on the order.

Instructions for drivers are available in Scanning with Opter Driver.

Setting which fields are to be displayed

To set the fields to be displayed in the scan list, use the Design field for mobile window or the XML file App.OpterDriver.Design (or App.Design). For more information, see Customising the layout and features of Opter Driver. The fields are described in Design field for mobile (window).

For example, perhaps the following fields are to be displayed:

  • Package ID number [PACKAGE.PACKAGEID]

  • Status (package) [PACKAGE.STATUS]

  • Scan time (package) [PACKAGE.SCANTIME]

  • Terminal name (package) [PACKAGE.HUBNAME]

  • Resource (package) [PACKAGE.RESOURCE]

  • Comment (scanning) [PACKAGE.SCANCOMMENT]

  • Dimensions (package - scanning) [DIMENSIONSSTRING] (more information in Setting which package information to display below)

Setting the package information to be displayed

In the scan list, package information such as weight, volume, pallet location, package type and type of goods can be displayed. Package information is shown for each package in the order.

To display package information in the scan list, proceed as follows:

  1. Use the PackageDimensionsString mobile data setting to set which text and information is to be displayed about the packages in the scan list, for example "Pallet space: 17”. For more information, see Detailed instructions for PackageDimensionString below and in Mobile data settings (window).

  2. To make the settings in PackageDimensionsString show, proceed in one of the following ways:

    • If using the Design field for mobile window:

      The Design field for mobile is accessed by clicking on Settings > Mobile data > Design field for mobile.

      Click on the Scanning view tab and search for the Dimensions (package - scanning) [DIMENSIONSSTRING] field. If it is in the Excluded list, drag and drop Dimensions (package - scanning) [DIMENSIONSSTRING] into the Included list. It is also possible to double-click on a field to move it to the other list. Click on Save at the bottom.

    • If using the App.OpterDriver.Design XML file (or App.Design):

      What is between the tag pair <scanrows> </scanrows> and App.OpterDriver.Design is displayed in the scan list.

      Add PACKAGE.DIMENSIONSTRING between the tag pair <scanrows> </scanrows>, where you want it.

      For complete examples of what the XML file App.OpterDriver.Design might look like and for more information, see App.OpterDriver.Design. Save your changes once you are done.

Add the mobile data setting PackageDimensionsString and enter “| Package type: {14} | Weight {1:0.##} kg | Volume: {2:0.##}" in the Value column. The variables ({0}-{15}) take their values from the package rows.

PackageDimensionsString is a free text field. This means that any text required can be written around the variables, for example:

  • “Package type: {0}, total weight {1:0.##} kg, volume: {2:0.##}.”

  • “The package is of type {14}, has a volume of {2:0.##} and weighs {1:0.##} kg.”

For information on what other dimensions can be displayed, see Mobile data settings (window).

Variables that return numbers

For variables that return numbers, it is possible to specify how many decimal places to display in the scan list, and whether to exclude unnecessary trailing zeros at the end of the number. In our example (“Weight: {1:0.##} kg”), we have limited the number of decimals for the weight to a maximum of two, but if the weight is “8.00” on the package row, only “Weight: 8 kg” is displayed in the scan list. If the weight in the package row is “8.10”, “Weight: 8.1 kg” is displayed in the scan list. The unnecessary trailing zeros after the decimal point are deleted.

The syntax works in the same way as in text and HTML reports. The number of decimal places is limited by the number of zeros after the decimal point (0.00). To exclude unnecessary trailing zeros, enter # signs instead of zeros. The dot is converted to a comma in the app.

Numbers are stored with six decimal places in the Opter database. If a limit is not defined, all numbers are always displayed to six decimal places. For example, if “Width: {5} m” is entered in PackageDimensionsString, “Width 2.000000 m” will be displayed in the scan list.

Vikt: {1:0.00}
Volym: {2:0.##}
Flakmeter: {3:0.00#} 
Pallplats: {4:0}
Bredd: {5:0.00}
Höjd: {6:0.00}
Djup: {7:0.00}

Returns

Weight: 8.00

Volume: 8.12, or 8.1 (if the number on the package row is 8.10), or 8 (if the number on the package row is 8.00)

Load metres: 8.123, or 8.12 (if the number on the package row is 8.120), or 8.10 (if the number on the package row is 8.100)

Pallet space: 8

Width: 8.00

Height: 8.00

Depth: 8.00

Block or warn about another resource when scanning

It can be set so that scanning is blocked or that drivers receive a warning if they try to departure scan and/or pickup scan a shipment that is not scheduled for that resource. You set from which status the departure scan and/or pickup scan should be blocked or that the driver should receive a warning. For instructions, see Block or warn about another resource when scanning in Opter Driver.

Warning for early collection

You can set it up so that the driver receives a warning if they pick up too early from the sender. Instructions and more details are available at Warning for premature collection, Opter Driver.

Limitation in the scan list settings

For Opter Driver (classic) for Android, you can set whether collision scans are displayed in a block or as separate scans in the scan list using the Mobile data settings OneScanRowPermission. For Opter Driver for iOS and Opter Driver Labs for Android, collision scans are always displayed in blocks, regardless of the setting you have made for OneScanRowPermission. For more information, see Mobile data settings (window).

Troubleshooting

If you are using Design field for mobile and your changes Design field for mobile are not visible in the app, see Setting which fields are displayed in Opter Driver.

See also