Introduction to carrier configuration
Last updated
Developer Docs
Last updated
LU.XY uses two carriers for fulfilling orders. For orders inside of Germany, the CEP (Courier, Express and Parcel Services) service provider DHL is used. For other orders, they use UPS. Let's add DHL as a first carrier to the tenant. To make it simple, we'll assume that usually the parcels have a weight of 2 kilograms.
With an API call to the , a new CEP partner can be added:
The key property defines which carrier to add, see this list to check which key to use for which carrier. The name can be defined freely. The status can either be ACTIVE or INACTIVE. When creating the CEP partner as an ACTIVE one, it can immediately be used after creation. When setting the defaultParcelWeightInGram to 2000, labels are created with that weight. The credentials are received by the CEP partner.
When everything was correct in your request, you'll receive a 201 CREATED response. In this response you'll find the ID of that carrier.
After successful creating DHL, let's create UPS as a carrier. Here, the same API endpoint is used, only the payload differs a bit:
You might have noticed that this looks similar to the DHL creation, but that the username and password have a prefix called "VCE". This is our technology partner enabling us to faster provide some of the CEP service providers. The credentials for this technology partner will be provided by your professional services representative.
After we created the carriers in the fulfillmenttools platform, we need to create a connection between the facility and the carrier. This might have several reasons, for example some contract topics or the issue that some CEP is not supported in a country. Therefore you first need to create a connection between a carrier and a facility.
For the connection we need the ID of the carrier which we created above and the facility ID from the creation of the facility. When the connection was made successfully, the response should be 200 OK with a payload like this:
Now we just need to activate that connection, the endpoint stays the same, only the verb changes from POST to PUT:
You might have noticed, that w used version 1 for the call here. It is crucial to use the same version the carrier has in the payload you received. Again, the response ist a 200 OK like that:
Now that we have made the first connection between a carrier and a facility, we need to do that with the other ones as well.
This is done by an easy API call to the . In our case, an empty JSON for the payload is good here: