fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
Edit on GitHub
  1. Carrier management

Carrier country service mapping

PreviousCarriers and connection to facilitiesNextSame day delivery

Last updated 4 months ago

While Carrier companies such as DHL or FedEx serve the same business (in a nutshell: transporting goods from A to B) their APIs and Interfaces look and behave differently.

In fulfillmenttools, Carrier Country Service Mappings (CCSMs) are used to simplify the implementation of clients that gather all the information needed before even requesting a parcel label. In a way they serve as a template for successful label requests of arbitrary order contents.

Please visit for more information on how to add a Carrier Country Service Mapping via API.

A Carrier Country Service Mapping (CCSM) can be defined per carrier.

  • For carriers operated by fulfillmenttools it is not necessary to set any CCSM as it is already provided by fulfillmenttools.

  • A carrier can have one, multiple or none Carrier Country Service Mappings. When there is no configuration for a needed source/destination combination the possibility of issues during runtime increases due to clients not knowing which data needs to be present.

  • A CCSM can have one source but multiple destinations to allow for configurations like "For every parcel with carrier X from Germany to France, the US, Canada or Sweden the following configuration is valid". This eases the configuration of new carriers as they often need to be configured similarly.

Developer Docs