Prevent delivery scanning if the resource is not stated on the last shipment
Last updated: 29.10.2024
In this article
The scanning done upon delivery to the receiver on the order is called delivery scanning. This sets the POD type to Delivered (if you have not renamed it). The delivery scan is therefore the scan that is carried out when unloading the last shipment on the order, and sets the entire order to the status Delivered.
It can also be configured so that only the resource stated on the last shipment can do a delivery scan in Opter Driver. The resource stated on the last shipment must therefore be logged in to Opter Driver in order to be able to scan it for delivery. This is to prevent the order from being delivery scanned by mistake if the various shipments are assigned to different resources.
Click on Settings > Offices > Scanning tab and select Block delivery scan if the shipment is not allocated to the resource.
Example
If an order has two shipments with different resources, the resource on the first shipment cannot delivery scan when unloading that shipment at the terminal, even though the resource has "finished" its part of the order.
The setting does not prevent incorrect use of delivery scanning. If the two shipments in the example above are allocated to the same resource, they can scan the first shipment upon arrival at the terminal, when they should actually have scanned the goods on arrival.
Sometimes the POD type Delivered is set on shipments other than the last one, for example if the remaining shipments on the order are carried out by another supplier. This can result, for example, in notifications being sent to the receiver stated on the order, stating that the goods have been delivered, even though that is not the case. A certain proof of delivery type can be set so that it may only be used for the last shipment on an order. For more information, see Preventing a proof of delivery type from being used for shipments other than the last one on the order.
