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
Sales extra dataset for the Markdown & Promotions module, breaking down sales and return transactions by product variant.
The Sales extra dataset provides sales and return transactions broken down by product variant, for cases where a single product is sold in multiple variants (for example, size or colour).
Purpose
The Markdown & Promotions module uses the Sales extra dataset to:
- Capture variant-level demand where a product has multiple variants
- Support analysis at a finer grain than the product-level Sales dataset
Required fields
| Field | Description | Type | Use | Notes |
|---|---|---|---|---|
product_id | Unique identifier for the product SKU. | string | Application / Presales | Required. Primary key. Foreign key to product. |
location_id | Unique identifier for the store or location. | string | Application / Presales | Required. Primary key. Foreign key to location. |
product_variant | Identifier for the specific product variant (for example, size or colour). | string | Application / Presales | Required. Primary key. |
sold_at | Timestamp when the sale occurred. | timestamp | Application / Presales | Required. Primary key. |
created_at | Timestamp when the record was created. | timestamp | Application | Optional. |
sale_id | Source-system identifier for the sale. | string | Application / Presales | Optional. |
customer_id | Identifier for the customer associated with the transaction. | string | Application / Presales | Optional. |
sales_units | Net units sold, after returns. | integer | Application / Presales | Required. |
sales_value | Net sales value, after returns. | float | Application / Presales | Required. |
return_units | Number of units returned. | integer | Application / Presales | Required. |
return_value | Total value of the returned units. | float | Application / Presales | Required. |
demand_units | Number of units demanded or ordered. | float | Application / Presales | Optional. |
demand_value | Total value of the demanded units. | float | Application / Presales | Optional. |
returned_at | Timestamp when items were returned. | timestamp | Application / Presales | Optional. |
shipped_at | Timestamp when items were shipped. | timestamp | Application / Presales | Optional. |
updated_at | Timestamp when the record was last updated. | timestamp | Application | Optional. |
Usage notes
- Provide this dataset only where variant-level detail is required.
- Product and location identifiers must align with the Products and Locations datasets.
- Values should reconcile with the product-level Sales dataset.
Why this dataset matters
Variant-level sales let the solution analyse demand for sized or variant-based ranges that a single product-level record cannot represent.