Introduction
What is it?
The UPN integration connects Qargo to the United Pallet Network (UPN), allowing depot and traffic teams to receive, manage, track, and complete UPN consignments directly within Qargo.
Why does it exist?
To eliminate the need to switch between UPN's system and the TMS. Orders flow into Qargo automatically, status updates and proof-of-delivery data are exchanged in the background, and delivery images are shared back to UPN — all without manual re-keying.
How does it work?
UPN consignments are imported into Qargo via the UPN API. As work progresses, Qargo pulls tracking events from UPN every ten minutes and pushes consignee signatures and delivery images back to UPN upon delivery completion.
Terminology
Term | Definition |
Consignment | A UPN shipment, typically composed of one or more pallets under a single UPN consignment barcode. |
Consignment barcode | The unique barcode reference assigned by UPN, used to link records across both systems. |
Stage / Tracking event | A status milestone recorded against a consignment or individual pallet (e.g., Out for delivery, Arrived, Delivered). |
ePOD | Electronic proof of delivery — the consignee's signature captured in Qargo and pushed to UPN. |
Delivery image | A photo of the delivery (goods, location, or leave-safe) captured by the driver in Qargo and sent to UPN. |
Capture type | Whether a tracking event applies to the whole consignment (C) or a specific pallet (P). |
Prerequisites
An active UPN integration, configured and enabled for the depot by UPN and the Qargo admin team.
The tracking action and image download actions must be enabled by UPN for the depot (contact UPN IT if these are not active).
Driver devices configured to capture signatures and delivery photos through the Qargo driver app.
Order Import
UPN consignments are automatically imported into Qargo via the UPN API on a periodic basis. No manual entry is required.
RECEIVE new consignments
1. New UPN jobs appear in the Qargo Orders list with the UPN consignment barcode and basic consignment details (shipper, consignee, pallet count, weight, service type).
2. Orders are ready to plan and allocate immediately on import.
What's included in the imported order:
Consignment barcode (used for tracking, labels, and invoice matching)
Delivery address and consignee details
Pallet count, weight, and service level
Any special instructions provided by UPN
Status & Tracking Sync
Qargo automatically pulls tracking updates from the UPN API on a 10-minute cycle, keeping order statuses current without any manual intervention.
How it works:
Qargo calls the UPN and retrieves all events since the previous sync.
Tracking events are applied at either consignment level or individual pallet level, depending on the event type.
Key stages include:
Booked
Out for delivery
Arrived
Unloaded
Delivered
Exception statuses: Carded or Complaint raised.
VISUALISE tracking progress
Open any UPN order in Qargo to see the full tracking timeline under the order activity or status section.
Consignment-level events update all associated pallets; pallet-level events update only the specific good trace.
📚 Any processing failure during a sync cycle means that batch of events cannot be re-fetched. The integration architecture stores responses before processing to mitigate this risk.
ePOD and Delivery Images
When a driver completes a UPN delivery in Qargo, the consignee signature and any delivery photos are automatically pushed back to UPN.
How signatures work:
When a consignee signature is captured in the Qargo driver app, it is sent to UPN
This marks the consignment as delivered in UPN with the associated POD data (signature image, delivery name, timestamp, GPS coordinates).
How delivery images work:
Delivery photos captured by the driver in Qargo are sent to UPN alongside the consignee signature.
🧰 Delivery images are sent when a consignee signature has been created on the consignment.
If photos are captured before the signature, they are uploaded together with the signature when it is submitted.
Multiple delivery images per consignment are supported.
Where to find POD and images in Qargo:
Open the order and navigate to the *POD* or *Documents* section.
Signature and delivery photos appear as attachments once the delivery is completed and synced.
Feature Summary
Feature | Direction | Notes |
Order / consignment import | Push from UPN → Qargo | Automatic, periodic sync |
Tracking events (status updates) | Pull by Qargo from UPN | Every 10 minutes |
ePOD (consignee signature) | Push from Qargo → UPN | On delivery completion |
Delivery images | Push from Qargo → UPN | Sent with or after signature |
Invoice charge line matching | In Qargo | Matched using UPN consignment barcode |
Troubleshooting
Issue | What to check |
UPN consignments not appearing in Qargo | Confirm the UPN order import is active for the depot. Check that the integration is enabled in Configuration → Integrations. |
Tracking events not updating | Allow up to 10 minutes for the sync cycle to run. If statuses remain stale after 15+ minutes, contact your Qargo admin to verify the tracking action is enabled by UPN for the depot. |
ePOD not appearing in UPN after delivery | Confirm the POD is present in Qargo with a signature timestamp. Ensure the driver's device was connected when submitting. If the issue persists, raise with Qargo support including the consignment barcode and delivery timestamp. |
Delivery images not visible in UPN | Check that a consignee signature was also captured for the consignment — images are only sent to UPN once a signature exists. |
Invoice matching not finding a consignment | Confirm the UPN consignment barcode on the order matches the reference on the invoice exactly. See also: FAQ - Purchase invoice scan and match fields. |
💬 For ongoing issues, contact the Qargo support team with the UPN consignment barcode, depot name, and timestamps of the affected events.