A cross dock (XD) is a location where incoming goods, from various suppliers are unloaded from inbound trucks / containers. They are sorted and then loaded onto an outbound truck / container to the final destination. The main purpose of a cross dock is to streamline logistics operations:
cross docking allows consolidating shipments from multiple sources, enabling efficient distribution of goods that have a similar or nearby delivery location.
by consolidating shipments at a cross docking facility, transport companies can optimise load capacity, reduce the number of delivery vehicles needed, and minimise transportation costs.
for long distance transportation, repeated cross docking at strategically located facilities along the route allows to overcome the logistical challenges associated with covering vast distances.
Qargo has extensive cross dock functionality built in to the platform; including integrations with some of the leading pallet networks and the Cross Dock scanning function available in the Qargo Mobile App. Pallet tracking history is available directly from the consignment showing the current location, as well as previous scanned locations and status updates.
Terminology
Inbound Vehicle: Vehicle arriving at a location with collected freight on board.
Outbound Vehicle: Vehicle at a hub/depot location loaded with freight for delivery.
Requesting Depot: Depot that is requesting service and will report to customer, but will not actually complete collection or delivery; often used in Pallet Networks.
Collection Depot: Depot location associated to the collection leg of a consignment
Delivery Depot: Depot location associated to the delivery leg of a consignment
Transfer Depot: Depot location between collection & delivery legs; this stage is often referred to as shuttle or trunk (Owned / Partner network)
Hub: Transfer depot associated with Pallet Networks referred to as Hubs.
Terminal: Depot location often associated with carrier satellite locations; see also 'Hub' and 'Depot'
Scanned in: Scan status associated with arrival and unload events at hub/depot locations; uses fixed format structure comprised of location & event.
Scanned out: Scan status associated with load and departure events at hub/depot locations; uses fixed format structure comprised of location & event.
Free Scan: Use to scan either inbound or outbound freight.
Stored: Scan status indicating off-loaded freight that is not immediately sent out for delivery
Trunk: Transfer of goods between a collection and delivery depot; goods are offloaded to the new depot or can remain on a dropped trailer for allocation
Shuttle: See 'Trunk'
Transport Network: 3 types of networks identified
Owned Network: Transport company has 1 or more depots they use
Partner Network: Transport company works with partners to execute local collection & deliveries from own depots
Pallet Network: Transport company works with a central authority that decides how local collection / delivery are distributed and executed via central hubs.
Configuration
Location setup
To be able to cross dock, at least one location should be setup and marked as an internal depot. When combined with the Qargo Mobile App cross dock scanning function, locations marked as depots will be shown available on the app.
Step 1: Create the Depot as a Transport Network
Navigate to LOCATIONS > Transport networks
From the left menu, click '+Add transport network'
From network type, select from 3 available options:
Own network - use to create a network of owned depots, even if only a single location
Partner network - use to create a network of partner owned depots
Central network (pallet networks - see below) - use to create a network for an existing pallet network partner
Complete the General Info section - provide a name / description.
The code field is required when implementing integrations with networks.
Step 2: Add the Depot location to the Network
Click on the new Network - Hubs & depots will show in the right panel.
Click the green 'New Depot' button.
Complete the new depot details.
If the location is not showing in the drop down, use the '+ Create new location' to add to the location database.
Complete Depot leads times for collection & delivery depots
Default will be set as 'same day', with options for +1 and +2 days.
Complete *Exceptions: depots without a direct connection (*See details below)
Click Save
*Exceptions: depots without a direct connection
This section lists depots in a network that cannot be reached on a direct leg
Requires intermediate depot or hub on route
System will automatically create route via intermediate hub specified
Orders structured with stages that mirror real-world transfer points
Prevents errors in planning operationally impossible trips, while ensuring accurate order splitting across all legs
Cross dock modes (APP Configuration)
The cross dock app in Qargo offers two main modes to control how goods are handled during cross docking:
Location scanning mode: Operators are prompted to scan the physical location (such as a specific bay or outbound vehicle) where pallets are placed. This ensures that every move is precisely registered, helping track not only when but also where a pallet was placed within the depot.
Keep pallets on truck while unloading mode: In depots with limited space, operators may leave pallets on the inbound trailer and only fetch them when it's time to load them onto the outbound vehicle. When this mode is enabled, the app does not automatically assume that unloading results in a loading or storage action—so pallets can stay on the trailer until needed..
Barcode setup (Qargo Admin only)
From Order Input select Packaging types from Cargo Options.
Scroll to the 'Configuration' panel and ensure the 'Generate Barcodes' toggle is on.
This must be on in order for the barcodes to generate on orders.
Document types activation
Navigate to CONFIGURATION > Documents.
Use the ALL tab to see the whole list
Toggle templates ON:
Pallet Labels (orders)
Trip sheet / Loading sheet (trips)
This enables these document templates so they can be used as part of the workflow task: document generation.
Document generation: Labels with barcode
Documents can be generated as part of the task workflow in the system. A template for the document must be created.
From Configuration > Templates, click the green 'Add template' button.
Select the option 'Pallet label' from the list of available templates
Select the base template 'Pallet label with barcode'
Give the template a name.
A preview of the label will be displayed in the right panel.
Modifications to the label are possible by updating the appropriate row details
To add the barcode enter the code into the first INFO field.
Click SAVE
📚 To add trip number as a bar code on loading sheet for scanning in XD workflows use:
{{barcode "CODE128" shipment_name 10 3}}
Document generation: Loading sheet > Trip
From Configuration > Templates, click the green 'Add template' button.
Select the option 'Loading sheet > Trip' from the list of available templates
Select the base template from the drop down & give the template a name.
A preview of the sheet will be displayed in the right panel.
Modifications to the sheet are possible by updating the appropriate row details.
Click SAVE
Add Workflow task
With the document templates added, tasks that use these documents can be setup
From Configuration > Tasks
Add a task below Orders, for instance below 'Create consignment' to generate a pallet label
Enable users (APP Configuration)
Add new users and set role as 'Warehouse Operator'
Gives access to app with a separate 'Cross dock' tab
Features
Barcodes
Barcodes can be either Qargo generated or externally generated, ie: network or customer-provided
Generating barcodes can be configured as part of the task workflow
Barcodes are enabled per packaging type when being created in 'Order input'
Provides full traceability for every scan event (loading / unloading, etc)
Each scan contributes to a chronological history of the pallet
Externally generated barcodes may be imported via integration or API, creating the link to goods in Qargo
Qargo Cross Dock app will work with both Qargo and externally generated barcodes.
All barcode scans are stored as part of the pallets audit trail, regardless if scan is from Qargo app or alternate source.
Full track and trace visibility per pallet within the application.
Limitations:
If external barcode is not registered via integration, it may not be recognised and the warehouse may need to relabel pallet with Qargo barcode
Multiple pallets cannot be identified by a single barcode, each pallet requires it's own label with a barcode for scanning.
Pallet Labels
Labels include key operational information:
routing instructions
delivery address
service level (ie: next day)
number of pallets (ie: 1 of 3)
Warehouse can print Qargo labels on demand for unlabelled goods
Label templates are adjustable, including sizes and layouts.
Labels incorporating barcodes can also be used within warehouse locations or trucks, connecting pallet's movements with specific locations for visibility.
Scanners & Scanning App
Qargo supports Zebra and Honeywell barcode scanners for use with the cross dock mobile app.
Scanners should run at least Android 8 (released 2017) or higher for compatibility with the Qargo app.
The Qargo cross dock module is built for warehouse operations and is tested specifically on these brands for accurate and reliable scanning.
Other Android-compatible barcode scanners may also work if they meet the OS requirement.
Click the link below to learn more about how the Qargo app works for scanning.
Track & Trace
Qargo’s cross dock track & trace logs every pallet scan with time, place, and action—maintaining a complete, real-time history from arrival to final loading and sharing this visibility across internal and external systems.
Each time a pallet is scanned—inbound, moved internally, or loaded outbound—a 'scan event' is recorded.
Full chronological history of every barcode scan is linked to the pallet - visible within the order.
Visibility for each handling step (when/where it was unloaded, moved, loaded, or stored) in the system, providing total traceability for audit, KPI, and incident resolution purposes.
Scan events can be generated in Qargo’s own cross dock app or received from integrated external systems and pallet networks.
Scans are not limited to preset operational flows—you can scan pallets in any sequence (e.g., unloading, internal moves, or loading), and every movement is part of the pallet’s audit trail.
Statuses from external networks/pallet systems (like Palletline or Hazchem) can also sync with Qargo, so you get a single, consolidated view of all pallet movements throughout the network.
Driver Scan: Collection / Delivery
In some instances, the driver may be required to scan pallets at the collection and / or delivery locations. Drivers are able to scan multiple barcodes, improving visibility for which pallets were collected / delivered.
To enable this functionality:
Create a new TASK, on Trips to prompt driver to scan codes.
Driver scan workflow:
Once the barcode has been added in the mobile app and the user clicks ‘save’, it is no longer possible to edit or remove the barcode. Before clicking save it is possible to edit or remove it.
Pallet Networks
Configuration:
Each pallet network will have their own onboarding / setup steps, below is a general summary:
Configure pallet network in Qargo (LOCATIONS > Transport networks).
Add depot(s) locations and mark internal as required.
Define / update packaging types to match network pallet types & enable 'Generate barcodes' for proper scanning functionality.
Modes of operation: select mode for trunks (barcode vs static code)
Enable integrations and export mappings so that status updates, documents and labels sync to supported networks.
When setting up a Pallet Network a new Cross Dock option will show in the 'transport network configuration' panel. When selected this shows 'Trunks', with options to select from Header scan or Trunk code.
Relates to functions when loading / unloading, select trunk
Options depend on the Network partner require either:
Scan a trunk 'header' barcode
Select trunk by predefined code
Loading / Unloading functions
Dedicated flows for loading / unloading trunks specific to each network.
Select trunk either by scanning a barcode (header scan) or select from predefined codes (as set in the network config - above).
Inbound cross dock events include:
Unloading trunk at collection depot
Loading for delivery at a delivery depot
Scan trunk or select from list.
Scan pallet label to register movement (unload, store or load for delivery).
Pallet movements ('free scanning') can also be recorded in consignment's pallet history.
Scans logged and sent as status updates to respective network.
Trunk trips not explicitly planned in Qargo, pallets scanned and associated to selected trunks.
To learn more about loading / unloading workflow on the app, click the link(s) below.
Sending Scan status
Scan status via Qargo app pushed to pallet network systems and updated.
Scan status generated by network depots or network scanners can be imported & synced into Qargo.
Scan updates sent in near real time updates - sent as soon as scan is processed.
Trunk loading / unloading supported - all scanned pallets associated to trunk & scan events exported to network
Pallet tracking history visible in the consignment in Qargo & network
scan info includes:
time
event type (ie: arrived, loaded, held in depot)
barcode / identifier at pallet level
Incoming scan status from other depots or networks own hardware synced back to Qargo & visible in history.
Scan Status Definitions
Main pallet scan statuses reflect movement of pallets through network. Not every status is tied to a physical scan, some are automatically generated for operational visibility. Some of the main pallet scan statuses are defined below.
Stored / Held in depot: pallet stored in depot either at collection / delivery end
Variants: CD Held (collection depot held) / HUB Held / TD held (Transhipment depot held) / DD held (Delivery depot held)
Scanned in/out: pallet scanned into / out of a location ie: depot or trunk.
Variants: Collection depot scanned in / Collection depot scanned out (trunk) / Delivery depot scanned in / Delivery depot scanned out (to delivery vehicle)
Loaded / Unloaded: pallet loaded onto / unloaded from trunk or delivery vehicle
Variants: CD load (Collection depot load) / HUB load / TD load (Transhipment depot load) / DD load (Delivery depot load)
Delivered / Delivered sign: Delivered to consignee / signature taken
Departed: departure from specific location (ie: collection depot)
Variants: COL Dep (collection depot departed) / CD Dep (collection depot departed) / HUB dep (HUB departed) / TD dep (Transhipment depot departed) / DD dep (delivery depot departed)
Trip/Stop events: status linked to trip movements (ie: arrive / depart)
ARRI (Arrived at delivery location): driver arrived, pallet may still be on vehicle
EPOD: Consignee signature captured completing delivery
Specific Examples (Pallex/Fortec mapping to Qargo status):
Arrived at Collection Point → COLLECTION_ARRIVED
Loaded to C&D → COLLECTION_SCANNED_IN
Depot Scan In/Out → COLLECTION_DEPOT_SCANNED_IN / COLLECTION_DEPOT_SCANNED_OUT
Out for Delivery → DELIVERY_DEPOT_DEPARTED
Arrived at Delivery Point → DELIVERY_ARRIVED
Delivered (POD complete) → DELIVERY_DEPARTED
📚 Exact codes vary between networks. There may still be legacy scan codes: SCDV = Scanned onto delivery vehicle & ARRD = arrived at depot. If a status can't be mapped, it will show as 'Other'.
Add a Cross Dock
To add a cross dock (depot stop) to an order in Qargo:
Open the order you want to update.
In the order’s route/stop section, add a new stop at the location in the journey where you want the cross dock to take place.
Select the correct depot or cross dock facility as the stop location.
You can drag and reorder stops to make sure the cross dock appears between the collection and delivery legs.
If you want to do this for multiple orders at once, use the “Bulk add activities” feature from the Quick Actions menu on the order list to add depot stops to several orders simultaneously.
If you are using TMS-WMS integration (like Clarus):
Orders are often exported from Qargo to the WMS, where the cross dock (XD) is modelled as a stop (or order) in the warehouse management system.
For dual-leg orders (collection + delivery), the cross dock is placed between these legs.
The correct linkage and visibility of cross dock stops may also depend on integrations (ie: Clarus).
After adding a cross dock stop in Qargo and confirming/planning, the associated cross dock record/order will be created in the WMS (if integrated).
For groupage/cross docking operations:
Internal depots must be correctly configured as cross dock locations in your transport network settings for them to be available as stops when adding to an order.
Important notes:
If the cross dock stop has already been confirmed/synced to the integrated WMS, you may need to remove or adjust it on both sides (Qargo and WMS) for changes.
When importing orders in bulk or via API, you can include the depot stop in the import/template so that cross docking is planned automatically for all relevant orders.