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

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