By Type

A Fluent Connector project typically has the structure as defined below :
com.fluentcommerce.connect.custom

Any customizations/extensions can either be done under the custom folder or as a separate module (jar) altogether.

Regardless of which way one chooses to extend it, the key message here is that any custom code should be under the 

`com.fluentcommerce.connect`

`com.fluentcommerce.connect`

`@HandlerInfo(name = "CustomCategoryUpsert", priority = 100)`

• You would first need to have access to a Fluent account, and have

  `localstack`

   container running.
• There are two possible cache configurations: In-memory cache or External cache.

• The User can configure Kafka Connector on top of the Connect SDK.
• Some configuration is required. 

The commercetools-connector expects a minimum of 4 configuration files:

• application-connector.yml - Project and Connector specific configuration.
• application.yml - Core Connect commercetools-connector configuration. These are mostly default configurations and core settings.
• bootstrap.yml - Server/Container configuration. This file includes settings for all different environments and -follows the spring profile standards.
• logback-spring.xml - Log configuration also supports different configurations based on spring profiles.

It is possible to have dedicated configuration files for each environment. This is often used to override a common setting for a particular environment. To create such a file, follow SpringBoot's format having the additional desired spring profile name at the end of the application.yml file, for example: application-dev.yml.

The customer Collections feature is applicable to the Click and Collect fulfilments. This feature enables the store users to confirm the orders collected by customers in-store.

An Event represents something that has, will, or is happening within the system.

The Fluent Store Web App brings Order Management capabilities to the in-store experience, enabling Retailers to transform their existing Stores into fulfillment and distribution centers, optimizing costs and enhancing the customer experience.

The 

`@RuleInfo`

• A trick to display the full value regardless of the user's screen size

• Address Validation: Ensure that the address entered by the user is valid and correctly formatted to avoid shipping issues.
• Default Address: Allow customers to set a default address for a quicker checkout process.
• Edit Capability: Provide an option for users to edit customer address details in case of errors or changes.
• User Experience: Design the add and edit address process to be user-friendly and accessible, with clear instructions and error messages.

• Configuration

• A step by step guide on how to create Order Line / Order Item search page in Fluent Store

• Adding a Ruleset via the UI
• Adding a Ruleset via JSON

• It’s possible to add settings to a workflow via Json in order to improve the performance and the functionality of the workflow.

• It’s possible to add a new state into an existing WorkFlow by adding a new status to the

  `Statuses array`

  of the workflow JSON.

• A Trigger defines when a User Action is applicable to the given entity.  
• A trigger can be added via UI or via JSON. If there’s not trigger status for a ruleset, then all statuses are considered as trigger.

• User actions allow to manually trigger specific events in the Workflow.
• User Actions can be added, changed, or removed.
• User actions can be added via UI or via the Workflow JSON.

• Working with Rules
• Adding a Rule via the UI
• Adding a Rule via the Workflow JSON

• It’s possible to add a new entity to an existing Workflow by modifying the original Workflow. In order to do so, a “CREATED” status and a CREATE Ruleset need to be added for the new entity.
• This is not feasible via “ADD RULESET".

•  A category represents a lifecycle phase in the WorKFlow,  it appears as a vertical column in the WF UI.
• Within each lifecycle, we can have one or multiple statuses.

• Prior to installing the Adobe connector package, make sure that the versions are compatible. 
• In order to install the connector package, you would need to back up the system and the data base, download the package, enable the module and confirm the installation.

• This guide covers setting up a fresh new Adobe Connector in the below-required systems:
  •  Fluent OMS information details (account credentials, client secret, etc.)
  • Adobe Commerce
• This guide does not cover:
  • The standard setup of Fluent OMS, this guide is explicitly for the Fluent Adobe Connector configuration.
  • Detail on how to migrate an existing Adobe Commerce to use Fluent OMS.
• Please get in touch with Fluent Expert Services for guidance on any migration.

The Aggregate Inventory Sync will enable product inventory syncing from Fluent to commercetools at an aggregate level. The master source will be Fluent for inventory syncing.

• User action capability is used to create a Refund against an Order. Order workflow should be extended to have a rule to capture appeasement requests and then process them by looking up the billing account of that customer and creating a credit memo of that refund amount. 
• It is possible to configure Appeasement functionality via UI and via Postman.

• Login into Fluent Web Apps
• Multi-Factor Authentication
• Session Timeout

• The article offers detailed instructions for setting up Single Logout (SLO) for Azure AD, serving as an external identity provider.
• Users can establish a robust authentication system by following the precise steps outlined, enhancing security and efficiency.

• Create a profile
• Create a retailer
• Configure and Install the Fluent Reference Modules
• Configure and Install the Extension Data module
• Validate the Account setup

• A python script can be used for ad-hoc extracts of a large number of GQL entities into a CSV file. 
• Currently the Fluent platform does not support any bulk extracts. 
• This scripts helps to extract data in bulk using the pagination functionality provided by the schema.
• Depending on the amount of data that is extracted the script might run for a while.
• The above codes are provided as is and are for reference purposes. 

• Perform a bulk mutation update on the Location hours.
• Requires Postman and Pycharm 

Carrier Booking and the Carrier Collections feature is applicable to the Home Delivery fulfilments which are being shipped to a customer as well as the Click and Collect fulfilments which are being shipped from the fulfilling store to the customer's pick up location.

Carriers configuration contains:

• Carriers List page
• Carrier Details page

• Understanding the Market: Recognizing the importance of Cash on Delivery (CoD) in markets like India, where it is a preferred payment method.
• Global Adaptability: The workflow's design serves a global audience, providing a template that can be customised for regions where upfront payment is not the norm.
• Seamless Integration: Ensuring the CoD process is smoothly incorporated into the existing order journey to enhance customer experience.
• Operational Efficiency: Streamlining the CoD transaction to ensure quick and secure payment collection at the point of delivery.

The Category Module is responsible for synchronizing categories from Adobe Commerce to Fluent.

Key features:

