Introduction
This article explains how to configure the PALL-EX/Fortec integration in Qargo. Configuration is typically completed by the Qargo onboarding team. The steps below are provided as a reference for support and for customers who need to understand how the integration is set up.
What does this article cover?
Requesting Nexus API credentials from PALL-EX/Fortec
Adding the integration and depot code in Qargo
Enabling customer Nexus ID fields
Setting up subcontractor resources for each network
Configuring service levels, time windows, extras, and packaging types
Setting up the order import master
Who performs this configuration?
The Qargo onboarding team and technical support configure the integration
The depot provides the depot code(s) and a list of Nexus customer IDs for their customers
Terminology
Term | Definition |
Depot code | The unique identifier assigned to the depot by PALL-EX/Fortec (e.g. |
PallexID / FortecID | The Nexus customer IDs for each of the depot's customers, configured as extra fields in Qargo |
PALLEX_OUT / FORTEC_OUT | Resource codes that identify a subcontractor as belonging to the PALL-EX or Fortec network |
Transport network | A Qargo configuration object that maps pallet network service levels, time windows, and extras to orders |
Order import master | The Qargo configuration that controls automatic import of orders from Nexus |
Nexus | The API and portal platform shared by PALL-EX and Fortec |
Before You Start
The following information is required before configuration begins:
Whether the depot is a PALL-EX member, Fortec member, or both
The depot code(s) assigned by the network (e.g. PGD302 for a dual-network depot, UKD-prefix for PALL-EX only, FTD-prefix for Fortec only)
A list of Nexus customer IDs for each of the depot's customers (one ID per customer per network)
Nexus API credentials (obtained from PALL-EX/Fortec — see below)
Configuring the Integration
🧰 Qargo Admin may perform some or all of these steps, together with the SuperAdmin user.
Step 1: Add the Integration
Qargo Admin will complete this step
🧰 Dual network depots: Only one integration instance is needed, even if the depot is a member of both PALL-EX and Fortec. The network is determined per consignment by the subcontractor resource used.
Step 2: Enable Additional Fields
Customer records in Qargo need two extra fields to store Nexus customer IDs — one for PALL-EX and one for Fortec.
NAVIGATE to CONFIGURATION>Additional fields>Customers
ENABLE PallexID on the Customer entity.
ENABLE FortecID on the Customer entity.
📚 Once enabled, these fields appear on each customer record and must be populated for the integration to dispatch consignments for that customer.
Step 3: Configure Customer Nexus IDs
For each customer that will have consignments dispatched via PALL-EX or Fortec:
OPEN the company record in Qargo.
ENTER the customer's Nexus PALL-EX ID in the PallexID field (if the customer ships on PALL-EX).
ENTER the customer's Nexus Fortec ID in the FortecID field (if the customer ships on Fortec).
🧰 The Nexus customer IDs can be bulk-imported using the Import Company Data workflow in Qargo. The import file should include both the Nexus codes and the Customer Software Accounting Code for matching.
Step 4: Create Subcontractor Resources
A subcontractor resource must be created in Qargo for each network the depot is a member of.
NAVIGATE to RESOURCES>Subcontractors.
CREATE a subcontractor for PALL-EX and set its resource code to `PALLEX_OUT`.
CREATE a subcontractor for Fortec (if applicable) and set its resource code to `FORTEC_OUT`.
ENABLE the PALL-EX/Fortec integration on each subcontractor resource.
‼️ Only subcontractor resources with the integration enabled will generate a resource dispatch task when assigned to a trip.
Step 5: Add the Export Task
🧰 Add a 'Send to Pallex' task in the main Configuration>Tasks. Set this to 'Always skip task'. Once this task is setup, an override can be configured on the subcontractor.
NAVIGATE to the subcontractor resource profile
SCROLL to Tasks and select the Pallex option
CONFIGURE the task to auto-complete if desired (this sends consignments to Nexus automatically when the resource is assigned to a trip).
Step 6: Create a Transport Network
The transport network maps pallet network service levels, time windows, and extras to orders imported from or dispatched to Nexus.
NAVIGATE to LOCATIONS>Transport networks
CREATE a new transport network for PALL-EX/Fortec.
LINK the transport network to the transport service used for pallet shipments.
Service Levels
Configure the following service levels on the transport network. These map to the Nexus API service IDs.
PALL-EX service levels:
Nexus service | serviceID | Qargo service level | Qargo time window | Notes |
Premium | 1 | A | — |
|
Premium AM | 4 | A | AM |
|
Premium Timed | 5 | A | TD |
|
Premium Before Timed | 10 | A | BT |
|
Premium PM | 21 | A | PM |
|
Premium Before Defined Time | 10 | A | BDT |
|
Economy | 2 | B | — |
|
Economy AM | 7 | B | AM |
|
Economy Timed | 6 | B | TD |
|
Economy PM | 22 | B | PM |
|
Economy Before Defined Time | 17 | B | BDT |
|
Book-in | 11 | B | BI |
|
Specific Day | 3 | SD | — |
|
Saturday AM | 9 | A | SAT-AM |
|
Amazon | 8 | Any | — | Requires Amazon extras |
Fortec service levels:
Nexus service | serviceID | Qargo service level | Qargo time window | Notes |
Premium / Next Day | 1 | A | — |
|
24HR AM | 4 | A | AM |
|
24HR Timed | 5 | A | TD |
|
Economy | 2 | B | — |
|
Book-in / Book In | 11 | B | BI |
|
Specific Day / Spec Day | 3 | SD | — |
|
Spec Day AM | 7 | SD | AM |
|
Date Specific Timed | 6 | SD | TD |
|
Saturday AM | 9 | A | SAT-AM |
|
Amazon | 8 | Any | — | Requires Amazon extras |
‼️Not supported: Air (12), Sea (13), Customs House (14), Special Conditions (15), Next Day Priority (10 — Fortec), Spec Day Priority (17 — Fortec).
Time Windows
Configure the following time window codes on the transport network:
Code | Description |
AM | Morning delivery (before midday) |
PM | Afternoon delivery |
TD | Timed delivery (specific time) |
BT | Before time |
BDT | Before defined time |
BI | Book-in required |
SAT-AM | Saturday morning delivery |
Extras
Configure collection and delivery extras as required by the depot's service offering. The *AZ* extra is required for Amazon consignments.
Packaging Types
Configure the packaging types (pallet types) available on the network. Only domestic pallet types are supported. See the table below for the supported types and their dimensions.
Pallet type | Nexus palletTypeID | L (cm) | W (cm) | H (cm) | Max weight |
Full | 1 | 120 | 120 | 220 | 1,200 kg |
Half | 2 | 120 | 120 | 120 | 600 kg |
Quarter | 3 | 120 | 120 | 80 | 300 kg |
Full Plus | 4 | 160 | 120 | 220 | 1,200 kg |
Bundle | 5 | 300 | 15 | 30 | 25 kg |
Oversize | 6 | 510 | 240 | 220 | 2,000 kg |
Full Light | 7 | 120 | 120 | 220 | 600 kg |
Micro | 8 | 120 | 120 | 60 | 150 kg |
📚 International variants of pallet types (different dimensions/weights) are not supported. Fortec uses the same pallet type IDs.
Step 7: Add the Order Import Master (Qargo Admin will complete this step)
Step 8: Enable the Integration (Qargo Admin will complete this step)