fulfillmenttools
  • Welcome to the fulfillmenttools Platform Documentation
  • Getting Started
    • Setup your access to fulfillmenttools
    • Make your first API Calls
      • Add your first facility
      • Add your first listing
      • Place your first order
    • Core concepts & terminology
      • Order Flow
    • Postman Collection
    • Client SDKs
    • FAQ
  • Clients
    • Backoffice
      • First steps - Registration
      • Network view
        • Home
        • Orders
          • Unroutable orders
          • Pre-orders & Backorders
          • Order History
        • Inventory Management
          • Stock Overview
          • Channel Inventory
        • Facilities
        • Users
        • Returns
        • DOMS configuration
        • Settings
        • Analytics
          • DOMS Pages
          • Fulfillment Operations Pages
          • Inventory Pages
          • Downloads Page
      • Facility view
        • Home
        • Inbound
        • Tasks
        • Listings
        • Storage Locations
        • Facility
        • Users
    • Inventory app
      • Registration Inventory App
      • App sections
        • Inbound
        • Storage and relocation
    • Operations app
      • Android
        • Manual Registration
        • Android Enterprise Registration
        • Sections
          • Picking
            • Load Units (legacy)
            • Substitute items
            • Weighed or measured products
            • Scanning configuration
            • Picking Methods
              • Batch Picking
              • Multi Order Picking
          • Packing
          • Handover
          • Returns (legacy)
        • Printing
        • Notifications
      • Webapp
        • Packing
      • Overview features Android & Webapp
    • Technical requirements
      • Zebra Hardware Scanner Configuration
      • Honeywell Hardware Scanner Configuration
      • Supported barcodes for camera scanning
      • Requirements for fft applications
      • Zebra printer
    • Returns app
      • Handle unannounced returns
      • Handle announced returns
  • Products
    • Core Functionality
      • Process
        • External actions
      • Add and manage facilities
      • Notification Center
      • Checking on features
      • Tags and Stickers Concept
      • GDPR
      • Remote Configuration
      • Expiry
      • Target time
      • Time calculation for queries of future availabilities (LPS-calculation)
      • Interfacility Transfer
    • Carrier Management
      • Overview
        • Available Carriers
      • Concepts
        • Carrier Country Service Mapping (CCSM)
        • Non-delivery-days
        • Custom Carrier & Headless operation of Carriers
      • Providing needed data
    • Fulfillment Options
      • Fulfillability Check
      • Checkout Options
        • Available fulfillment options based on basket
        • Earliest possible delivery date
        • Available delivery dates within time-period
        • Availability for delivery date
      • Delivery Promise
    • Inventory Management
      • Configurations
      • Entities
        • Listing
        • Stock
          • Stock Properties
        • Storage Location
        • Zone
      • Global Inventory
        • Stock availability
        • Channel Inventory
        • Expected stock
        • Inbound Process
        • Reservations
        • Safety Stock
      • Inventory Control
        • Inventory Traits
        • Measurement Units
        • Outbound Inventory Tracking
        • Storage Location Recommendations
    • Order Fulfillment
      • Headless Order Fulfillment
      • Pick Jobs
      • Zone picking
      • Load Units
      • Custom Service
      • Handover Jobs
      • Add External Documents
      • Configurations
        • Picking Configuration
          • Picking methods
          • Short Pick Reasons
        • Packing Configuration
          • Packing Container Types
        • Print / Document Configuration
        • Tag Configurations
          • Parcel Tag Configuration
        • Handover Configuration
        • Operative Container Types
    • Order Routing
      • Entities
        • Ship-from-Store Orders
        • Click-and-Collect Orders
        • Locked Orders
        • Custom Services Orders
          • Simple Custom Service Order
          • Complex Custom Service Order
      • Fences
      • Ratings
      • Order Split
        • Order split - initial routing
        • Order split after shortpick
        • Item bundles
      • Reroute
      • Shape the routing with the DOMS Toolkit
      • Decision logs
    • Returns Management
      • Returns legacy
        • Available status
      • Returns 2.0
        • Return Reasons
        • Item Conditions
        • Integrating Returns with Events
    • Use Cases
      • Demand-Driven Replenishment
      • Expected stock in availability
      • Multi Order Picking
      • Interfacility transfer
      • Assigned Users
  • Connecting to fulfillmenttools
    • General Topics
      • Use external identity providers to authenticate to fulfillmenttools
        • Microsoft Entra ID / Azure Active Directory (AD)
      • Public Event Export
      • Available Regions
      • Backup Policies
    • GraphQL API
    • RESTful API
      • General Topics
        • API Release Life Cycle
        • Versioning
        • Authorization
        • Customization via Attributes
        • Update Guarantees
        • Rate Limits
        • Resource Timestamps
        • Pagination Interface
        • Localization
        • Custom Attributes
      • OpenAPI Specification
        • Swagger UI
        • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an Event
      • Available Events
      • Tutorial
    • commercetools Connect
    • Integration Tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout Options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
  • Incident Reporting
    • How to report incidents in fulfillmenttools
    • How to define incident priorities
  • Release Notes
    • Release Summary – May 2024
    • Release Summary – June 2024
    • Release Summary – July 2024
    • Release Summary – August 2024
    • Release Summary – September 2024
    • Release Summary – October 2024