• Manually synchronize the entire categories at any time using the CLI command.
• Automatic detection and synchronization of modified categories.
• Multi-retailer / multi-website configuration support.

The Category Sync is responsible for synchronizing categories from commercetools to Fluent.

Key features

• Manually synchronize the entire categories at any time
• Automatic detection and synchronization of modified category

• User action capability is used to update the Delivery Info of an Order.

• Enable customer order pick-ups
• Manage uncollected orders

• Adding Attribute details via the UI
• Adding Attribute details via the Workflow JSON

• Setting Example
• Defining the Dot for Each Value in the Cell
• Setting Naming Convention

• The 2.0 Commerce tools connector offers a range of new capabilities in regards to configurations, availability calls and DSK context creation.
• The migration requires a few Java changes and configuration changes that are covered in detail in this article.

•  In order to utilize the commercetools connector, you would need to download the Java-based commercetools Fluent Connector and make sure you have the right dependencies and tools.
• Development and deployment: The development environment needs to be configured with the correct credentials. The build and run are done via dockers and scripts. CloudFormation can be leveraged for production deployment.
• Connect SDK and commercetools Connector should have matching versions for increased stability.

• In order to integrate commercetools API, an API Client needs to be created on commercetools.
• When this is completed, you will need to proceed with the commercetools connect SDK installation to enable the connector. 

• It’s possible to commit a Workflow change via the UI as long as the user has the right permissions.

• Using Chrome developer tools and IDEA Webstorm to debug Fluent component SDK
• This article will only work for Chrome desktop browser

• Adding the application to PingOne
• Registering application with Microsoft
• Getting the client ID and client secret for the application
• Setting up API permissions
• Adding the identity provider in PingOne
• Adding the Redirect URI to the Microsoft portal
• Do not forget

• It is possible to use the generic SAML configuration to add an external identity provider that follows the SAML standard. 
• Steps to configure an external identity provider via SAML configuration

• Create your Master-Retailer Inventory Catalog
• Create your Sub-Retailer(s) Virtual Catalog(s)
• Configure your Inventory Catalog Workflow for Cross-Retailer events sending

• Use Bulk Threshold Controls to manage Out of Stock and At Risk Statuses for Inventory and Virtual Positions
• Create Control Groups for Inventory and/or Virtual Catalogs to respectively apply Bulk Threshold Controls
• Configure Bulk Threshold Controls with:
  • Context
  • Threshold
  • Status
  • and Execution Order

• The Unified View of Inventory (UVOI) is a powerful feature available out of the box. It offers comprehensive insights and real-time updates across inventory locations and sales channels.
• To configure its full functionality, you need to create several settings that define default filter values and ensure filters are populated with appropriate statuses from workflows.
• This guide will walk you through the configuration steps using examples from a reference solution. Note that the statuses and catalog names of these examples may differ from your specific implementation requirements.

There are two ways to perform integration tests. The first involves creating the tests within the same project as your custom connector code. Alternatively, if your custom connector logic is in a separate module from your main class, you can create integration tests for that module instead.

When your integration tests are in module that doesn't have a main class, then you need to have a class like below in your src/test/java folder to allow Springboot tests to start the application for the integration tests.

Connect SDK Libraries

• Prerequisites
• Manual Deployments
• Stack Provisioned

This module receives consignment updates from Fluent and creates/updates shipments in Adobe Commerce.

Key features:

• Can only be enabled at a global level making it available for all existing websites.
• Adds a new handler to order update webhook (from the order module) to accept and process consignment updates
• Configurable Fluent status that should trigger shipment creation in Adobe. a. It’s possible to have multiple values as long as they are separated by comma.

This process tracks the consignment updates from Fluent and pushes it to commercetools. Fluent use webhooks to achieve this.

Consignment updates are about Shipping and Delivery events and processes. Once fulfilment actions are completed at the Fluent side it would push consignment status to commercetools. On commercetools side, the delivery method should be created once the consignment webhook is triggered and the mapped handler is processed
The consignment entity is mapped to the fulfilment entity on the fluent side.

Control Group represents a collection of controls (buffers/exclusions) for a particular virtual catalogue.

• describes how to set up the user to see the “query” only page or “edit” entity page by using User Roles and UserAction in Manifest.
• The below example demonstrates where "Finance" users in "query" only mode on OMS data and "CustomerService" cancel orders and other user actions.

• Create and update control groups & controls
• Manage control groups and controls

• A step-by-step guide how to convert workflow statuses list into CSV / Excel table format

• Preprocessing Disabled (Skip Enabled): If preprocessing is disabled (set to skip), all event items are passed as is, regardless of changes.
• Preprocessing Enabled: If preprocessing is enabled, only changed items are passed through as events.
• Event Structure: The batch input includes optional fields, and default values are set if they are not provided.
• Event Name: If you specify a custom event name in the batch input, it will be used in the resulting event. If not, the default event name is

  `"InventoryChanged"`

  .

• A step-by-step guide to creating Rule SDK Plugin Project.
• The Rules SDK comes with a Maven Archetype for generating a new Rules Plugin Project, and a handy script file to run the project generation steps.
• A fully setup and functioning Fluent Account is required as of this activity.

• A new Workflow creation requires the correct permissions for the user, and a valid workflow JSON file (schema,

  `entityType`

  and statuses/rulesets).

• Comprehensive Data Entry: Ensure that all necessary customer information is captured accurately to create a complete profile. This includes personal details, contact information, and any specific requirements or preferences.
• Validation and Verification: Implement validation checks to prevent errors during the data entry process. Verify that mandatory fields are not left blank.
• User Experience: Design the customer creation process to be user-friendly. Provide clear instructions and feedback during the process to enhance the user's experience and minimize the likelihood of errors.

• Create Multiple Articles for a Fulfillment

• This tool is a quick easy way to generate manifest List Page by just providing a GQL query (with edges/node)

•  Create retailer batch can get stuck in PENDING status in a few case scenarios (incorrect payload, missing settings...)
• When this occurs, it’s not possible to create any new retailers on the account
• The only way to resolve this is though an SRE ticket

• The Connector SDK generates a blank Maven starting project for your custom integrations.

