Fluent Commerce Logo
Docs
Help & Feedback

Content in this track:

Fluent Big Inventory - Features Overview

1

Getting Started with Fluent Big Inventory

2

Inventory Ingestion

3

Inventory Batch

4

How to Submit Inventory Batches

5

Fluent Big Inventory Web App

6

Metrics Overview

7

How Metrics works

8

Metrics usage for Platform Observability

9

Inventory Feeds

10

How do Inventory Feeds work

11

End Of Track

12

Inventory Batch

Essential knowledge

Author:

Fluent Commerce

Changed on:

29 Aug 2025

Overview

Inventory Batch enables bulk uploading of inventory updates to the Fluent Commerce platform, handling high data volumes from thousands to million updates per operation. Leveraging Fluent Big Inventory's Batch API and Inventory Batch Pre-Processing, it ensures faster processing and accurate inventory availability in the Fluent Order Management System. This scalable solution keeps inventory data synchronized across channels, empowering businesses to manage stock efficiently and meet customer expectations with accurate, up-to-date stock information.

Key points

  • Use Cases for Inventory Batch
  • Platform Capabilities leveraged
  • Best practices for Inventory Batch
  • Reference Inventory Module and Inventory Batch

Use Cases for Inventory Batch

  • Periodic Stock Updates:
    Designed to handle periodic inventory updates from an ERP or similar inventory source of truth. These updates typically consolidate changes collected during a predefined cycle, such as daily updates, ensuring that the OMS reflects the most current stock levels.
  • Stocktake Adjustments:
    Used to inform the OMS of stock adjustments following manual stocktakes. This ensures that any discrepancies, such as missing or damaged stock, are accounted for accurately.

Platform Capabilities leveraged by the Inventory Batch

CapabilityDescription
Job API & Batch APIAPIs to create & manage batch loading of information.
Inventory Batch Pre-ProcessingOptimized inventory processing by de-duplicating redundant updates and filtering out unchanged records.

Best Practices for Inventory Batch

To ensure successful Inventory Batch processing, consider the following key factors:
  • Optimal use of Jobs and Inventory Batch Pre-Processing
  • Inventory Batch Sizing
    • Size of Inventory Batches
    • Number of Inventory Batches
    • Spread of Inventory Batches
    • What about small real-time inventory updates?
  • Visibility of successful Batch processing 

Jobs and Inventory Batch Pre-Processing

Jobs are used to group Inventory Batches, providing a structured way to track each distinct set of Inventory Batches sent together. This grouping enables better visibility into the success or failure of related updates, ensuring that inventory processing is efficient and transparent.
  • A single Job remains open until midnight on the day it is created.
  • It is recommended to create a new Job for each Inventory Batch group, especially for periodic updates like hourly Inventory Updates.
    Example:
    If sending updates hourly, create a separate Job for each hour’s batch run to maintain clarity and tracking.
Additionally, Jobs determines whether Inventory Batch Pre-Processing is applied to the associated Inventory Batches. This ensures redundant updates are removed and unchanged records are filtered before processing, optimizing the handling of inventory data. For more information, refer to the details on Inventory Batch Pre-Processing.

Inventory Batch Sizing

Size of Inventory Batches
Inventory Batches are restricted to a maximum of 5,000 records per batch. For larger datasets, the updates must be divided into multiple batches, with each batch adhering to this limit.Example:
If you need to upload 1,000,000 updates, split them into 200 batches of 5,000 records each to ensure compliance and efficient processing.
Number of Inventory Batches
While each Batch can contain up to 5,000 records, sending only a small number of batches may reduce processing efficiency. The Batch API is designed to handle multiple datasets concurrently, distributing the workload across the platform for asynchronous processing. To maximize performance, it is recommended to spread a full dataset across 10 individual Inventory Batches.Example:
For 15,000 inventory updates, instead of splitting them into 3 batches of 5,000 records each, divide them into 10 datasets of 1,500 records. This ensures optimal load distribution. As update volumes grow, the integration should scale accordingly, maintaining a minimum of 10 datasets until individual batches reach the 5,000-record limit, after which additional batches can be added.
Spread of Inventory Batches
When running a Job with more than 10 Inventory Batches, it’s common to have several batches containing a maximum of 5,000 records and one smaller batch with fewer records. To ensure more consistent processing, it’s recommended that the total updates be distributed evenly across all Inventory Batch datasets.Example:
If you have 53,900 items to update, distribute them into 11 batches of 4,900 records each rather than 10 batches of 5,000 records and one batch of 3,900 records.
What about small real-time inventory updates?
For real-time or near-real-time updates, we recommend using Delta Inventory updates, which are ideal for handling incremental changes to inventory levels instead of full data updates.

