Sales extra dataset

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

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	Primary key Foreign key to product
location_id	Unique identifier for the store or location.	string	Primary key Foreign key to location
product_variant	Identifier for the specific product variant (for example, size or colour).	string	Primary key
sold_at	Timestamp when the sale occurred.	timestamp	Primary key
created_at	Timestamp when the record was created.	timestamp	Nullable
sale_id	Source-system identifier for the sale.	string	Nullable
customer_id	Identifier for the customer associated with the transaction.	string	Nullable
sales_units	Net units sold, after returns.	integer	Non-null
sales_value	Net sales value, after returns.	float	Non-null
return_units	Number of units returned.	integer	Non-null
return_value	Total value of the returned units.	float	Non-null
demand_units	Number of units demanded or ordered.	float	Nullable
demand_value	Total value of the demanded units.	float	Nullable
returned_at	Timestamp when items were returned.	timestamp	Nullable
shipped_at	Timestamp when items were shipped.	timestamp	Nullable
updated_at	Timestamp when the record was last updated.	timestamp	Nullable

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.