• A guide on how to set up SCIM Secret Configuration

Cross-Catalogue Views represent displaying of information from cross-catalogue perspective (Virtual Catalogue, Inventory Catalogue, and Control Group).

• To aid with the picking process, Users can download a printable pick list that details the items required to complete the outstanding fulfilments. Customisable via a setting, the custom pick list allows developers to define their own fields and layouts to create a more efficient picking process.
• Enabling the Custom Pick List

This module creates customers in Fluent when an order is created in Adobe and before it is pushed to Fluent.

Key Features:

• Creates a customer when one doesn’t exist in Fluent after an order is placed in Adobe.
• The key identifier of a customer is its username (customer email in Adobe). When a customer is pushed to Fluent, it will carry a prefix of the 

  `retailer ID`

   it belongs to. That means the same 

  `username/email`

   will generate a new customer in Fluent for different 

  `retailers`

  . There is also no distinction between a guest user and a registered user when they are pushed to Fluent. If the same email is used for guest checkout and a registered checkout, both orders will be linked to the same customer in Fluent.
• This is not an integration to keep customers in sync between the two systems. It does not update the customer after it has been created in Fluent. A customer is only created if one doesn’t exist in Fluent when an order is placed. If an existing customer places subsequent orders then this integration will not be executed, meaning no customer updates will be pushed should they exist. The order will use the existing details that are present at Fluent.

Customer Sync is responsible for synchronizing customers from commercetools to Fluent.

Key features

• Automatic detection and synchronization of customers Created/Modified.

Fluent Store's configurable dashboard displays key information about orders and fulfilment and their statuses. It helps in-store staff monitor orders waiting for pick-up and plan the pick-and-pack process, and also provides visibility to retail managers, allowing analysis of performance at a store level. Tiles display fulfilment quantities and their statuses.  For example, a tile may display the total count of fulfilments in 'Awaiting Pick' status (Orders Awaiting Pick) for one day (or more) at a specific location. Tiles are clickable, navigating to a separate page showing data for that tile.

• the best approaches to debugging your custom rules and plugins
• Debugging locally in your IDE can be done as per standard Java practice while running rules in Unit Tests or with the TestExecutor.
• Debugging on Sandbox - The primary mechanism for debugging on a deployed environment is by activity tracking or Orchestration Audit Events. You can easily query these for any context via the Event API, or the Admin Console.

• Lodge shipments with carriers
• Manage carrier parcel pickup
• Validate delivery addresses and coordinates

Delivery Date Range is a feature that enables Fluent Order Management to manage where customers can request a single delivery date range or specify the delivery date range per line item.

• A step-by-step guide to deploy your custom Rules Plugin and run the project.
• A fully setup and functioning Fluent Account is required.
• An API User with the 

  `DEVELOPER`

   role (Note: If using a Training Account, the Account Admin already has this role applied)

• This article providfes you with templates to setup your local environment for developing with the Connect SDK 
• Local development uses a Docker localstack to emulate AWS services.

•  In the current OMX (OMS webapp and STORE), depending on the user’s resolution, it will render the contents to fit within the screen. For some string that are longer than the screen’s width, The OMX will be showing “…" at the suffix.
• To overcome this issue, you can use charCutoff in the manifest. 

• Often you might need to display JSON payload on the Admin Console
• You can use a mustache helper, or you can display individual values with deep references

• Fluent OMS apps support time-zone-specific display of date and time values in the UI.
• It is a good practice to store the date-time value in UTC format and let the OMS UI display the value based on the user's locale.

• step by step to teach you how to add order attribute values into the PACK screen in STORE APP
• the byName function will allow OMS to display the specific attribute value on the UI.

• You can show the Inventory Quantity sum and count in the UI via modifications of the manifest

• `sum`

  and

  `count`

  values are retrieved via custom queries and then displayed in the UI

• A Virtual Catalogue can be created and modified via the UI.
• In order to create a new Virtual Catalogue or to edit the existing one, the user needs to have the right permissions, and the required mutations need to be enabled in the manifest.

• Data Modification: Ensure that users can modify customer data, including the ability to correct typos in existing information.
• Error Handling: Implement error handling procedures in case the edit fails or invalid data is submitted.
• User Experience: Aim for a seamless and intuitive editing process to minimize the risk of user errors.

• enable updateCustomer on the UI via manifest modifications

•  Comments can be added to Fluent OMS web app by modifying the manifest, this article covers the required steps.

• To enable cancelling orders via the UI the cancel order ruleset needs to be used
• Update the mystique manifest to show the list action.

• This document describes how to enable the Chinese language in Fluent OMS webapps.  
• There are 2 Chinese Languages in writing:  Traditional and Simplified.  The Simplified Chinese are mainly used in Mainland China and Traditional Chinese are typically used in Taiwan, Hong Kong and Macau.

• enable Japanese language in OMS via settings modifications

• A Guide for enabling Multi-parcel with ES starter Pack via workflow, settings and manifest modifications.

• 2 main steps to enable order activity view in STORE app. 
  • add OMS plugin to your store fragment,
  • add EVENT_VIEW permission to your location user

• A step-by-step guide to enable phone camera scanning for product picking.
• Configuration
• 
  

• Local Developer Setup
• Fluent Platform Sandbox
• Fluent Platform Production

This section provides Rules SDK reference and guidelines for Writing Rules.

• Extend the Order Module schema
• Modify the Rule for Return Order creation and the Order Workflow Return Order Ruleset
• Update the Order Management Manifest

The Connect SDK offers seamless integration with 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 Connect SDK and outlines the steps to integrate it into your application.

The Fluent Big Inventory Web App simplifies inventory management with key features like the Feeds Dashboard, Products, and Inventory sections. Gain real-time insights into feeds, efficiently manage products, and ensure robust inventory control. Whether tracking sources, managing stores, or accessing comprehensive insights, this app delivers a seamless user experience for optimal business value.

The Fluent CLI provides command line tooling for interacting with Fluent Accounts and Modules.

Usage

The Fluent CLI is activated by typing the keyword

