Question	Answer
Why is warehouse dispatch report coming blank?	Check store list, planogram, warehouse stock, end date, consider warehouse stock flag
How do I change the stores considered for runs?	Log in to the UI. Go to Setup -> Master data -> download store master. Change the enabled and dist_enabled column to 1 for the stores to be considered and upload.
How do I select the seasons for which I want to run distribution?	From the side menu go to Distribution -> Replace/Replenish -> Configure -> Stock Selection -> Relevant season merchandise for distribution. Select the seasons for which you want to run distribution from the multi-select dropdown.
How to change the style season tagging list?	• Log in to the UI. Go to Distribution -> Replenish/Replace -> Upload data -> Style Level Merchandise Tagging. Add/change the styles to be considered for the run and upload. Some guidelines to keep in mind:
• Style should be present in style master
• Duplicate styles should not be present.
• One style can’t have multiple seasons tagged against it within a channel
Where do I define the period for ROS calculation?	Go to Distribution ->Replace/Replenish -> Configure -> ROS Calculation. Change the ROS periods. Please note that period duration must be in increasing order.
How do I allocate a group of styles?	• Go to Distribution -> Replace/Replenish -> Upload data -> Story Style List. Add the group wise list of styles
• Go to Distribution -> Replace/Replenish -> Configure -> Advanced -> Minimum percentage number of styles to send in a group. Change this to the value that you want. (If the value of “Minimum percentage number of styles to send in a group” is 90. This group will only go to a store if at least 90% of the styles present in the group are available)
How do I increase the planogram?	• If you want to increase the planogram limit at an overall level, Go to Distribution -> Replace/Replenish-> Configure -> Planogram Increment Limit for Replenishment/ Planogram Increment limit for Allocation.
• If you want to increase the planogram of a certain store-category combination, go to Setup -> Master data -> Planogram and re-upload the file
Why are there no remarks printed when replenishment doesn't happen due to pack size condition(requirement>pack size/3)	“Pack sizes input is given” remark is printed in such cases
why size tag is coming as blank/untagged?	You have to give this tagging in the style level merchandise tagging input (cat size sequence)
Why sales are not getting printed in ROS calculation period	Sales in ROS period can be checked from Final store level output
Why is warehouse Inventory and warehouse dispatch reports are showing empty for a completed run.	WH stock for some client is truncate file and hence is updated everyday. As a result when run is done for the previous day, there is no WH stock present for that date so warehouse inventory will come blank
How to correct validation error- No sku is live on the end date: yyyy-mm-dd. Please check for Season list, Warehouse mapping and End date stock- data is uploaded as on today in DB	Merchandise tagging is mentioned as fresh, and stock selection was selected as replenish, so the merchandise tagging as well as the stock selected for replenish should be selected same
Where do we print existing stocks more than planogram in remarks and suggested allocation = 0.
and where do we print existing stocks more than planogram in remarks and suggested allocation >1?	If store inventory is already greater than or equal to planogram, we will get this remark.
If running is without pullbacks alloc_suggested will be there in the places where there is some Healthy store stock.
If there is no store stock, you may get this remark with alloc_suggested as 0
In cases where there is no initial store stock and suggested alloc = 1 with this remark, check GIT and open orders as store stock+GIT+openorders are considered to give suggested alloc suggestion.
1. a. I am checking the store style ranking for 2 style codes 128662, 136173 at a store LKST889 for Lenskart. the ranking as we discussed is done in a descending order that is a store + style combination with the highest revenue will have rank 1. then rank 2 for store+style combination with the second highest revenue. and this ranking is done basis final_rev_per_day (weighted rev per day of all 17 levels) in interim_dist_store_style_ranking table. if that is the case then the ranking here looks wrong as higher revenue combination should have lesser rank but here its the opposite.

1. b. for this style 136173 in store LKST889, we have revenue in the last 1 month (22nd july to 22nd Aug) as 3500, sales in the last 1 month as 1pc and MRP of the style is 3000, healthy days live is also 17 and still the rev per day is coming as 0 in level 1 in the store style rank table image above. Can you check on how can this happen? | 1.a. Styles which have sales in recent period is given priority in ranking(level01) Those styles are ranked first. Others are ranked separately based on final rev per day. And then we take the combined list. ROS and sales is defined for 'period 1 ROS input while ranking is done basis 'duration in month to analyze ranking and top seller' input 1.b. So there is a additional check, for a style to be considered for level 1,it should be a top seller or store inventory should be greater than zero so first we would rank all styles which have rev per day in level 1 after it qualifies these criteria. then from level 2 to level 17 it will just calculate rev per day for all styles in a store, and once we calculate final rev per day basis the weightages, then the ranking is done for remaining styles. | | Why the style is being tagged as a top seller at a store LKST759 and still suggested_alloc is coming as 0, remarks have PSA percentage low which should not affect the suggested_alloc value. Can you please share why PSA percentage low is coming as a remark and affecting the suggested_alloc? | PSA benchmark low remark doesn't affect suggested_alloc in case of Lenskart | | Sales in period 1 were recorded for a particular PID but ROS for period 1 was zero and recent sku ros was same as period 2 ROS. How so? | Period 1 ROS for these PIDs is zero here as the no. of healthy live days does not match the min. days benchmark set of 15 days for ROS to be calculated. For the ROS calculation, since the ROS for period 1 is zero here - the weightage given to this period is carried over to ROS of period 2 while calculating recent sku ros. As a result, the weightage assigned for ROS of period 2 is 75% + 25% while calculating recent sku ROS in these cases, and the weightage defined for ROS of period 3 is 0% so we don't consider it. | | Particular category was now showing up in WH store cat map template even though it was present in style master and enabled in category config. Why so? | This category was missing from the brand category which also need to be updated in order for the category to show up in the WH store cat map template. |