Fluent Commerce Logo
Docs

RFP Essential Knowledge: Architecture and Technical

Essential knowledgeCore knowledge to understand Fluent Commerce

Author:

Michael Wholohan

Changed on:

29 May 2026

Overview

Fluent Commerce is a cloud-native, API-first, event-driven platform built on AWS and GCP. This article covers the core architectural principles, API architecture, audit trail capabilities, data archiving approach, and scalability characteristics of the platform for technical evaluation and implementation planning purposes.

Key points

  • Intended Audience: Solution Architect, Developer, IT Leadership  
  • Classification: Architecture and Technical

Data Archiving

Fluent makes all historical data (e.g. completed orders) available through the same API mechanisms as current in-flight datasets. There is no separate archive-specific query interface.

Archiving behaviour:
  • Data is not automatically purged by default. Archiving and purging are executed on client request.
  • Custom archive strategies can be implemented based on configurable data type and retention period.
  • Backups are automatically lifecycle-managed as part of the standard retention policy.
  • Purge rules can be defined per data type (personal data, transactional data, logs, etc.) based on retention duration or data sensitivity.
  • Document attachments (invoices, PDFs, customs documents) are not stored directly in Fluent. Links or encoded PDFs are stored as order attributes. AWS S3 is a common document storage solution for Fluent implementations.


API Architecture

Fluent's architecture is based on the following core principles:

Principle:
  • API-first - All business capabilities are exposed via API; no functionality is hidden from integration
  • Event-driven - Every action within the platform produces a structured event that can be subscribed to and actioned
  • Versionless - All environments always run the latest version; backward compatibility is guaranteed 
  • Headless - Front-end UX is decoupled from the platform; clients can build any UI on top of Fluent APIs 
  • Multi-tenant - Logical data segregation per client via tenant identifiers, separate databases, and encryption 

API protocols supported:
  • GraphQL (primary, recommended)
  • REST
  • Webhooks and events

Authentication: OAuth 2.0 bearer tokens, time-bound to 24 hours. All communications are over HTTPS (TLS 1.2+).

Single Sign-On (SSO): Fluent supports SSO via SAML 2.0 and OpenID Connect, integrating with existing enterprise identity providers.

API versioning: As GraphQL is a single endpoint, no versioned URL management is required. Changes occur in the underlying data model. Some legacy REST APIs retain backward-compatible versioning. Backward compatibility is a mandatory release principle for Fluent Commerce.

Audit Trail

Fluent's event-driven architecture provides comprehensive, immutable audit trails across all user and system actions.

Audit log captures:
  • What activity was performed
  • Who or what performed the activity (including source system and IP)
  • What the activity was performed on
  • When the activity occurred (date and time)
  • The result (authorised or denied)

Centralised audit logs are maintained with:
  • Log file integrity checks
  • Restricted access to authorised personnel only
  • Automated analysis to detect anomalous activity
All access to client data is logged. Logs can be pulled via open APIs and pushed to any third-party SIEM or analytics platform. Audit trail data is retained for 7 years.

Fluent does not allow direct access to log directories, databases, or sensitive infrastructure without the appropriate access level — all access is controlled through the SaaS operating platform and AWS security infrastructure.

Scalability and Performance

Fluent leverages AWS auto-scaling to handle variable demand, including peak events such as Black Friday, flash sales, and pre-orders.

Scaling characteristics:
  • Auto-scaling is triggered by CPU utilisation thresholds (e.g. exceeding 80% for 5 minutes).
  • Scaling response time is typically under 5 minutes, with EC2 instances added dynamically.
  • Both horizontal and vertical scaling are supported.
  • The platform is highly available with zero downtime for releases.
API performance:
  • API response times typically below 1,000ms.
  • The platform handles high concurrent API call volumes — existing customers use real-time ATP requests to surface availability on eCommerce PLPs and PDPs at scale.

Version management:
  • Fluent is a versionless PaaS platform. All accounts always run the latest version.
  • New features are enabled/disabled through configuration rather than versioned deployments.
  • Backward compatibility is guaranteed across all releases.

Multi-region data residency:
  • The platform supports data residency requirements through regional deployment choices (Dublin for EU, Sydney/Singapore for APAC, Ohio for US).
  • Data can be expanded to additional countries while complying with local data residency obligations.

Data Privacy Addendum

The Data Privacy Addendum details Fluent Commerce's obligations in line with applicable data protection laws as data processor when processing personal data as data processor in context of its Clients' use of the Fluent Order Management Platform and Services. The Data Privacy Addendum can be found at https://docs.fluentcommerce.com/essential-knowledge/data-privacy-addendum