fulfillmenttools
API documentationIncident ManagementFeedback
Developer Docs
Developer Docs
  • Developer docs
  • Getting Started
    • Quickstart
    • Integration tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
    • Free trial
  • Technical Basics
    • Access to fulfillmenttools
    • Feature status
    • Available regions
    • Backup policies
  • Connecting to fulfillmenttools
    • Client SDKs
    • commercetools connect
    • OpenID connect
      • Configure Microsoft Entra ID / Azure Active Directory
      • Configure Keycloak
  • API
    • Core concepts
      • Authentication & authorization
      • API Versioning & lifecycle
      • Assign user to jobs
      • Localization
      • Resource timestamps
      • Custom attributes
      • Article attributes
      • Recordable attributes
      • Data update guarantees
      • Rate limits & scaling
      • Retries
      • Performance on test vs. production systems
      • Load testing
    • API calls
      • Postman
      • cURL
      • GraphQL Explorer
    • GraphQL API
    • RESTful API
      • Pagination interface
      • RapiDoc
      • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an event
      • Available events
        • Event flows
      • Eventing example
      • Event export
  • Integration Guides
    • Basics
      • Article categories
      • Audits
      • Facilities
      • Facility groups
      • GDPR configuration
      • Listings
      • Remote configuration
      • Receipts
      • Search
      • Subscribe to events
      • Sticker
      • Stocks
      • Storage locations
      • Tags
      • Users
    • Channel inventory
    • Inbound process
    • Outbound stocks
    • Purchase order
    • Receipt
    • Routing strategy (context-based multi-config DOMS)
    • Show sticker to clients
    • Stow jobs
  • More Integration Guides
    • Carrier management
      • Introduction to carrier configuration
      • Required data when operating carriers
      • Adding & connecting carriers to facilities
      • Custom carrier
    • Configurations for order fulfillment
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing and document configuration
      • Packing container types
      • Parcel tag configuration
      • Headless order fulfillment
      • Short-pick reasons
      • External documents in order fulfillment
      • Service jobs
      • Load units
      • Running sequence
    • DOMS - distributed order management system (routing)
    • External actions
    • Interfacility transfer
    • Notifications
    • Orders
      • Place your first order
      • Ship-from-store orders
      • Click-and-collect orders
      • Locked orders
      • Order with custom services
      • Bundled items in an order
      • Order process status
    • Availability & promising
    • Returns
Powered by GitBook
On this page
  • Introduction
  • Company
  • Needs
  • Locations
  • Prerequisites
  • Structure
Edit on GitHub
  1. Getting Started

Integration tutorial

Introduction

Hello, and a warm welcome to this tutorial. It aims 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 that 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

Currently, 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 results from not knowing their global inventory levels, as no ATP (Available to Promise) is provided to the online shop. Additionally, since we only operate 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 fulfill 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

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 integrating 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. To fulfill 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 the last step, we configure the local fulfillment.

Last updated 5 months ago

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

free trial tenant