Fluent Commerce Logo
Docs

RFP Essential Knowledge: Returns and Refunds

Essential knowledgeCore knowledge to understand Fluent Commerce

Author:

Michael Wholohan

Changed on:

29 May 2026

Overview

Fluent Order Management provides comprehensive return and refund capabilities, including return order creation, inventory adjustment, refund workflow configuration, and configurable reason codes. Returns can be initiated via Fluent Store (in-store), the Fluent OMS, or via API — enabling omnichannel return journeys.

Key points

  • Intended Audience: Business User, Customer Service Representative, Implementation Partner
  • Classification: Returns and Refunds

Return Processing

Return orders can be created through multiple channels:

Channel:
  • In-store - via Fluent Store Application
  • Customer service - Admin Console UI 
  • Third-party or headless - via API
Key return processing capabilities:
  • Return orders are linked to original orders and order items via a `returnableQty` field. The calculation and definition of eligible return quantities is configurable to meet client-specific rules (e.g. return window, item condition).
  • Inventory is updated in real time upon return receipt — Fluent differentiates between sellable and non-sellable returns, updating inventory buckets accordingly.
  • When returns are received via WMS, Fluent automatically adjusts on-hand inventory for the relevant SKU and location.
  • Return shipment tracking is supported via third-party carrier integration.
  • Shipping label generation for returns is supported via integration with carrier APIs or third-party label generation services, with custom workflows triggering label creation and automatic email to the customer.
  • Finance systems can be provided with return transaction data for reconciliation, including differentiation between sales and return transactions at the invoice level.

Non-returnable items: Clients can define which products are returnable or non-returnable within the orchestration engine. Rule exceptions using product attribution can override non-returnable status in specific scenarios.


Refund Management

Fluent provides configurable payment settlement and refund workflows, with direct integration to payment service providers (PSPs).

Payment configuration:
  • Payment methods and providers can be defined at both global and retailer level.
  • Workflow logic controls when and how payments are settled and refunds issued.
  • An event (purchase, shipment, cancellation) can be configured to trigger a call to the integrated payment provider for authorisation, capture, or refund.
Re-authorisation: Fluent can store a payment token representing an authorisation, enabling future re-authorisation, capture, or refund calls to the PSP. This is used when the original authorisation has expired by the time of fulfilment.

Partial and selective refunds:
  • Selective voiding based on specific line items within an order is supported.
  • Refund invoices are generated by the third-party invoicing system, with Fluent passing relevant product and order details following the return event.
PSP integrations: Fluent connects to PSPs including Adyen and CyberSource via API and webhooks. Additional PSP integrations are available through the iPaaS partnership programme.

Payment gift cards: Physical and virtual gift card authorisation and capture at order creation or modification are supported. Gift card balance tracking is managed as a financial transaction linked to the order.

Reason Codes

Reason codes are a configurable component of Fluent's return, cancellation, inventory adjustment, and appeasement workflows.
  • Custom reason codes can be created and managed within the platform configuration.
  • Reason codes are supported for: cancellations, short picks, inventory adjustments, appeasements, and return reasons.
  • Appeasements capture the user ID of the initiating agent, the amount, the reason code, and a timestamp — all logged in the order's audit trail for compliance and reporting.
  • Appeasement tracking enables pattern analysis of agent-applied goodwill gestures (amount, reason, frequency).

Configurable changes: Most reason code updates, email trigger frequency changes, backorder rescheduling, and node-level settings can be implemented quickly through configuration rather than custom development. Only complex, custom functional features require additional coding or extensions.