Inputs

Wherever Replace/Replenish is mentioned, it can also be replaced with Inter-Store Transfer, Fresh Allocation or Replenishment depending on the type of distribution you are running.

1. 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 columns to 1 for the stores to be considered and uploaded.

2. 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.

3. 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

4. Where do I define the period for ROS calculation?

   • Go to Distribution ->Replace/Replenish -> Configure -> ROS Calculation. Change the ROS periods. Please note that the period duration must be in increasing order.

5. 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)

6. 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

7. At what level can I run Inter-Store Transfer (IST)?

   • You can run IST at a city level or a region level. If you want to run the IST at the channel-region/city level then replace the city/region column with a concatenation of channel+city/region.

8. I don’t want to consider GIT/Open orders in my distribution run. How do I disable them?

   • Go to Distribution -> Replace/Replenish-> Configure -> Stock Selection -> GIT/ Orders to be considered -> No

9. I only want to outward from a store during IST. How do I disable inwards?

   • Go to Setup -> Master data -> download store master. Change the inwards column to 0 and the outwards column to 1 for the required store(s).

10. I only want to inward to a store during IST. How do I disable outwards?

    • Go to Setup -> Master data -> download store master. Change the inwards column to 1 and the outwards column to 0 for the required store(s).

Outputs

1. How do I check the reason for non-allocation for a store-SKU combination?

   • Log in to the UI. Go to Setup -> Distribution -> Reports -> Log in to Tableau -> Go to reasons non-allocation -> Select the Store/Style/Category which you want to check.

2. Why is the CBS in the output file not matching the CBS from the input (End Date Stock) file?

   • The product takes the sum of CBS + GIT + Open orders as initial stock at a store.

3. How do I check the warehouses considered for the run and change their priority?

   • Go to Distribution -> Replenish/Replace -> Upload Data -> Warehouse store category map. This has all the warehouses considered at a store-category level.

4. How do I download distribution outputs?

   • Go to Distribution -> Replace/Replenish -> Reports -> Download Reports

5. What could be the reason for no allocation happening for an entire category?

   • Check if the planogram is present for that category, warehouse stock is present with size continuity, styles of that category are present in the style list and the planogram has space for allocation

6. What can be the reasons for non-allocation?

   • Planogram not present – Please download the planogram from master inputs and check if the planogram for the store category combination is present.

   • Style not present in style list – Please download style-level merchandise tagging from module inputs and check if the style is present in it.

   • Store doesn’t have space – Please download the Fill-rate report from output reports and check if the fill rate is 100%. 100% fillrate means that 100% capacity of the store is utilized.

   • Styles not present in continuous sizes – Please check if the remaining warehouse stock has stock present in continuous sizes. (If a style has 30,32,34,36,38 sizes and size 34 has 0 remaining qty, it won’t get allocated to a store).

   • Warehouse stock is not present- Please check if warehouse stock is present for that style from the warehouse stock output report.

   • Warehouse not considered – Please download the warehouse store category map input and check if the warehouse is present in the warehouse column.

   • Max SKU depth is reached – This means that the max depth constraint for the size is less than the depth we are suggesting. Please go to max SKU depth input to change the size depths.

7. Can I send a story/ collection even if only 70% of the styles are present?

   • Yes. You can define the minimum percentage of styles that should be present in a story for it to be eligible for allocation.

   • 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.)

General FAQs

1. Planogram was given for a certain store category but still got the planogram limit was exceeded.

• Present inventory in-store stock is already equal to/ greater than planogram stocks.

• Planogram is specified at the attribute level and a certain store style has a different attribute.

1. Store style iteration flag > 0, but the remark still says that the planogram limit is exceeded.

• Since allocation for Pivotal And Non-pivotal sizes separately, the planogram might get filled after Pivotal allocation and before NP allocations, in such cases, the remark will come against all NP sizes.