YOOX: marketplace guide

About this guide

This is a ChannelEngine guide on the Milan-based marketplace YOOX. Here you can find information on how to request a YOOX account, how to configure this marketplace on ChannelEngine, what the specific requirements are, and more.

Table of contents

Commercial information

How to request an account

Associated costs

Marketplace features

Settings and configuration

Marketplace-specific requirements and exceptions

• Setup
• Categorization
• Mappings
• Pricing
• Listed products

FAQs

Commercial information

Founded	2000
Founder	Federico Marchetti
Headquarters	Milan, Italy
Area served (orders)	Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United States
Website	YOOX
Setup cost	none
Commission	around 24%, based on seller potential
Other costs	monthly fee of EUR 50
Payment	three times a month (on the 8th,  18th, and last day of the month)
Product categories	fashion & accessories (a combination of out-of-season, high-end designer clothing, and in-season fashion)
Input language	English, French, German, Italian, Spanish, Greek
Input currency	EUR
Content creation	yes
Profile on ChannelEngine	YOOX

How to request an account

To start selling on YOOX, contact your customer success manager at ChannelEngine. If YOOX approves your onboarding, the process can begin.

Associated costs

Selling on YOOX comes with the following costs:

• Monthly fee - YOOX provides sellers with a dedicated account manager, and charges a monthly fee once you sell your first product.
• Commission - YOOX charges a commission based on the seller's potential and the categories they offer. YOOX does not charge a commission on returned items.

Marketplace features

Supported	Not supported
Product offers	HTML formatting
Product content	Cancelations (marketplace)
Orders	Marketplace fulfillment service
Shipments	Returns (marketplace)
EAN matching	Repricing
Returns (merchant)	Pick-up point delivery
Carrier mapping	Automatic relationships
Cancelations (merchant)	Multiple stock locations
Vintage (used) products
Sales channels*
Bundles

* A marketplace that supports sales channels allows merchants to list and sell products across multiple markets (e.g.: countries, regions, and states), all from the same connection.

Settings and configuration

Setting up each marketplace on ChannelEngine follows the same flow, though not every marketplace includes the steps listed below.

1. Go through the Setup.
2. Create a Product selection.
3. Complete the Categorization.
4. Set up the Mappings: content, offers, and carriers.
5. Configure the Pricing: rules and currency conversion.
6. Finish the Activation.
7. Check the Listed products overview.

Marketplace-specific requirements and exceptions

YOOX is an online high-end fashion retailer and ecommerce wholesaler. With the launch of its marketplace, YOOX transitions into a hybrid operating model. YOOX uses a pure marketplace business model, which means that the seller controls price and assortment, and manages order fulfillment – as well as customer service.

Requirements to join YOOX:

• Stock
• Legal entity
• VAT number in the EU

Technical requirements for images:

• Refer to the YOOX photo guidelines to learn more about their image requirements.
  

  

Other:

• YOOX orders are paid on shipment. This means that the order status may be set to Debit in progress.
• Carrier mapping is not required on YOOX. However, you can map your carrier to a specific list of carriers maintained by YOOX. This allows for working track-and-trace links in the back-end, as well as for the buyer. If your default carrier is missing, please contact YOOX.
• Currently, YOOX only supports the new products.

Setup

On ChannelEngine

YOOX is a Mirakl-based channel, so you can connect it with ChannelEngine using a Mirakl Connect SSO account. For more information on this, check out the Mirakl-based channels: SSO authorization article.

You can leave the Mirakl seller name field empty, as YOOX does not support repricing.

Invoice uploads

To configure your invoice settings, click Advanced settings. You can then click the dropdown menu Enable invoice uploading, which contains the following options:

• ChannelEngine invoices - when ChannelEngine receives a shipment, it automatically generates an invoice and attaches it to the shipment before exporting it.
• Merchant invoices (optional) - when ChannelEngine receives a shipment, it exports it – even if there is no invoice attached to it.
• Merchant invoices (required) - when ChannelEngine receives a shipment, it only exports it if an invoice is attached to it. If not, you receive a notification.
• None - when ChannelEngine receives a shipment, it takes no action other than notifying you that no invoice is present.

