Configure the Inventory Catalog Workflow to Release Stock Held by Late Reservations

How-to Guide

Author:

Holger Lierse

Changed on:

6 Nov 2026

Key Points

Late reservations no longer hold stock after the sale. A late reservation is a `RESERVED` quantity created after its Fulfillment is already confirmed.
Inventory Module 2.3.1 adds 3 rules that catch these when the quantity is created: `IfRelatedQuantitiesArePresent`, `IfRelatedQuantitiesAreNotPresent` and `SendEventForInventoryPosition`.
The rules aren't part of the reference Inventory Catalog workflow. To opt in, you need to change your workflow as described in this guide.
Fulfillment quantity refs must follow the reference pattern `{inventoryPositionRef}:{quantityType}:{fulfilmentId}`, which the reference modules use. If a quantity also has a Fulfillment `associationRef`, the rules use it instead of the ref to find related quantities.
Opting in increases the number of queries and mutations during inventory processing.

Prerequisites

Install Fluent Modules into your sandbox

Steps

Why reservations get stuck

How it happens

Inventory events are processed from a standard queue, so for one Fulfillment the confirm event can be processed before the reserve event. The confirm creates the `SALE` quantity and deactivates the Fulfillment's `RESERVED` quantities, but there aren't any yet. The `RESERVED` quantity arrives afterwards, moves to `ACTIVE` and is counted in on hand. Nothing resets it, so available stock stays too low.

Check your quantity refs first

The rules need Fulfillment quantity refs that follow the pattern `{inventoryPositionRef}:{quantityType}:{fulfilmentId}`. They read the Inventory Position from this ref. If a quantity also has a Fulfillment association (`associationRef`), the rules use it to find the related quantities. If your refs follow a different pattern, the rules can't find the `SALE` quantity and `RESERVED` quantities are activated as before.

Update the Inventory Catalog workflow

Make sure Inventory Module 2.3.1 is installed

The 3 rules ship with Inventory Module 2.3.1. Check that the `globalinventory` plugin on your account is at 2.3.1 or later before you change the workflow. Otherwise the workflow upload fails because the rules don't exist.

Add the ActivateQuantity ruleset

This ruleset keeps the old `CREATE` behaviour. It activates every new quantity that has no related `SALE` or `CORRECTION` quantity.

1{
2  "name": "ActivateQuantity",
3  "description": "Activate a newly created inventory quantity",
4  "type": "INVENTORY_QUANTITY",
5  "eventType": "NORMAL",
6  "rules": [
7    {
8      "name": "[[account.id]].core.SetState",
9      "props": { "status": "ACTIVE" }
10    }
11  ],
12  "triggers": [ { "status": "CREATED" } ],
13  "userActions": []
14}

Add the DeactivateQuantity ruleset

This ruleset moves the late `RESERVED` quantity to `INACTIVE`. It keeps the record and then asks the Inventory Position to recalculate on hand.

1{
2  "name": "DeactivateQuantity",
3  "description": "Deactivate a quantity whose related fulfilment quantities already exist, then recalculate on hand",
4  "type": "INVENTORY_QUANTITY",
5  "eventType": "NORMAL",
6  "rules": [
7    {
8      "name": "[[account.id]].core.SetState",
9      "props": { "status": "INACTIVE" }
10    },
11    {
12      "name": "[[account.id]].globalinventory.SendEventForInventoryPosition",
13      "props": { "eventName": "CalculateOnHand" }
14    }
15  ],
16  "triggers": [ { "status": "CREATED" }, { "status": "ACTIVE" } ],
17  "userActions": []
18}

Replace the rules in the CREATE ruleset

Replace the `SetState` rule in the `INVENTORY_QUANTITY` `CREATE` ruleset with the 2 condition rules. Each quantity goes to exactly one of the 2 new rulesets.

