Skip to main content
All CollectionsFAQ
Channel V2: all you need to know
Channel V2: all you need to know

Find all the important information about our new columns mapping interface

Angelica avatar
Written by Angelica
Updated over a week ago

SUMMARY:

1. Channel V2: What does it mean?

In order to improve the user experience and make it easier to adapt your catalog to the marketplaces requirements, we have optimized the columns mapping section and create a new version we call "Channel V2".

This new version includes a dynamic mapping that adapts to:

  • Your product categories

  • Your product attributes

  • Your field values

With this new version, you will be able to see only the fields that are expected for your specific mapped categories. You can also see the available valid values that are expected for those fields.

❕ Don't worry about the offer attributes. They are still available, and you will see them first on the mapping (example: sku, price, state, quantity...).

☑️ Note: It is now possible to map the same catalog column or custom field to multiple attributes.


a. Product attributes

After all offer attributes, you will see a new section called Product Attributes. Next to which you will find a dropdown list.

This list contains the channel categories you have chosen for your categories on the categories mapping section.

Once you select a category, you will see the list of attributes expected for that specific category. You will find the complete category path and category code by hovering over the name:

☑️ Note: You will always see an item on the list called Cross Categories. Here you will find the list of attributes expected for all products regarderless of their categories. For example: title, description, images...


b. Values mapping

You might notice a new icon next to some product fields.

This means that the marketplace expects specific codes that might differ from the values in your catalog.

It will no longer be necessary for you to create a custom field with different conditions in order to send the expected codes found in our dedicated application.

Now you can simply map a field from your catalog that contains the requested information and then click on the "Open values mapping modal" to open the new tool.
Note that you might need to save page mapping before being able to access the value mapping tool.

On the left, you will find the list of values that can be found on your catalog for the mapped field. On the right, you will have all the available values that the marketplace expects for that field.

🔵 For example, the marketplace expects to receive the code 1810_4 instead of the value "marron".

You can choose to:

  • Map each value manually: by dragging a value from the left list and dropping it in the corresponding section on the right.

  • Try to map automatically: by clicking on the "Auto-map identical remaining values" button.

You have the possibility to restart the process by clicking on "Unmap all values".

⚠️ Important: check all your values are in the correct section and save all your changes before closing the tool.

Once all the mapping has been completed, you will see the following message:

The mapped values will be visible on the columns mapping, and you can identify them by the small table that will appear next to it:

☑️ Note: If you do not see the new modal button next to an attribute, this means that there is no list of valid values expected on the marketplace side. You can proceed with your mapping as usual for these fields.

⚠️ Important: it is not mandatory to use the values mapping tool. If your catalog field already contains the expected values, you can simply map as usual.

⚠️ Important 2: if you start using the value list mapping tool, make sure to map all your values, otherwise the not mapped values will be sent empty to the marketplace.


c. Practical information

  • Filter attributes:

    At the top of the column mapping page, you have filters available that allow you to display required fields, recommended fields, optional fields, already mapped fields and non mapped fields.

  • Identify the requirement level of the fields:

    1. All required fields will have a red asterisk next to it.

    2. All recommended fields will have a blue exclamation mark next to it.

    3. Optional fields won't have any of the previous icons next to it.

    ☑️ Note: an attribute can be required or recommended for one category but not for another, so you might see it multiple times on the mapping with different requirement levels.

  • Search for attributes:

    You can use the attribute name or the attribute code to find it in the mapping.

  • Search for specific values on the values mapping tool:

    You can use the search bar on the top left to search within your catalog values, and on the top right to search within the available options on the marketplace.

  • Display only mapped values:

    The list of available values on the marketplace can be quite long depending on the attribute. You can select the "Display only mapped values" case in order to see which values you have already selected to match your products.


2. Which channels are concerned?

Currently, mostly Mirakl channels are going to be migrated into channel V2.

We will proceed with a migration of 10 to 20 channels by month. Feel free to consult our dedicated planning page.

