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
  • Receiving orders at fulfillmenttools
  • Fulfillment status update at commercetools
Edit on GitHub
  1. Connecting to fulfillmenttools

commercetools connect

Last updated 5 months ago

Getting started

Do you want to try out the certified integration of fulfillmenttools with your project? Then please contact us at , and we will provide you with a test system to get started.

The in the is a certified integration connector that synchronizes information between your commercetools and your fulfillmenttools project. It is fully customizable and very easy to set up and deploy, so you can start fulfilling orders from your eCommerce system without a complicated integration process.

lets you add functionality to your project without buying and maintaining dedicated hosting or runtime environments.

Our fulfillmenttools connector app is published as open source under the MIT license. You can check it out from our .

Receiving orders at fulfillmenttools

The fulfillmenttools connector app uses to get notified once the of an order is changed to Confirmed. With this status the commercetools order is ready and a new order is created in the fulfillmenttools platform.

Depending on the shipping method of the commercetools order, either a ship-from-store or a click-and-collect order is created in fulfillmenttools.

Fulfillment status update at commercetools

Event
Action

ORDER_CREATED

Set custom field fft_order_id

PICK_JOB_CREATED

Set custom fields fft_pickjob_id, fft_short_id, and fft_facility_id

PICK_JOB_PICKING_FINISHED

Set custom field fft_load_units_amount

HANDOVERJOB_CREATED

Set custom field fft_handoverjob_id, update ShipmentState to Ready

HANDOVERJOB_HANDED_OVER

Update ShipmentState to Shipped

As a result of the order routing process, a pick job will be created in the fulfillmenttools platform. During the lifetime of the pick job (picking started, finished) and the corresponding handover job (created, handed over), the fulfillmenttools platform will send out events with status updates. The fulfillmenttools connector app processes this information to update the custom fields and the .

The following are used to update the commercetools order:

ShipmentState of the commercetools order
fulfillmenttools events
professionalservice@fulfillmenttools.com
fulfillmenttools connector app
commercetools marketplace
commercetools Connect
GitHub repository
commercetools subscriptions
commercetools OrderState
ct order