1"rules": [
2  {
3    "name": "[[account.id]].globalinventory.IfRelatedQuantitiesArePresent",
4    "props": {
5      "eventName": "DeactivateQuantity",
6      "quantityTypes": ["RESERVED"],
7      "relatedQuantityTypes": ["SALE", "CORRECTION"],
8      "relatedQuantityStatuses": ["CREATED", "ACTIVE"]
9    }
10  },
11  {
12    "name": "[[account.id]].globalinventory.IfRelatedQuantitiesAreNotPresent",
13    "props": {
14      "eventName": "ActivateQuantity",
15      "quantityTypes": ["RESERVED"],
16      "relatedQuantityTypes": ["SALE", "CORRECTION"],
17      "relatedQuantityStatuses": ["CREATED", "ACTIVE"]
18    }
19  }
20]

`quantityTypes`: only `RESERVED` quantities are checked. Every other type goes straight to `ActivateQuantity`.
`relatedQuantityTypes` and `relatedQuantityStatuses`: what counts as "the sale already happened".

Upload and test the workflow

Upload the workflow, then confirm a Fulfillment before you reserve it. The `RESERVED` quantity should move to `INACTIVE` and on hand should be recalculated.Then reserve and confirm another Fulfillment in the normal order, and check that nothing changes compared with before.

Related artifacts

Inventory Catalog Workflow Template

IfRelatedQuantitiesArePresent

IfRelatedQuantitiesAreNotPresent

SendEventForInventoryPosition

Related content

Inventory Module 2.3.1 - Release Stock Held by Late Reservations

Edited 1 day ago

Inventory Reference Module

Edited 8 days ago

The Inventory Reference Module is the foundation for inventory related implementations. It provides reference Workflows for inventory ingestion and processing. Extensible by design, use this Module as a base to build a solution to the needs of your customers.The Inventory Module includes the following areas:

Product Catalog workflow
Inventory Catalog workflow
Control Group workflows
Virtual Catalog workflows

Core Reference Module

Edited 7 days ago

The Core Reference Module is a foundational Reference Module. It provides a base set of general purpose Rules:

that other Modules are built upon
or that can be included in your own Workflows

Extensible by design, use this Module as a base to build a solution for the needs of your customers.

Replace the rules in the CREATE ruleset

Replace the `SetState` rule in the `INVENTORY_QUANTITY` `CREATE` ruleset with the 2 condition rules. Each quantity goes to exactly one of the 2 new rulesets.

1"rules": [
2  {
3    "name": "[[account.id]].globalinventory.IfRelatedQuantitiesArePresent",
4    "props": {
5      "eventName": "DeactivateQuantity",
6      "quantityTypes": ["RESERVED"],
7      "relatedQuantityTypes": ["SALE", "CORRECTION"],
8      "relatedQuantityStatuses": ["CREATED", "ACTIVE"]
9    }
10  },
11  {
12    "name": "[[account.id]].globalinventory.IfRelatedQuantitiesAreNotPresent",
13    "props": {
14      "eventName": "ActivateQuantity",
15      "quantityTypes": ["RESERVED"],
16      "relatedQuantityTypes": ["SALE", "CORRECTION"],
17      "relatedQuantityStatuses": ["CREATED", "ACTIVE"]
18    }
19  }
20]

`quantityTypes`: only `RESERVED` quantities are checked. Every other type goes straight to `ActivateQuantity`.
`relatedQuantityTypes` and `relatedQuantityStatuses`: what counts as "the sale already happened".

Configure the Inventory Catalog Workflow to Release Stock Held by Late Reservations

Key Points

Prerequisites

Install Fluent Modules into your sandbox

Steps

Why reservations get stuck

Update the Inventory Catalog workflow

Make sure Inventory Module 2.3.1 is installed

Add the ActivateQuantity ruleset

Add the DeactivateQuantity ruleset

Replace the rules in the CREATE ruleset

Upload and test the workflow

Related artifacts

Inventory Catalog Workflow Template

IfRelatedQuantitiesArePresent

IfRelatedQuantitiesAreNotPresent

SendEventForInventoryPosition

Related content

Inventory Module 2.3.1 - Release Stock Held by Late Reservations

Inventory Reference Module

Core Reference Module

Holger Lierse

Building Blocks

By Type

Helpful Resources

Quick Links

Make sure Inventory Module 2.3.1 is installed

Add the ActivateQuantity ruleset

Add the DeactivateQuantity ruleset

Replace the rules in the CREATE ruleset

Upload and test the workflow