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? |
|
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? |
|
How do I increase the planogram? |
|
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. | If store inventory is already greater than or equal to planogram, we will get this remark. |
| 1.a. Styles which have sales in recent period is given priority in ranking(level01) 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. |
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. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article