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
Locations dataset
The locations dataset contains metadata for the locations used by the inventory management solution. Locations typically represent stores, distribution centres, or other sites where inventory is stored, replenished, or planned.
This dataset provides contextual information about where inventory exists and how locations function within the supply chain.
Purpose
The inventory management solution uses the locations dataset to:
- Identify where inventory is held or replenished
- Distinguish between different types of locations, such as stores and distribution centres
- Support analysis and reporting across the supply network
During analysis, location metadata helps the solution correctly interpret inventory flows and planning behavior across the network.
Required fields
| Field | Description | Type | Use | Notes |
|---|---|---|---|---|
location_id | Unique identifier for the location. | string | Application | Required |
location_name | Name of the location. | string | Application | Required |
country | Country where the location is based. | string | Application | Required |
is_store | Indicates whether the location is a store. | boolean | Application | Required |
is_dc | Indicates whether the location is a distribution centre. | boolean | Application | Required |
updated_at | Date and time (UTC) when the record was created or last updated. | datetime | Application | Optional. |
Usage notes
- Every location referenced in other datasets (for example, Stock, Customer orders, Purchase orders, or Transfers) must exist in the locations dataset.
- Location identifiers must be consistent across all datasets.
- The
is_storeandis_dcflags help distinguish how locations are treated in planning and analysis. - If additional location attributes are required for specific use cases, they can be incorporated during onboarding.