Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases

Implementing Fluent Order Management

External Mappings (Metadata for example; Locations, Products, Retailers, Users & Roles, etc.), Project Discovery, Out-Of-The-Box features, Ready for Launch process, Recommended Practices, Testing, and Project Checklists.

Customer Sync - commercetools Connector

Essential knowledgeExplains how the commercetools Connector synchronizes customer profile data from a storefront to Fluent Order Management. Partners will learn to configure, validate, and extend this outbound data pipeline from the storefront trigger to the final GraphQL delivery. For the business, this real-time pipeline removes profile fragmentation, giving customer service agents instant access to accurate records.Note: This article forms part of the outbound pipeline category, where data flows out of the commercetools environment to an external destination.

Core Function & Outcome: You will learn how the commercetools Connector detects and processes customer creations and modifications automatically the moment they occur on the storefront, removing the need for manual batch data transfers.
Asynchronous Queue Infrastructure: The architecture routes payloads through an external `ct-queue` and an internal Event Queue sequentially, decoupling storefront event triggers from backend database processing to protect platform stability.
Declarative Route Filtering: Implementing partners can manage message types, configure explicit inclusion filters, and reassign target data pathways directly within the `application-connector.yml` configuration file without modifying core system code.
Extensible Handler Architecture: The core message routing and transformation layers are completely decoupled, enabling developers to cleanly introduce custom profile fields and data-mapping logic by extending the base `MessageHandler` class.

Connect SDK Libraries

Essential knowledgeThe Connect SDK Libraries comprise a modular software development framework designed for building integrations with Fluent Order Management. The architecture centers around a mandatory core module that handles foundational communication, configuration storage, and routing capabilities. Implementation teams can extend this baseline engine using specialized, pluggable add-on libraries to introduce web frameworks, security filters, specific cloud or infrastructure adapters, and isolated simulation testing suites.

What You Will Learn: You will understand the structural purpose of each component within the Connect SDK framework and learn how to select the appropriate core, web, cloud infrastructure, or testing dependencies for your implementation project.
Mandatory Core Requirement: The `connect-sdk-core` library is a mandatory dependency for all SDK-based implementations. It houses the baseline engine components, including the REST and GraphQL API client, authentication management for sensitive credentials, message routing, and the configuration manager.
Asynchronous Processing Boundary: All transactional endpoints and internal processing steps handled by the SDK execute asynchronously in the background. The explicit exception to this design rule is product availability processing, which runs synchronously.
Pluggable Architecture Strategy: Advanced technical capabilities are intentionally isolated into decoupled modules. Developers append specialized add-ons like `connect-sdk-core-web-security` for Spring Security filters, `connect-sdk-core-aws` for Amazon Web Services (AWS) deployment services like Amazon Simple Queue Service (SQS) and AWS Secrets Manager, or `connect-sdk-core-kafka` for Apache Kafka support.
Isolated Testing Frameworks: The SDK segregates quality assurance utilities into specific test scopes. Teams deploy `connect-sdk-test-core` to mock external API calls with Wiremock, or utilize the AWS and Kafka test extensions to run integration tests inside software containers alongside LocalStack or virtual Kafka brokers.

Connect SDK - Fluent Webhooks Integration

Essential knowledgeThe Fluent Connect SDK offers seamless integration with Fluent Webhooks, enabling you to receive messages and perform various actions based on incoming calls. This document provides an overview of the core features of the Fluent Connect SDK and outlines the steps to integrate it into your application. Go here to read about Fluent Webhooks.

Standardized Webhook Ingestion: You will learn how the Connect SDK natively exposes a dedicated endpoint (`/api/v1/fluent-connect/webhook`) to receive inbound HTTP calls from Fluent Webhooks, automatically transforming raw payloads into the SDK's internal message queue format for scalable processing.
Automated Signature Verification: To protect the authenticity and integrity of system interactions, the SDK automatically runs signature validation checks on all incoming messages using environment-specific public keys pre-configured within the `application.yml` file.
Routing & Handler Dependencies: An important operational consideration is that an inbound webhook payload will only execute successfully if its event name explicitly corresponds to a designated internal message handler and an active, matching configuration route.
Local Development Tunnels: Because local execution environments (`localhost:8080`) are isolated from the internet, developers testing live Fluent workflows locally must utilize a secure tunneling utility like `ngrok` to create a publicly accessible URL that safely routes traffic back to the local webhook endpoint.

commercetools Connector Project Configuration

Essential knowledgecommercetools Connector Project Configuration

Configuration files
Route Mappings
Routes
Listeners

UX Configuration - Common Concepts

Essential knowledgeSome common types and conventions are used across many component definitions. These items are not directly configurable in the manifest but will often be referenced in other component definitions that use them.

The Mystique manifest configures icons, cards, and template strings. Icons come from React Icons.
Cards have common fields, and template strings allow dynamic values. Dynamic attributes (standard, image, component) offer flexibility based on conditions.
A selection of helper functions are also available to control and transform these values as required, for example, number, logic, i18n, array, date, and string functions.
Additional options like TextOptions and ImageOptions provide styling choices.

Salesforce Connectors Overview

Essential knowledgeFluent Commerce offers a scalable cloud platform with Distributed Order Management functionality. This functionality includes support for Click and Collect, Ship from Store, Omnichannel Returns, and a Single View of Inventory across all locations. The Salesforce connectors enable integration between Salesforce Commerce Cloud (SFCC)storefront, Salesforce Service Cloud (SFSC) customer service application, and Fluent Order Management.

