Overview
When orders are imported into the system via one of the many connection options or uploaded via the spreadsheet loader, it's possible to map the courier service tag received from that channel directly against a Courier Service or a Service Type in Mintsoft, using Courier Service Mapping. This is one method of automating your courier selection against orders.
Finding the shipping tag on orders
To use this functionality, you will need to identify the shipping tag (SourceCourierServiceName) found on relevant orders.
Matching must be exact to prevent errors in mapping courier services in Mintsoft, and the field accommodates a maximum of 60 characters.
You can get this value from previously imported orders by going to the order details and then history comments, or the ExtraInfo Tab and then SourceCourierServiceName at the bottom.
You can get these values in bulk via Shipping Management then Extras finally Mapping Terms. This will show all values imported in the last 180 days.
β(3PLs will need to filter by Client first)
To locate the source courier service name specifically:
Find the affected order in Mintsoft.
Click Actions then Details.
Go to the History tab and select the Extra Info sub-tab.
Use the displayed source courier service name as input for the Name field in the Courier Service Mapping rule.
Mapping to a single service
This method links a shipping tag from the source (Shopify, eBay, Amazon etc.) such as "Next Day Delivery Before 3 PM" to a specific courier service within Mintsoft.
Click Shipping Management then Courier Service Mapping.
Next, click Create New then complete the following information:
Option | Description |
Source | The source of the orders, e.g. eBay, Amazon, Shopify. |
Client | (3PL Only) Select All or a specific client. |
Courier Service | The courier service you want Mintsoft to set these orders to, e.g. DPD Next Day. |
Courier Service Type | Leave blank. |
Name | The tag from the order source e.g. "Next Day Delivery Before 3 PM". βNote: There's a character limit of 60 characters for the Name field of a courier service mapping. It must also match exactly. |
Mapping to a service type
With this approach, you aren't mapping the shipping method tag to a specific courier service, and instead you are mapping to a Shipping Type such as 'Standard' or 'Express'. This is used in conjunction with Courier Service Selection rules to set different weight, value and country based rules for different 'types' of shipping to determine the correct service.
Example: You ship with RM 24 Letter, RM 48 Letter, RM 24 Parcel & RM 48 Parcel. Your customer selects "Next Day Delivery" at checkout on Shopify and you have mapped this to the 'Express' Courier Service Type in Mintsoft without specifying a service. This routes the order to the selection rules for Express only, and based on the order weight, Mintsoft can decided if it is a RM 24 Letter or a RM 24 Parcel.
To set this up:
Click Shipping Management then Courier Service Mapping.
Next, click Create New then complete the following information:
Option | Description |
Type | The source of the orders. |
Client | (3PL Only) Select All or a specific client. |
Courier Service | Leave blank. |
Courier Service Type | Standard or Express, etc. |
Name | The tag from the order source must match exactly what you receive. We list all SourceCourierServiceName values here (3PLs will need to filter by Client) |
To troubleshoot common mapping issues, ensure 'Name' matches exactly and there are no conflicting rules or inactive services.
Use of special characters
When creating the courier service on the order source integration, please use alphanumeric characters only, some special characters can cause the mapping to fail.