industry-department-solutions
latest
false
- 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
Supply Chain & Retail Solutions user guide
The purchase orders dataset contains details of orders placed with external suppliers to replenish stock or raw materials, disaggregated by order number. It provides a history of purchase orders, including amendments, and is used by the inventory management solution to project future inventory availability.
Purpose
The inventory management solution uses the purchase orders dataset to:
- Account for stock on order when calculating inventory positions
- Generate stock parameters based on the total of on-hand stock and incoming supply
- Project future availability and support replenishment recommendations
By incorporating open and incoming purchase orders, the solution evaluates inventory exposure based on actual supply in transit, not just current on-hand stock.
Required fields
| Field | Description | Type | Use | Notes |
|---|---|---|---|---|
product_id | Unique identifier for the product SKU. | string | Application | Required |
location_id | Unique identifier for the store or distribution centre. | string | Application | Required |
order_number | Unique identifier for each purchase order. | string | Application | Required |
source_id | Unique identifier for the supplier. | string | Application | Required |
ordered_at | Date and time (UTC) when the purchase order was placed. | datetime | Application | Required |
order_due_date | Date and time (UTC) when items on the purchase order are due to arrive. | datetime | Application | Required |
ordered_units | Number of units ordered for the purchase order line item. | float | Application | Required |
receipted_at | Date and time (UTC) when items on the purchase order were received. | datetime | Application | Required |
receipted_units | Number of units received for the purchase order line item. | float | Application | Required |
order_line_value | Cost price of units ordered for the purchase order line item. | float | Application | Required |
order_line_status | Status of the purchase order line item (for example, Open, Pending approval, Closed). | string | Application | Required |
updated_at | Date and time (UTC) when the record was created or last updated. | datetime | Application | Optional |
Usage notes
- Purchase orders should be provided at line-item level to support accurate inventory projections.
- Both open and completed purchase orders should be included to preserve historical context.
- Partial receipts should be reflected using
receipted_unitsandreceipted_atfields alongside the original ordered quantities. - Identifiers (
product_id,location_id,source_id) must align with the corresponding Products, Locations, and Suppliers datasets. - Units of measure must be consistent across purchase orders, stock, and demand datasets.