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
Last updated Apr 16, 2026
Transfer dataset
The transfers dataset contains details of inventory transfers between internal locations, such as distribution centres and stores. It represents internal stock movements used to replenish inventory within the customer's supply chain.
This dataset is optional if internal transfers are already captured in the purchase orders dataset. When provided separately, it enables the inventory management solution to more accurately project future inventory levels across locations.
Purpose
The inventory management solution uses the transfers dataset to:
- Track internal inventory movements between locations
- Project future stock availability based on expected transfers
- Evaluate how internal supply flows affect inventory positions and replenishment decisions
This dataset complements external purchase order data by representing internal supply movements.
Required fields
| Field | Description | Type | Use | Notes |
|---|---|---|---|---|
product_id | Unique identifier for the product SKU. | string | Application | Required |
location_id | Identifier for the destination store or distribution centre. | string | Application | Required |
order_number | Unique identifier for each transfer order. | string | Application | Required |
source_id | Identifier for the supplying location or distribution centre. | string | Application | Required |
ordered_at | Date and time (UTC) when the transfer order was placed. | datetime | Application | Required |
ordered_units | Number of units ordered for the transfer line item. | float | Application | Required |
expected_departure_date | Date and time (UTC) when the transfer is expected to leave the source location. | datetime | Application | Required |
actual_departure_date | Date and time (UTC) when the transfer actually left the source location. | datetime | Application | Required |
expected_delivery_date | Date and time (UTC) when the transfer is expected to arrive at the destination. | datetime | Application | Required |
actual_delivery_date | Date and time (UTC) when the transfer arrived at the destination. | datetime | Application | Required |
delivered_units | Number of units delivered for the transfer line item. | float | Application | Required |
status | Status of the transfer 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
- Transfers should be provided at line-item level to support accurate inventory projections.
- Both planned and completed transfers should be included to preserve historical context.
- Partial transfers should be reflected using delivered quantities and actual delivery dates.
- Identifiers (
product_id,location_id,source_id) must align with the corresponding Products and Locations datasets. - Units of measure must be consistent across transfers, stock, and demand datasets.