Introduction
Pall-Ex and Fortec are two of the UK's largest pallet networks, both operating on the same platform — Nexus. Qargo's integration connects to both networks simultaneously through a single API, allowing depots that are members of one or both networks to send and receive orders, track shipments, and sync delivery proof documents without leaving Qargo.
What does the PALL-Ex integration do?
Dispatches consignments from Qargo to PALL-Ex or Fortec via the Nexus REST API
Imports incoming orders from the network into Qargo automatically
Downloads pallet labels immediately after dispatch
Syncs tracking statuses from the network into Qargo in real time
Syncs delivery proof documents (signatures, POD images, photo evidence) bidirectionally
Exports ETAs to Nexus via the Optimize module (optional, additional cost)
Why use this integration?
Eliminates double-keying of consignments between Qargo and the Nexus portal
Keeps a single source of truth for order status across both networks
Provides automatic label generation, removing the need to download labels manually from Nexus
Supports depots that are members of both PALL-EX and Fortec — the network is determined automatically per consignment based on the subcontractor resource used
How does it work at a high level?
A depot obtains Nexus API credentials from PALL-EX/Fortec and adds them to the integration configuration in Qargo
Consignments are dispatched to the network by assigning a PALL-EX or Fortec subcontractor resource on a trip and completing the resource dispatch task
Qargo polls Nexus every few minutes to import new orders and status updates
The network is determined by the subcontractor resource assigned to the trip, not by a separate configuration switch
Terminology
Term | Definition |
Nexus | The shared portal and API platform used by both PALL-EX and Fortec |
Depot Code | A unique identifier assigned to a depot by the pallet network (e.g. PGD302) |
PGD depot | A depot that is a member of both PALL-EX and Fortec (dual network member) |
UKD depot | A depot that is a member of PALL-EX only |
FTD depot | A depot that is a member of Fortec only |
Nexus customer ID | A unique code assigned in Nexus to each of the depot's customers — required on export to identify which network account the consignment belongs to |
Resource dispatch task | The Qargo action that triggers export of a consignment to the pallet network |
PALLEX_OUT / FORTEC_OUT | The resource codes used in Qargo to identify which network a subcontractor resource belongs to |
Service level | The delivery speed category: A (Premium/Next Day), B (Economy), or SD (Specific Day) |
Time window | A delivery time constraint associated with a service, such as AM, Timed (TD), or Book-in (BI) |
MPOD | Digital Signature Capture — the consignee's signature collected at delivery |
POD | Proof of Delivery — an image of the signed delivery note |
MPODPHOTOE | A photo of the pallets at the delivery location |
Optimize | A third-party route optimisation module; used to push ETAs from Qargo to Nexus |
Integration Features
The table below summarises the full scope of the PALL-EX/Fortec integration.
Feature | Supported | Notes |
Order export (Qargo → Nexus) | ✅ | Via resource dispatch task |
Order import (Nexus → Qargo) | ✅ | Polled every few minutes |
Label download | ✅ | Automatic immediately after dispatch |
Status import (Nexus → Qargo) | ✅ | Full tracking lifecycle |
Status export (Qargo → Nexus) | ✅ | Triggered by stop completion events |
POD / signature sync | ✅ | Bidirectional |
ETA export (via Optimize) | ✅ | Optional; requires separate Optimize API key and agreement |
Dual network (PALL-EX + Fortec) | ✅ | Single integration handles both networks |
International pallet types | ❌ | Domestic pallet types only |
Amazon consignments | ✅ | Requires Amazon extra fields configured |
Dual Network Support
A depot may be a member of PALL-EX only, Fortec only, or both networks simultaneously. Qargo supports all three configurations with a single integration instance.
The network is determined at dispatch time by the subcontractor resource assigned to the trip:
Resource Code | Network |
PALLEX_OUT` | Consignment dispatched to PALL-EX |
FORTEC_OUT | Consignment dispatched to Fortec |
Each of the depot's customers must have a Nexus customer ID configured in Qargo for each network they ship on. At dispatch, Qargo passes the correct ID to the Nexus API, which routes the consignment to the appropriate network.
🧰 Ensure the additional field 'Nexus origin' is enabled under 'CONFIGURATION>Additional fields>Consignments'
Typical Workflow
1. A new order is received and imported from Nexus into Qargo automatically (or created manually in Qargo).
2. The dispatcher assigns the consignment to a trip and selects the PALL-EX or Fortec subcontractor resource, depending on the network required.
3. The dispatcher completes the resource dispatch task which sends the consignment to Nexus.
4. Qargo downloads the pallet label from Nexus immediately after dispatch and attaches it to the consignment.
5. As the consignment moves through the network, Nexus scan events are synced to Qargo's status history.
6. On delivery, the delivering depot captures a signature and POD image; these are synced back to Qargo.
7. If ETA export is enabled, optimising the delivery trip in Qargo pushes ETAs to Nexus for the consignee.
Troubleshooting
See the article PALL-EX/FORTEC - Troubleshooting for a full list of questions and solutions.