...
Specifies the store + style combinations that should not be allocated/replenished. Store name can be left blank if a Style needs to be excluded from all the Stores or a channel name can be mentioned against the style to exclude it from all stores belonging to that channel. This list needs to be changed every time there is a change in the season.
This list needs to be given at the parent-style level. If either a parent/child style is present in the exclusion list, the entire family of styles will be part of the exclusion.
...
In case there are multiple styles for a single store in this list, the system decides the priority using its algorithm. This list needs to be given at the parent-style level. If either a parent/child style is present in the inclusion list, the entire family of styles will be part of the inclusion.
Warehouse Planogram:
Warehouse capacity - the total quantity that the warehouse can hold at a given point of time at a category level. The same can be set as target cover days of inventory in the replenishment cycle days column
...
JIT Style Depth Override:
For JIT styles, the over ride override depth in which the mentioned style has to be allocated and replenished where the default JIT depth of 1 is not sufficient
...
Defines the Maximum allowed quantity in Pivotal and Non-pivotal SKUs for every Store+ Category+ Sub Category combinationscombination.
Style Level Merchandise Tagging:
...
Store Category combination priority: The combination of categories that are allowed to be dispatched to a store in a story/theme/collection in case all the categories of the story/collection are not available. The priority defined here does not play any role in the order in which the combinations are dispatched.
Possible Pitfalls:
Getting in-season styles –
Desired The desired style is not in the output across all stores for a channel
It’s Its season is not given in the season list.
Season The season is overridden with some channels, and no store for that channel is present in the distribution store list.
Distribution failed with the “No style is live” error
No style belongs to the given season list.
Season tagging is overridden for incorrect channels.
2. Getting inventory for in-season styles –
End-date stock is not taken correctly
End The end date for the run , doesn’t match the date of the end date stock.
Style is not in season.
Store_inventory_flag is turned off.
GIT, Open orders, and IST in transit are not taken correctly
End The end date for the run , doesn’t match the date of the corresponding tables.
Style is not in season.
Git_inventory_flag is off.
Warehouse stock is not considered properly
End The end date for the run , doesn’t match the date of the corresponding tables.
Warehouse mapping is not given for a store category, or the table is empty.
Wh_stock_alloc_flag is set to false.
Style is not in season.
Distribution failed with “No style is live” error – All the above-mentioned errors can cause this error.
...
A style is not present in the distribution output
It was not present in the in-season style style list.
Inventory was not present for the style.
Distribution failed with the “No style is live” error
No in-season style was present in the inventory.
Calculating size depths –
No allocation happened for a store style
Size The size set may not be there for the Store-cat-subcat combination.
Incorrect allocation happened for a store style
Size The size set may not be there for the Store-cat-subcat combination and suggested allocation might be coming only from ROS, so for zero ROS store skusSKUs, alloc_suggested is zero.
...
Incorrect warehouse stock in distribution output :
Some inventory got removed due to warehouse inefficiency.
Some inventory got reserved due to lead time.
...
ROS is zero/incorrect even though sales is are there
Sales might have been cleaned up, check cleanup benchmarks
Sales might not lie in the ROS period.
It is USPL.
Top seller identification –
A style is incorrectly identified/Not identified as a top seller
Check benchmarks for top seller identification.
If a style is not identified as a top seller then sales might have been cleaned up.
...
A store style is not present in the final distribution output
There was no sales present even at the channel category level for the store style.
Total The total inventory available in the store and warehouse for the store style is zero.
Rev Per Day for a store style is printed wrongly
Sales might have been cleaned up for the store style.
It is a new store, and the rev per day printed is from the reference store.
It is a parent parenting style and revenue and live days are coming from child styles.
...
Store Style 1 is below/above Store Style 2 even though Store Style 1 is better/worse than store style 2
It can happen for store style resolved at different levels, and store style which was resolved at a lower level can be better ranked because we have to maintain relative ranking for store styles resolved at the same level. For example There , there is a store style SS3 between SS1 And SS2 such that ranking is SS1 > SS3> SS2, where SS1 was better than SS3 because both were resolved at the same level and SS1 has better rev per day, and SS3 is better than SS2, so a comparison between SS2 and SS1 never happened.
A store style(SS1) with no sales is ranked above than a store style(SS2) which has sales
Store 1 might be a new store and rev per day was computed wrt reference Store.