---
title: "PN - Pall-Ex: what, why & how."
description: ""
url: https://help.qargo.com/us/articles/608940-pn-pall-ex-what-why-how
locale: us
updated: 2026-03-17
---

# PN - Pall-Ex: what, why & how.

## Introduction {#h_4d2c66b2f3}

Pall-Ex and Fortec are two of the UK's largest pallet networks, and both operate on the same platform: Nexus. Qargo's integration connects to both networks at the same time through a single API. Terminals that are members of one or both networks can send and receive orders, track shipments and sync proof-of-delivery documents without leaving Qargo.

### What does the Pall-Ex integration do? {#h_b28e351ec6}

-   Dispatches shipments 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 proof-of-delivery documents (signatures, POD images, photo evidence) in both directions
-   Exports ETAs to Nexus via the Optimize module (optional, additional cost)

### Why use this integration? {#h_2dd2ef4879}

-   Eliminates double entry of shipments between Qargo and the Nexus portal
-   Keeps a single source of truth for order status across both networks
-   Provides automatic label generation, so labels no longer need to be downloaded manually from Nexus
-   Supports terminals that are members of both Pall-Ex and Fortec: the network is determined automatically per shipment, based on the contract carrier resource used

### How does it work at a high level? {#h_3750e46ddd}

-   A terminal obtains Nexus API credentials from Pall-Ex/Fortec and adds them to the integration configuration in Qargo
-   Shipments are dispatched to the network by assigning a **Pall-Ex or Fortec contract carrier resource** on a load 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 contract carrier resource assigned to the load, not by a separate configuration switch

* * *

## Terminology {#h_23312906f5}

| **Term** | **Definition** |
| --- | --- |
| Nexus | The shared portal and API platform used by both Pall-Ex and Fortec |
| Terminal code | A unique identifier assigned to a terminal by the pallet network (e.g. PGD302) |
| PGD terminal | A terminal that is a member of both Pall-Ex and Fortec (dual network member) |
| UKD terminal | A terminal that is a member of Pall-Ex only |
| FTD terminal | A terminal that is a member of Fortec only |
| Nexus customer ID | A unique code assigned in Nexus to each of the terminal's customers. It is required on export to identify which network account the shipment belongs to |
| Resource dispatch task | The Qargo action that triggers export of a shipment to the pallet network |
| PALLEX\_OUT / FORTEC\_OUT | The resource codes used in Qargo to identify which network a contract carrier 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 receiver's signature collected at delivery |
| POD | Proof of delivery: an image of the signed delivery receipt |
| MPODPHOTOE | A photo of the pallets at the delivery location |
| Optimize | A third-party route optimization module, used to push ETAs from Qargo to Nexus |

## Integration features {#h_cd50b51e0a}

The table below summarizes 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 a separate Optimize API key and agreement |
| Dual network (Pall-Ex + Fortec) | ✅ | A single integration handles both networks |
| International pallet types | ❌ | Domestic pallet types only |
| Amazon shipments | ✅ | Requires Amazon extra fields to be configured |

## Dual network support {#h_c3b24f2e0a}

A terminal may be a member of Pall-Ex only, Fortec only, or both networks at the same time. Qargo supports all three configurations with a single integration instance.

The network is determined at dispatch time by the contract carrier resource assigned to the load:

| **Resource code** | **Network** |
| --- | --- |
| PALLEX\_OUT\` | Shipment dispatched to Pall-Ex |
| FORTEC\_OUT | Shipment dispatched to Fortec |

-   Each of the terminal'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 shipment to the appropriate network.

:::callout{tone="info"}
🧰 The additional field 'Nexus origin' must be enabled under **Configuration > Additional fields > Shipments**.
:::

![](https://help.qargo.com/media/5a1374184b83-image.png)

* * *

## Typical workflow {#h_be7be78a20}

1\. A new order is received and imported from Nexus into Qargo automatically (or created manually in Qargo).\
2\. The dispatcher assigns the shipment to a load and **_selects the Pall-Ex or Fortec contract carrier resource_**, depending on the network required.\
3\. The dispatcher completes the **_resource dispatch task_**, which sends the shipment to Nexus.\
4\. Qargo downloads the pallet label from Nexus immediately after dispatch and attaches it to the shipment.\
5\. As the shipment moves through the network, Nexus scan events are synced to Qargo's status history.\
6\. On delivery, the delivering terminal captures a signature and POD image. These are synced back to Qargo.\
7\. If ETA export is enabled, optimizing the delivery load in Qargo pushes ETAs to Nexus for the receiver.

* * *

## Troubleshooting {#h_3282d283ff}

See the article [Pall-Ex/Fortec - Troubleshooting](https://help.qargo.com/us/articles/456742-pall-ex-fortec-unable-to-remove-pallex-export-resource-from-a-dispatched-order) for a full list of questions and solutions.


## Related articles

- [Pallet network: PALL-EX/Fortec order export and import](https://help.qargo.com/us/articles/609022-pallet-network-pall-ex-fortec-order-export-and-import.md)
- [PN - Configure Pall-Ex/Fortec](https://help.qargo.com/us/articles/608986-pn-configure-pall-ex-fortec.md)
- [Pallet networks: sending ETAs to Pall-Ex](https://help.qargo.com/us/articles/887947-pallet-networks-sending-etas-to-pall-ex.md)
- [PN - UPN: What, why & how overview](https://help.qargo.com/us/articles/609623-pn-upn-what-why-how-overview.md)
- [PN - Pallet Track integration: What, why & how.](https://help.qargo.com/us/articles/879827-pn-pallet-track-integration-what-why-how.md)