`fluent`

`fluent <command> <subcommand> <argument> [options]`

• The

  `<command>`

  will refer to a noun (or “a thing”).
• The

  `<subcommand>`

  will refer to a verb (or action).
• The

  `<argument>`

  is the primary required name of the “thing” identified by the

  `<command>`

  .
• The

  `[options]`

  may include required or optional additional parameters to be used by the

  `<command>`

  and

  `<subcommand>`

  .

Fluent OMS is a web-based interface, a central application with rich capabilities that deliver value across many different user journeys, use cases, and business operations. This module provides the interface to manage orders, product availability, inventory, and order fulfillment. Businesses and Administrators use Fluent OMS to access an extensive range of functionality provided by the following Fluent Commerce modules:

• Order Orchestration 
• Inventory 
• Availability 

Each module provides the out-of-the-box capabilities that the Fluent OMS accesses.

• The article offers a step-by-step configuration for setting up Fluent OMS session timeout specifically tailored for Single Sign-On (SSO) users.
• It focuses on configuring session timeout within Fluent OMS while utilizing Azure as the external Identity Provider (IDP).

• Guide for a user to add an order list page into Fluent Store.

Fluent Store is an in-store responsive web application that provides Store staff with end to end order management capabilities.

• A Client Business Requirement:
  • The returnOrder created by Store Staff must require a Manager’s Approval
  • 2-step process to ensure the customer is refunding the right products/amount. This is done through workflow and roles/permissions modifications.

•  A typical scenario where the EAN 13 barcode (e.g.,

  `0123456789123`

  ) and sometimes the barcode on the physical product might not include the leading 0. So when the product gets scanned, it will return

  `123456789123`

  rather than

  `0123456789123`

  , and the Pick screen will not be able to find the product from the pick list.
• We can utilize product attributes to include possible barcodes and to include fields.

• A simple way to add user action to capture driver name and vehicle number in the carrier collection process.

The Fulfillment module allows Adobe Commerce to receive Fulfilment updates from Fluent and track these details against each order line.

Key Features:

• Adds a new handler to the order update webhook (from the order module) to accept and process fulfilment updates.
• Currently only tracks the details at each order line. Does not drive any behavior in Adobe like status changes or updates to orders or shipments.

• Manage stock throughout an orders lifecycle
• Manage stock discrepancy
• Free up stock when orders are cancelled

Fulfilment updates are done at the Order Item level. Where each item can have a specific fulfilment status or multiple items can have the same fulfilment status.

• Overview
• Prerequisites
• Installation
• Next Steps

The Rules SDK is a Java based software development kit, which provides Java developers with a toolkit for creating custom Rules for the Fluent OMX Workflow Framework.

The Workflow Framework is a highly configurable and extendable part of the Fluent OMX Platform, which facilitates orchestration of business logic for the Fluent Order Management System.

• Collection of GraphQL samples handy for accessing Fluent OMS

• Quick Example of how to use GraphQL mutation

  `removeUserRolesFromUser`

• How to customise a Pick List

• A step-by-step guide on how to add a custom help menu to the header to serve as inspiration for other custom components that can be added

Don't hesitate to reach out if you feel stuck or are unsure what best practices apply for your setup. 

•  OOTB, the create wave button on Fluent Store will always be displayed whether there are pending fulfilments or not.
• It’s possible to only display the button when there are pending waves when a condition is added.

• A Comment provides an additional piece of information to the entity it is related to. 
• An Order can contain multiple comments associated with it.

• Understanding the default Order and Fulfilment Types
• Users with SETTING_VIEW, SETTING_CREATE, and SETTING_UPDATE permissions can add new order and fulfilment types to Fluent Store.
• A guide to add a new Order Type to customise the Fluent Store
• A guide to adding a new Fulfilment Type to customise the Fluent Store

• Custom Service Personnel have an ability to appease a customer in certain situations by providing a refund for an existing customer order. 
• This functionality is available via OMS for orders of all types in all statuses.

• This guide shows you how to assign an article to a Storage Area as part of the Scan to Storage Area feature of the baseline Fluent Store web app
• Prerequisites
• Step-by-step guide

• Customer Service Personnel can change the home delivery (HD) addresses for HD orders. 
• This functionality is available via Fluent OMS for HD orders PENDING_PAYMENT, BOOKED, CREATED, PICK_PACK statuses.

• Drawers can be added in any mystique components by modifying the mystique manifest.
• The drawer’s custom data source can be defined via queries and variables.

• This article describes how to configure complex calculation in Manifest
• Target audience: Architect, Partner Developer, Partner BA.

• The Shipment clock section in Order item Details is not shown by default. This functionality can be turned on via a setting.  

• Session timeout for Fluent OMS can be configured for SSO users without external IDPs via Ping Identity.
• In order to configure the timeout, you would need to configure Access token time to live and the authentication policy on Ping Identity.

• Configure Fluent OMS session timeout for SSO users with external IDPs (Okta)

• It is possible to use the generic SAML configuration to add an external identity provider that follows the SAML standard
• This page provides a guide on how to configure an external identity provider via SAML configuration.

• Register application with Okta
• Add the identity provider in PingOne
• Add Metadata URL
• Continue IDP Configuration
• Do not forget

• Fluent OMS can display the order list in two ways: Compressed and Standard.
• The manifest needs to be modified in order to enable the compressed view.

• You will understand how to configure workflows to adjust delivery dates for processing orders to suit your business needs.
• You will learn about the necessary settings and their functionalities. 

•  Mixed basket functionality is not covered in Fluent's base default pre-configurations. 
• In order to enable mixed basket functionality on the UI, you would need to modify the manifest and add a few settings. The process is explained in detail in this article. 

• The Fluent Big Inventory Web app is pre-configured with certain standard functions. 
• The IPU and IPC reports functionality is not a part of the default configuration. 
• This guide will enable users to configure the web app to display the IPU/IPC reports.

• The Pack Slip on Fluent Store can be customised via an HTML template.
• This guide will take you through the setup and fragment changes required to customise the Pack Slip.