If you select one of the Merchant invoices options, make sure to upload the invoice to ChannelEngine via the Merchant API or via the web interface. To learn more, check out the article ChannelEngine: merchant invoices.

Categorization

Categorization is mandatory if you want to create or update existing product information on YOOX. Both categorizations and mappings only result in updates if the content connection is enabled, and the relevant credentials have been entered (see the Setup section).

Mappings

Content

All products (required)

• Brand - the product's brand.
• Color - the product's main color.
• Gender: the product's target gender. Currently, YOOX supports unisex only for some categories.
• Image1 - F: packshot photo of the article.
• Material composition - 1, the main material of the article.
• Product title - the title of the article, must be in Italian or English. This product title is not visible on  the YOOX front-end, but the Model title is.
• Seller SKU - the product's SKU. Usually this is the product's Merchant product number on ChannelEngine.
• Variant group code - enables group variations of the same product. E.g.: a t-shirt in different colors and/or different sizes.

The following required attribute is common to all Mirakl-based marketplaces:

• Export strategy - choose a strategy for exporting the product data. You can select from the following export strategies:
  • Yes - export all of the product content to the marketplace, including its EAN (GTIN), category, and other mapped attributes. This option is ideal if you manage both product content and offers through ChannelEngine for the marketplace. Before you set this option, ensure that you map all required attributes.
  • No - do not export product content to the marketplace. Choose this option to keep the product content excluded from exports and only export the offers. This option is ideal if you do not want to export the product content yet, or you want to export only the product offers because the product content already exists on the marketplace.
     
    NB: the default export strategy is Yes, even if the Export strategy attribute is left unmapped.

All products (optional)

• Item description (country code) - this attribute becomes mandatory if you want to list the product in related markets (e.g.: DE for Germany and Austria, ES  for Spain, etc.). If the description is unavailable, map the brand accordingly – but the attribute cannot be left empty. Make sure your description does not exceed 2,000 characters. HTML is not supported.
• Made in - the country in which the article was manufactured.
• Material _1 % - the percentage of the main material (only the digits, without the percentage symbol).
  NB: if you use this attribute and its number is lower than 100, you must add values for the other materials – and make sure that the sum of the percentages of all the Material attributes is 100%. 
• Material _2-5 % - the percentage of the additional materials in digits (without the percentage symbol).
• Material composition-2-5 - the composition of the additional materials.
• Model code - the manufacturer's model code.
• Model color code - the manufacturer's color code.
• Model title - the name of the model. This title is displayed in the YOOX front-end. The maximum number of characters allowed is 100.
  
  NB: the Model title must be the actual name of the model (e.g.: Nike Air Force 1). A general description, such as 'white sneakers', is not allowed. If this field is empty, YOOX displays the brand and the category (e.g.: Nike sneakers).
• Preowned condition - the condition of a second-hand or vintage product.
• EAN - the product's European article number or GTIN.
• Image1 - R, front with model photo.
• Image3 - D, back with model photo.
• Image4 - E, total look with model photo.
• Image5 - A, detail photo.
• Image6 - B, detail photo.

Category-specific

• Size fields - in the content mapping of the specific categories, there are usually multiple optional size fields. It is mandatory to map one of the sizes available – and only one size can be mapped. E.g.:
  • Size - EU MAN - Footwear
  • Size - EU WMN - Footwear
  • Size - UK MAN - Footwear
  • Size - UK WMN - Footwear

  In the example above, the men's shoes should have the field Size - EU MAN - Footwear mapped, while the women's shoes should have the field Size - EU WMN - Footwear mapped. Check out the Advanced rules. For more information on size fields, see the FAQs.

Offer

Required