In March 2024:

  • Leroy Merlin (already available in FRA)

  • Conforama (already available in FRA)

  • Leboncoin (already available in FRA)

  • Boulanger

  • Vente Unique

  • Fnac

  • But

  • Decathlon

  • Darty

  • Brico Dépôt

  • Worten

  • Home 24

  • Maison du Monde

  • Brico Privé

  • Carrefour

  • PC Componentes

  • Ubaldi

  • Showroomprivé

  • Blokker

  • Media Markt

  • Manor

  • xxxLutz (already available in DEU)

In April 2024:

  • Saturn

  • Bricomarché

  • E.Leclerc

  • El Corte Inglés

  • Maty

  • Venca

  • Kiabi

  • Sprinter

  • Castorama

  • Gifi


3. Migration to V2: steps to follow

1. Go to the «Channels» page and search "V.2". You will then see the available channels with the new version :

2. Add the desired channel as usual, and fill in the API settings.

3. If you already have mapped the categories in the old version of the channel, then you can use the "copy to" button found in the Categories Mapping of the old version. Otherwise, proceed to map your categories (more info here).

🔵 For example, if you already use Leroy Merlin API FRA, you can copy the existing categories mapping into Leroy Merlin FRA API V.2

4. Go to the «Columns Mapping» page map, at the very minimum, all required fields.

5. Add any product exclusion you wish to apply on this channel.

6. Go to the «Channels» page and deactivate the old version of the channel to then activate V.2.

⚠️ Important: it is now forbidden to have both active channels (old version and new version) for the same marketplace. Once you activate V.2, you must deactivate the previous version.

☑️ Note: If you have two different BeezUP stores that are publishing to the same account on the marketplace (same API settings), please contact our technical support for more information on how to adapt your current settings to the new channel version.


4. FAQ

  • What is the difference between Channel V2 and a channel with a 2 at the end?

We must not confuse two instances of the same channel (for example, Amazon Direct FRA and Amazon Direct FRA 2), with the new Channel V.2.

The name of the new version will contain "V.2" specifically, and the logo will contain it as well:

Same channel

Different versions of the channel

  • How to map the same attribute for different categories?

⏩ Case 1: The code is the same for several attributes.

If the code is the same, once you map a field for this attribute, it will automatically be mapped for all other categories where the attribute code is the same.

🔵 Example: Let's say you want to map the attribute Product Material that exists for the marketplace categories House decoration and Office furniture.

If you map your catalog field material on the House decoration section of the mapping (1), it will automatically be mapped to the Office furniture section of the mapping (2):

Now, you must map the values of this field to the expected values on the marketplace. You can click on either of the values mapping modal (1 or 2) and you will see the same values:

⏩ Case 2: The code is different for each attribute, but they have the same name.

If the code changes, then you have to map a catalog or custom field for each instance of the attribute. This means that you will also have to map the values for each particular field, as the list of accepted values is different.

🔵 Example: Let's say you want to map the attribute Product type that exists for the marketplace categories Console table and Furniture and basin assembly.

When you map your catalog field Category 2 on the Console table section of the mapping, it will not be mapped on the Furniture and basin assembly section of the mapping:

This happens because each attribute has a different code associated to it.

In fewer words, they are two separate attributes that you must map independently of each other.

  • Is the values mapping tool case-sensitive?

No. You can use the auto-map option, and it will ignore any upper and lower case in order to match the marketplace value that corresponds to your catalog value.

  • Is there an indicative gauge of completion rate for value mapping?

No. You can only know if you have mapped all mandatory attributes or not.

If you still haven't mapped all required attributes, you will see a red icon next to Columns Mapping in the menu:

  • What do I do if there is not a matching marketplace value in the values mapping tool?

You would have to choose a value that approaches the most to your value. You can also contact the marketplace directly to request for them to add a value to their list.

  • I don't want to open the values mapping tool in each category, what can I do?

You do not need to open each of the values mapping tool in each category. As mentioned before, once you have mapped the values of a specific field, the mapping will also apply for all instances of that same field.

Did this answer your question?