Feed essential variables

Your feed should include at least the following attributes to provide sufficient information for Size Adviser to work:

unique_product_id

Unique product identifiers (UPIs). This ID defines the product you are selling in the global marketplace.

They uniquely distinguish products you are selling and help match search queries with your specific products.Valid IDs for this field include Google’s Item_group_id , UPC, EAN, ISBN, MPN, Parent SKU …

💡

Each ID should be unique for each product in your feed, and only repeated as many times as there are variations for each product. For example, a product with 6 sizes should repeat the unique_product_id 6 times in the feed.

If you do not use any of those international references, you may include any unique ID that identifies your product. Feel free to use any reference at your disposal as long as the chosen ID is unique and regroups all product colour/material/pattern/size variations for each specific ID.

💡

We encourage you to include a combination of any or all variables that represent a Unique Product Identifier if they are available in your system. Please review the following example of how to include UPIs in your feed

💡

Example

This Nike AirMax 90 shoes is identified by the following unique EAN code: 0194958086596

Each single size should have its own Stock Keeping Units (SKUs) under that same EAN in the feed.

variation_id

The variation ID (Stock Keeping Unit or SKU) represents a unique identifier for each product/item variation.

💡

Each variation ID should not appear more than once in your entire feed, as it must be a unique ID.

You may use any sequence of letters and digits for each item in your catalogue, as long as the ID is unique to each product variation.

The SKU is an internal reference that is not standardized between Ecommerce platforms. A universal reference equivalent to SKU can also be used to define Variation IDs: **Universal Product Codes (UPCs) **

title

Indicate the product name for each item. We recommend including characteristics such as colour or brand in the title to better differentiate one product from the next.

link

Indicate the direct URL to each specific product page. Landing pages requiring sign-ups, passwords, or direct links to files/email addresses are not allowed. Links should not contain raw IP addresses.

brand

Indicate the Brand name for each product. This is required for all products. (Example Nike, Adidas, New Balance, …)

gender

Indicate the product gender of each item. Accepted values are: ‘Male’, ‘Female’, ‘Unisex’.

💡

Ecommerce platforms that only sell products for one gender (example: Female fashion shop) do not have to include this attribute in the feed as long as Usizy is informed during the integration process.

age_group

Indicate the product age group for each item. Accepted values are: ‘Adult’ or ‘Child’.

This attribute is essential to differentiate child products from adults’, in order to connect each product to its correct size guide and measurements, and provide accurate size recommendations.

💡

Ecommerce platforms that only sell products for one specific age group (example: Adult only sports shop) do not have to include this attribute in the feed as long as Usizy is informed during the integration process.

google_product_category

Use the ‘google product category’ attribute to indicate the product category for each item in the feed, according to the Google product taxonomy.

This attribute only accepts a pre-defined value, taken from the product taxonomy tree, and only one category is permitted per product.

If your items fall into multiple categories, include only the one that is most relevant and best represents the actual product type.

For a more detailed explanation from Google, please visit the Merchant Help Center.

💡

An alternative solution is to use the “product_type” attribute that may include Ecommerce specific internal product categories, as long as the information is sufficiently detailed to categorize products efficiently.

Please review the Feed Additional variables section for more details.

💡

Example

A product indicating “Female clothes” as a category does not contain explicit enough information compared with a category such as “Female dress” or “Male trousers”…

size

Define the size for each product variation. (example: 28, 30, XS, S, M, L …)

💡

We strongly recommend to include all sizes available for each product, regardless of stock, in order to improve product identification and coverage.

size_system

Whenever possible, it is highly recommended to include the size system for each product variations (example: INT, UK, FR, US, UK, JP …) to ensure that the correct size system is identified for each size included in the feed.

💡

Ecommerce platforms that only sell their own brand in one size system (such as S, M, L, XL…) do not have to include this attribute in the feed as long as Usizy is informed during the integration process.

💡

If you are unable to send the correct size system dynamically for each product, please do not include a hardcoded value for your whole catalogue as this will cause issues and reduce coverage. We recommend in that case to leave this field empty and let our system try to recognise the correct size system on its own.

ecommerce_name

Include the name of your ecommerce platform.

image_link

Include the main product image URL. Submit full-size images of your products and not a thumbnail version of the images.

The image will be displayed in Size Adviser during the Size recommendation process, to increase user confidence that each recommendation provided is specific to the product being visited.

💡

We recommend including the main image showed by default on your product page so that visitors can recognize each product easily, and to optimize load time, as the default image will already be in the visitor’s cache memory when they open Size Adviser.

💡

We highly recommend including as many available attributes as possible between the list of essential variables and the additional ones. Please consider the following feed examples:

Recommended feed example

Feed with minimum required content only.

Where next?

Feed additional variables

Feed examples

Building your feed

Onboarding guide