• Price - you must enter the price in euros for all countries and zones. YOOX takes care of the price conversion for countries that do not use the euro, so that customers can view the price in their own currency in YOOX’s front-end. The conversion is based on the rate of the Italian Central Bank and is updated once a day. Note that all payments are in euros.

Optional

The following offer attributes are common to some Mirakl-based marketplaces:

• ECO #1-5 amount - the amount due for the eco-contribution related to the product. E.g.: 2.50.
• ECO #1-5 EPR category code - the extended producer responsibility (EPR) code that applies to the product. For a list of category codes, check out the article Providing data to comply with circular economy regulations in Mirakl's help center (note that you need to be logged in to Mirakl to access this page). E.g.: DE-WEEE, FR-DEA, etc. 
• ECO #1-5 producer ID - your producer ID, received upon registering with a packaging register, such as Germany's LUCID. The maximum number of characters is 255.

The following offer attributes are common to all Mirakl-based marketplaces:

• Discount end date - the date until when the product's sale price is valid, if applicable. The date format is YYYY-MM-DD HH:MM:SS ZZ. E.g.: 2022-12-31 23:59:59 +00.
• Discount price - the product's sale price, if applicable. This attribute must have a lower value than the Price attribute.
• Discount quantity threshold - the minimum quantity required for the discount rate to be available.
• Discount start date - the date from when the product's sale price is valid, if applicable. The date format is YYYY-MM-DD HH:MM:SS ZZ. E.g.: 2022-12-31 23:59:59 +00.
• Leadtime to shipment - the number of days before you ship the product. By default, this is set to two. You can create your own unique rules, if applicable. For more information on this, check out the article Lead time to ship in Mirakl's help center.
• Minimum quantity alert - map this attribute to receive a notification from Mirakl if your stock drops below the threshold defined.
• Offer state - the product's condition. Find your option from the dropdown menu by selecting the fixed value to apply to all.
• Product tax code - the taxation code applicable to the product.
• Logistic class - your optional shipping class. Make sure to map it using the marketplace’s codes, not the labels visible in the front-end. These codes vary per marketplace. If this marketplace makes use of logistic class codes, they can be found below.

Logistics classes

Code	Label	Description
S	Small	Small package, less than a kilo, dimensions: L + W + H < 150 cm with L < 100 cm
M	Medium	Medium package, between 1 and 3 kilos, dimensions: L + W + H < 150 cm with L < 100 cm
L	Large	Large package, between 3 and 5 kilos, dimensions: L + W + H < 150 cm with L < 100 cm
OLC1	Open Logistic Class1	If none of the above fits your parcel please define your own charges using this class.
OLC2	Open Logistic Class2	If none of the above fits your parcel please define your own charges using this class.

 

Working with discounts

• To set up a discount, you must map the Discount price, Discount start date, and Discount end date attributes. If you want to set a permanent discount, map the Discount end date attribute with a date in the far future instead of leaving it unmapped. Otherwise, the offer is not exported, and errors are shown on the Validation and feedback tab.
• The discounted price is only exported if it is lower than the base price.
• If you do not want to set a bulk discount, leave the Discount quantity threshold attribute unmapped – otherwise, the export is broken.
• To set a bulk discount, the Discount quantity threshold must be set to a value higher than 1. E.g.: a value of 2 indicates that two or more of the product must be purchased at the same time for the buyer to benefit from the discount.

 

Carrier mapping

Carrier mapping is not required on YOOX. However, you can map your carrier to a specific list of carriers maintained by YOOX. This allows for working tracking codes in the back-end, as well as for the buyer. If your default carrier is missing, please contact YOOX.

Listed products

If you have problems with products not appearing on Mirakl-based marketplaces – especially if you are trying to create products –, check the Listed products page for more information.

You can either use the Channel status filter (e.g.: products that ChannelEngine has failed to exported, such as those with an empty GTIN or that do not exist on the marketplace yet, are shown as Invalid) or the Validation and feedback tab to see all known errors for specific products.