Visibility of successful Batch processing

The current best tool for visibility is to use the Inventory Domain Events to understand the success and failures of Inventory updates sent via the Inventory Batch. This provides visibility into the individual items included in the Batches.Note: Right now, only Failures & Exception Audit Events are visible for Inventory processing.

Reference Inventory Module & Inventory Batch

The Fluent Inventory Module provides a foundational solution for integrating Inventory Batch updates into your inventory management workflows. It is designed to calculate an accurate Stock on Hand value using a set of predefined Inventory Quantity types. These types represent various inventory states and activities, ensuring precise inventory management.Key Inventory Quantity Types:
  • LAST_ON_HAND: Represents the absolute inventory count at a given location from the most recent Inventory Batch update.
  • RESERVED: Quantities allocated during the fulfilment reservation process, representing stock on hold for pending order fulfillment.
  • SALE: Quantities picked and fulfilled during the fulfilment sale process, representing items completed in an order for a customer.
  • CORRECTION: Adjustments made during the fulfilment cancellation process to account for items not found during picking or packing (e.g., short-picks), removing them from the sale.
  • DELTA: Incremental changes triggered by external systems e.g. POS, representing relative updates from external systems in the Order Management process.
These quantity types work together to calculate the Stock on Hand, providing an up-to-date value that reflects the current available inventory for each Inventory Position. This ensures accurate inventory visibility and supports effective decision-making in stock management and order fulfillment.

Related content

Inventory Ingestion
Edited 161 days ago
Inventory Ingestion in Fluent Commerce ensures that stock levels across all sales channels remain accurate and up-to-date, enabling effective inventory management. It allows businesses to send inventory updates to the platform using two distinct methods: Inventory Batch and Inventory Delta. Each method is tailored to different scenarios, depending on data volume, frequency, and operational needs.
Inventory Batch Pre-Processing
Edited 161 days ago
This page describes how Inventory Batch Pre-Processing (BPP) works, the opportunities available for configuration, and the implementation improvements enabled by using Inventory Batch Pre-Processing.
How Inventory Batch Pre-Processing works
Edited 359 days ago
This document outlines the functionality of Inventory Batch Pre-Processing, offering insights into how unchanged records are filtered during the inventory ingestion process using Inventory Batches.
Job API
Edited 351 days ago
A Job represents a container that can hold multiple batches. A job stays open until midnight (UTC), where the status will change to CLOSED. All jobs are processed concurrently.
Inventory Batch Events
Edited 161 days ago
Inventory Batch Events offer insights into the processing status of Inventory Batches, helping to determine whether the corresponding records within a batch were successfully submitted for processing.
Fluent Commerce

Fluent Commerce

Knowledge Tracks Related To This Topic

All about Big Inventory
  • Fluent Big Inventory - Features Overview
  • Getting Started with Fluent Big Inventory
  • Inventory Ingestion
  • Inventory Batch
  • How to Submit Inventory Batches
  • Fluent Big Inventory Web App
  • Metrics Overview
  • How Metrics works
  • Metrics usage for Platform Observability
  • Inventory Feeds
  • How do Inventory Feeds work
    • Building Blocks
    Building Blocks
    Packages & Modules
    All UI Components
    Workflows
    Settings
    Interface Contracts
    All Rules
    By Type
    All Types
    Knowledge Tracks
    Extend Knowledge
    Glossary
    All How-to Guides
    Sitemap
    Topics
    Use Cases
    Helpful Resources
    Platform Limits
    Support Policy
    Service Level Agreement (SLA) - Enterprise
    Deprecation Policy
    Extend Knowledge Content – Terms and Conditions
    System and Organization Controls (SOC) 3 Report
    Data Privacy Addendum
    Security Policy
    Quick Links
    For Partners
    Customer Resources
    Webinars and Events
    Certifications
    Training Resources
    Knowledge Tracks
    Builders Portal
    Product Update Newsletter
    Industry Blogs & Events Newsletter
    Trust Center Portal

    Copyright © 2024-2026 Fluent Retail Pty Ltd (trading as Fluent Commerce). Unless otherwise expressly stated in a current written agreement with Fluent Commerce or any of its affiliates or on any single page of the docs.fluentcommerce.com site, use of the materials on this site is strictly limited to viewing by individuals over 18 years old for legitimate commercially appropriate reasons; and any downloading, copying or other actions or uses of any kind or by any means of the materials on this site, including by artificial intelligence tools, is strictly prohibited. All other rights reserved.

    Fluent Logo