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
  • Company
  • Needs
  • Locations
  • Prerequisites
  • Structure

Was this helpful?

  1. Connecting to fulfillmenttools

Integration Tutorial

Previouscommercetools ConnectNextAdding facilities

Last updated 5 months ago

Was this helpful?

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

Hello and a warm welcome to this tutorial aiming to give you an understanding of how you can integrate the fulfillmenttools platform into your system environment. In the following pages we will describe the case of a fictional fashion retail company which wants to use the fulfillmenttools platform. In the following set of articles you will learn how to set up your tenant, configure it and eventually get inspired on how your integration might look like.

Company

Our company is focused on selling fashion for style-conscious 25-35 year old adults who now found their place in the world and feel the need for a good clothing style. Their customers have finished studying and have started their first full-time jobs and now look for a style that can fit them for some years. They therefore don't want to follow the latest fashion trends while still being stylish.

Needs

At the moment, online orders are only fulfilled by the warehouses the company operates. If ordered items are not available, customers either have to wait for the distributor to send that item to the warehouse, or customer service has to cancel this order line. This is a result of not knowing their global inventory levels, as no ATP (Available to Promise) is provided to the online shop. Additionally, by only operating in three countries, the shipping costs for small orders are very high.. With the fulfillmenttools platform the company wants to give the end customer a real omnichannel experience and increase their revenue by being able to fulfil online orders faster and with more margin. The management has declared to roll-out a new strategy by offering their customers:

  • Ship directly from stores

  • Including brick & mortar stores in shipping of ecommerce orders

  • Real checkout experience

Locations

With headquarters in Frankfurt, Germany the company is focused on the European market having stores in the following cities:

  • Vienna, Austria

  • Graz, Austria

  • Copenhagen, Denmark

  • Aarhus, Denmark

  • Odense, Denmark

  • Berlin, Germany

  • Munich, Germany

  • Hamburg, Germany

  • Frankfurt, Germany

  • Cologne, Germany

  • Stuttgart, Germany

  • Hanover, Germany

  • Amsterdam, Netherlands

  • Rotterdam, Netherlands

  • Utrecht, Netherlands

  • The Hague, Netherlands

  • Helsinki, Norway

  • Lisbon, Portugal

  • Zurich, Switzerland

  • Geneva, Switzerland

  • Basel, Switzerland

  • Bern, Switzerland

Currently, the central warehouses are located in

  • Frankfurt, Germany

  • Rotterdam, Netherlands

  • Bor, Czech Republic

The company does not exclude further expanding to other markets like North America or Asia.

Prerequisites

In order to follow this tutorial, the following things are helpful:

  • fulfillmenttools tenant and login credentials*

  • Postman, Insomnia or similar - any HTTP tool of your choice

  • curl (optional)

In this tutorial the API calls are made using curl.

Structure

This tutorial guides you through the usual steps of an integration of fulfillmenttools into your environment. This is the order of the steps we see in most of the projects.

  1. Firstly we will add the facilities to our tenant.

  2. After that we will add listings for these facilities.

  3. When the listings are added, we add stocks.

  4. To fulfill Ship-from-Store orders, we need to configure carriers.

  5. With the first four points we are ready to test the order placement.

  6. For fulfilling orders, we need to add users.

  7. To see whether an order is fulfillable, we use the checkout options.

  8. The full potential of our platform is used when the Distributed Order Management System is used.

  9. As last step we configure the local fulfillment.

*Your credentials will be received either by your professional services representative or when requesting a .

https://docs.fulfillmenttools.com/documentation
free trial tenant