Order cannot be sent to the carrier over an unmapped address
A merchant connected a carrier successfully, yet Send to carrier fails with Address is not mapped for this carrier. This is common when new cities are added before mapping them.
Why this happens
Usually because the merchant connected account credentials but skipped area mapping, or the order address spells the city differently from the mapped rows, or new orders arrive from a city that was never added.
What Vareons does about it
Vareons shows Area mapping under Connection Settings once the carrier is Connected and active, supports adding rows and bulk paste with a single save, and after saving the order address becomes sendable from the Orders tab or the Send to carrier card.
- shipping.carriers.connect — Connecting shipping carriers: Available
- shipping.management.supported — Shipping management: Available
Limitations
The current facts registry does not claim that Vareons guesses the carrier city id automatically. The carrier city id must be entered manually, such as EG-01 for Cairo on Bosta.
Related problems
Frequently Asked Questions
I linked the carrier fine but sending fails, why?
Because sending needs area linking next to the account connection, and a missing row for the city refuses creation with an unmapped code. Open area linking inside connection settings, add the matching row, save, and retry.
Does the system guess the city match automatically?
No, the facts registry claims no automatic guessing, and each city match must be entered by hand. Review city spellings in order addresses and align them with the linked rows to avoid repeated refusal.
Orders from a new city keep refusing, what now?
Add a fresh linking row for the new city from connection settings and save, and the order address becomes sendable at once. Make adding new cities an instant habit with every geographic expansion of your activity.
Last verified: 2026-09-18