Powered by GitBook
On this page

Was this helpful?

  1. Products
  2. Carrier Management
  3. Concepts

Carrier Country Service Mapping (CCSM)

This Concept supports in defining, checking & reassuring the presence of values needed for specific carrier & country combinations.

PreviousConceptsNextNon-delivery-days

Last updated 5 months ago

Was this helpful?

This page is outdated. Please go to our new documentation under .

Overview & Idea

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 very differently. The access is very unique from carrier to carrier and also the provided information varies - even within the interface of the same carrier but with different source or destination countries.

In fulfillmenttools we use Carrier Country Service Mappings (or: CCSMs for short) in order to tackle this situation. They aim at easing 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 an arbitrary order contents.

Description

A CCSM is definable per Carrier. The information it holds is structured in the following way:

Taking a look at the example above the following statements are useful to understand the concept:

  • For carriers operated by fulfillmenttools you do not need to set any CCSM - it is provided by fulfillmenttools

  • A carrier can have multiple or none Carrier Country Service Mappings. In case it does not have a set configuration for a needed source/destination combination increases the possibility of issues during runtime 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 and their often similar configuration

Currently only the following combination of mandatory fields will be transformed into valid fields during a Label request from our Clients:

Category: Dimensions Values: weightPerUnit

Category: Customs Values: hsCode, currency, valuePerUnit, countryOfManufacture, numberOfDecimalPlaces

Which means: The combination xx.yy could be a valid mandatory field configuration inside a CCSM, but this field will not be mapped into a label request field and ultimately could result in failing label request because of missing data.

This does not mean that all of these fields are needed in a valid CCSM or are needed for a valid label request

Example

Let's find out about the CCSMs of a carrier provided by fulfillmenttools. We start by retrieving the ID of the carrier we are interested in:

In this example the response looks like this:

200 OK

{
    "total": 13,
    "carriers": [
        {
            "id": "2f7fc1c8-ed29-4772-814a-28c139919cc7",
            "name": "INTEX",
            "key": "INTEX",
            "deliveryType": "DELIVERY",
            "status": "ACTIVE",
            "version": 1
        },
        ...12 more...
    ]
}

We are facing a system with 13 configured carriers. We will take a look at INTEX in this example which is used for sending from germany to germany.

Let's fetch the CCSMs for said carrier

200 OK

[
    {
        // deprecated fields omitted
        "id": "76486a41-f84c-4ebd-b46d-1654915ae8d4",
        "source": {
            "countryCode": "DE"
        },
        "destinations": [
            {
                "countryCode": "DE"
            }
        ],
        "mandatoryShippingItemAttributes": [
            {
                "referencedField": "quantity",
                "dataType": "Number",
                "descriptionLocalized": {
                    "en_US": "Quantity",
                    "de_DE": "Menge",
                    "nl_NL": "Hoeveelheid",
                    "fr_FR": "Quantité en grammes",
                    "it_IT": "Quantità",
                    "nb_NO": "Antall",
                    "es_ES": "Cantidad",
                    "pl_PL": "Ilość",
                    "ru_RU": "Количество"
                }
            },
            {
                "referencedField": "parcelItemValue.value",
                "dataType": "Number",
                "descriptionLocalized": {
                    "en_US": "Value per item",
                    "de_DE": "Wert pro Artikel",
                    "nl_NL": "Waarde per item",
                    "fr_FR": "Valeur par article",
                    "it_IT": "Valore per articolo",
                    "nb_NO": "Verdi per vare",
                    "es_ES": "Valor por artículo",
                    "pl_PL": "Wartość za sztukę",
                    "ru_RU": "Стоимость за штуку"
                }
            }
            {
                "referencedField": "parcel.values.insurance.currency"
                "dataType": "String",
                "descriptionLocalized": {
                    "en_US": "Currency",
                    "de_DE": "Währung",
                    "nl_NL": "Valuta",
                    "fr_FR": "Monnaie",
                    "it_IT": "Moneta",
                    "nb_NO": "Valuta",
                    "es_ES": "Divisa",
                    "pl_PL": "Waluta",
                    "ru_RU": "валюта"
                }
            }
        ],
        "mandatoryShippingAttributes": [
            {
                "referencedField": "pickUpInformation.startTime",
                "dataType": "Date",
                "descriptionLocalized": {
                    "en_US": "Start pickup time",
                    "de_DE": "Beginn Abholzeit",
                    "nl_NL": "Begin afhaaltijd",
                    "fr_FR": "Heure de début de l'enlèvement",
                    "it_IT": "Orario di inizio ritiro",
                    "nb_NO": "Starttidspunkt for henting",
                    "es_ES": "Hora de recogida",
                    "pl_PL": "Czas rozpoczęcia odbioru",
                    "ru_RU": "Время начала самовывоза"
                }
            },
            {
                "referencedField": "pickUpInformation.endTime",
                "dataType": "Date",
                "descriptionLocalized": {
                    "en_US": "End pickup time",
                    "de_DE": "Ende Abholzeit",
                    "nl_NL": "Eindtijd ophalen",
                    "fr_FR": "Heure de fin d'enlèvement",
                    "it_IT": "Ora di fine ritiro",
                    "nb_NO": "Sluttidspunkt for henting",
                    "es_ES": "Fin del horario de recogida",
                    "pl_PL": "Końcowy czas odbioru",
                    "ru_RU": "Время окончания самовывоза"
                }
            }
        ]
    }
]

