Fluent Commerce Docs

Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases

Content in this track:

Fluent Platform Integrations and Connections

API Retries and Exponential Back-offs

Webhooks Frequently Asked Questions

commercetools - Send Payload to External webhook

commercetools - Receive External webhook

Connect SDK - Fluent Webhooks Integration

Build a Webhooks Monitoring Dashboard

End Of Track

Content in this track: Fluent Platform Integrations and Connections

Essential knowledge

Author:

Fluent Commerce

Changed on:

12 June 2025

Overview

Fluent platform functionalities are designed to be flexible by integrating with other APIs and Connectors and provides a real time view of the Inventory to the sales channels, enables integration with Warehouse Management Systems (WMS), carrier services, ERPs, etc.

Key points

Some common interfaces, and the information shared between these interfaces and the Fluent Platform
GraphQL, and understand its benefits over REST APIs.
Events API, Inventory Batches, Webhooks, and Connectors

Common Interfaces

There are many interfaces that you may come across in your projects, below we talk about some of the more common ones, and the information that's shared between them and the Fluent Order Management System.

Online Store	Source of orders can come from: eCommerce store Marketplaces Other sales channels Where these data sources may share the following with Fluent: Orders Payment transactions And, Fluent will respond will the following information: Available to Sell (inventory) Realtime fulfilment options for PDP/carts/checkout Order status updates
Product Master (PIM)	Product information management systems share the following data with Fluent: Master data (products/categories) Product descriptions / names / pricing / images Fluent is not the master of product data but it needs it to process orders Note: While Fluent Order Management needs a master data list from the PIM, Fluent doesn't maintain this master data.
Inventory Master (ERP)	Can be multiple sources One of the primary integrations Batch inventory Delta inventory (store sales) Note: The updated Available to Sell (ATS) is used by Product Availability / Fulfilment Options
Carrier Service	The Carrier Service may: Receive a carrier booking request Send consignment / shipping labels / tracking details Receive a manifest request
Payment Service	Can be used for Capturing payments (eCommerce) Refunds
Warehouse Management System	The Warehouse Management System or a Drop Ship Vendor may: Receive a Fulfilment request from Fluent OMS Send fulfilment updates to the Fluent OMS, such as updates on the Pick & Pack process

Integration Layers

Not all the integration payloads coming into and going out of the Fluent OMS need to follow a pre-defined structure. This is because the Fluent platform is designed to accept and process payloads in a particular format only. Third-party systems too, may follow a payload structure of their own. Hence, in order for Fluent OMS to communicate with third-party systems, it will need to transform its payload structure to a format that the Fluent platform understands and vice versa. This transformation is carried out by the Integration Layer between the Fluent OMS and the third-party systems.

Methods of Integration

APIs

Platform (REST) APIsFluent's Platform APIs are REST based and deal with platform related activities such as:

Authentication (OAuth)
Plugin Uploads/Installation
Handling Events
Workflow Updates

Domain (GraphQL) APIsFluent's Domain related APIs are GraphQL based, and used for activities such as:

Creation of entities like orders, fulfilment options, etc.
Getting information about location, inventory, etc.
Getting orders that are in a particular state
Getting details of a particular order, etc.
Any other information that's sitting within the domain side of things)

OMX Workflow Framework

The OMX Workflow framework which is driving business logic inside the Fluent OMS receives information from external sources via Events, and sends it out using Webhooks.

Batches

These are REST based and are primarily used to send Inventory feeds into Fluent from an integration point of view. The same API is also used to create retailers.

Connectors

Fluent Commerce also provides connectors to some common Enterprise Ecommerce platforms including the Salesforce Commerce Cloud, Salesforce Service Cloud, Adobe Commerce, and Commerce Tools.Note: We'll look at all the different integration options mentioned here, in more detail later in this course.

Related content

The Fluent GraphQL API provides powerful access to data, integration, and orchestration-driven business logic. It provides an opportunity to streamline and optimize requests to the Fluent Order Management platform in a way that is more flexible than the REST-based API.