Dynamic Markdown Help Section
- Alaf Azam Khan
- Shrutik Rajesh Talawat (Unlicensed)
- Abhist Srivastava
- Surya M
Store Grouping:
Defines the group of stores in which users would want to put the same discounts.
Column | Description |
|---|---|
channel | Store’s channel |
store_code | Store’s code |
discount_store_group | Grouping of stores for which we would like to offer discounts. Eg., All the stores within a store group will have the same discount recommendation for any style |
discount_flag | Indicates if the Store’s data needs to be included in Discounting analysis. The value should be either 1 or 0 if a Store needs to be enabled/disabled respectively |
Store Group Style Discount Override:
Discount that should be considered for the store group-style combination irrespective of the suggestion
Column | Description |
|---|---|
store_group | Store’s group |
day | the date on which the override should be considered |
style_code | Style’s code |
discount | discount that should be considered for the store group-style combination irrespective of the suggestion |
Style Grouping:
Defines a group of Styles(at any attribute level) for discounting, planned trading days, season type(OSM/NSM), and discount override
Column |
|
|---|---|
style_code | Style’s code |
style_group | Grouping of styles at any attribute level, for example, a grouping of styles can be at category level or within T-shirts you want to compare polos separately and round neck separately |
season_type | The season type of the style for example it could be OSM(Old Season Merchandize), NSM(New Season Merchandize), Fashion or Flexi |
lifecycle | The planned trading days/ lifecycle (e.g.,60,90,etc) of the style. |
discount_override | If there is a new season(NSM) and old season merchandise(OSM), brands may not want to change(increment) Discounting for certain styles of NSM. So we can add these NSM styles to the override. We will consider these override styles for comparison but still not change anything on them. Value could be 1 or 0 to consider or not consider style as an override respectively. |
category | Syle’s category |
subcategory | Style’s subcategory |
gender | Style’s gender |
brand | Style’s brand |
master_category | Style’s master category |
store_group | The store group for which this style grouping is to be followed |
Discounting Guardrails:
Guardrails at Brand/Category/ Season level to limit the maximum discount or to avoid offering a discount on good performers
Column | Description |
|---|---|
store_group | The store group for which the guardrails are being defined |
brand | Style’s brand |
category | Style’s category |
season_type | The season type of the style for example it could be OSM(Old Season Merchandize), NSM(New Season Merchandize), Fashion, or Flexi |
start_discount | Minimum discount put when a style is discounted for the first time |
max_discount | Maximum discount to cap discount increments |
incremental_discount | Percentage value by which the discount needs to be increased or reduced basis recommendation of Increase/Decrease in each cycle |
Discounting Engine Logic:
Discounting decision matrix with ROS, lifecycle (DOH+Age), and health as factors
Column | Description |
|---|---|
ros | Classification of unique ROS values as HIGH/MEDIUM/LOW in the product according to the benchmarks provided at store group style group level |
doh_ageing | Classification of unique Lifecycle(DOH+Ageing) values as HIGH/MEDIUM/LOW in the product by comparing it with the planned trading days of the style provided by the brand |
health | Classification of styles as HEALTHY/UNHEALTHY in the product according to the pivotal size benchmarks provided |
sell_through | Classification of sell-through values as HIGH/MEDIUM/LOW in the product compared to the values input by the user. |
action | Decision as Increase/Decrease/Continue according for the 3x3x2 matrix of ROS and Discount |
perc_of_max_discount | Flexible capping based on a combination of high-medium-low |
perc_of_discount_increment | Flexible increment based on a combination of high-medium-low |
Sell Through Benchmarks:
Defines the sell-through benchmarks at a category and lifecycle level.
Column | Description |
|---|---|
category | Style’s category |
lifecycle | Planned lifecycle of styles in the respective category |
min_live_days | Defines the bucketing of styles basis live days. Styles falling in the respective buckets will be compared with the given benchmarks for that bucket |
medium | Styles below high but above medium benchmark will be tagged with medium sell-through |
high | Styles above the high benchmark will be tagged with high sell-through |
GRN:
Day+Warehouse+SKU level GRN quantity. GRN resets aging – can be cases where it's in a warehouse but not at stores.
Column | Description |
|---|---|
warehouse | Warehouse name |
sku | EAN code |
qty | Quantity GRNed |
day | Day on which the SKU was GRNed |