FAQ: Palletforce cross-dock and barcode
Answers to common questions about Palletforce cross-docking in Qargo: barcode generation, mobile scanning, supported scan codes, and known limitations.
Table of contents
Q: How does Qargo now support Palletforce cross-dock operations, and what data is provided at dispatch? What happens with a multi-terminal pallet network setup: will the barcode still scan?
A: Qargo provides comprehensive support for Palletforce cross-docking by enabling barcode generation early in the workflow and facilitating mobile scanning updates.
- Barcode generation at dispatch: Pallet barcodes are now generated directly in Qargo immediately after an order is imported or dispatched. This ensures that every pallet has a corresponding barcode assigned to its goods trace before the cross-docking process begins.
- Mobile scanning and transmission: Users can use the Qargo mobile application to scan these Palletforce labels during the physical cross-dock process. This scan data is then sent to Palletforce to update shipment tracking and status.
Scanning workflow
Cross-docking allows drivers and terminal staff to scan Palletforce barcodes using the Qargo mobile app. Each scan transmits a status update directly to Palletforce.
The standard scanning sequence for a cross-docked pallet is:
- Pickup from shipper: the scan triggers a SCOT (pickup from shipper) status update to Palletforce.
- Receipt at inbound terminal: the scan triggers a SRID (scan on receipt at inbound terminal) status update.
- Arrival at delivery terminal: the scan triggers an ARRD (arrival at delivery terminal) status update.
- Delivery to receiver: the scan triggers a DELV (delivery) status update.
Supported scan codes
The following Palletforce scan codes are supported in the Qargo mobile app:
| Code | Description |
|---|---|
| SRID | Scan on receipt at inbound terminal |
| SCOT | Pickup confirmation from shipper |
| ARRD | Arrival at delivery terminal |
| DELV | Delivery confirmation |
Barcode changes after generation
If the delivery terminal or service level on an order is changed after the cross-docking barcode has been generated, the existing barcode will no longer reflect the correct routing.
- The barcode must be regenerated before the pallet is scanned into the Palletforce network.
- Scanning an outdated barcode may cause routing errors at the inbound terminal.
External barcode changes
If Palletforce assigns a different tracking number to the shipment after export (for example, due to a terminal reassignment), the barcode on the physical label will differ from the one in Palletforce’s system.
- The label must be reprinted after the correct tracking number is returned from Palletforce.
Handling multi-terminal barcode scans
-
What does this feature do?
- It makes cross-dock barcode resolution terminal-aware. When several orders share the same barcode, a scan is attributed to the order whose shipment actually passes through the terminal where the scan is performed.
-
Why does it matter?
- In multi-terminal pallet network setups, the same physical shipment can exist as two orders that share the same barcode. Previously, the scan was attributed to the most recently created order, which could belong to the wrong terminal. This sent incorrect status updates back to the network.
-
How does it work?
- The pallet shown on screen, the stop that is completed, and the order the scan attaches to all reflect the correct terminal. Outbound Palletforce status updates sync to the integration instance of the scanning terminal. Unique-barcode scanning is unchanged; the terminal tiebreaker only runs when a barcode is genuinely ambiguous.
Use cases
- A carrier runs a multi-terminal pallet network where a shipment is dispatched from one terminal to another. The same shipment exists as two orders sharing one barcode and tracking ID. When a driver scans at the sending terminal, the scan now attaches to that terminal’s order and the correct status flows back to the network, rather than being attributed to the receiving terminal’s order.
Terminology
| Term | Definition |
|---|---|
| Cross-dock scanning | The process of scanning a pallet barcode at a terminal to record its movement and complete the relevant stop. |
| Barcode resolution | The step that matches a scanned barcode to a single goods trace (and therefore to one order). |
| Terminal-aware resolution | Resolution that uses the terminal where the scan is performed to choose the correct order when a barcode is shared. |
| Goods trace | The internal record that links a barcode to a specific order and shipment. |
| Integration instance | The connection between a terminal and the pallet network used to sync status updates. |
How terminal-aware resolution works
- Scan a pallet barcode at the terminal during cross-dock handling.
- View the pallet details on screen. These belong to the order that actually moves through the scanning terminal.
- Complete the scan. The resulting status update completes the correct stop on the correct order.
- The outbound Palletforce terminal event (pickup or delivery) is attached to the integration instance of the scanning terminal.
Troubleshooting
| Issue | Guidance |
|---|---|
| A scan still attaches to the wrong order | Check whether both shipments sharing the barcode have a stop at the scanning terminal. In that case, the system falls back to the previous most-recent-match behavior and logs a warning. |
| A bulk or offline scan resolves differently | Bulk and offline scans, and older mobile builds, rely on terminal-aware barcode resolution rather than the round-tripped pallet identifier. Accuracy is the same, but resolution happens on the backend. |
| Incident report lookups are not terminal-specific | Bulk barcode lookups used by incident reports are not terminal-scoped in this version. |
