Last updated: 2025-09-02

Mandatory deviation in case of delay in Opter Driver

Applies to all variants of Opter Driver, (i.e. Opter Driver (classic) for Android, Opter Driver for iOS and Opter Driver Labs for Android).

In this Price item

When a driver sets the status of a shipment to unloaded or performs a delivery scan later than the last delivery time indicated on the order, the delivery is considered late. This only applies to deliveries to the recipient, not to the Terminal.

You can choose whether the driver must enter:

You can make exceptions to the general setting for certain customers.

If you have made it mandatory to enter a deviation, the following happens:

  • In Opter Driver for iOS and Opter Driver Labs for Android, the Deviation button appears in the POD view where the driver must enter a deviation. The button is highlighted in yellow (mandatory) and turns green when the driver has registered a deviation.

  • In Opter Driver (classic) for Android, the option Deviation appears in the POD view where the driver must enter a deviation. The option Deviation is highlighted in yellow (mandatory) and turns green when the driver has registered a deviation.

It is not possible to save the pod until the deviation has been registered.

Conditions

  1. Check that the Mobile data settings AddNewDamagePermission are not set to "false". If it is, the driver cannot add new deviations. For more information, see Mobile data settings (window).

  2. Check that the settings for the deviation view are as you wish. You set which fields are displayed using the Mobile data settings DAM_. For example, DAM_CommentPermission controls whether the field Comment is displayed or not. For more information, see Mobile data settings (window) and Customising the deviation view in Opter Driver.

Plan

The steps below provide detailed instructions, but first choose the scenario that best suits your organisation:

  • Drivers should indicate deviation for one or a few customers.

    Set App.ForceDamageOnDelay to "False" (default) and tick the checkbox Force deviation if delayed delivery for the customers you want the driver to enter deviation for.

  • Drivers should indicate deviation for all customers.

    Set App.ForceDamageOnDelay to "True".

  • Drivers should indicate deviation for all customers except one or a few customers.

    Set App.ForceDamageOnDelay to "True" and untick the checkbox Force deviation if delayed delivery for those customers where the driver is not required to provide deviation.

Step 1: Setting whether deviation should be indicated

Valid from version 2.4.23 of Opter Driver for iOS and Opter Driver Labs for Android, and all versions of Opter Driver (classic) for Android.

Select whether it should be mandatory for drivers to indicate deviation in case of late delivery. To set what should apply generally to customers, do the following:

  1. In Opter, click on Settings > Mobile data > Settings mobile data.

  2. Click on an empty row in the Name column and then on the down arrow in the row being added.

  3. For example, select App.ForceDamageOnDelay from the list. Enter “True” or “False” in the Value column as follows:

    • “True”: Drivers must indicate deviation in case of delayed delivery.

    • ”False” (default): Drivers do not have to declare deviation in case of late delivery.

  4. Click on Save.

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

Step 2: Make exceptions for certain customers

If you want to exclude some customers from the general setting (App.ForceDamageOnDelay) in the step above, please do so:

  1. Click on Register > Customers. In the list on the left, select for which customer the setting is to be made.

  2. Click on the Dispatching tab.

  3. Use the Force deviation if delayed delivery checkbox in the Alternative for Opter Driver box to select what should apply for that customer. The Force deviation if delayed delivery checkbox can be set in one of the following ways:

    • : Drivers must indicate deviation in case of delayed delivery.

      This setting replaces the one defined in App.ForceDamageOnDelay for the customer that has been selected.

    • : Drivers do not have to declare deviation in case of late delivery.

      This setting replaces the one defined in App.ForceDamageOnDelay for the customer that has been selected.

    • : (Default). The mobile data setting App.ForceDamageOnDelay is followed for the customer that has been selected.

    The mobile data server may need to be restarted for this setting to take effect. Contact for more information.

  4. Click on to save all changes.

Step 3: Require approval in dispatch

Choose whether or not deviations need to be approved in the dispatch centre by doing the following

  1. Click on Settings > Mobile data > Shipment Change Elements.

  2. Select Deviations in the list on the left and set the Require Approval checkbox as follows:

    • : Any deviation must be authorised by the dispatch.

    • : Deviations do not need to be approved by the dispatch centre.

    This setting applies to all deviations, not just those recorded in case of late delivery.

  3. Click on to save all changes.

Step 4: 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.

Troubleshooting

If it doesn't work as it should in the case of late delivery, check the following, for example:

  • Check the settings in the Deviation events window. If the checkbox Available in mobile device is unticked for all deviation events, drivers will never be able to enter any deviation in Opter Driver. See also the checkbox Available in mobile device the windows Deviation reasons and Deviation types.

  • If the settings do not seem to take effect, ask support to restart your mobile data server. Contact for more information.

  • Only delivery to the order receiver can be considered to constitute a delayed delivery, not delivery to the terminal.

See also