Last updated: 27.03.2024

Valid from: 2023.02.00 and later

Require deviation for POD registration in Opter Driver for iOS

It can be made mandatory for the driver to add a deviation when a POD of a certain type is registered for a shipment. For example, there may be a specific POD type for failed delivery for which a deviation is always required. A specific deviation type, event and reason can also be set up to be pre-filled in the app when the deviation is registered.

Note:

This setting only applies when the proof of delivery is registered in Opter Driver for iOS, not when it is registered in Opter Terminal, dispatch or order reception.

Conditions

Check that the mobile data settings DamagesPermission and AddNewDamagePermission are configured as desired:

For the driver to be able to see deviations that are already on the shipment, DamagesPermission has to be "True" (default), in which case the following applies:

For more information, see Mobile data settings (window).

Step 1: Define the POD types that require a deviation

Click on Settings > Proof of Delivery (POD) > Proof of delivery types and select the POD type (e.g. “failed delivery”) for which deviations are required in the list on the left. Then select the Deviation mandatory checkbox.

Step 2: Enter the preselected deviation type, event and reason (optional)

Select the values to be pre-filled in the app from the Deviation type, Deviation event and Deviation reason drop-down lists. Click on to save all changes.

When the driver taps Deviation in the app, the fields are pre-filled with the “failed delivery” deviation type, for example.

Step 3: App users have to log out

Users who are logged in to Opter Driver when the changes are saved in Opter must log out and then log back in to the app to see the changes.


See also

Mobile data settings (window)

Proof of delivery types (window)

Introduction to POD (proof of delivery)

Adapting the POD view in Opter Driver for iOS