Fluent Commerce Logo
Docs
Holger Lierse

Holger Lierse

Global Head of Partner Delivery & Principal Technical Consultant

I authored

51

articles. I write about:

Analytics

14

Other resources

14

Analytics and Reporting

13

Developer tooling

12

Implementation

11

Increase speed-to-market

11

Rule performance

11

Rule SDK

11

Utility bundle

11

Tracking success metrics

10

Boiler plates and reference modules

10

Order Workflows

8

Event

7

Fluent Big Inventory

5

Inventory quantity

5

Inventory processing

5

Availability management

5

Inventory entities

5

GraphQL query

5

GraphQL

5

API

5

Integrate

4

Enterprise Inventory Availability (GI)

4

Intelligent Inventory Processing

4

Inventory Reference Module

4

Platform flexibility

4

Decision logic / Orchestration

4

Event API

4

Optimize Fluent Commerce

3

Reference Apps

2

Order domain entities

2

Fulfillment domain entities

2

Inventory management lifecycle

2

Virtual inventory position

2

Responsive Sourcing

2

UX framework

Content components

Setting

UI Component SDK

Webhook

Configuration manifest

Store customer service

Product entities

Web Apps

Object attributes

Entities

Account

Order entity

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:
Embedded Analytics Query Settings
Edited 25 days ago
Embedded
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