Skip to main content
Qargo

Status import/export

Table of contents
  1. Status import

Qargo polls 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 (this happens as a side effect of specific events, e.g., delivery stop completion).

​

Status import

Most statuses are only 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):


Pickup terminal use case

  • DEPD will complete the pickup terminal 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 terminal use case

  • SCOT will complete the pickup stop and set the driving task to the delivery terminal stop on the pickup stage to in progress (it is the earliest Palletline status Qargo receives; no Palletline statuses exist for the pickup itself)
  • ARRD will complete the delivery terminal stop on the pickup stage

Status export

Qargo sends out statuses when:
Pickup terminal use case:

  • SCOT when the pallet is scanned in at the pickup terminal by the cross-dock app

Delivery terminal use case:

  • ARRD when the pallet is scanned in at the delivery terminal by the cross-dock app
  • SCDV when the pallet is scanned out of the delivery terminal by the cross-dock app
  • ARRI when the delivery stop is started by the driver via the FMS/mobile app
  • EPOD when the receiver signature is created in Qargo
  • POD when the POD is uploaded in Qargo