The Fruugo category structure is a neutral category tree that aggregates all types of products without favouring any categories. It's got an extensive range of categories which should accurately account for all product types.
Our category tree is closely aligned to the Google Shopping Taxonomy to ensure that all products can be easily mapped from information which most retailers already hold to ensure a smooth integration process. The key benefit of the Fruugo category tree is the extended nature of some key categories to allow the retailer to specify a gender and/or age for their product types.
Category Value
The value to categorise your products in to the relevant Fruugo category is carried out by your product data feed using the 'Category' / <Category> field of the feed format. It allows you to specify the category of the product in your product feed to smoothly list your products on Fruugo and means that you do not have need to do any additional manual mapping or process work - your product feed handles the entire process for you.
Categorisation Process
There are two options for retailers for you to place your products accurately within the correct category in the Fruugo system. These are:
- Your Own Category Path - Provide your own category path from your website in the 'Category' field in the data feed and a member of the Fruugo Integration team will map these values to the relevant Fruugo category which will allow all your products to go live on Fruugo without any delay or manual process. In order to use this method your own category path much be granular so that the Fruugo Integration Team can map it to a leaf-level Fruugo Category, and can not contain a range of different product types. The Fruugo Integration team will map these categories during your integration process, if you then add further categories in the future please ensure you inform the team so they can set-up the relevant mapping. The category path should also include gender and/or age where relevant to the product type, such as Clothing & Footwear.
Examples are below:- CORRECT - Clothing > Footwear > Mens > Boots is a suitable category path.
- INCORRECT - Footwear > Boots would not be sufficient as it does not highlight the gender of the product.
- CORRECT - Home > Kitchenware > Pizza Trays is a suitable category path.
- INCORRECT - Home > Kitchenware > Pots, Pans & Trays would not be sufficient as it contains a range of different product types.
- Fruugo Category Path - You can ensure your products go live on Fruugo after your integration with no manual involvement by providing the full Fruugo category path in the 'Category' field of your product data feed. The value provided should be the full category path of one of the suitable Fruugo mappable categories and be case sensitive. You can find department specific and a full mappable category list of the Fruugo categories in the Categories > Mapping Category Tree section. The category path must be provided in English when using the 'Fruugo Category Path'.
Examples are below:- CORRECT - Apparel & Accessories > Clothing > Baby & Toddler Clothing > Baby & Toddler Sleepwear > Boys is a correct full Fruugo category path down to age/gender.
- INCORRECT - Baby & Toddler Sleepwear > Boys would not be sufficient as it does not include the full category path.
- CORRECT - Apparel & Accessories > Clothing Accessories > Sunglasses > Mens is a correct full Fruugo category path.
- INCORRECT - Apparel & Accessories > Clothing Accessories > Sunglasses would not be sufficient as it does not list the leaf-level of the category to highlight the age/gender.
Key Category Information
The following points should be considered when providing a value in the 'Category' field of your product data feed:
Is the product age specific?
Is the product gender specific?
Is there only one product type in the category product?
Is the category provided accurate for that product?
Is the category path provided in English if you're using the Fruugo Category Tree?
Disclaimer: In exceptional circumstances our Partnership Team who make an exception to the rule and allow the category field to be optional. However this must be agreed with them prior to completion of the Merchant Application Form (MAF) and is subject to internal approval when the case is reviewed.