Fluent OMS Production Volume Testing (PVT)
Essential knowledgeCore knowledge to understand Fluent Commerce
Intended Audience:
Business User
Author:
Randy Chan
Changed on:
5 Feb 2025
Overview
The Production Volume Testing (PVT) is one of the test phases to ensure the OMS can handle peak production volume such as Black Friday or Boxing Day Sale. This test phase is typically execute during the implementation cycle. In order to mimic the peak production scenario, this requires the project team to set up the following:- An OMS account scaled to production level;
- Middleware to production level with preparation of peak period data payload (if does not require eCom);
- eCom frontend in production level (if eCom is needed to be tested for PVT);
Key points
- Explanation of Purpose of PVT
- The benefit of executing PVT
- Considerations of what can be included as part of the PVT
Purpose
- Production Volume Testing (PVT) is aimed to simulate the Production expected volume into an identical test environment and ensure that Fluent Platform supports appropriately during the peak Production volume.
- Given that the development sandboxes are only for implementation and functional testing, it is a common practice to rent an additional sandbox that will be used for PVT activities at a production scale.
- This activity helps high volume retailers to assess if any of the workflows (or settings) need to be optimised further for peak volume but also helps to identify potential performance issues in the E2E environment (i.e. other systems).
- The PVT results are specific to the particular implementation (e.g. a given region), and are driven by the below elements:
- The unique workflows and custom rules of the implementation
- The nature of inventory passing through the platform i.e. Delta vs. Full snapshot, new inventory records vs. changed inventory records
- The inventory volume i.e., the Number of Inventory Position Updates (IPUs)
- The order volume i.e., the Number of orders that are pushed through to Fluent OMS from any channel and processed through the Fluent workflows for allocation