Master's Data Help Section

Style Master

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

The style master is one of the most important tables and needs to be updated with caution. Key-value is the style code in this input. Frequent changing of category and subcategory values is not advised. Other dependent inputs work based on these combinations, and the system will throw an error if they aren’t revised accordingly.

Check for the following to avoid errors:

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

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

3. Check for 0 and negative MRPs

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

Maestro de estilo

Tabla maestra que contiene información sobre estilos como Categoría, Marca, etc.

El maestro de estilo es una de las tablas más importantes y debe actualizarse con precaución. El valor clave es el código de estilo en esta entrada. No se recomienda cambiar frecuentemente los valores de categoría y subcategoría. Otras entradas dependientes funcionan en función de estas combinaciones y el sistema arrojará un error si no se revisan en consecuencia.

Verifique lo siguiente para evitar errores:

1. Compruebe si hay duplicados y también si un estilo tiene más de un conjunto de atributos.

2. Cada combinación de depósito Brand-Cat-Subcat-Gender-MRP debe estar presente en los maestros de atributos

3. Verifique MRP 0 y negativos

4. Compruebe si hay errores ortográficos en todos los campos (como Cortos, Cortos)

EAN Master:

The master table that contains the EAN/SKU to Style_code mapping.

This has similar importance as the style master table and has to be dealt with in the same manner. The key value is style code and size in this input.

Check for the following to avoid errors:

1. All SKUs should be unique (no 2 SKUs should have the 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:

The master table containing store-related information such as channel, region, area etc.

For any addition of a new channel, change in the channel name, or store code, the support team should be approached and should not be done by the user. Ideally, only the store name, enabled column and distribution enabled columns should be modified by the users.

Note: The Store code in this file will be mapped to the store codes in the transactional data. Changing the store code will lead to having split data within the system leading to errors.

Check for the following to avoid errors:

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

Warehouse Master:

Contains the list of different Warehouses with the assigned IDs.

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. 

The system automatically generates this file based on the deficit calculation using the MBQ files and other guidelines. For eg., in STORE03 + shirts, the existing stock is 100 units and the deficit is 25 units, the planogram is defined as 125 units.

Check for the following to avoid errors:

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 style master

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

Annual Operating Plan (AOP):

Provides the revenue target for each store. 

AOP provides the period-wise revenue target for each Store for future periods.. The date range to which each period corresponds is set in the ‘Input Periods’ input.

Check for the following to avoid errors:

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. The number of forecast months should be the same as the 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.

Check the following to avoid errors:

1. Check if all sizes for a Brand-Cat-Subcat are in the same format (2D/UK sizing, S/M/L, Waist Sizes, etc.)

2. Check for size sequence

3. Check for duplicates

4. Convert cat size set column to string

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

JIT Categories: Specifies the Categories + Subcategories 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 sizes.

Size Set:

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

Minimum quantity per style to be followed for every Store + Category + Sub-Category combination. Used in Distribution and Buying. In the case of JIT combinations, the value here specifies the quantity to be reserved at the warehouse along with the 1 piece that is put for display.

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.