Learn About Workflows
Essential workflow knowledge
Webhook Retries and Inline Events
Essential knowledgeCore knowledge to understand Fluent CommerceThis page explains how the Orchestration Engine retries a webhook that is reached through inline events, and helps you decide which value of `fc.rubix.webhook.retry.event` to use for your account.It describes how each workflow pattern is affected, what each value does, and what to check before you change the setting.- Prerequisites: Webhooks, Inline Event, Understanding Event Execution
- A webhook action is retried only when its request fails with a network error, such as a timeout. This happens most often when the receiving system is under load, for example during peak trading
- With
`webhook-event`, the retry uses the webhook event, which is the event that triggered the ruleset in which the webhook action was produced:- The retry is posted to the same endpoint with the same event as the original call
- If the receiving system responds, with any HTTP status code, the retry counts as delivered and retries stop
- If all retries fail, the Exception event is raised for the ruleset and entity of the webhook event
- With
`initial-event`, the retry uses the initial event, which is the event that started the event context:- The retry is posted to the same endpoint, but with the initial event, so the event name, the entity, and the attributes can differ from the original call
- If the receiving system responds, with any HTTP status code, the retry counts as delivered and retries stop. The original call isn’t sent again, and the Send Webhook audit event shows
`SUCCESS`, so the failure goes unnoticed - If all retries fail, the Exception event is raised for the ruleset and entity of the initial event, not for the ruleset of the webhook event
- The values differ only when the webhook event is an inline event. When the webhook action is produced in the ruleset triggered by the initial event, both values give the same retry
- Accounts created before the setting was introduced keep
`initial-event` until you change it. Accounts created since then use `webhook-event`. Check your workflows with this page, then switch to `webhook-event` - For custom webhook rules and the reference
`SendWebhook` rule, also add `preserve-event-details` to the workflow, so the retry reruns the rule that produced the webhook action. Without it, the retry is sent by the built-in platform webhook rule. See `fc.rubix.sdk.webhook.retry.method`.
Synchronous vs. Asynchronous Integration with Fluent Order Management
Essential knowledgeCore knowledge to understand Fluent CommerceFluent’s platform philosophy and integration guidance applies to payment, fulfillment, invoicing, WMS, ERP, and other external systems. Fluent OMS is intentionally asynchronous and event driven to support scalability, reliability, and stable workflow processing. Synchronous calls should occur in a separate integration or middleware layer, which handles the external response and sends the outcome back to Fluent as an event. This prevents delays, timeouts, duplicate actions, and stuck orders while keeping each system within its intended role.- Fluent OMS is an eventdriven, asynchronous platform designed for scalable, stable and reliable integrations.
- Fluent’s workflow engine does not support blocking synchronous calls to external systems such as payment providers, WMS or ERP platforms.
- Synchronous integrations are still possible, but must be managed through an external integration or middleware layer alongside Fluent.
Responsive Sourcing Framework Overview
Essential knowledgeCore knowledge to understand Fluent CommerceThe Responsive Sourcing Framework is a configurable, scalable alternative to custom Workflows and Rules for managing sourcing strategies. You’ll learn how to define and optimize sourcing logic using Sourcing Profiles, Strategies, Conditions, and Criteria. The Framework empowers both technical and business users with faster implementation, greater control, and transparency into how sourcing decisions are made and why.- Prerequisites: You should have knowledge of Order Management and Order lifecycle, Order Reference Module, and GraphQL API
- The Responsive Sourcing Framework is designed for both technical and business users - logic is transparent and comes with a configurable User Experience (UX)
- Enables faster implementation by reusing modular sourcing logic building blocks such as Sourcing Profiles, Strategies, Conditions, and Criteria
- Sourcing Profile GraphQL API is required to correctly set up your sourcing logic
- Supports custom Sourcing Conditions and Criteria through externally developed extensions for advanced or domain-specific logic
ICP, Qualification Criteria and Additional Use Cases
Essential knowledgeCore knowledge to understand Fluent CommerceThe article provides a comprehensive guide to identifying the Ideal Customer Profile (ICP) for an Order Management System (OMS), highlighting key criteria and red flags to ensure successful implementation. It also explores Fluent OMS use cases, showcasing its capabilities in order capture, fulfillment, tracking, promising, shipping, and inventory management.- Ideal Customer Profile (ICP) based on specific industries, company maturity, and high order volumes
- Poor fit indicators, such as outdated legacy infrastructure or a lack of executive buy in
- Fast Qualification Framework to rapidly assess a prospect's Budget, Systems, Volume, and Channels.
Workflow Framework Overview
Essential knowledgeCore knowledge to understand Fluent CommerceThe Workflow Engine (aka Rubix) is the engine that drives the Fluent platform. The Workflow Engine enables business process orchestration, workflow automation, and underpins the specific feature sets and functionality for each of the Fluent apps. Additionally, the Workflow Engine is built to be highly scalable, and provide high-performance workflow execution across any domain.- Cloud-native, high availability, scale-on-demand workflow execution.
- Pre-built, customizable workflows delivering capabilities across each of the Fluent App domains.
- Rich Rule Library containing reusable rules across each of the Fluent Apps.
- Software Development Kit (SDK) and Developer Tooling, enabling the implementation of custom rules and integrations.
- Business Tools to manage, configure, and implement workflow and process automation.
A collection of links to get started with your Fluent OMS journey.
Essential knowledgeCore knowledge to understand Fluent CommerceFluent Commerce is a flexible, cloud-native distributed order management system (OMS) designed to help retailers manage inventory, orders, fulfillment, and customer experience more efficiently. This guide outlines the key resources and steps to get you started.- Fluent Commerce is a cloud-native OMS designed to optimize inventory, orders, and fulfillment for retailers.
- Key resources include Core Concepts, Fluent CLI, API integration, workflows, and environment setup.
- Training and certification are available to enhance expertise in Fluent Commerce.