As you can see:

  • For parcels from Germany to Germany (indicated by ISO code "DE" and further definable into postalcodes (not used here)) there are

  • two required attributes for each parcel called "Start pickup time" and "End pickup time" which define a time window for picking up the shipment.

  • Furthermore you need to have the Quantity and Value of each shipped line (used to calculate insurance & helps to select this carrier automatically in specific cases) as well as

  • the overall Value of the parcel.

https://docs.fulfillmenttools.com/documentation
Drawing

Returns all configured CEP partners

get
Authorizations
Query parameters
startAfterIdstringOptional

all entities after given Id

sizeintegerOptional

number of entities to show

Default: 25
localestringOptional

Provide the localized names and descriptions for the parcel label classifications. If not provided the default locale is used., for example de_DE.

Responses
200
The current list of available carriers
application/json
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this endpoint
application/json
404
No more elements available
application/json
get
GET / HTTP/1.1
Host: %%HOST%%
Accept: */*
{
  "carriers": [
    {
      "created": "2020-02-03T08:45:51.525Z",
      "lastModified": "2020-02-03T09:45:51.525Z",
      "version": 42,
      "deliveryType": "SAMEDAY",
      "id": "climk4dcQFiPdA5ULuhS",
      "key": "text",
      "lifecycle": "GA",
      "name": "DHL Köln",
      "status": "ACTIVE"
    }
  ],
  "total": 42
}

Get a CarrierCountryServiceMappings for carrier with given ID

get
Authorizations
Path parameters
carrierIdstringRequired

ID of the carrier you want to get the countryservicemappings for

Responses
200
Carrier's countryservicemappings found & you are allowed to access it. The result is in the body.
application/json
Responseany
401
Your user is not allowed to operate against this API instance
application/json
403
Your user, although recognized, is not authorized to use this endpoint
application/json
404
Carrier's countryservicemappings Configuration not found
application/json
get
GET / HTTP/1.1
Host: %%HOST%%
Accept: */*
[
  {
    "id": "bc5b581a-8f65-45b0-9f81-6e0d4babbcb2",
    "source": {
      "countryCode": "DE",
      "postalCodes": [
        "text"
      ]
    },
    "destinations": [
      {
        "countryCode": "DE",
        "postalCodes": [
          "text"
        ]
      }
    ],
    "mandatoryShippingAttributes": [
      {
        "referencedField": "dimensions.weight",
        "dataType": "Number",
        "description": "text",
        "descriptionLocalized": {
          "de_DE": "Wert",
          "en_US": "Value",
          "ru_RU": "значение"
        }
      }
    ],
    "mandatoryShippingItemAttributes": [
      {
        "referencedField": "description",
        "dataType": "Number",
        "description": "text",
        "descriptionLocalized": {
          "de_DE": "Wert",
          "en_US": "Value",
          "ru_RU": "значение"
        }
      }
    ],
    "product": "EXPRESS",
    "carrierProductCategory": "STANDARD",
    "transitTime": {
      "minTransitDays": 1,
      "maxTransitDays": 3
    },
    "deliveryCosts": [
      {
        "cost": 10.99,
        "currency": "EUR"
      }
    ]
  }
]
  • Overview & Idea
  • Description
  • Example
  • GETReturns all configured CEP partners
  • GETGet a CarrierCountryServiceMappings for carrier with given ID