industry-department-solutions
latest
false
Supply Chain & Retail Solutions user guide
- 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
Locations dataset for the Markdown & Promotions module, defining the stores or locations where products are sold and stocked.
The Locations dataset defines the stores or locations where products are sold, stocked, and priced. It provides the geographic and currency context used across the Markdown & Promotions module.
This dataset acts as a reference dataset and is joined to other datasets, such as Sales, Stock, and Product pricing daily, using the location_id.
Purpose
The Markdown & Promotions module uses the Locations dataset to:
- Define where products are sold and stocked
- Enable analysis across stores, regions, and channels
- Provide the currency context for value-based metrics
Required fields
| Field | Description | Type | Use | Notes |
|---|---|---|---|---|
location_id | Unique identifier for the store or location. | string | Application / Presales | Required. Primary key. |
country | Country in which the location operates. | string | Application / Presales | Required. |
created_at | Timestamp when the record was created. | timestamp | Application | Optional. |
updated_at | Timestamp when the record was last updated. | timestamp | Application | Optional. |
name | Name of the location. | string | Application / Presales | Optional. |
region | Region used to segment locations for analysis. | string | Application / Presales | Optional. |
currency | Currency used at the location. | string | Application / Presales | Optional. |
Usage notes
- Every location referenced in other datasets must exist in the Locations dataset.
- The
location_idmust be consistent across all datasets.
Why this dataset matters
Location context lets the solution analyse markdown and promotion performance by store, region, or channel, and normalise values across currencies.