Fluent Commerce Logo
Docs
Holger Lierse

Holger Lierse

Global Head of Partner Delivery & Principal Technical Consultant

I authored

42

articles. I write about:

Analytics

14

Tracking success metrics

12

Analytics and Reporting

12

Implementation

9

Order Workflows

8

Other resources

8

Developer tooling

7

Increase speed-to-market

7

Rule performance

7

Rule SDK

7

Boiler plates and reference modules

6

Utility bundle

6

Fluent Big Inventory

5

Inventory quantity

5

Inventory processing

5

Availability management

5

GraphQL query

5

Event

5

Integrate

4

Enterprise Inventory Availability (GI)

4

Intelligent Inventory Processing

4

Inventory Reference Module

4

Inventory entities

4

Optimize Fluent Commerce

3

Platform flexibility

3

GraphQL

3

API

3

Inventory management lifecycle

2

Virtual inventory position

2

Decision logic / Orchestration

2

Event API

2

UX framework

Content components

Setting

UI Component SDK

Configuration manifest

Store customer service

Product entities

Web Apps

Object attributes

Entities

Account

Order entity

Fulfillment domain entities

Order domain entities

Reference Apps

Fulfillment lifecycle

Order management lifecycle

Inventory position

Inventory Batch API

Batch processing

Implement Fluent Commerce

Order Orchestration

Workflow

Single Sign-On (SSO)

User management

Testing

Support and maintain

Monitor and alert

API recommendations

Core API

Authentication API

Batch API

I have worked on:
Analytics Query Settings
Edited 168 days ago
Analytics Queries are configured through settings that map query names to analytics resources in the Fluent Analytics backend services. Each setting follows the pattern `fc.analytics.queries.{domain}` and defines available queries, their resource locations, access permissions, and optional default parameters. Use this document to:
  • Understand query setting structure and naming conventions
  • Configure new analytics queries
  • Set default parameters for queries
  • Control query access through role-based permissions