1. Home
  2. IRIS ENTERPRISE
  3. Help Section
  4. Masters Data

Masters Data

Style Master: Master table containing information about styles like Category, Brand, etc

ColumnDescription
STYLE_CODEStyle code of the 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
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
MASTER_CATEGORYBroader classification of Categories to be used only for reporting (Optional)
DESCRIPTIONBrief description of the Product to be used only for reporting (Optional)
BRAND_SEGMENTType of brand (Private/External etc). Relevant for Multi brand retailer (Optional)

EAN Master: Master table containing the EAN/SKU to Style_code mapping

MRP Bucket: Specifies the buckets into which the MRPs can be grouped for each Category

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

Store Master: Master table containing the Store related information such as Channel, Region, Area etc

ColumnDescription
CHANNELChannel to which the Store belongs. Eg. Online, EBO etc
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
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
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
DIST_ENABLEDIndicates whether the Store should be considered for Stock distribution/ IST. Value should be either 1 or 0 if a Store needs to be enabled/disabled respectively
REPL_CYCLE_DAYSReplenishment frequency. Used to identify the quantity required during replenishments based on Rate of Sale

Planogram: Specifies the Store capacity in terms of options and quantity for every Store+ Category combination

ATTRIBUTERefers 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_OPTIONSMinimum Display options at the defined level (Store+Category or Store+Category+Attribute)
QUANTITYBase Stock Quantity requirement at the defined level (Store+Category or Store+Category+Attribute)

Annual Operating Plan: Provides the period-wise revenue target for each Store for future periods. The period for which AOP is needed is dependent on the period in input periods.

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

Reference Store Mapping For New Stores: Provides reference stores for all the new stores

ColumnDescription
NEW_STORENew Store name 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_NEW_STOREChannel type to which the new store belongs
REFERENCE_STOREDemand pattern from this Store will be used for the corresponding new store
CHANNEL_REF_STOREChannel type to which the reference store belongs

Category Size Sequence: Provides the list of relevant size sequences for each Category

ColumnDescription
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

Style Parent Mapping: Provides Mapping of Styles with Parent Style if the brands have different Style codes for the same product (Optional Input)

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

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

Was this article helpful to you? Yes 3 No

How can we help?