Alternatively, you can access the marketplace's back-end and download the error report generated by Mirakl. To do so:

1. Log in to the Mirakl back-end and go to Catalog, Product imports.
2. Identify the latest report and click the See details button by it.
3. Download the CSV file Non-integrated products report.

FAQs

What should I do if I have sizes in different formats, such as in EU and US sizes?
You can map one of the size classes, YOOX makes the conversion to other formats.

Which size attribute should I use?
In some categories there are several different size attributes available:

• Brand - if you are a brand and you list your products on YOOX for the first time, you can choose to map whichever size class you want. YOOX recommends that you stick to the size information in your labels.
• Retailer - if you are a retailer and sell a brand that already exists on YOOX, you must use the size class that has already been associated with that brand. E.g.: women's jeans by Levi’s have the size based on the waist size. In this case, you map Size - JEANS WMN - waist, other options are not possible.

How can I map unisex products? 
YOOX supports the gender unisex for the following categories:

• belts
• swimwear
• underwear and sleepwear
• accessories and small leather goods

For all other categories, the Gender attribute should be mapped to Man or Woman.
If you map an article from another category with unisex, YOOX still accepts it and makes it visible for both genders in the front-end. However, you are not be able to map any unisex size attribute, with the consequence that the sizes might not be converted properly and might result misleading for the end customer. For this reason, YOOX discourages from mapping an article as unisex – if there are no unisex size classes available.

YOOX offers the following solution specifically for shoes:

• map the smallest sizes for women (from size 34 to 41)
• map the largest for men (from size 41.5 to 46)

Keep in mind that this solution makes sizes visible only for men or for women, depending on your mapping. Also, if you adopt this solution, make sure that the Variant group code is different between the Female size and the Male size articles. Products grouped under the same Variant group code must have the same Size class.

How do I create variations on YOOX?

To create variations on YOOX, the content attribute Variant group code must contain the same value for all the articles you want to group together. That can be done by mapping the attribute Parent SKU (or any other relevant attribute) to the Variant group code attribute, as long as Parent SKU's value is the same among all the variations of the product. E.g.: if you are selling a t-shirt in three colors, with five sizes each, all fifteen products must contain the same value in the attribute Variant group code.

Keep in mind the following when creating variations:

• There are only two kinds of variation on YOOX: color and size.
• All products that belong to the same variation group (and thus share the same value for Variant group code) must have a unique color/size combination. E.g.: if you are creating a variation for a model of shoes which has variants with similar colors, make sure to map different values in the Color attribute, such as ‘blue’ and ‘dark blue’.

How often does each task run on Mirakl-based marketplaces?

By default, Mirakl-based marketplaces follow the schedule below:

Task	Frequency
Export product data to marketplace	every 60 minutes
Export product offers to marketplace	every 15 minutes
Import product offers from marketplace	every 15 minutes
Import orders from marketplace	every 15 minutes
Export order shipments to marketplace	every 15 minutes
Export returns to marketplace	every 30 minutes

Can I map attributes on ChannelEngine and in the Mirakl back-end?

No. Mapping attributes in the Mirakl marketplace back-end interferes with ChannelEngine's content export. Therefore, it is recommended to stick to categorizing and mapping content only on ChannelEngine.

Why am I not receiving feedback on my content and/or offer exports?

Chances are you are receiving the feedback. However, different types of error report can take a couple of hours or several days to be generated:

• Offer feedback
  • Error reports are mostly generated automatically, and are imported quickly.
• Content feedback
  • Transformation error report - this is automatically generated, and usually imported within a maximum of one day.
  • Conventional error report - this requires a manual review by the Mirakl-based marketplace, and not all do so. It can take several days for this report to be imported.

Note that the previous feedback report is not removed from ChannelEngine until both the latest transformation and conventional reports have been fully processed by ChannelEngine – or no new reports have been generated because there are no errors to report.