Q: Why can’t I remove the Pallex (export) resource from an already dispatched order in Qargo?
A: There may be several reasons, depending on the consignment status.
If the consignment was cancelled in Pallex/Nexus, recall or refresh the dispatch in Qargo. Qargo now checks the status and will remove the Pallex resource allocation automatically. You can then assign the order to your own driver.
If the consignment is still active or already accepted downstream, removal remains blocked. In that case, add your driver and vehicle as an extra resource and dispatch to the driver as a workaround.
Collection Date Error: Date Outside Allowed Range
Q: When dispatching a consignment, an error is returned: `The date is outside the allowed range for ServiceID (SpecificDay)`. What is this and how can I fix it?
A: The collection date on the consignment violates one of the following rules:
The export was submitted after the 12 PM cut-off for the selected collection date
The collection date is more than 6 days in the future
The collection date falls on a Saturday (collections are not accepted on Saturdays)
The export was submitted over a weekend for a Monday collection after the cut-off has passed
Resolution:
Scenario | Action |
After 12 PM cut-off for same-day | Adjust the collection date to the next valid working day |
Saturday collection requested | Pallex does not accept Saturday collections — change the date to the following Monday |
Collection date more than 6 days ahead | Move the collection date to within the 6-day window |
Weekend submission for Monday before cut-off | Verify the collection date is set to Monday; if still failing, move to Tuesday |
📚 Qargo automatically selects the collection service level (`PREMIUM` or `SPECIFIC_DAY`) based on the export time. If the cut-off has passed for the desired date, the system will return an error rather than silently changing the date. The date must be adjusted manually.
Status Updates Not Appearing in Qargo
Q: Consignments dispatched to PALL-EX/Fortec are not receiving status updates (e.g. Hub Arrived, Delivery Depot Scanned In) in Qargo. Why is this happening and how can I fix it?
A: C&D (Collection and Delivery) routes may not have been created in Nexus for the current day. Status export from Qargo to Nexus requires active C&D routes in Nexus.
Resolution:
1. LOG IN to the Nexus portal.
2. NAVIGATE to the C&D routes section.
3. CREATE the C&D routes for today using the auto-create button.
4. Allow a few minutes for the next polling cycle to pick up status updates.
📚 C&D routes must be created in Nexus every day for status export to function. If this is not being done consistently, contact the Nexus support team about automating the daily route creation.
Oversize Pallet Dimensions Not Updating
Q: Oversize pallet consignments are being sent to Nexus with fixed dimensions of 510×240×220 cm, even when the packaging type in Qargo has been updated to different dimensions. Why is this happening and how can I fix it?
A: The Nexus API uses fixed, hardcoded dimensions for the Oversize pallet type (palletTypeID 6). Qargo sends the correct pallet type ID, but the dimensions are determined by Nexus based on the type, not from the dimensions entered in Qargo.
Resolution:
There is no workaround at the API level — the Nexus API does not accept custom dimensions for the Oversize pallet type. If the consignment physically differs from these dimensions, this should be communicated to the receiving depot directly through standard pallet network channels.
Depot Code Not Recognised / Changed
Q: The integration is returning errors or not processing orders after a depot code change. Previously working depot codes with a `PGD` prefix have been replaced with a `UK`-prefixed code.
A: PALL-EX periodically issues updated depot codes to members. Depots that previously had a `PGD`-prefixed code may have been migrated to a `UK`-prefixed code.
Resolution: Qargo Admin will need to assist with resolving this.
1. OBTAIN the new depot code from PALL-EX.
2. NAVIGATE to Configuration> Integrations in Qargo (Restricted Qargo Admin only)
3. UPDATE the depot code field on the PALL-EX/Fortec integration to the new code.
4. SAVE and verify that order export resumes correctly.
🧰 If the depot is a member of both networks, verify whether both the PALL-EX and Fortec depot codes need to be updated.
💬 Contact your Qargo Account Manager or Qargo Support for assistance updating Integrations.