Release 25.1

Summary

Added a flag to toggle the key size continuity check for Replenishment Iteration in Distribution
Added a flag to toggle the new allocation of cut and fringe sizes
Key Sizes Override file input to override Iris M key sizes
Parent-Child SKU Mapping file input to map child SKUs to parent SKUs

A flag to check key size continuity in the replenishment iteration is introduced in the Distribution module
The flag helps the business take more granular calls for certain styles, hence enabling them to have more control over continuity checks while replenishing styles
With this brands will have an option to replenish styles only if key sizes are available (flag enabled) or if continuous sizes are available (flag disabled)
Example: For STYLE1, if S, M, L, XL, XXL are the sizes present and S, M, L are the key sizes. The style will be replenished only if S, M, L are available in the store after replenishment. When the flag is disabled, only continuity will be checked and style will be replenished if any three sizes are continuous (For e.g. if L,XL,XXL are available and S,M are not available, still this style will be replenished to the store if the flag is disabled).

Key Sizes	S,M,L
Sizes	XS	S	M	L	XL	XXL
Sales in replenishment period	1	3	5	5	2	1
Store Stock	3	0	0	0	2	4
Warehouse Stock	0	0	0	10	10	10
Replenishment(flag enabled)	0	0	0	0	0	0
Replenishment(flag disabled)	0	0	0	5	2	1

A flag to allocate/ not allocate cut or fringe sizes in the new allocation is introduced in the Distribution module
Since brands buy cut/fringe sizes in limited quantities they might want to send it to only specific stores it was bought for or only in limited quantities. This flag will help business take more granular calls for these styles, hence enabling them to have more control over the distribution
With this brands will have an option to allocate at least one piece in cut/fringe sizes even if a size doesn’t have any past sales with flag enabled
Disabling this flag, will lead to no allocation of cut/fringe sizes which doesn't have any past sales
Example: In STYLE1, S, M, L, XL, XXL are the sizes present and XXL has zero sales in the past, i.e, analysis period, then the tool allocates one piece in XL, considering warehouse stock is present (when flag is enabled). With the flag disabled, that one piece will also not be allocated.

Key sizes override input is introduced in Distribution module
It is an optional input
The tool will calculate the key sizes for every store + product attribute level based on the past sales by correcting for liquidation, understocking, size cuts, recency, seasonality, events, rate of sales (sales volume & value)
With the key sizes override input, users can override the key sizes calculated by the system. This will help brands dispatch only if these key sizes are available in stock. Unavailability of any of these key sizes will lead to no-allocation
Example: For Store1, Brand1-TShirt-Slim Fit-Half Sleeves, S, M, L, XL, XXL are the sizes present and S, M, L are the key sizes calculated by the tool. All iterations in distribution are based on these key sizes. The user has given an override as M, L, XL. So, in all iterations in the distribution module, the allocation will be based on the overridden key sizes

Key Sizes calc. By IrisM	S,M,L
Key Sizes override	M,L,XL
Sizes	XS	S	M	L	XL	XXL
Sales	2	3	3	4	2	1
Store Stock	0	0	0	0	0	0
Warehouse Stock	0	0	15	15	15	15
Allocation(IrisM calc. Key sizes)	0	0	0	0	0	0
Allocation(Key sizes Overridden by brand)	0	0	3	4	2	1

Parent-child mapping input is introduced in the distribution module
Multiple EANs with the same style-size combination can’t be uploaded into the system
With parent-child mapping, the EANs with the same style-size combination can be tagged as parent-child and the tool will accept those EANs
- Example: SKU1 and SKU2 are the EANs with the same style-size STYLE1-L, earlier the user cannot upload these two EANs in the SKU master, either of those SKUs can be uploaded. With parent-child mapping, both the EANs can be uploaded by mapping them as parent-child in the input available in the distribution module. Tool will consider the total sales/stock/inventory cover of both the SKU1 and SKU2 for taking any planning/distribution calls
Also, if the user has two sizes that are inter-replaceable as a single size, with parent-child mapping those two sizes can be combined
- Example: If SKU1 is of size 30/30 and SKU2 is of size 30/32 and for the user, both the sizes are the same (replaceable) and the user is comfortable sending either of them, then these two EANs can be mapped as parent-child and these two EANs will be treated as one by the tool