Skip to main content

PN - Palletforce: Tracking pallet barcodes and status

Tracking: Pallet barcodes and status

Written by Duygu Demir
Updated yesterday

Palletforce provides detailed status updates for the pallets that flow through the system.

These statuses are provided on individual pallet level. The pallets themselves are identified with a barcode, each status update contains a barcode to indicate the pallet it belongs to.

These barcodes are physically present on the pallets, the statuses may be generated upon a scan of such a barcode with a physical barcode scanner, or by other means.

The list of status codes is as below:


Implementation in Qargo

The barcodes assigned to the pallets are registered in Qargo when the first status update is received from Palletforce.

The barcodes are visualised on the consignment together with the latest status update. Te full history can be visualised as well.


Cross-docking barcode generation

For orders processed through the Palletforce cross-docking workflow, barcodes are generated at order creation or import — not at the point of dispatch.

  • Barcodes available immediately so that labels can be printed, applied to pallets, and scanned throughout the collection and delivery journey.

📚 The barcode follows this format:

506 + {delivery depot code} + {service level} + {tracking number} + {pallet number}

Once generated, the barcode and its associated status updates are visible on the consignment in the same way as barcodes registered through the standard post-dispatch flow.

  • The full scan history (including SRID, SCOT, ARRD, and DELV events) is available on the consignment timeline.

‼️ If the delivery depot or service level changes after the barcode is generated, the barcode will need to be regenerated to remain valid.

Did this answer your question?