- Overview
- Platform setup and administration
- Platform setup and administration
- Platform architecture
- Data Bridge onboarding overview
- Connecting a Peak-managed data lake
- Connecting a customer-managed data lake
- Creating an AWS IAM role for Data Bridge
- Connecting a Snowflake data warehouse
- Connecting a Redshift data warehouse (public connectivity)
- Connecting a Redshift data warehouse (private connectivity)
- Reauthorizing a Snowflake OAuth connection
- Using Snowflake with Peak
- SQL Explorer overview
- Roles and permissions
- User management
- Inventory management solution
- Commercial pricing solution
- Merchandising solution
Order parameters dataset
Order parameters dataset containing planning configuration per product, location, and supplier combination, used by Rebuy & Replenishment for replenishment recommendations.
The order parameters dataset contains planning configuration data for each product, location, and supplier combination. It defines the timing and service assumptions used by the Rebuy & Replenishment capability when calculating inventory parameters and replenishment recommendations.
This dataset plays a critical role in determining how inventory decisions are evaluated over time.
Purpose
The Rebuy & Replenishment capability uses the order parameters dataset to:
- Understand how frequently inventory is reviewed and replenished
- Calculate the ordering cycle (also known as the risk period)
- Evaluate demand volatility over lead times and review periods
- Support accurate safety stock and replenishment calculations
During presales, this dataset is also used to validate planning assumptions and assess potential inventory improvements.
Required fields
About the Constraint column: every field listed must be provided in your data. Non-null means its value cannot be null; Nullable means the value may be sent as null (or left blank in your source). Primary key, Unique, and Foreign key describe the field's role in the data model; a Primary key is always non-null.
| Field | Description | Type | Constraint |
|---|---|---|---|
product_id | Unique identifier for the product SKU. | string | Primary key |
location_id | Identifier for the store or distribution centre where the product is delivered. | string | Primary key |
source_id | Identifier for the supplier or internal distribution centre. Can represent an external supplier or an internal source. | string | Non-null |
review_period_days | Number of days between reviewing purchase orders. May be determined during scoping. | int | Non-null |
service_level | Target service level for the product, expressed as a value between 0 and 1. May be determined during scoping. | float | Non-null |
lead_time_days | Number of days between placing an order and receiving the product. | int | Non-null |
minimum_guardrail | Minimum inventory guardrail quantity applied when generating replenishment recommendations. | int | Nullable |
Usage notes
- The ordering cycle for a product is calculated as the sum of the
lead_time_daysandreview_period_days. - If
review_period_daysorservice_levelvalues are not provided, they may be defined during onboarding or scoping. - Identifiers (
product_id,location_id,source_id) must align with the corresponding Products, Locations, and Suppliers datasets. - This dataset typically changes less frequently than demand or stock data but is critical to planning accuracy.