Custom Carrier

Introduction

Apart from the provided carriers fulfillmenttools offers another option of carrier usage: The so called Custom Carrier. Those represent carriers that are not natively supported by fulfillmenttools, but are connected by an external service or operative process.

The concept is that a an own last mile fleet or an arbitrary carrier is integrated seamless into fulfillmenttools. Therefore a mechanism is implemented, so that partners or customers can do this work themselves, stay nimble and support their innovations in the best way possible.

Some examples for a custom carrier setup could be

• Sending parcels via a local bike carrier, that is called by phone or messenger when needed

• the shop owner, who takes parcels to a local carrier pickup point whenever it suits the operational process (maybe on his way home after work)

• an own carrier fleet that delivers goods on its own schedule using detached tooling (like a standalone routing service & delivery app)

Please go to the Developer Docs for more information on how to add a custom carrier via API.

Multiple custom carriers

While it is not possible to have more than one provided carrier in fulfillmenttools, it is very well possible to configure multiple custom carriers. Since the carrier key is used for identification and thus must be unique, a custom carrier must have the key starting with CUSTOM_ followed by any appendix (e.g. CUSTOM_BOSSONBIKE) to ease identification.