Authors:
Girish Padmanabha, Randy Chan
Changed on:
29 July 2024
To ensure that Batch Pre-Processing works correctly and won’t impact your inventory accuracy, the first step is to ensure your inventory workflows are compatible with Batch Pre-Processing.
Batch Pre-Processing is based on the logic within the inventory module. This diagram details the high-level view of the logic.
Batch Pre-Processing is enabled by default, you will see that the setting
`fc.enable.batch.preprocessing`
Once the setting is updated, the new value will take effect within 5 minutes. Once this time has elapsed, all traffic will either be routed through BPP or be directly processed, depending on whether the setting is enabled or not.
Due to the way Batch Pre-Processing works, it is most efficient with large amounts of updates and a significant unchanged rate. Through our Metrics API we provide metrics to track the total number of batch items processed and the ratio of unchanged items.
For the total amount of batch inventory updates, you should be aiming for the following:
For the unchanged rate of batch inventory updates, you should be aiming for the following:
The metric to use here is bpp_records_processed_total. This will return the total count of all batch inventory updates processed through Batch Pre-Processing for the given time period
This will use an additional metric. To calculate the unchanged rate you will want to divide the total unchanged records by the total records. The metric for unchanged records is bpp_records_unchanged_total.
E.g. (bpp_records_unchanged_total / bpp_records_processed_total)
Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.