2. Home
  4. Iris M
  6. File Formats

File Formats

Various inputs required by the system are given below. Note that Masters are crucial for data validation. If your sales, planogram, AOP inputs contain data which are not in the master, then the system will not upload that data and an error will be shown on the screen. 
All data must be uploaded in TSV format (tab separated values). You can always store your Excel files using TSV format. We don’t use CSV, as it creates issues in reading data when the values contain a comma.

Data Format
Stores Master List of all stores. We do not support new stores currently.

  • partner_id represents your store partner network. E.g. Amazon, EBO (exclusive brand outlets), Costco (a partner chain) etc.
  • region represents how you’ve divided your stores into regions. This helps in understanding your business in and across regions
  • store_id represents a unique identifier for your store. It must be unique across all rows.
  • enabled represents if a store is enabled or not. Value 1 represents enabled and value 0 represents disabled.
partner_id region store_id store_name enabled
EBO south BLR_123 Bangalore Indranagar Outlet 1
EBO south BLR_124 Bangalore Indranagar Outlet 1
Amazon country AmazonStore Amazon E-Commerce 1
Alibaba country AlibabaStore Alibaba E-Commerce 0
Attributes Master Valid data ranges to accept for styles attributes, e.g. brand, category. All your sales data is clustered using these attributes.

  • The mrp_bucket parameter is used to identify MRP range for that style. Example, it could be 101-200, 201-300 etc. Another example could be LOW, MEDIUM, HIGH. This parameter helps us understand what MRP price ranges your customers are comfortable in buying.
brand category subcategory gender mrp_bucket
Victor’s Secret shoe casual shoe M 101-200
Victor’s Secret shoe casual shoe M 201-300
Styles Master All styles along with their attributes are uploaded in this file. All sales data is clustered using these attributes.

  • The style parameter must be an ID (not a name) and must be unique for all styles.
  • The mrp_bucket parameter is used to identify MRP range for that style. Example, it could be 101-200, 201-300 etc. Another example could be LOW, MEDIUM, HIGH. This parameter helps us understand what MRP price ranges your customer’s are comfortable for buying.
  • The image_url parameter may be used to specify the image location for a style.
  • enabled represents if a style is enabled or not. Value 1 represents enabled and value 0 represents disabled.
style brand category subcategory gender mrp mrp_bucket image_url enabled
S3001 Victor’s Secret Shoe Casual Male 99.90 50-100 http://vs.com/s3001.img 1
S3002 Victor’s Secret Shoe Formal Male 102.90 101-150 http://vs.com/s3001.img 0
Category Size Set Master All valid sizes for different brand, categories, subcategories and gender are provided here.

  • The size_exit_flag flag tells the system whether to exit a size from the store, if it is not selling well there. This is generally relevant only where number of sizes is too large (e.g. Lingerie). Value 1 means the size exit is enabled, while value 0 means size exit is disabled.
brand category subcategory gender sizes size_exit_flag
Victor’s Secret shoe casual shoe M 6,7,8,9,10,11,12 1
Victor’s Secret shirt tshirt M s,m,l,xl,xxl 1
Victor’s Secret shirt formal M 32,34,36,38,40 1
SKU Master All SKUs, which style they belong to, and their sizes are uploaded in this input.

  • sku is the SKU barcode (e.g. EAN). Must be unique across rows.
  • style and size must refer to the inputs above
sku style size
1239878987 S3001 6
1239878989 S3002 8
Sales Daily sales data for every store and SKU

  • date must be in yyyy-mm-dd format
  • revenue is daily aggregated value.
  • discount will be calculated using revenue, MRP and quantity (discount = (MRP * quantity) – revenue). The MRP is used from the style data.
  • large data can be uploaded in multiple smaller file chunks
  • sales data is updated every time you upload a file. If a new day, store_id and sku combination is uploaded, it is treated as a new entry. However, if an existing day, store_id and sku combination is uploaded, the corresponding revenue and quantity is updated.
  • delete option is provided to delete sales data for a store or within a given date range
day store_id sku revenue quantity
2018-01-18 BLR_123 1239878987 74.00 1
2018-01-18 BLR_123 1239878989 198.60 2
2018-01-19 BLR_123 1239878987 74.00 1
Parent Child Sku Mapping (Optional) Mapping of child to parent SKUs

child_sku parent_sku
EAN1 EAN4
EAN2 EAN4
EAN3 EAN4
New Store Mapping (Optional) Mapping of new stores to reference stores

new_store reference_store
STORE999 STORE101
STORE1000 STORE154
AOP Annual Operating Plan at Store level. This corresponds to the revenue target for each store for each month.

  • month must be in yyyy-mm format
  • revenue is the targeted monthly revenue. This cannot be derived, as one may change targets based on changing business conditions (e.g. working capital, promotions etc.).
