Some surcharges cannot be applied for certain depots or destination postcodes. Submissions with disallowed surcharges are rejected by the network and must be corrected before export.
Q: What does this error mean?
A: The network you are exporting to enforces surcharge eligibility rules based on depot coverage, destination geography, or service constraints. If a surcharge is not permitted for the receiving depot or postcode, the job will fail validation during export.
Typical symptoms
Export fails with a surcharge validation or eligibility error
Error mentions a specific surcharge code or name
Error may reference the destination depot, area, or postcode sector
Common causes
Surcharge not accepted by the receiving depot or area
Surcharge conflicts with service type or piece profile
Surcharge only valid for defined postcode ranges or zones
Legacy or custom surcharge code not mapped in the network schema
How to resolve
Identify the surcharge in the error message
Check if the destination depot or postcode allows that surcharge
If disallowed, remove or replace the surcharge
Re‑export the job
Recommended checks in Qargo
Confirm the destination postcode and assigned depot are correct
Review the job’s surcharges and remove those flagged as out of scope
If needed, use a different valid surcharge that matches the service and geography
Examples
Remote area surcharge rejected for an urban postcode
Tail‑lift surcharge disallowed at a depot that does not provide that capability
Saturday delivery surcharge blocked for a postcode sector not covered on Saturdays
Best practices
Avoid adding surcharges until the correct depot is allocated
Use saved rate rules that reflect network eligibility
Keep surcharge mappings aligned with network documentation