• A Product Catalogue can be created and modified via the UI.
• To create a new Product Catalogue or to edit the existing one, the user needs to have the right permissions, and the required mutations need to be enabled in the manifest.

• An Inventory Catalogue can be created and edited via the UI.
• To create a new Inventory Catalogue or edit an existing one, the user needs to have the right permissions, and the required mutations need to be enabled in the manifest.

• When creating or editing roles, ensure to define permissions accurately to maintain system security.
• Follow the best practices for naming conventions and role descriptions for easier management and clarity.
• Test role changes in a controlled environment before applying them to the live system to avoid unintended access issues.

• It’s possible to enhance Service Point to show order items from the current order on the collection screen.
• This can be achieved by adding a specific setting and making sure that the user’s role has the appropriate permissions.

• Control groups can be created and modified via the UI.
• In order to create or modify Control Groups, the user needs to have the correct permissions.

• A dynamic total Refund Summary can be configured into the Returns Wizard, on both Fluent Store and Fluent OMS.
• In order to configure the returns summary, to would need to enable to returns workflow, add the appropriate setting and modify the manifest.

• Working with barcodes

• Inventory Batch Pre-Processing (BPP) occurs before batch inventory updates reach the workflow engine. If you rely on every incoming inventory item hitting the workflow, ensure you configure the job-level meta value appropriately or disable BPP at the relevant account/retailer level. However, we recommend using the job-level option for greater flexibility. Be sure to read through this article in full—especially the “Managing Batch Pre-Processing” section—before making any changes.
• If enabled at an ACCOUNT level, every retailer under that ACCOUNT will have their batch inventory updates pre-processed
• If enabled at RETAILER levels, it will only pre-process updates for that specific retailer
• The RETAILER context setting overrides the ACCOUNT context setting. This allows you to enable the whole account and disable it for specific retailers. 

• This document serves as a practical hands-on guide to enable Multi-Parcel in your account. 
• It is recommended to be used alongside the Multi-Parcel field document.

• A practical hands on guide to enable Multi-Parcel in your account. It is recommended to be used alongside the Multi-Parcel field document.
• Articles are now called Parcels.
• This guide is aimed at technical implementors who are looking to enable In-Store Associates to capture multiple parcels per fulfilment.
• Step-by-step setup multi parcel feature in Fluent Store.

• Verify Compatibility: Ensure your existing account meets all prerequisites for enabling Fluent Store.
• Follow Step-by-Step Guide: Adhere to the provided instructions to enable Fluent Store on your account seamlessly.
• Utilize Support Resources: Refer to the official documentation and support channels for any issues or queries.

• Location context switcher allows you to switch the location without having to log off and back in with the specific credentials. This is feasible as long as the user permissions are configured accordingly. 
• The context switcher requires a few manifest modifications, which are detailed in the article below. 

• Overview
• Who is this guide for?
• Steps to enable navigation bar badges with an example

• Retailer context switcher allows you to switch the retailer without having to log off and back in with the specific credentials. This is feasible as long as the user permissions are configured accordingly. 
• The context switcher requires a few manifest modifications, which are detailed in the article below. 

• Properties of CUSTOM_PICK_LIST_SORT_CONFIG Setting

• To enable the storage scanning feature in Service Point the following setup and workflow changes are required

• Enabling scan to storage area is only possible on Fluent store (not on Service Point).
• This guide will take you through the setup and workflow changes required to enable the Storage Area Scanning feature in Fluent Store.

• Target audience: Configurers or Fluent Partners.
• The guide explains how to successfully configure the status filter with predefined values.

• steps on how to install modules into your OMS sandbox

• The new print component enables faster printing and additional features.
• You can update to the new print component by updating the component name and adding the relevant configuration.

• The UX Framework in the Fluent platform automatically checks for configured manifests in Account settings. If none exist, the Fluent web app defaults to loading using baseline manifests within the platform, ensuring a seamless and standardized user experience.
• To customize the main web app manifest or specific fragments, users should follow the naming convention, with the setting name for the main web app manifest file.
• It is recommended to override the main manifest only when adding or removing fragments; otherwise, users can efficiently modify specific fragments by overriding them individually.

• This page helps to understand the new functionality that helps users to change own password during the authentication process.
• This is only applicable to users who doesn't use corporate identity to login into Fluent OMX. 
• If you use corporate identity to log into Fluent, please contact internal IT team or administrator and follow internal process for changing password.

• Selecting fulfilments to add to a wave and create wave
• Generating standard or custom pick list
• (Optional) Scanning items to pick via the ENFORCE_BARCODE_SCAN setting.

• In the default reference mystique manifest, a store user can log in to OMS web apps, and sometimes, the user can see other location data within the OMS web apps.  
• One way to solve this issue is to introduce the “

  `role`

  ” in the

  `fc.mystique.manifest.oms`

  context.

• Step-by-step configuration guide to enable Returns functionality in ServicePoint.
• The configurations include the following:
  • User Role assignments
  • Settings
  • workflows

• Order Revision User Guide

• A setting can be modified directly on Fluent OMS UI.

• A setting can be added or modified directly via UI.
• A new setting requires its name, context, the identifier of the context, the value, and the value type.

• This guide shows you how to seamlessly switch Retailers within the Fluent Order Management System web app.
• This guide is aimed at multi-retailer Admin users.

• This guide shows you how to seamlessly switch Store Locations within the Fluent Store web app
• This guide is aimed at In-Store users

Direct Inventory Updates are one of the two reference ways to send last-on-hand inventory updates into your inventory workflows. Direct Inventory Updates are best used when you have a small volume of inventory updates (maximum of 1000 updates).

• Example on how to use fragments in GQL

A topic on how to run Inventory batches in the OMS. 

Delta Inventory updates are incremental inventory updates used to create relative updates against Inventory positions. These are used to notify the OMS of offline stock movements that have occurred during the day.

• A user can be created and modified via UI.
• The user creation requires the associated Location, Retailer, Role, and Context. It’s also possible to add extra attributes.
• It’s only possible to ADD roles to the user on the UI. Removing roles is not feasible from the UI.

