Optimize your Inventory Workflows with Inventory Reference Module 2.1.0
Release
Author:
Kirill Gaiduk
Changed on:
5 Sept 2025
| Target release date: | 2024-10-28 |
|---|---|
| Release status: | Released |
Description
Here's what's new in Inventory Module 2.1.0:- Share your Inventory pool across regions or brands by sending Cross-Retailer events to Sub-Retailers' Virtual Catalogs whenever the Master-Retailer's Inventory Catalog is updated.
- Optimize Aggregate Virtual Position Available-to-Sell (ATS) calculations by extracting all relevant Controls at once, reducing the number of Control queries.
- Speed up and simplify the Inventory Reference Module configuration with optimized Reference Workflows, ensuring seamless module implementation and consistent approach across all the Reference Modules provided by Fluent Commerce.
- Manage Product attributes flexibly with any plain string values (for example,
`JSON`) now accepted by the`UPSERT_PRODUCT`for a Product attribute`type`. Previously, saving a Product attribute`type`was restricted to the corresponding Enumerated type and`CUSTOM`values. - And a fix for pagination issues with Inventory and Product Catalog Workflows Rules.
Changelog
Rules and Utilities- New Rules have been introduced to enable Cross-Retailer events sending for Master/Sub-Retailer(s) setup:
`CreateAggregateVirtualPosition`and`UpdateAggregateVirtualPosition`Rules have been optimized to load all the related Controls (by Product, its Categories, and list of Locations) at once for efficient Aggregate Virtual Position Available-to-Sell (ATS) calculations.- Attribute Utils have been updated to use a plain
`string`type instead of the`enum`, ensuring that a Product attribute`type`is saved in the same way as it was sent via the`UPSERT_PRODUCT`event. `NotifyVirtualCatalogueOnNetworkMatch`and`ValidateProductCategoriesExist`Rules have been extended with a pagination logic to ensure correct execution for the following scenarios:- A given Location belongs to more than 10 Networks, and the Virtual Catalog to be updated has a Network outside the first 10 Networks fetched.
- A given Product has more than 100 Categories assigned.
- All the Workflows:
`SendEventGQL`Rules have been switched to the`SendEvent`(Core Reference Module).- “Deactivate” Rulesets have been removed:
`DeactivateProductCatalogue``DeactivateIC``DeactivateIP``DeactivateIQ``DeactivateVC`
- Inventory Catalog Workflow:
`NotifyVirtualCatalogueOnNetworkMatch`Rules have been replaced with the new`NotifyVirtualCataloguesByRefsOnNetworksMatch`Rule for the`NotifyVirtualCatalogues`Ruleset.`CalculateOnHandForFulfilment`Ruleset has been replaced with a generic`CalculateOnHand`one.`UpdateOnHandForFulfilment`Ruleset has been removed.`UpdateInventoryQuantitiesStatus`Rule has been removed from the`BatchInventoryQuantityCreate`Ruleset.
Package
| Released capability depth: | Enhancement |
|---|---|
| Release bundle / Capability type: | Module |
Use case
Problem
A company wants to use a shared Inventory pool for its sales under the different regional brands following its market segmentation strategy.Example
A multi-region consumer brand operated several regional banners under distinct names but kept inventory siloed by brand and country site. Each storefront maintained its own ATP and safety stock, so a fast-selling SKU showed “sold out” in one market while identical units sat idle under sister brands. Marketing pushed localized campaigns and price points, yet the underlying stock picture was fragmented: duplicate buffers, stale reservations, and no way to respect market segmentation while tapping excess supply during spikes. Cross-border demand signals were invisible to planners, leading to emergency transfers, late carrier injections, and inconsistent promise dates at checkout.
Solution
