Fluent Commerce Logo
Docs

Inventory Management Lifecycle

Big Inventory, Inventory Processing (Batch Pre-Processing & Events), Inventory Monitoring, Inventory Entities (Inventory Position, Virtual Position, Controls, etc.) and Availability Management (Inventory Feeds Management).

Stock Segmentation - Data Model and API Overview

Essential knowledgeCore knowledge to understand Fluent Commerce
Stock Segmentation extends Fluent’s Inventory and Virtual Catalog data models to represent multiple logical segments for the same product and location using explicit, queryable factors.Stock Segmentation supports scenarios such as channel-specific reservations, manufacturing batch traceability, compliance restrictions (for example by country of origin), and supplier-level inventory management while preserving a single physical inventory model per product and location.This document explains the data model and GraphQL API capabilities introduced for Stock Segmentation.
  • Physical stock in the Inventory Catalog is stored as Inventory Quantities. You can segment them with these fields: `condition`, `expiresOn`, `countryOfOrigin`, `channel`, `manufacturer`, `manufacturerBatchNumber`, `supplier`, `storageAreaRef`, `segment1`, `segment2`, and `segment3`.
  • Inventory Quantities support parent-child hierarchies. Use the parent relationship to model multi-level segmentation trees.
  • Inventory Quantities can be linked to operational entities using `associationType` and `associationRef. `The main use cases are linking reservations and tracing stock.
  • Use Virtual Segments to expose customer-facing segments in virtual availability.
  • Segmentation fields only support exact match. Partial matching isn't supported. 
    • Exception: the `inventoryQuantities` query supports wildcard search on `condition` and `storageAreaRef`.
  • Filter values ignore case, except `type` and `status` in `updateInventoryQuantitiesStatus`.

Send Enhanced Inventory Attributes in Your Payloads

Essential knowledgeCore knowledge to understand Fluent Commerce
Inventory payloads can include additional Inventory Quantity attributes to capture richer stock context.This article explains how to use the `attributes` object to include additional data in inventory payloads. It supports both simple key-value pairs and custom JSON structures to meet diverse business requirements - whether you’re:
  • managing detailed product information
  • optimizing warehouse processes
  • or integrating with custom workflows
The Inventory Reference Module supports a set of reference attributes that are persisted automatically, while custom attributes provide additional flexibility.
  • Prerequisites: To fully leverage the extended attributes functionality within the inventory payload, ensure that you are using the Inventory Reference Module v2.3.0 or later
  • Flexible attribute structure: The `attributes` object supports any combination of key-value pairs, including complex JSON structures and arrays. This flexibility allows you to customize the data sent in your inventory payloads to meet specific business needs
  • Use reference attributes first: Certain key attributes (such as `associationType`, `associationRef`, `parentRef`, `expectedOn`, `expiresOn`, `condition`, `storageAreaRef`, `supplier`, `manufacturer`, `manufacturerBatchNumber`, `countryOfOrigin`, and `channel`) will be directly updated in the Inventory Quantity associated with the incoming record, facilitating seamless integration with existing fields
  • Use segment fields for flexible key-value extensions: `segment1`, `segment2`, and `segment3` provide flexibility for additional flat classification data without introducing new custom attributes
  • Custom attribute availability: Any custom attributes that you include in the `attributes` object will be available in workflows via `inventoryPosition.inventoryQuantity.attributes.<fieldName>`. This enables you to incorporate custom data into rule-based processes or other logic tailored to your business requirements