Purchase orders dataset

Purchase orders dataset containing details of supplier orders, used by Rebuy & Replenishment to project future inventory availability from inbound procurement.

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 Rebuy & Replenishment capability to project future inventory availability.

Purpose

The Rebuy & Replenishment capability 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

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	Non-null
location_id	Unique identifier for the store or distribution centre.	string	Non-null
order_number	Unique identifier for each purchase order.	string	Primary key
source_id	Unique identifier for the supplier.	string	Non-null
ordered_at	Date and time (UTC) when the purchase order was placed.	datetime	Non-null
order_due_date	Date and time (UTC) when items on the purchase order are due to arrive.	datetime	Non-null
ordered_units	Number of units ordered for the purchase order line item.	float	Non-null
receipted_at	Date and time (UTC) when items on the purchase order were received.	datetime	Nullable
receipted_units	Number of units received for the purchase order line item.	float	Nullable
order_line_value	Cost price of units ordered for the purchase order line item.	float	Non-null
order_line_status	Status of the purchase order line item (for example, Open, Pending approval, Closed).	string	Nullable

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_units and receipted_at fields 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.