The Salesforce connector enables integration between SFSC, SFCC and Fluent OMS.

About Reference And Extension Modules

Essential knowledgeModules are the package structure used by Fluent Commerce to ship preconfigured features and functions. They are designed to be self-describing, isolated, but inter-dependent assets that can work together with other modules, or be extended by custom modules, all while remaining upgradeable.Here we'll look at the different designations of Modules and describe the Module's Package Structure and Project Structure.

3 types of Modules: Reference, Extension and Data
Reference Modules are authored and maintained by Fluent Commerce
Extension Modules are created and maintained by customers and partner's teams
Module Structure defines the contents of a Module Archive
Module Project describes all the Module Assets, source code for Rules or Components and is checked into Source Control
A build step assembles the Module Assets into the Module Structure and creates the Module Archive
Fluent CLI commands like `fluent module install` only operate on the Module Archive or Module Structure

Working with Workflows and Workflow Fragments

Essential knowledgeIn this document we will describe how to work with workflows and workflow fragments using the Fluent CLI. Then delve into how the tool is tracking the installed workflows, fragments in the workflow log.

Use the Fluent CLI command `workflowlog` to manage the workflow and fragment lifecycle
For background on workflows and fragments, read the page On Workflows and Workflow Fragments.

On Workflows and Workflow Fragments

Essential knowledgeWorkflows are the backbone of the Fluent platform as they describe the lifecycle of an entity. Defining subsections or sub-processes within a workflow allows to manage and evolve them independently. Thus fostering loosely coupled and self-contained fragments with no duplication of shared or unchanged behavior of a baseline workflow.On this page we will look at the different ways of structuring workflows into fragments and then how to optimally merge them into a final workflow that is used to orchestrate entities. Finally how to package both workflows and fragments into a module.

A Workflow defines behavior of an entity, such as order, fulfillment, or an inventory position.
A Workflow Fragment is a sub-process within a larger workflow, managed separately from the rest of the workflow.
Keeping workflow customizations in a workflow fragment and applying one or more fragments on top of a reference workflow reduces the duplication of rulesets and minimizes future maintenance.
At module deployment time, the Fluent CLI will combine multiple fragments into a final workflow and upload to the target retailer. More details on the CLI commands are in Working with Workflows and Fragments.
Asset execution order: `workflows` before `workflow-fragments`.

Utility Bundles Overview

Essential knowledgeThe Fluent Commerce Utility Bundles are a set of libraries designed to accelerate Rule development, reduce boilerplate code, and improve the overall quality and maintainability of implementations. They are the cornerstone of writing maintainable, reusable, and easily upgradeable Rules for the Fluent Commerce platform.

Prerequisites: You should have knowledge of the Rules SDK, including Designing Rules, Rule Structure, Writing Rules, Rule Development Guidelines, General Principles, and Rules SDK - Getting Started.
Focus on Business Logic: The libraries handle common, repetitive tasks (like data fetching and JSON conversion), allowing developers to concentrate on writing the business logic that delivers value.
Three Specialized Bundles: The utilities are organized into three modules: `util-core` for essential daily tasks, `util-dynamic` for building runtime queries, and `util-test` for simplifying testing.
Easy Upgrades: Receive bug fixes and new features from Fluent Commerce by updating the dependency version in your `pom.xml`, ensuring your implementation stays current.
Built for Extensibility: The utilities are designed to be flexible, allowing you to inject your custom logic into standard processes.

Ready for Launch Process

Essential knowledgeThe Ready for Launch process (RFL) is an engagement with the Fluent Commerce Expert Services team throughout the lifecycle of a Fluent project. The process is initiated at the beginning of a Fluent Commerce project and completed with the go-live of the project in production.The final review ("RFL Launch Gate") should be planned for 3-4 weeks before the desired Go-Live event to receive the approval to move into production.

The Kickoff stage covers the introduction to the Ready for Launch process and the initial project & solution overview.
The Design Review stage covers a detailed presentation of the solution by the partner and the review of the implementation by Fluent Commerce.
The Launch Gate stage covers the presentation of the final solution and performance test results as well as the confirmation of the desired launch date. After a final review, Fluent Commerce provides the production go-live approval.

Users Configuration Overview

Essential knowledgeOMS Webapp's Users List page allows users to efficiently search and view existing users using a versatile filter component. The Users table provides essential user details, with a clickable Username link leading to a detailed User Details page displaying user information. The paging control at the bottom ensures easy entry management with customizable rows per page and intuitive navigation.

`Type`: Understand the different types of users; ADMIN, RETAILER, API, and AGENT
User Status: Be aware of the user status options, ACTIVE and INACTIVE, which reflect the user's current accessibility.
Filtering Users: Utilize the filter component to efficiently search for users based on various criteria like username, status, creation date, and type.
Roles and Permissions: Assign roles to users to manage permissions within the system, ensuring each user has the appropriate level of access.
Paging Control: Utilize the paging controls at the bottom of the Users table to navigate between pages and manage the number of entries displayed per page, with options for 10, 25, or 100 entries.
Deprecation Notice: Be aware that certain user types such as AGENT, SUPPORT, and others have been deprecated and should not be used for new users.