Note II: These settings are configured for all order connections. You cannot configure transporters for separate order connections.
Configuring the transporter settings
To configure the transporter for your order connections, go to the project you are working in and navigate to "Setup > Setup orders > Transporter".
Here, you can configure your Default transporter and add Transporter mapping. If you only have one transporter, you only have to add a default transporter.
IMPORTANT I: Always add the default transporter! When this is not added, we will not send the tracking information to the corresponding channel.
If you have multiple transporters, you have to add transporter mapping. With the transporter mapping you can create rules for the tracking code. If the tracking code meets the requirements of a rule, the selected transporter will be used. If none of the transporter mappings match the tracking code, the default transporter will be used. In the example below, DHL Express will be used as transporter if the tracking code ends with '3345'. Otherwise, DHL will be used.
The table below contains an example overview of frequently used transporters for which the T&T codes usually start with the same value. These values could be used to configure the transporter mapping as explained above.
|Transporter||T&T codes usually start with|
IMPORTANT II: These are frequently used examples, you will still have to look in your own backend to see what value the T&T codes start with in your case.
PostNL Letter post
IMPORTANT: if you use PostNL letter post as your transporter for orders without a T&T code, you have to be aware of the following things:
- You need to select the transporter "Letter post", not "PostNL letter".
- You need to set the Default transporter to "Letter post". Do not set a rule like 'If tracking starts with '[empty value]'.
- Set transporter to 'Letter post', as in the screenshot below:
- If you have other transporters (with T&T codes), add these with Transporter mapping rules.
Using the 'Remove value' checkbox
You can also check the Remove value box in a transporter mapping rule. If you do this, the input value will be removed from the tracking code before sending it to the marketplace. This is useful if you use different transporters for different marketplaces, but their tracking codes follow the same structure. You can add a custom string to the tracking code that we can use to identify which transporter to use, which we will then remove from the tracking code before sending it to the marketplace.