Reach the delivery stop
The trip and stop context identifies what is expected at the location.
Delivery closure should leave evidence, outcome and exception context attached to the shipment.
The trip and stop context identifies what is expected at the location.
Complete delivery or record a failed delivery reason when delivery is not successful.
POD can include photo or document evidence linked to the shipment.
Damage, shortage, loss or other receiving exceptions should be recorded as explicit data.
POD and delivery state can feed customer visibility, billing, reporting and exception queues.
Failed delivery belongs to a follow up workflow.
Return movement stays connected to the original shipment context.
The Control Tower can treat absent delivery evidence as an operational exception.