Content Comparison

Style Master

Master table containing information about styles like Category, Brand, etc.

...

1. Check for duplicates and also if one style has more than one set of attributes

2. Each Brand-Cat-Subcat-Gender-MRP bucket combinations must be present in attribute masters

3. Check for 0 and negative MRPs

4. Check for spelling errors across all fields (like Shorts, Short)

EAN Master:

Master table containing the EAN/SKU to Style_code mapping.

...

1. All SKUs should be unique (no 2 SKUs should have same Style + size combination)

2. Check for duplicates

3. All sizes should be present in Cat Size Sets

4. All styles must be present in Style masters 5.Parent Child mapping file to be created in case of duplicate style size combinations

Price Bucket:

Specifies the buckets into which the MRPs of the styles can be grouped for each Category. The system does this grouping automatically by picking MRP values from the EAN master.

...

Each category can have one or more price bucket names and the minimum and maximum MRP in that price bucket. Eg: if ‘M1’ is the name and min_mrp=0 and max_mrp=999, then the price_bucket would be ‘M1-0-999’.

Store Master:

Master table containing the store related information such as channel, region, area etc.

...

1. No 2 store IDs and names should be the same

2. All partners must have the same spelling (like amazon/amazon.com should not exist)

3. Correct list of active and inactive stores must be there

4. New Stores if present should be mentioned and enabled 5. Enable only active stores

Planogram:

Specifies the store’s capacity in terms of options and quantity for every store+ category combination. In allocation/replenishment, the system compares the existing inventory at the store with this value to fill the gaps. 

...

1. All Store IDs should be present in Store Master

2. Planogram & Size Set values can not be negative

3. All the Brand-Categories should be present in the attributes master

4. No duplicates should be present across Store – Brand – Category

Annual Operating Plan (AOP):

Provides the revenue target for each store. 

...

1. All store IDs should be present in Store Master

2. Months should be in ‘yyyy-mm’ format

3. Revenue can not be negative or 0

4. Months should be forecast months (future months)

5. Number of forecast months should be same as number of revenue split start and end date months

Reference Store Mapping:

New stores are provided with a 1:1 mapping with existing stores as reference stores.

Category size Sequence:

Provides the list of relevant size sequences for each category.

...

Specifies the category + subcategory that is JIT at a Store.

JIT Categories:

If the value is 1, it is treated as a JIT combination otherwise it is OTC. This input if left blank or skipped for some stores/categories will lead to those category + subcategory combinations at a store being considered as OTC.

JIT Categories: Specifies the Categories + Sub categories that are JIT in the Stores. IS_JIT columns value can be 1 if it is a JIT category + Subcategory at that store and 0 if over the counter

Style Parent Mapping:

Provides Mapping of Styles with Parent Style if the brands have different Style codes for the same product.

...

Size Mapping: Provides the mapping of standard sizes in cases where there are multiple names for the same size

Size Mapping:

Provides the mapping of standard sizes in cases where there are multiple names for the same sizes.

...

Size set: Minimum Quantity per Style to be followed for every Store+ Category+ Sub Category combinations. Used in Distribution and Buying

Size Set:

Minimum quantity to be sent in a style when being sent to the store for the first time (as a fresh allocation).

...

Style MRP:

This table is only consumed if SKU level data is not present. If SKU is available then it will be used over MRP.