Carrier configuration
What is a carrier?
Inside the fulfillmenttools platform, a carrier is an entity enabling you to connect Courier, Express, and Parcel services (in short CEP services). If your favorite provider isn't yet listed, let us know using our feedback form.
Adding the first carrier
This tutorial uses a sample company, LU.XY, which uses two carriers for fulfilling orders: DHL for domestic orders within Germany and UPS for all other orders. The first step is to add DHL as a carrier. For this example, a default parcel weight of 2000 grams is assumed, which corresponds to the API field defaultParcelWeightInGram.
The key property specifies the carrier to add; refer to the list of available carriers for the correct key value. The name can be defined freely. The status can be set to either ACTIVE or INACTIVE. If a carrier is created with an ACTIVE status, it is immediately available for use. If defaultParcelWeightInGram is set, labels are created with that weight. The credentials are provided by the carrier.
A successful request returns a 201 CREATED response. The response body contains the unique ID assigned to the new carrier.
Next, create the UPS carrier. The same API endpoint is used, but with a different payload:
Note that the user and password values in this example are prefixed with VCE. VCE is a technology partner that enables fulfillmenttools to provide an expedited integration for some CEP service providers. The professional services representative provides the necessary credentials for this partner.
Connect a facility to a carrier
After the carriers are created in the fulfillmenttools platform, a connection must be established between a facility and each carrier. This connection is necessary for reasons such as contractual agreements or country-specific carrier availability.
This is done by an easy API call to the endpoint for facility carrier connections. In our case, an empty JSON for the payload is good here:
This call requires the carrierId from the previous step and the facilityId from when the facility was created. A successful request returns a 200 OK response with the new connection details:
The connection is created with an INACTIVE status. To activate it, send a PUT request to the same endpoint:
Note that the payload includes the version number (1) from the previous response. It is crucial to provide the current version of the resource when making updates to prevent conflicts.
Repeat this process to connect and activate all other required carriers for the facility.
Last updated