Note II: We setup order connections for our customers and will also ask for the transporter to configure this initially. You can later change the transporter settings yourself by following the guide below.
Important: Always add the default transporter! When this is not added, we will not send the tracking information to the corresponding channel.
Note III: These settings are configured for all order connections. You cannot configure transporters for separate order connections.
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. 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, PostNL will be used as transporter if the tracking code starts with '3S'. Otherwise, DHL will be used.
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.