Send historical data

Why do we need data?

We use millions of data points to score purchases made by your customers with high accuracy and flag as many returns as possible. Data is provided by our partners: online shops, fashion brands and third-party services. The data we collect does not contain any personal information on your customers, and all data is anonymized.

With all this data, we leverage network effect in each market we operate in - with each new customer, each new data deposit, the predictions for all our partners improve. The more clients we have, and the more data we accumulate, the more value we bring to each of our clients. That’s why it’s important to contribute data from your order history at setup and on the daily basis thereafter.

Before going live

New clients (shops or third-party services) are urged to send us historical data at least for the 12 months preceding the launch. This initial dataset allows our algorithms to build predictions for your customers and brands sold at your shop, as well as learn the behaviors and order patterns specific to your customers and your shop.

An additional benefit, we will also use this initial dataset to build for you a report on behavioral insights and market trends report from this initial dataset. More information on the data format is below.

We are happy to assist you with data extraction and setting up automatic daily updates. Please contact us at info@easysize.me

After launch

After your launch our solution, we strongly recommend that you set up regular data updates to be sent to us. These updates should focus on sending new orders/returns/cancellations (deltas). Daily intervals usually work the best.

The data format should exactly follow your initial submission of historic data (more information below).

The easiest approach to regular data updates is through regularly scheduled automatic data extractions which send us the data extract in a CSV format via email or FTP.

How to send your data extracts

Regardless whether you’re sharing your historical data, or a daily update, please prepare the data file as follows:

  1. Compress the CSV file (zip would be best)
  2. Upload it to our SFTP server (Login details will be provided upon contact)

We take security and privacy of you, your customers, and your data very seriously and use highly secure SFTP (secure file transfer protocol) to secure your submissions. Details of our security can be found here

Data format:

To simplify the extraction and handling the data should be separated into transactions, catalog and users.

In order for your data to be easily processed into our system, please ensure it contains the following fields, and that these fields conform to the noted specifications

  • Fields marked with * are required
  • Transactions:

    Column name Type Formatting Notes
    user_id* Strings Any Your internal id for customers
    purchase_date* Strings Any date format (should contain year, month, day and time) Please let us know what format you use
    delivery_date Strings Any date format (should contain year, month, day and time) Please let us know what format you use
    return_date Strings Any date format (should contain year, month, day and time) Please let us know what format you use
    order_status* Strings Sent - for sent orders; Returned - for returns; Any additional statuses could be also provided Please let us know what statuses you track
    order_id* Strings Any Your internal order id
    product_id* Strings Any Your internal id for the purchased product (will be a reference for the catalog)
    discount Strings Discount in % (eg. 30%) If applicable
    return_reason Strings Any If applicable
    purchased_quantity* Strings Any Any additional attributes
    Strings Any Any additional transaction’s attributes

    Catalog:

    Column name Type Formatting Notes
    product_family_id* Strings Any Your internal id for the family of products (products that only differ in size)
    product_id* Strings Any Your internal id for the purchased product
    product_sku* Strings Any SKU of the product
    product_title* Strings Any A description of the product
    product_price Strings Price + Currency (eg. 123.2 EUR) Price for an item
    product_gender* Strings male, female, unisex or Other Gender of the purchased item
    product_brand* Strings Any Brand of the product
    product_subbrand Strings Any Sub-brand of the product
    brand_collection Strings Any Brand’s collection of the product
    product_category* Strings Any Category of the product (if several please separate with commas)
    product_subcategory* Strings Any Sub-category of the product (if several please separate them with commas)
    size* Strings Any size format Product size
    size_text Strings Any size format Additional information about size
    size_country* Strings Any size system Origin of the sizing (UK, US, MEX, EU, INT, etc.)
    product_fit Strings Any Fit of the product (loose, tight, etc.)
    product_manufacturer Strings Any Factory that produced the product
    product_fabric Strings Any Fabric, the product is made of
    product_ean Strings Any EAN for an item, if applicable
    product_image* Strings URL URL for the product’s image
    Strings Any Any additional product attributes

    Users:

    Column name Type Formatting Notes
    user_id* Strings Any Your internal id for customers
    created_date Strings Any date format (should contain year, month, day and time) Please let us know what format you use
    user_email* Strings SHA256 Hash Please use SHA256 hash of the email. Please find more info here
    user_phone_number* Strings SHA256 Hash Please use SHA256 hash of the phone number. Please find more info here
    user_gender Strings Male, Female Gender of the buyer, if known
    Strings Any Any additional user’s attributes