We poll the Palletline API once every minute to receive new statuses.
Statuses that are generated by Qargo are pushed to the API as part of the visibility framework (happens as a side effect of specific events, e.g. delivery stop completion).
Status import
Most statuses are just registered in Qargo on the barcodes but some also trigger actions in Qargo (all barcodes need to have this status before the status transition is triggered):
Collection depot use case
DEPD will complete the collection depot stop on the delivery stage (start time = end time)
ARRI will start the delivery stop
EPOD / DELD / DELS / DNDS / DOML / DRDC / LASI / MPOD / DEBC / POD will end the delivery stop
Delivery depot use case
SCOT will complete the pickup stop and put the driving task to the delivery depot stop on the collection stage in progress (it is the earliest Palletline status we receive; no Palletline statuses for the collection itself exist)
ARRD will complete the delivery depot stop on the collection stage
Status export
Qargo sends out statuses when:
Collection depot use case:
SCOT when the pallet is scanned in the collection depot by the cross dock app
Delivery depot use case:
ARRD when the pallet is scanned in the delivery depot by the cross dock app
SCDV when the pallet is scanned out the delivery depot by the cross dock app
ARRI when the delivery stop is started by the driver via the FMS/mobile app
EPOD when the consignee signature is created in Qargo
POD when the POD is uploaded in Qargo