Current Problem
We are unable to set offshore courier service mappings by client. This means when different clients want to use different courier services for shipping offshore, we are unable to facialite this. This means we have to manually update offshore orders for different clients. This wastes alot of time. |
|
Idea to resolve Problem | Setup offshore courier service mappings per client |
If you used sets in off shore postcodes you can also pair it with different courier service names and courier service code mappings to split it for different clients.
It would help if when defining postcodes you could add another field so you can create postcode sets
Then being able to specify the set in the offshore courier service mapping rules. This would allow for different offshore postcodes for different courier services and also help with rules around shipping zones.
If offshore postcodes could be set against a 'specific courier' then this might also work. APC and Hermes have different definitions of what is considered 'offshore' (for example).
Hi there, Not sure if this may be a setup issue as we do this all the time. If you setup the Courier Service Mapping and select either standard or express but leave the courier blank it goes to None Set when you view it. When this is the case, it then flips over to use the Courier Service Selection rules where you can map specific rules buy standard or express and on client, connector, country, weight, cost etc.....