• A user can be edited directly on the Fluent OMS UI.
• It’s only possible to ADD roles to the user on the UI. Removing roles is not feasible from the UI.

• This guide is about displaying HTTP(S) links in Admin Console.
• This can be achieved through a Mystique configuration.
• Store a HTTP(S) link to a document e.g. packing slip as an attribute against an entity.
• Display the attribute as a clickable link in the Admin Console.

• Converting JSON Introspection to SDL allows for a human-readable format of GraphQL schema, which is essential for documentation and understanding the API structure.
• Tools such as GraphQL Voyager and Apollo Studio can automate the conversion process, providing a visual representation and SDL output without manual coding.
• Understanding the structure of the introspection query result is crucial for manually converting the JSON to SDL, should automated tools not be available or suitable.

• Open Postman, click Import, then choose "Upload Files" in the dialog box.
• Upload the GraphQL SDL File named

  `fluent-graphql.graphql`

  .
• Confirm settings, including "Include deprecated fields," and click Import; a success message confirms installation in the APIs tab.

• Prerequisites
• Steps to Follow

• Prerequisites
• Steps to Follow

• To Introspect the Fluent GraphQL schema, run an Introspection Query against the Fluent GraphQL API Endpoint. Below is the raw GraphQL Introspection Query.

• This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
• This idea/solution will provide a new feature where the Store User can take a photo of the returning item and attach it as part of the returnOrder entity.
• The source code will not be provided in this article.

In-store Fulfilment features to support fulfilment process

• step-by-step guide on how to install modules into your OMS sandbox

• Update multiple Inventory Positions at once
• Updating of the inventory records to reflect the latest stock count

While the majority of inventory management may happen through integrations and business rules. The Fluent OMS provides a high-level view of inventory.

Users need to have sufficient permissions to view the inventory module in the OMS.

The Inventory module is responsible for aggregate stock synchronization between Fluent and Adobe Commerce. The main purpose of this module is to keep Adobe Commerce Inventory up to date.

• Detect Inventory problems or anomalies with the Total Failures card on the Sources Dashboard.
• Identify the specific failure events with advanced filtering on the Events page. 
• Understand the what, where, and why of the event failure by using the Event Details Drawer.

Fluent's Global Inventory app meets customer expectations by aggregating product data, defining visibility rules, and efficiently allocating inventory. It enables precise retrieval of granular information and ensures accurate identification of available-to-promise levels while implementing inventory buffers to prevent overselling, enhancing the overall customer experience.

• The SDK allows to import data into Fluent OMS via batch jobs.
• The data can be stored in an Amazon S3 bucket and imported into Fluent OMS via API. 
• The inventory job handler requires various settings that need to be defined in the account’s settings list ( location-pattern, archive-folder... )

This article covers the key components of Fluent Order Management and how these are used to build out and browse the platform's documentation.

The Adobe Commerce Connector provides a swift, configuration-based integration that instantly enables all essential features you can expect from a modern OMS. 

The key features provided by the commercetools Connector, required to make the commercetools and Fluent integration valuable to clients, partners, and developers, include:

• Local development uses localstack to emulate AWS services
• AWS CLI Configuration is optional
• IntelliJ and Eclipse / STS  Setup in local environment

Location Inventory Views represent inventory from a location perspective. The Location Inventory Views page displays the list of locations.

A Location is any place where an order can be fulfilled and/or collected by the customer. Locations can include a physical store, warehouse, drop ship vendor, lockers or third-party collection points. Locations will be synced from Fluent to commercetools. The existing entity in commercetools for Fluent location is Channel.

• In the fluent platform, a log action allows to generate a specific log event when a rule executes. 

• Create orders
• Perform fraud checks 
• Manage order revisions, appeasements, and cancellations 

• The Fluent platform allows sending events with a workflow "attached" in the meta section of the event. This means that Rubix will execute the rulesets and rules which have been passed through as part of the event. This is especially useful to manually execute particular rules on an entity and is mostly used for operational purposes.

• This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
• This idea/solution will provide a new feature where the Store User can enter the rejection reason code during the Pick Confirm Process.
• This feature allows customer service to reroute an existing

  `fulfilment`

  to a specific location that can fulfill the order.

• This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
• This idea/solution will provide an extended new feature where the Store User can update the Store inventory through the UI to ensure the OMS has the most accurate product inventory.
• New custom UI component and rules to capture the user input in the UI user Action screen. Then, the backend will create a new Inventory Quantity entity and update the Inventory Position and the downstream workflow.

A centralised inventory management approach that simplifies integration, enhances visibility, and enables flexible fulfilment across regions, making cross-border operations efficient and scalable.

• Describe the steps to create a new module with a custom plugin
• TL;DR from module creation to installation:
• Create:

  `fluent module create`

• Update

  `resources/module.json`

  with the module's version, dependencies and module name
• Add in the source code + unit and integration tests under the

  `plugins/`

  folder

• Describe the steps to create a new Data Module
• Use B2C Sample data for reference
• Build and Install the Extension Data Module

• Create the new module:

  `fluent module create -n <module-name> `

• Populate the plugin structure in

  `plugins/`

  
    

  `rules/`

  - Contains rules, unit tests and GraphQL queries/mutations
    

  `types/`

  - Stores model classes and extended DTOs
    

  `util/`

  - Holds service classes and utilities
• Build the module:  

  `./scripts/build-module.sh`

• Install the module:

  `fluent module install dist/<module-name>-<version>.zip -p <profile> -r <retailer>`

• In order to enable MFA, you need to log into pingOne to make sure that MFA is enabled for Fluent App and for the logged user.
• You would then need to log in the system via Fluent’s self service link.
• Once this has been completed, a new authentication method needs to be added on Ping Identity.

Multiple Delivery Addresses is a feature that enables Fluent Order Management to manage an order with items delivered to different addresses.

Multiple Delivery Methods is a functionality in Fluent Order Management that enables the management of orders containing line items delivered through multiple delivery methods.

