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.

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

• Adding new file deletes the data already present and the latest input is utilized

• store_id must be unique

Product Master

Master file consisting of all SKU and Style details like Category, Subcategory, MRP etc.-

• SKU is the SKU barcode (e.g. EAN). Must be unique across rows

• Style is the ID of the style to which the SKU belongs to. This parameter must be an ID (not a name)

• The image_url parameter may be used to specify the image location for a style.

• style_enabled represents if a style is enabled or not. Value 1 represents enabled and value 0 represents disabled.

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.

• Adding new file deletes the data already present and the latest input is utilized

• Brand + Category + Subcategory + Gender combination must be unique

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.

• Data present already is updated and new rows are added when a new file is uploaded.

• Style must be unique.

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.

• Adding new file deletes the data already present and the latest input is utilized

• Brand + Category + Subcategory + Gender must be unique

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

• Data present already is updated and new rows are added when a new file is uploaded.

• SKU/EAN must be unique

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

• Data present already is updated and new rows are added when a new file is uploaded.

• Store + SKU + Day combination must be unique

• Sales delete functionality available.
  If there are duplicates within a file, the revenue, qty and discount are added up

Parent Child Sku Mapping

(Optional) Mapping of child to parent SKUs

New Store Mapping

(Optional) Mapping of new stores to reference stores

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

• Adding new file deletes the data already present and the latest input is utilized

• Store + Brand + Month combination must be unique

• Brand column can be either empty for all rows or it should be present for all rows

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.

• Adding new file deletes the data already present and the latest input is utilized

• Store+Brand+Category combination must be unique

• Brand/Category column can be either empty for all rows or it should be present for all rows.

Store Stock

Current store stock

• Adding new file deletes the data already present and the latest input is utilized

• Store + SKU combination must be unique

• Duplicates if present are added

Warehouse Inventory

Combined inventory across all warehouse on sku level

• Adding new file deletes the data already present and the latest input is utilized

• SKU must be unique

Category Style Size Quantity

(Optional) Minimum number of sizes required to distribute per style

Key Size Override

(Optional) Key Size Override input at a Store – AG level

RU Sales

Daily regional utilization (RU) transactional sales data for each pin code 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.

• Data present already is updated and new rows are added when a new file is uploaded

• Pincode + Partner + SKU + Day combination must be unique

• Sales delete functionality available.If there are duplicates then revenue and qty are added up

Partner Pincode – Warehouse Map

Ideal Regional warehouse source mapping for each pincode for every sales channel

• Adding new file deletes the data already present and the latest input is utilized

• Partner+Pincode combination must be unique

Regional Warehouse Capacity

Stock capacity for each regional warehouse

• Adding new file deletes the data already present and the latest input is utilized

• Warehouse Id must be unique

Regional Warehouse Stock

Current regional warehouse stock

• Adding new file deletes the data already present and the latest input is utilized

• Warehouse ID + SKU combination must be unique

• If there are duplicates, the quantity is added up

Mother Warehouse Stock

Mother warehouse stock that needs to be distributed among regional warehouses.

• Adding new file deletes the data already present and the latest input is utilized

• SKU must be unique

• If there are duplicates, the quantity is added up

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.

• Data present already is updated and new rows are added when a new file is uploaded

• Store + SKU + Day + Reason combination must be unique

• If there are duplicates, the revenue and qty are added up

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 Stock

Last day store stock

Warehouse Stock

Combined inventory across all warehouse on sku level, at the last day

Style Attributes

Style wise attributes input for attribute level STR report

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.

• Data present already is updated and new rows are added when a new file is uploaded

• Partner + Style + Day