store_id brand month revenue
BLR_123 Victor’s Secret 2021-01 80000
Store Planogram Store planogram corresponds to the capacity for each store for each category. Further

  • size_set_qty is the quantity of a style which should be sent to a store while allocating.
store_id brand category capacity size_set_qty
BLR_123 Victor’s Secret shoe 100 4
BLR_123

Victor’s Secret

 shirt 200 3
Store Stock Current store stock

store_id sku quantity
BLR_123 1239878987 8
BLR_123 1239878989 4
Warehouse Inventory Combined inventory across all warehouse on sku level

sku quantity
1239878987 70
1239878989 32
Category Style Size Quantity (Optional) Minimum number of sizes required to distribute per style

brand category subcategory gender min_size_qty
BRAND1 JACKET ZIPPER MALE 2
BRAND1 TROUSER SLIMFIT MALE 2
Key Size Override (Optional) Key Size Override input at a Store – AG level

store_id brand category subcategory gender size_set
Blr_123 BRAND1 JACKET ZIPPER MALE S,M,L,XL
Blr_123 BRAND1 TROUSER SLIMFIT MALE 28,30,32,34,36
RU Sales Daily regional utilization (RU) transactional sales data for each pincode and SKU

  • partner is the sales channel
  • date must be in yyyy-mm-dd format
  • pin_code is customer order pincode
  • quantity is daily aggregated value
  • revenue is daily aggregated value
  • Large data can be uploaded in multiple smaller file chunks
  • RU sales data is updated every time you upload a file. If a new day, pincode and sku combination is uploaded, it is treated as a new entry. However, if an existing day, pincode and sku combination is uploaded, the corresponding revenue and quantity is updated.
partner day pin_code sku revenue quantity
Amazon 2018-01-18 560068 124987898 74.00 1
Alibaba 2018-01-18 110010 125987898 198.60 2
Myntra 2018-01-19 400029 123987898 74.00 1
Partner Pincode – Warehouse Map Ideal Regional warehouse source mapping for each pincode for every sales channel

partner pin_code wh_id
Amazon 560068 BGLR
Alibaba 110010 DEL
Regional Warehouse Capacity Stock capacity for each regional warehouse

wh_id capacity
BLR 1,00,000
BLR_123 2,00,000
Regional Warehouse Stock Current regional warehouse stock

wh_id sku quantity
BLR 123987898 8
DEL 125987898 4
Mother Warehouse Stock Mother warehouse stock that needs to be distributed among regional warehouses.

sku quantity
123987898 8
125987899 4
Returns Daily returns data for every store and SKU

  • date must be in yyyy-mm-dd format
  • quantity is daily aggregated value
  • revenue is daily aggregated value
  • discount will be calculated using revenue, MRP and quantity (discount = (MRP * quantity) – revenue). The MRP is used from the style data.
  • reason is the reason due to which the product return was initiated
  • large data can be uploaded in multiple smaller file chunks
  • returns data is updated every time you upload a file. If a new day, store_id and sku combination is uploaded, it is treated as a new entry. However, if an existing day, store_id and sku combination is uploaded, the corresponding revenue and quantity is updated.
day store_id sku revenue quantity reason
2018-01-18 BLR_123 1239878987 74.00 1 Size & fit
2018-01-18 BLR_123 1239878989 198.60 2 Look & feel
2018-01-19 BLR_123 1239878987 74.00 1 Bad Quality
Historical Annual Plan (AOP) Past/Historical Annual Operating Plan at Store level. This corresponds to the past AOP for each store for each month.

  • month must be in yyyy-mm format
store_id brand month revenue
BLR_123 Victor’s Secret 2019-01 80000
Store Stock Last day store stock

store_id sku quantity
BLR_123 1239878987 8
BLR_123 1239878989 4
Warehouse Stock Combined inventory across all warehouse on sku level, at the last day

sku quantity
1239878987 70
1239878989 32
Style Attributes Style wise attributes input for attribute level STR report

style attribute1 attribute2 … attribute9 attribute10
STYLE10246 Black Slim Fit … Cotton Printed
STYLE10249 Brown Straight Fit … Denim Non-print
Online Analytics Daily sales and page views for each style for every sales channel.

  • The style parameter is your style code/listing id/style id listed on marketplace and it must be an ID (not a name) and must be unique for all styles.
  • partner represents your online marketplace platform.
  • brand is your brand name.
  • day must be in yyyy-mm-dd format.
  • category represents your style attribute like dresses, shirts etc.
  • revenue is a daily aggregated value of income generated by sales of goods.
  • quantity is a daily aggregated value of quantity sold.
  • page_views is a daily aggregated value of the total number of pages viewed. Repeated views of a single page are counted.
style partner brand day category revenue quantity page_views
S3001 Amazonia Victor’s secret 2020-01-18 Casual shoe 102.40 1 5137
S3001 Clickart Victor’s secret 2020-01-19 Tshirt 198.60 2 24513

Was this article helpful to you? Yes 3 No 1

How can we help?