Multiple Pickup Locations is a feature that enables Fluent Order Management to manage orders with specified pickup locations by line item.

• This is an enhanced feature that allows users (e.g., Customer Service Representatives) to look up customer orders by using either the customer's email address or phone number. 
• This feature can be achieved by configuration in the setting manifest without any custom components nor custom rules.
• This article will provide the following:
  • code snippet of the search Order by Customer phone/email manifest
  • Language settings
  • Display the page on the left panel menu by adding a code snippet in the setting:

    `fc.mystique.manifest.oms`

     

There are numerous ways of monitoring the Fluent platform and its functionality. We can distinguish between different types of monitoring, such as business or technical monitoring.

The Order module is responsible for exporting orders to Fluent and receiving order updates.

Key Features:

• Triggers customer export when an order is placed.
• Exports new orders to Fluent.
• Opens a webhook to receive Fluent order-related updates. Other extensions like fulfillment and consignment will leverage this webhook.
• Updates order status based on Fluent updates.
• Creates shipments for all order items based on an incoming order status update. Note that this will blindly mark all items as shipped regardless of how they have been consigned at Fluent.
• This is disabled by default in favour of the consignment module that creates shipments based on how items are actually consigned and shipped at Fluent.

Limitations:

• Does not sync old orders created before the extension is installed.
• If the order sync is temporarily disabled, it will not sync orders placed while it has been disabled once it is re-enabled.

The Order Module delivers full order management capabilities for advanced omnichannel sourcing and fulfilment strategies. The Order Module allows Retailers to orchestrate Order sourcing and fulfilment from multiple sources across their networks, resulting in cost optimisation and enhanced customer experience.

• Order Revision implementation can be done either from the UI or via Postman.
• This implementation requires workflow changes and adding a few specific settings. The detailed process is covered in this article.

This process tracks the order updates from Fluent and pushes it to commercetools. Fluent use webhooks to achieve this. Webhook processing happens in 2 stages.

The Order Sync is responsible for exporting orders from commercetools to Fluent and receiving order updates.

This is a quick reference of the most important Account and Payment Settings.

• Predefined Filters: Provide a way to access commonly used search parameters with a single click, enhancing the user experience.
• User Efficiency: Predefined filters are designed to save time and streamline workflows.
• Customization: Users may have the ability to create and save their own filters for recurrent use (via manual Manifest changing).
• Consistency: Predefined filters ensure that the same criteria are used for searching, leading to consistent results.
• Learning Curve: New users can quickly become proficient in finding the information they need due to the intuitive nature of predefined filters.
• Integration: These features should seamlessly integrate with the user interface for maximum effectiveness.

• a trick on how to print the current list page to the printer

The Product Module is responsible for synchronizing products from Adobe Commerce to Fluent.

Key features:

• Manually synchronize the entire product catalog at any time.
• Automatic detection and synchronization of modified products.
• Multi-retailer / multi-website configuration support.
• Current product type support is limited to the following: Simple and Configurable.

The Product Catalogues configuration contains:

• Products Catalogues – Retailer List page
• Products Catalogues List page
• Product Catalogue Details page

• Create and update products and their categories
• Manage product variants

Product Sync is responsible for synchronizing products from commercetools to the Fluent OMS app.

Learn how to effectively plan and execute Fluent OMS projects and apply similar steps to your projects.  Also, discover our recommended practices, key project milestones and overall guidelines.

Read this document to learn:

• How to run discovery workshops
• How to perform gap analysis and estimation, solution delivery, and launch readiness processes.
• Project roles and responsibilities

• You can configure provisioning function for Fluent OMS in Azure Active Directory.
• You would first need to have access to Microsoft Azure Portal to update the credentials and map the relevant attributes. Next step is triggering the start/stop provisioning form the portal. 

• Quick Search Functionality: Enables users to find information rapidly by typing keywords or phrases.
• User Efficiency: Quick search is designed to save time and streamline workflows.
• Learning Curve: New users can quickly become proficient in finding the information they need due to the intuitive nature of quick search.
• Integration: These features should seamlessly integrate with the user interface for maximum effectiveness.

This feature enables partners to receive updates through webhook from a 3rd party system to the connector to be processed further

Developers can add new components to OMX via the registries.

There are three available:

• Component Registry - for standard in-page components
• Field Registry - for interactive form field components
• Template Registry - for adding new template helpers

• This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
• This idea/solution will provide a new feature where the Store User can enter the rejection reason code during the Pick Confirm Process.
• This feature allows specifying the rejection reason for fulfillment on the picking step of wave processing. The user can select the rejection reason code when the picked item list is confirmed as the first step of wave processing.

• The below example demonstrates how the visibility of the CREATE WAVE button in Fluent STORE can be customised via roles, permissions, and the manifest.

The Returns feature in the Fluent Store Web App provides the ability for in-store associates to process Customer Returns for orders within the Fluent ecosystem.

• When an enterprise application needs to be configured in Azure, App roles need to be added on Azure Active Directory, and dynamic roles need to be set up on Fluent OMS.
• it’s possible to manage the roles individually or via Group management on Microsoft Entra.

Rules are written using Java, and contain a specific structure and metadata for describing and validating the Rule. Rules are designed to be building blocks for workflow logic, and typically produce a single outcome or action. The Rules SDK also provides a number of built-in dependencies for implementing Rules, including working with GraphQL and other Utilities.

• Create and manage available to sell stock per channel
• Manage safety stock

• The Salesforce Service Cloud (SFSC) connector can be downloaded on Salesforce marketplace (Appexchange).
• In order to launch the connector: A SFSC administrator would need to download the Fluent OMS app from Salesforce App Exchange and deploy it within the SF organisation. API configurations and settings would then need to be added on Fluent OMS app to complete the set up.

• Provisioning a user
• App Role Convention
• Scenarios

• The SCIM connector is a Java based project that enables seamless integration with the SCIM. In order to install the SCIM Connector, you’d need to make sure you have the right dockers and tools. Next step is setting up the local environment, configuring the connector, and finally deploying the connector.
• The SCIM connector and connect SDK versions need to be aligned.

