Increff Merchandising Solution - Enterprise Release Notes

Following are the enhancements/fixes in MS Enterprise with the latest deployment

User Interface - 8.0.4

Application - 5.12.0

Algorithm - 12.19

The current release has been tested and will work best with Chrome version - 106.0.5249.119.

Allocating included styles on priority: Inclusion list styles which are not at stores will be prioritized before normal replenishment increasing the introduction of desired styles at the store
Logistically aligned movement suggestions: Pullbacks and ISTs now will be done on the Stock on Hand instead of Stock on Hand at store+Goods In-Transit for stores+Open Orders at the warehouse for stores
Intuitively disabled inputs: Constrain inputs that are not required when their parent inputs are disabled will be automatically disabled

By Default in the Replenishment with allocation runs, the tool prioritizes all the replenishments before doing any allocation
To prioritize the allocation of certain styles that are needed in the stores as part of inclusion, a new option has been introduced to choose to do allocation Inclusion immediately after replenishment allocation
This option is available in the setup section of the inputs page of the Replenish with Replace module

Running Allocation inclusions before replenishments

In the tool, during IST and pullbacks the whole store's initial quantity comprising of Store SOH, Open Orders at the warehouse and the Goods In Transit from warehouse to store were pulled out of the store if it was not required at the store.
Now the system will not be moving the GIT and OO from the stores and will move only the store stock already present in the store
While doing this, the system will check for health, and cover required at the store with just the store stock and by including both store’s initial stock and stock in movement before deciding to pull the stock at the store.
for eg: if the stock at the store is unhealthy, but the stock on hand + GIT+ OO is healthy for that store then the style will be considered healthy and will not be moved out of the store

There are some constrain-inputs in different modules that are dependent on another input being enabled
These will be automatically disabled when the the parent input is disabled

When 'Should Category level planogram be met?' is set to TRUE or 'Level at which planogram is defined' is at NO ATTRIBUTE, then the following factors will get disabled:
1. 'Set Up' → 'Breach factor for attribute planogram quantity'
2. 'Advanced' → 'Breach factor for attribute planogram options'
When 'Planogram Increment allowed?' is set to NO, then the following factors will get disabled:
1. 'Set Up' → 'Planogram Quantity Increment for Allocation'
2. 'Advanced' → 'Planogram Options Increment for Allocation'
When 'Should IRIS Assortment Plan be followed?' is set as NO, then the 'Assortment plan rollup level' will get disabled.
When 'Are pullbacks allowed?' is set as NO, then the 'Minimum Planogram Fill rate %' will get disabled.

When 'Should last cycle be considered?' is set as NO, then the 'ROS Factors' for Hold, Rollback, and Rollforward will get disabled.

In the Attribute group level Output in the distribution, the module helps us to check the ideal options needed at the store as per assortment plan vs fulfilment post distribution at a store+AG level.
To add more info to this output for easier comprehension, the % revenue contribution is added as a new column

In the OTB flow output, there are multiple steps pointing towards how the buy qty is calculated, to be more specific with the calculations, these quantities will be displayed with two decimal values

Please feel free to contact your account manager if you have any queries.

MS Enterprise Public