1. Home
  2. Iris X
  3. Help Section
  4. Masters Data

Masters Data

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.

ColumnDescription
STYLE_CODEStyle code of the product
SEASONSeason in which the Style was introduced. A style can be mapped to only one season
The tagging can be Core too, in cases where the Styles are repeated continuously and are not season specific
CATCategory to which the style belongs
SUBCATSubcategory of the style
GENDERGender of the style
BRANDName of the brand for which a particular article is belonged to in style master table , for example- a boys category white t-shirt belonged to X
SEGMENTType of brand (Private/External etc). Relevant for Multi brand retailer (Optional)
DESCRIPTIONBrief description of the Product to be used only for reporting (Optional)
MASTER_CATEGORYBroader classification of Categories to be used only for reporting (Optional)
IMAGE_URLLink to the image of a particular product
ATTRIBUTE 1Design attribute to be used for Attribute Grouping
For every Category (Eg. Shirts), attribute 1 can be Sleeves and for another category (Eg. T Shirts), attribute 1 can be colour

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

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.

ColumnDescription
EANEAN code of the style
STYLEstyle code of the product
SIZEsize of style
MRPMaximum Retail Price of the Product

Check for the following to avoid errors:

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.

ColumnDescription
CATEGORYCategory to which the style belongs
NAMEMRP Bucket name to be used in the Attribute Group. User can define them as M1,M2 etc. along with the minimum and maximum MRP of each bucket
MIN_MRPMinimum MRP for each price bucket (Inclusive)
MAX_MRPMaximum MRP for each price bucket (Inclusive)

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.

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

ColumnDescription
CHANNELChannel to which the Store belongs. Eg. Online, EBO etc
STOREName of the store
STORE_CODEUnique code of the store
CITYThe city in which the store is located
REGIONRegion to which the store belongs (East, West, North, South, Central)
ENABLEDIndicates if the Store’s data needs to be included in analysis. Value should be either 1 or 0 if a Store needs to be enabled/disabled respectively
ETL_NEWThis flag will be set to 1 whenever a new Store gets added during the inflow of transactional data. Helps the user in identifying the new stores so that they can update the remaining details
AREACarpet Area of the store in square feet. Used for Operational metrics like Sales per square foot etc for reporting purposes
CLASSRefers to Store Classification. Can be High Street/Mall/ Premium depending on the requirement (Used for reporting purposes)
BI_ENABLEDIndicates whether if the Store’s data needs to be considered for BI dashboards. Value should be either 1 or 0 if a Store needs to be enabled/disabled respectively
IS-ONLINEValue should be 1 if store is online, else 0 if offline
REPL_CYCLE_DAYSReplenishment frequency. Used to identify the quantity required during replenishments based on Rate of Sale

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

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, planogram is defined as 125 units.

ColumnDescription
ATTRIBUTE Refers to the attribute level (apart from the Category) at which the planogram is defined. Can be any of the attributes used for Grouping
Optional- Can be left blank if there are no such constraints
FRONT_OPTIONS Minimum Display options at the defined level (Store+Category/Store+Category+Attribute)
QUANTITYBase Stock Quantity requirement at the defined level (Store+Category/Store+Category+Attribute)

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

ColumnDescription
STORE_CODEunique code of a store
PERIODPeriod referring to the duration defined in the Analysis periods
REVENUERevenue target for the Store+ Period combination. Used for both Buying and Distribution

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

ColumnDescription
CHANNEL_NEW_STOREChannel type to which the new store belongs
NEW_STORE_CODENew Store code for which the reference store’s transaction data will be used. Should be used when the store is new or doesn’t have sufficient data
CHANNEL_REFERENCE_STOREChannel type to which the reference store belongs
REFERENCE_STORE_CODEDemand pattern from this Store will be used for the corresponding new store

Category size Sequence:

Provides the list of relevant size sequences for each category.

ColumnDescription
CATEGORYCategory to which the size belongs
SIZE_SEQUENCEComplete list of relevant sizes separated by # for every category. Would be used to ensure the size continuity while distributing the stock. Eg., XS#S#M#L#XL#XXL#XXXL
If a Category has multiple size sequences (Eg. S,M,L,XL and 26,28,30,32), then they can be entered as two different entries

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

ColumnDescription
STYLE_CODEStyle code which needs to be mapped to an existing/older Style code
PARENT_STYLE_CODEParent Style code to be used in cases where same design/ product has different Style codes. Used for reporting purposes too

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.

ColumnDescription
CLIENT_SIZESize naming followed by the clients in the Master
SIZEStandard Size to be followed if the same size is named differently in the EAN master
Eg., Both XXL and 2XL can be mapped to XXL so that IRIS treats both the entries in the master as the same

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

Minimum quantity per style to be followed for every Store + Category + Sub-Category combinations. 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.

ColumnDescription
CATEGORYCategory to which the size set belongs
SUBCATEGORYSubcategory to which the size set belongs

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.

Was this article helpful to you? Yes 4 No

How can we help?