Introduction
What does this article cover?
Dispatching a consignment to PALL-EX or Fortec
How the network is determined (PALL-EX vs Fortec)
Label generation after dispatch
Cancelling a dispatch
Collection date rules and the 12 PM cut-off
How orders are imported from Nexus into Qargo
Tracking status synchronisation
POD and document synchronisation
ETA export via Optimize
Who is this for?
Dispatchers and planners sending consignments to the pallet network
Operations staff monitoring shipment status in Qargo
Terminology
Term | Definition |
Resource dispatch task | The Qargo task that, when completed, sends a consignment to the pallet network via the Nexus API |
PALLEX_OUT | The resource code identifying a subcontractor as the PALL-EX network resource |
FORTEC_OUT | The resource code identifying a subcontractor as the Fortec network resource |
Nexus customer ID | The unique code identifying a customer in the Nexus system; must be configured per customer in Qargo |
Cut-off time | 12:00 PM (noon) — the deadline after which same-day or next-day collections require a later collection date |
MPOD | Digital Signature Capture collected at delivery |
POD | Image of the signed delivery note |
MPODPHOTOE | Photo of pallets at the delivery location |
Optimize | The route optimisation module used to push ETAs from Qargo to Nexus |
Order Export (Qargo → Nexus)
Dispatching a Consignment
ASSIGN the trip to the PALL-EX or Fortec subcontractor resource, depending on the network required for the consignment.
COMPLETE the resource dispatch task on the trip. This sends the consignment to Nexus via the API.
VERIFY that a pallet label has been downloaded and attached to the consignment documents panel.
📚 Single-consignment trips only: The export only works when the trip contains a single consignment. Multi-consignment trips are not supported for pallet network export.
How the Network is Determined
The network (PALL-EX or Fortec) is determined by the subcontractor resource assigned to the trip:
Resource code | Network |
PALLEX_OUT` | Consignment sent to PALL-EX |
FORTEC_OUT` | Consignment sent to Fortec |
At dispatch, Qargo passes the corresponding Nexus customer ID (configured on the customer record) to the API. The API routes the consignment to the correct network based on this ID.
What Happens After Dispatch
After the resource dispatch task is completed:
A pallet label is automatically downloaded from Nexus and attached to the consignment in Qargo
The consignment is visible in the Nexus portal
Nexus begins sending scan events back to Qargo as the consignment moves through the network
Cancelling a Dispatch
A dispatch can be cancelled by removing the subcontractor resource from the trip.
This triggers a cancellation request to Nexus and removes the consignment from the network.
‼️ If a barcode conflict exists in Nexus, removing the resource may not be possible directly. See the Troubleshooting article for the resolution steps.
Collection Date Rules
PALL-EX/Fortec applies strict rules to collection dates. Qargo determines the collection service level automatically based on the date and time of export:
Scenario | Result |
Same-day export, before 12 PM cut-off |
|
Same-day export, after 12 PM cut-off | ❌ Error — collection not possible |
Friday export → Saturday pickup | ❌ Error — not supported |
Friday export → Monday, before 12 PM |
|
Friday export → Monday, after 12 PM |
|
Next-day (Mon–Thu), before 12 PM |
|
Next-day (Mon–Thu), after 12 PM |
|
Weekend export → next working day | ❌ Error |
Future date (>1 day ahead) |
|
📚 Maximum collection window: Pallex only accepts consignments for collections scheduled within the next 6 days. Attempting to dispatch with a collection date beyond this window will result in an error.
Label Generation
A pallet label is downloaded from Nexus automatically immediately after a successful dispatch.
The label is attached to the consignment's documents panel in Qargo and can be printed from there.
No manual step is required to obtain the label — it is generated and downloaded as part of the dispatch process.
Order Import (Nexus → Qargo)
How Import Works
Qargo polls the Nexus API every few minutes to fetch new and updated consignments for the depot.
Imported orders follow the standard Qargo order import flow.
📚 If a transport network has been configured on the relevant transport service, imported orders are automatically split into collection and delivery stages and assigned to resources according to that transport network configuration.
Dual Network Import
Because PALL-EX and Fortec share the Nexus API, Qargo imports orders for both networks simultaneously in a single polling cycle.
The network (PALL-EX or Fortec) is identified from the data returned by the API and the relevant codes are used in the import mapping.
Status Synchronisation
Status Import (Nexus → Qargo)
Qargo polls Nexus for status updates every few minutes. The statuses below are imported and mapped to Qargo's tracking lifecycle:
Nexus status | Qargo status |
| Collection Arrived |
| Collection Scanned In |
| Collection Depot Scanned In |
| Collection Depot Scanned Out |
| Hub Arrived |
| Hub Scanned In |
| Hub Stored |
| Hub Scanned Out |
| Hub Departed |
| Delivery Depot Scanned In |
| Delivery Depot Departed |
| Delivery Arrived |
| Delivery Scanned Out |
| Delivery Scanned Out |
🧰 Status import and export happen automatically in the background and cannot be configured in the UI. Only the results are visible in the consignment status history.
Status Export (Qargo → Nexus)
Qargo sends status updates back to Nexus as part of the visibility framework. These are triggered automatically by specific events in Qargo:
Collection complete → status exported to Nexus
At delivery stop → status exported
Delivery confirmed → status exported
🧰 C&D routes requirement: For status export to work correctly, Collection and Delivery (C&D) routes must be created in Nexus on a daily basis. These can be auto-created using a button in the Nexus portal.
POD and Document Synchronisation
Delivery proof documents are synced bidirectionally between Nexus and Qargo.
Nexus document type | Description | Qargo document type |
| Digital Signature Capture / Sign-On-Glass image from the consignee | Consignee signature |
| Image of the signed delivery note | POD/CMR |
| Photo of the pallets at the delivery location | Photo of goods (delivery) |
Import: Documents are periodically synced from Nexus and stored against the consignment in Qargo.
Export: When a document of the above types is created or uploaded in Qargo and the depot is the delivery depot for the consignment, the document is sent to Nexus automatically.
ETA Export (via Optimize) - Optional
ETAs can be pushed from Qargo to Nexus via the Optimize route optimisation module.
💬 ETA export is configured separately from the main PALL-EX/Fortec integration. Contact the your account manager for additional information.