• The overview of the SCIM Connector Setup and Configuration

• Local development uses localstack to emulate AWS services
• AWS CLI Configuration is optional
• IntelliJ and Eclipse / STS  Setup in local environment

This feature enables partners to send payloads to external systems via webhook .

Customer service capabilities allow customer care staff to understand and respond to how consumers think, act, and engage. Fluent Commerce supports all the necessary processes to enable flexible customer support, engage customers from one end of the buying journey to the other, and deepen customer relationships.

• Settings Template

• Create a profile
• Create a retailer
• Install the Fluent Reference Modules
• Install B2C Sample Data modules
• Validate the Account set up

• Step-by-step guide to setup Rule SDK in your local Environment. 

• This guide covers the common symptoms and associated steps to debug issues with the ShippIt Connector.
• In most cases, if there is an issue, the most likely symptom is if Fluent Store shows the consignment entity status as FAILED.

• Request a delivery date for all items in your order.
• Request a pickup date for all items in your order.

• Source items to fulfil an order from one or more locations
• Set a split limit for the number of locations that can fulfil an order 
• Reallocate short-picked items to another location 

• This guide covers setting up an SSO connection between PingOne and Google Workspace using SAML.
• Ensure you have admin access in PingOne and a Google Workspace account with an active subscription.
• You need to register the application in Google Workspace to configure it as an external identity provider.

• In order to configure the SSO, you would need to first sign the DPA, define the number of required SSO users, and raise a support ticket.
• Second step is to configure your company IDP in Ping Identity.
• Third step is to test to test to make sure that the user can log in.

• This guide will walk you through configuring the main sections of the Pack Wizard: Unpacked Items, Packed Items, Rejected Items, and the scanner, enabling you to tailor it to your specific requirements.
• The default configuration does not include a list of parcel types with predefined dimensions. It only displays basic details of the items being packed (such as image, product name, and reference) and allows users to select from four predefined reasons for rejecting items.

The Store Locator Module is responsible for synchronizing locations from Fluent to Adobe Commerce.

Key features:

• Manually synchronize all locations at any time.
• Manually synchronize locations by updated date at any time.
• Background synchronization of recently modified locations.
• Multi-retailer / multi-website configuration support.

The Store Module brings Order Management capabilities to the in store experience. The Store Module allows Retailers to turn their existing Stores into fulfilment and distribution centers, and optimise costs while delivering an improved customer experience.

• how to use Computer Chrome Browser to view Phone / Tablet layout
• A handy way to test the layout on your computer without using an actual phone 

The Rule Interface defines a class as a Workflow Framework compatible executable Rule.

• This component simplifies the addition of networks to locations by providing an easy to use selector of available networks
• The basic principles can be used in other scenarios where complex fields and values may be required

• Create new Inventory Batches using the Job API 
• Sample Inventory batch payload 
• Inventory batch details

• After following this guide a user will be able to create a new Inventory Feed
• The output from this feed can be used to supply inventory availability data to any system
• Additional steps will outline optional configuration that can be applied to Inventory Feeds

• This guide explains how to enable Store Associates to select Fulfillments to add to a Wave in Fluent Store. 
• Once this capability is enabled in Fluent Store, Store Associates can filter and select Fulfilments (including by custom attributes) to be added to a new Wave.
• This guide will require knowledge of how to configure your manifest and workflow. If you wish to extend this functionality even further, you'll need to be able to compose rules.

• The Pack Slips can be customized using an HTML template.
• This guide outlines the setup and fragment modifications required for generated PDF customization.

• After following this guide a user will be able to update an existing Inventory Feed
• Various updates are available once an Inventory Feed has been created and started running

• Overview
• Configuring the Dashboard
• User Role and Permission
• Understanding Dashboard View
• Customization Example

• This section will detail a few common issues and troubleshooting options for Inventory Feeds.

• Inventory Feed runs can be individually tracked for their status and data about the run
• A user will know how to analyse Inventory Feed Runs from this guide

• An easy step-by-step guide on how to add a new ruleset to update fulfilmentChoice status.
• This example can be used on the MULTI order type (mixed basket) workflow.

• A step-by-step guide to update your plugin Project for SDK 17+

• A Workflow can be updated as long as the user has the right permissions.
• A Workflow can be updated via the IMPORT/EXPORT button or via API.

• Upgrade an Existing Plugin to the latest SDK

In this article you will learn about the Users configuration and components:

• Users page: To show you how to view all users, set permissions for different users 
• User Details page: To show you how to view user details, including status, roles and types. 

• The

  `tag1`

  ,

  `tag2`

  , and

  `tag3`

  filters allow users to filter orders based on an exact match of the entered value.
• These filters can be configured to use predefined values instead of a text input field that is available out of the box, enhancing usability and consistency.

The UX framework provides some "component primitives" that can be used to build more complex components on top. The advantage of this is that these utility components:

• provide a consistent look and feel
• update according to theme options
• enable mobile responsiveness

• This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
• This idea/solution will provide an extended new feature where the Store User can validate the Customer ID during the Customer Collection Process.
• New custom UI components and rules are needed to capture the user input and confirm the selected articles in the UI user Action screen.  Then, the store/business can track and trace the proof of the shopper's collection.
• Due to security reasons, the shopper's sensitive personal information should not be stored within Fluent OMS. Therefore, the proof of collection should be stored at a third-party storage.

This pages shows you how to navigate the Virtual catalog and understand the correlation with other related inventory entities. 

Admin section helps in managing users, carriers, and retailers and contains the following configurations.

Dive into suggetsed articles covering the basics of the Fluent Commerce OMS platform. 

Fluent Commerce is a flexible platform with two core components: the UX component for rendering UI and the Workflow Framework responsible for order processes. The platform comes with a range of SDKs for custom development and a set of reference modules.

The GraphQL Plugin for IntelliJ provides useful features for working with GraphQL:

• Schema Introspection
• Auto-complete
• Syntax highlighting and validation
• Query and Mutation execution

• A step-by-Step guide to creating your first custom Rule to log "Hello World"