ACRIBOR
SimplyOSWhy SimplyOSDuratPlatform PricingIntegrationsHelp Centre DevelopersSecurityAboutContact
Help / Delivery

Delivery, POD and exceptions.

Delivery closure should leave evidence, outcome and exception context attached to the shipment.

Working model

01

Reach the delivery stop

The trip and stop context identifies what is expected at the location.

02

Record the outcome

Complete delivery or record a failed delivery reason when delivery is not successful.

03

Capture evidence

POD can include photo or document evidence linked to the shipment.

04

Structure the exception

Damage, shortage, loss or other receiving exceptions should be recorded as explicit data.

05

Close downstream work

POD and delivery state can feed customer visibility, billing, reporting and exception queues.

Good to know

NDR is not a free text dead end

Failed delivery belongs to a follow up workflow.

RTO can remain linked

Return movement stays connected to the original shipment context.

Missing POD can be surfaced

The Control Tower can treat absent delivery evidence as an operational exception.

Related help