Metro

METRO is a B2B focused e-commerce platform where sellers and suppliers meet in a growing and hospitable community.

1. Registering with METRO

Join the seller community of the European non food marketplace and connect with millions of HoReCa customers and professionals from different branches.

Visit the Selleroffice and register as a seller.

2. Installing the plugin in PlentyONE

To connect to METRO in PlentyONE. first install the METRO plugin in your PlentyONE system. You can download this and other plugins in the plentyMarketplace.

Important: Install the plugin in the plugin set of the main client.

METRO: Adding and installing the plugin

Adding plugin to the system:

  1. Go to Plugins » plentyMarketplace.
    → The marketplace opens in a new tab.

  2. Navigate to the plugin METRO.
    Tip: Either use the search function or open the category Plugins » Sales » Marketplaces.

  3. Open the detail view of the plugin.

  4. In the column to the right, click on Go to checkout.
    → The Checkout window opens.

  5. Read and accept the General Terms and Conditions.

  6. Click on Order now.
    → Wait a few minutes before installing the plugin.

Installing plugins:

  1. Go to Plugins » Plugin set overview.

  2. Click on the plugin set of your main client.
    Important: In other words: The plugin set must be linked to the main client.
    → The plugin set opens.

  3. Click on Add plugin.

  4. Select METRO from the plugin list.

  5. Click on Install.
    → The plugin is installed.
    → The plugin set is shown.

  6. Switch the plugin to active ().

  7. Save () the plugin set.
    Tip: Problems saving the plugin set? Click on Open details to show additional information.

3. Frequency of data exchange

After setting up Metro in PlentyONE. the automatic processes described in Table 1 are available:

Table 1. Frequency of data exchange
Data Interval

Item export

once per night

Price and stock synchronisation

Stock and prices are updated dynamically. The update interval depends on the number of variations to be updated:

  • Every 15 minutes for up to 500 variations

  • Hourly for 500 to 1500 variations

  • Once per day for more than 1500 variations

Order import

every 15 minutes

4. Setting up the market in PlentyONE

Installed the Metro plugin? Great. Now, set up the market in PlentyONE.

4.1. Activating an order referrer

Go to Setup » Orders » Order referrer to activate the order referrer. This ensures that orders are assigned to the correct sales channel.

What is an order referrer?

An order referrer tags an order with the sales channel on which the order was generated. Sales channels can be e.g. your online shop or markets on which you sell your items. Each sales channel has an individual order referrer. Some order referrers are available by default in your PlentyONE system. Further order referrers are added e.g. if you install a new plugin. For further information about the order referrer, see the page Order referrer of the PlentyONE manual.

Activating the order referrer for METRO:

  1. Go to Setup » Orders » Order referrer.

  2. Click Search (search).

  3. In the list, navigate to the option METRO.

  4. On the right of the referrer’s line, click on Edit (edit).
    → The window Edit referrer opens.

  5. Activate the option Visible in selection (toggle_on).

  6. Click on Save (save).
    → The referrer is active.

→ Plugin menu and assistants become visible.

4.2. Defining a sales price

To sell variations on METRO, you need a sales price in which the order referrer METRO is activated. The price that you save for this sales price is the price that will be shown on METRO.

What is a sales price?

Sales prices define the conditions under which a variation is sold at a specific price and on a specific sales channel. For example, you can sell your items at a lower price in your webshop than on Amazon. Or you can sell products cheaper to B2B customers than to B2C customers.

Two default sales prices are already configured in your PlentyONE system. However, you can also create new sales prices and edit them individually. In addition to default sales prices, you can also create RRPs, special offers, and set prices.

Notes:

  • The currency of the sales price must be EURO.

  • The sales price must be the sum of Sales price GROSS + Gross shipping costs.

  • The sales price for a minimum quantity of 10 pcs. cannot be higher than the sales price for a minimum quantity of 5 pcs.

  • Sales prices are not exported to METRO with the item export. Instead, they are exported in the Stock and price export.

Defining a sales price for METRO:

  1. Go to Setup » Item » Sales prices » [Open sales price].
    Important: Select a sales price that is the sum of Sales price GROSS + Gross shipping costs.
    Tip: No sales prices? Then create a sales price first.

  2. Open the Settings tab.

  3. Activate the referrer Metro.

  4. Save () the settings.

4.3. Completing the configuration assistant

Use the Plugin configuration assistant in the Setup » Assistants » Plugins » [Select plugin set] menu to set up Metro in PlentyONE. Keep the API access data at hand that you received from Metro.

Important: The assistant is only visible after you have installed the plugin and activated the order referrer METRO. You can change the assistant settings at any time.

Carrying out settings in the assistant:

  1. Go to Setup » Assistants » Plugins.

  2. Click on the assistant Plugin configuration assistant.

  3. Follow the instructions on the screen. If you need additional information about one of the options, expand the info boxes below this description ().

  4. In the Summary step, check your settings to make sure they are correct.
    Tip: In the Summary step, click on the arrow () to show the settings.
    Tip: You can run through the assistant again at any time to update settings.

Step API connection
Setting Explanation

Customer key

Enter the METRO customer key.

Customer secret

METRO customer secret
Step Item export
Setting Explanation

Should we export item data to METRO?

Possible options:
Item export On or Off

Note: The item export runs once a day. Item data is not directly uploaded to your METRO back end. The CSV file exported by the plugin undergoes manual screening by METRO staff. You can check the status of uploaded files in your Metro dashboard. If issues are identified, you can download a report from the tab Produkte aus METRO-Inventar verwalten of your METRO seller account.

Important: METRO items are unique. The system does not allow duplicate entries. If you are the first uploader of an item, you become the sole manager of that item’s details and specifications. If another seller uploads the same item, this only results in an offer for the item.

Note: Items for which you are not the owner only become visible in your METRO backend once you have submitted an offer for this item.

Which barcode type should we use as an identifier for exported items?

Select a barcode type.
Step Stock and Price Export
Setting Explanation

Should we export stock and price data to METRO?

Possible options:
Stock and price export On or Off

METRO offers are available for B2B and B2C customers by default. Should we enable B2B customers only?

Flip the switch to green if your offers should be available for B2B customers only.

Automatically generated SKU is based on:

Possible options: * Variation no. * Variation ID * Model * Barcode

Which property should we use to tag items for METRO freight forwarding?

Assign a property to be used as METRO freight forwarding tag.

Tip: This property must exist on variants which require METRO freight forwarding.

The maximum delivery time buffer is?

Assign a numerical value. This input defines the maximum time for an item to be delivered.

Note: The input is added on top of the Variation availability 1-10 you assigned. maxProcessingTime must be less than 100.

Should we send a fixed stock quantity each time?

Assign a numerical value. This value is exported as stock quantity for all items.
Step Order Processing
Setting Explanation

Should we import orders from METRO?

Possible options: Order Import On or Off

Orders cancelled by METRO will be set to status:

Select an order status.

Auto reject cancel requests starting with order-status:

Select an order status.
Step Return request processing
Setting Explanation

Should the plugin create return orders for pending METRO return requests?

Possible options: Create Return orders On or Off

Status for accepted return requests

Select an order status.

Status for customer cancelled return requests

Select an order status.

Important: The plugin automatically imports customer cancelled return requests.The return order is moved to the order-status you selected only if the return request has not already been accepted. This plugin behaviour requires that you have order-status defined for: * Accepted return requests. * Cancelled return requests.

4.3.1. Completing the Return Reasons Mapping Assistant

The METRO plugin automatically imports all return requests as return orders. This assistant helps you to map METRO return reasons to your reasons for return in PlentyONE:

  1. Go to Setup » Assistants » Plugins » [Open plugin set].

  2. Open the Return Reasons Mapping Assistant.
    Important: The assistant is only visible after you have installed the plugin and activated the order referrer METRO.

  3. Link your return reasons.

  4. Save the settings.

4.4. Setting up item delivery times

METRO requires you to define a minimum and a maximum delivery time for submitted offers. The sum of the minimum delivery time and maximum delivery time buffer may not be greater than 89 days.

Configuring a minimum delivery time:

  1. Go to Setup » Item » Availability.

  2. Define Average delivery periods you consider relevant.

  3. Save () the settings.

  4. Go to Item » Items » [Open variation] » Section: Availability and visibility.

  5. Select the appropriate availability level (symbols 1 to 10) from the dropdown-list Displayed delivery time.

  6. Save () the settings.
    → The minimum delivery time is defined and assigned.

Configuring a maximum delivery time:

  1. Go to Setup » Assistants » Plugins » [Open plugin set].

  2. Open the Plugin configuration assistant.

  3. Open the step Stock and Price Export.

  4. Add a value for the option The maximum delivery time buffer is?.
    → The maximum delivery time is defined and assigned.

4.5. Setting up stock and price updates by SKU instead of GTIN

Note the following requirements for updating stock and prices on METRO:

  • The item availability must be active in the menu Item » Variation » Settings » Area: Availability.

  • Stock and prices of variations are updated based on the GTIN. Variations can only be updated if they have the same GTIN in both PlentyONE and on METRO.

  • By default, stock and prices are updated by matching the PlentyONE GTIN to the identical GTIN on METRO. If you want to compare the SKU instead of the GTIN for updates, additional settings are required:

Setting up stock and price updates based on SKU matching

  1. Go to Setup » Assistants » Plugins » [Open plugin set].

  2. Open the Plugin configuration assistant.

  3. Open the step Stock and Price Export.

  4. Select a data source for the option Automatically generated SKU is based on:.

  5. Complete the assistant.

  6. Check if an offer exists in Your METRO dashboard for the item in question.
    Note: You can also manually create an offer from your METRO dashboard.

  7. Ensure that the SKU is identical in both systems.
    Tip: You can create SKU bulk assignments on METRO by going to Angebote verwalten. For additional details, contact your METRO support.

5. Setting up the item export

Item data is exported to Metro using catalogues. Use the assistant Item Export Preparation to create a marketplace format for each Metro category.

What is a catalogue?

Catalogues are used to export data from your PlentyONE system. There are two different catalogue formats:

  • Marketplace formats are used to export item data to markets.

  • Standard formats are used to export data from your PlentyONE system into a file.

Catalogues with marketplace formats allow you to tailor your item information exactly to the needs of the market. Because here, you assign a suitable PlentyONE data field to each of the data fields of the market. When your variation data is exported to the market, the market’s data fields are then filled with the correct PlentyONE data.

5.1. Creating a catalogue in the assistant

The item export uses the PlentyONE catalogue to decide which item data is exported to METRO. This assistant supports you in creating catalogue templates for the METRO item export.

Creating a catalogue in the assistant:

  1. Open the menu Setup » Assistants » Plugins » Open plugin set.

  2. Click on the assistant The Item Export Preparation Assistant.

  3. Follow the instructions on the screen. If you need additional information about one of the options, expand the info boxes below this description ().

  4. In the step Summary, check your settings to make sure they are correct.
    Tip: In the Summary step, click on the arrow () to show the settings.

  5. If everything is as it should be, click on Finalise.
    → The catalogue is created.

  6. Open the catalogue in the Data » Catalogues menu to map the fields.
    Note: You need a separate catalogue for each category on METRO.

Note: You should not change the format in the catalogue’s Format settings. To ensure that the export to the market works, all required settings are already configured when you create a catalogue. If you change the settings, errors might occur during the export.

Settings in the assistant
Setting Explanation

Select a METRO category.

Select a product category from the drop-down list.
→ The catalogue is created with the name of the category and shown in the Data » Catalogues menu.
→ A property with the name of the METRO category is created. Link this property with the variations that you want to sell on METRO.
Note: You need a separate catalogue for each METRO category.

Enter a name for the new catalogue.

Enter a name for the catalogue.

5.2. Mapping data fields in the catalogue

After you have created a catalogue, map the market’s data fields to item data saved in PlentyONE. Check the documentation of the sales channel to find out what data the market expects for the individual data fields.

  • The market expects product data that cannot be saved in the PlentyONE item menu? Then create a property for this data. Link this property with your variations. The actual values are saved as property values for this property. Is this your first time working with properties? Then read up on the principles of properties first.

Getting to know the catalogue menu for marketplace formats
catalogue menu colours
Availability Explanation

Navigation

When you open a catalogue, the view Mapping is shown. On the very left is the navigation.

  • Switch to other views of the catalogue.

  • Open the catalogue settings.

  • Use filters that limit the data that is exported.

  • Go back to the list of catalogues.

  • Create a new catalogue.

Toolbar

The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.

Marketplace data field

To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱).
Tip: Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions (more_vert).

PlentyONE data fields

On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Mapping catalogue fields:

  1. Go to Data » Catalogues.

  2. Click on the catalogue.
    → The Mapping tab opens.
    → In the left-hand column, the market’s data fields are listed.
    Tip: Mandatory fields are flagged with an asterisk (*).
    → In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.

  3. Map suitable PlentyONE data fields to the market data fields.
    For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.

    • Simple 1:1 mapping

    • Simple 1:1 mapping with properties

    • Complex 1:1 mapping

    • 1:1 mapping with fallback data fields

    • 1:n mapping

    • Own value mapping

    • Mapping with mathematical calculations

  4. Save () the catalogue.
    → The mappings are saved.

Simple 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. If no suitable setting exists in PlentyONE. you can map a property instead.

As such, simple 1:1 mappings allow you to:

  • I want to fill this marketplace data field with the data from this PlentyONE setting.

  • If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

  3. Click on the plus to the right of the PlentyONE data field you want to select.
    → The PlentyONE data field is added to the right.

  4. Click on Confirm.

Example: Sales price and RRP for Otto Market

This gif shows you how to map the marketplace data fields Sales price and RRP for Otto Market to PlentyONE data fields:

gif catalogue mapping simple en
Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

Reminder: In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. However, what can you do if PlentyONE does not offer a suitable data field? Then it’s the properties' moment to shine. Properties allow you to save any kind of information in your properties.

Creating a property:

  1. Create a property with the necessary values.
    Tip: Find out how to do that here.

Creating a simple 1:1 mapping with properties:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. Expand the group Property.
    → The property groups are shown.

  3. Expand the group you need.

  4. Click on the Plus sign on the right of the property you want.

  5. From the drop-down list Language, select the language in which you send the data to the market.

  6. Click on Confirm.
    → The property is mapped to the marketplace data field.

Complex 1:1 mapping: 1 marketplace data field, 1 PlentyONE data field

Like with the simple 1:1 mappings, you map a PlentyONE setting or property to a marketplace data field. Complex mappings are necessary whenever a marketplace data field has more than one possible value. Instead of mapping data fields, for complex mappings you map individual values of these data fields. For example, you cannot simply map the PlentyONE data field Shipping profile to the marketplace data field Shipping method. Why? The market cannot know which of your shipping profiles in PlentyONE corresponds to which of their shipping methods.

Do not enter own values for complex mappings. All values that you enter must be saved for the variations, either in a setting or as a property value. This also applies if the value Comparative value is shown. You still need to enter exactly the value of the setting or property that you mapped.

In complex mappings, the value of the market is always exported. Only when you map an own value, the own value that you enter is exported.

You can recognise complex mappings from the field that is shown below the name of the marketplace data field. Click on the field to show the values available for the marketplace data field.

catalogue complex mappings

Examples for complex 1:1 mappings are:

  • Categories

  • Brands

  • Shipping setting

Important: For complex mappings, do not map own values or properties of the type None.

Creating a complex 1:1:n mapping:

  1. Click on the field for the marketplace data field.
    → A list of the available values is shown.

  2. Select the value that you want to map a PlentyONE data field to.
    → The value is mapped.

  3. Next to the marketplace data field, click on + Add data field.
    → To the left, the available PlentyONE data fields are listed in groups.

  4. Click on a group.
    → The PlentyONE data fields of the group are shown.

  5. Click on the PlentyONE data field for which you want to map values.
    Important: Do not map own values or properties of the type None.

  6. Your next steps depend on the PlentyONE data field you selected:

    • Alternative 1: The available values for the PlentyONE data value are shown on the left.

      • Next to the value you want to select, click on the plus.
        → The value is added to the field on the right.

      • Click on Confirm.

    • Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.

      • In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.

      • Click on Confirm.

    • Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.

      • Select a value from the drop-down list.

      • Click on Confirm.
        → The value of the marketplace data field is exported, not the value of the PlentyONE data field.
        Exception: Only when you map an own value, the own value that you enter is exported.

Example: Delivery time in days for Otto Market

This gif shows you how to map suitable PlentyONE values to the values of the marketplace data fields Delivery time in days for Otto Market:

gif catalogue mapping complex en
1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

In a 1:1 mapping with one or more fallback data fields, you map a PlentyONE data field to the marketplace data field. In addition, you specify one or more fallback data fields. This ensures that the system keeps looking if the first PlentyONE data field is missing or empty.

So this mapping specifies:

  • I want to fill the marketplace data field with the data from the selected PlentyONE setting.

  • If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.

  • If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

The fallback data field is used if the data field above is mapped in the catalogue but not linked to the variation.

The condition "Null" is useful when you want to map fallback data fields for the following types of PlentyONE data fields:

  • SKU

  • Barcodes

  • Sales prices

  • Properties

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Empty

The fallback data field is used if the data field above is mapped in the catalogue and linked to the variation, but is empty.

The condition "Empty" is useful when you want to map fallback data fields for the following type of PlentyONE data fields:

  • PlentyONE data fields that are available for variations by default

Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting.

Note: Even if you assign one or more fallback data fields, the value of only one of those fields is exported. For each variation, the mapped PlentyONE data fields are checked in the order in which you mapped them. This means that if the first data field does not provide a value for a variation, the first fallback data field is exported etc.

Creating a 1:1 mapping with fallback data fields:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

  3. Click on the plus to the right of the PlentyONE data field you want to select.
    → The PlentyONE data field is added to the right.

  4. In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
    → The fallback data field is added with the fallback condition "null".

  5. Alternative 1: To add the fallback data field with the fallback condition "null":

    1. Click on Confirm.
      → The fallback data field is exported if the data field above is not linked to the variation.

  6. Alternative 2: To add the fallback data field with the fallback condition "empty":

    1. To the left of the fallback data field, click on the cog ().
      → The window Data column settings is shown.

    2. For the setting Fallback condition, select the option Empty.

    3. Click on Save.
      → The fallback data field is added with the fallback condition "empty".

    4. Click on Confirm.
      → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

This GIF shows you the mapping for the OTTO Market marketplace data field SKU. The PlentyONE data field SKU is mapped to this marketplace data field. The PlentyONE data field Variation ID is mapped as the fallback data field. The fallback condition "null" is applied automatically.

Result: The fallback data field Variation ID is exported if the data field SKU is not linked to the variation.

gif catalogue mapping fallback en
1:n mapping: 1 marketplace data field, several PlentyONE data fields

In a 1:n mapping, you map several PlentyONE data fields to the marketplace data field. You can link these data fields with a separator.

So this mapping specifies:

  • I want to combine these PlentyONE data fields during export so that the marketplace data field is filled with the data of these two or more PlentyONE settings.

Creating a 1:n mapping:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

  3. Click on the plus to the right of the PlentyONE data field you want to select.
    → The PlentyONE data field is added to the right.

  4. Click on Confirm.

  5. To the right of the mapped PlentyONE data field, click on Add data field ().
    → To the left, the list of available PlentyONE data fields again are shown in groups.

  6. Map one or several additional PlentyONE data fields to the marketplace data field as described above.

  7. Click on Confirm.

  8. To the very right of the row, click on Settings ().

  9. Select a separator from the drop-down list Separator or add a custom separator.

  10. Click on Save.

  11. Save () the catalogue.
    → The mappings are saved.
    → During the export, the content of the PlentyONE data fields is combined and exported as one field.

Own value mapping: 1 marketplace data field, the same value for all variations

You are sure that you want to export the same value for all variations of a catalogue for a marketplace data field? Then specify an own value. This own value is then exported for all variations.

So this mapping specifies:

  • For this marketplace data field, I want to export the value that I entered in the field Own value for all variations of this catalogue. The value you enter is always exported. The value overwrites the market value also in complex mappings where usually the value of the market is exported. As such, make sure you enter an own value that the market accepts for this marketplace data field.

Creating an own value mapping:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. Click on the plus next to Own value at the top of the list.
    → The field for the own value is added to the view.

  3. Enter a value into the input field.
    → This value is exported for all variations.

Example: Diameter information

You want to export diameter information for some of your variations. The diameter is saved in centimetres for all your variations. Instead of creating a property for the unit and linking this property to the variations, you can enter the own value cm.

This is an example of how you can map an own value for the diameter unit:

gif catalogue own value en
Mapping with mathematical calculations: 1 Marketplace data field, the PlentyONE value is recalculated using the formula during export

Mathematical calculations allow you to change numerical values automatically during the export.

  • This function only works for data fields that contain numerical values.

  • This functionality is new and not available for all catalogue formats.

So this mapping specifies:

  • I want the numerical value of a PlentyONE data field to be recalculated during the export. Basic arithmetic operations are available for the formulas.

Recalculating numerical values:

  1. Next to the marketplace data field, click on + Add data field.
    → To the left, the list of available PlentyONE data fields are shown in groups.

  2. At the very top of the list, click on the plus icon next to Formula (calculate).
    → The data field Formula is added to the field on the right.

  3. Click into the data field.
    → The window Modify value is shown.

  4. Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation (add).
    Tip: Use the search function. This helps you to find data fields quickly.

  5. Optional: If the symbol more_vert is shown in the data field, select the correct assignment for the data field.
    Tip: A number tells you how many assignments are necessary for the data field.

    1. Click on the icon more_vert.

    2. In the window shown, select the assignments from the drop-down list.

    3. Save the settings.

  6. Enter numbers and mathematical operators with the on-screen calculator or the keyboard.

  7. Save the settings.
    → The entered formula is displayed in the overview.
    → The calculation will be carried out in the next export.

5.3. Creating properties for units of measurement

Create a property for each unit of measurement that you want to map.

6. Preparing variations

Continue with preparing your variations.

6.1. Activating variations for the market

You need to activate the variations that you want to sell on METRO. This is done in the Availability and visibility section of a variation within the Item » Items » [Open item] » [Open variation] menu.

  • For one variation

  • Using variation group function

  • Using batch processing

Making a variation available for METRO:

  1. Go to Item » Items » [Open item] » [Open variation].
    Tip: To sell all variations of an item on METRO, carry out the settings for the item’s main variation. If the inheritance function is active for the variations, then this activates the availability of all variations of the item.

  2. In the Availability and visibility section, activate the option Active.

  3. In the Sales channels section, click Add sales channels (add).
    → The window Add sales channels opens.

  4. In the drop-down list Sales channels, select the option METRO.

  5. Click Apply.
    → The sales channel is added.

  6. Save () the settings.
    → The variation is available for METRO.

Use the variation group function to edit multiple variations at once. You select the variations that you want to edit.

Making several variations available for METRO using the variation group function:

  1. Go to Item » Items.

  2. Set search filters as needed and start the search.

  3. Select () the variations to be edited.

  4. In the toolbar, click on layers » layers Variation group function.
    → The Variation group function window opens.

  5. Select the action Sales channels from the drop-down list Actions.
    → The action is added to the lower part of the window.

  6. In the drop-down list Sales channels, select the option METRO.

  7. Select the action Active from the drop-down list Actions.
    → The action is added to the lower part of the window.

  8. Activate the option Active.

  9. Navigate to the area Availability.

  10. Click Execute to apply the settings.

Batch processing allows you to edit several variations at once. You use filters to limit which variations are edited.

Making several variations available for METRO using batch processing:

  1. Go to Item » Batch processing.

  2. Click on the tab Variations in the upper left corner.

  3. Use the filters on the left to specify which variations should be processed.

  4. Navigate to the area Market availability.

  5. Activate the checkbox to the left of the option METRO.

  6. Activate the checkbox to the right of the option METRO.

  7. Navigate to the area Availability.

  8. Activate the checkbox to the left of the option Active.

  9. Activate the checkbox to the right of the option Active.

  10. Click on Apply to apply the settings to the variations.

6.2. Linking variations to a Metro product category

After you created the first catalogue for Metro with the assistant The Item Export Preparation Assistant, the property METRO market category group / METRO market Kategoriegruppe is created in your PlentyONE system. With this property, you define in which category your variations are sold on Metro.

In addition, a first property value is created for the property. This property value has the same name as the Metro product category that you created the catalogue for.

Each time you create a new catalogue for Metro, a new selection value is added to the property METRO market category group / METRO market Kategoriegruppe. This selection value has the same name as the Metro product category.

The property METRO market category group / METRO market Kategoriegruppe determines in which Metro product category a variation is published. To do so, link the variation to the appropriate property value of the property METRO market category group / METRO market Kategoriegruppe.

Linking a variation with the property for Metro product categories:

  1. Go to Item » Items » [Open item].

  2. Open the variation that should be linked.

  3. Open the Properties tab in the navigation bar on the left.

  4. In the navigation bar at the top, click Add properties (add).
    → The window Add properties opens.
    Tip: If you know the property type, then you can also expand the section of the respective property type, for example Selection and multi selection. In the sections, the properties are already filtered by type.

  5. Place a check mark next to the property METRO market category group / METRO market Kategoriegruppe.
    Tip: Use the search (search) or the filters (tune) to search for the property METRO market category group / METRO market Kategoriegruppe.

  6. Click APPLY.
    → The property is added.

  7. For the property METRO market category group / METRO market Kategoriegruppe, select the desired category group from the drop-down list Value.
    Tip: Product categories are only added as a selection value for the property after you have created a catalogue for this Metro category.
    → The variation is listed in this Metro product category.

  8. Save () the settings.

Further possibilities to link variations:

  • Via import: Go to Setup » Settings » Properties » Configuration and open the property METRO market category group / METRO market Kategoriegruppe. Click Values. This will show you the selection value IDs that are needed for the import.

  • Via REST API: Use the REST routes from the sections Property and Item to link the catalogue with the variation.

6.3. Check list: Requirements for the item export

  • The variation must be active.

  • Variation must be activated for the market METRO.

  • The Metro property METRO category and a specific property value must be linked to the variation.

  • The variation must have at least one image that is activated for the market METRO.

  • The variation must have a barcode type GTIN or the MPN + manufacturer as the export identifier.

  • The item description must only contain the following HTML tags:

    • <p>

    • <ul>

    • <ol>

    • <li>

    • <span>

    • <br>

Important: Sales prices are not exported to METRO with the item export. Instead, they are exported in the Stock and price export.

6.4. Check list: Requirements for the stock export

  • The warehouse is available for the order referrer Metro.
    Tip: You can add the order referrer in the menu Setup » Stock » Warehouse » [Open warehouse] » Tab: Settings in the Available for order referrers section.

  • Net stock must be positive.
    → Variations with negative stock are exported with a stock of 0.

  • Variations must have a sales price for the market METRO. The currency of this sales price must be EURO.

  • The sales price must be the sum of Sales price GROSS + Gross shipping costs.

  • For stock and prices to be updated, the GTIN or the SKU must be identical in PlentyONE and on METRO. If you selected the SKU to be matched instead of the GTIN, then the SKU must be identical in PlentyONE and on METRO instead.

Important: Sales prices are not exported to METRO with the item export. Instead, they are exported in the Stock and price export.

6.5. Submitting offers to existing METRO items

This functionality does not require an item export. Instead, offers for a variation are exported with the Stock and price Export.

During the export, one of the following identifiers to create an offer:

  • GTIN

  • SKU

To create an offer, the following settings must be in place:

  • The variation must have a value for the stock export identifier you selected in the METRO Plugin Configuration Assistant » Option: Automatically generated SKU is based on:.

  • For an offer to be exported, the GTIN must be identical in PlentyONE and on METRO. If you selected the SKU to be matched instead of the GTIN, then the SKU must be identical in PlentyONE and on METRO instead.

  • The variation must be active in the menu Item » Variation » Settings » Area: Availability.

  • The item must have referrer METRO set in the menu Item » Variation » Tab: Availability » Area: Marketplace.

  • Item must have the Standard Client set in the menu Item » Variation » Tab Availability » Client.

  • Net stock must be positive.

  • Variation must have a sales price for the market METRO.

  • The currency of the sales price must be EURO.

  • The exported value for the sales price must be the sum of Sales price GROSS + GROSS shipping costs.

7. Understanding order processing

7.1. Information about the order import

Information about order import and order processing for METRO.

  • The plugin creates individual orders from each METRO order item.
    Example: A customer orders 2 pieces of the item X and 3 pieces of the item Y. In PlentyONE. two orders are created: one order for 2 x item X and another order for 3 x item Y. You can find related orders by using the order search filter Ext. order number.

  • Each METRO order line-item is processed separately (fulfilment, invoice, event procedures, returns, etc.).

  • All orders are imported as paid.

  • Because METRO sales prices already include shipping costs, orders are imported with a shipping cost of 0 Euros.

7.2. Supported payment methods

The following payment methods are supported and automatically recognised during the order import:

  • Direct debit payments are imported as "Metro Direct Debit".

  • RatePAY invoices are imported as "Metro Open Invoice".

  • *PayPal payments *are imported as "Metro PayPal".

  • Klarna Sofortüberweisung payments are imported as "Metro SOFORT".

  • Credit card payments are imported as "Metro Direct Checkout".

  • All other payment methods are also imported as "Metro Direct Checkout".

Note: The plugin imports anonymous proxy-email-addresses for METRO buyers.

7.3. Automating order processing

The event procedures provided by the plugin allow you to send information about your orders to METRO.

7.3.1. Available event procedures

Table 2. Available event procedures
Event procedure Explanation

Send cancel notification to METRO,
reason "No inventory"

This event procedure sends a cancellation notification for the METRO order.

Send cancel notification to METRO,
reason "Wrong price"

This event procedure sends a cancellation notification for the METRO order.

Send cancel notification to METRO,
reason "Wrong product data"

This event procedure sends a cancellation notification for the METRO order.

Send fulfilment notification to METRO

This event procedure triggers the fulfilment notification. A tracking number is not required.

Send order "Processing" to METRO

On successful order import, this event triggers an order confirmation on the METRO order, it also moves the order from status Placed to status Processing. This is an important step, since only orders on status Processing can be moved to the status Shipped.

Here, we recommend the following event procedure setup:

  1. Go to Setup » Orders » Events » New.

  2. Enter a name.

  3. Select Status change from the drop-down list.

  4. Pick status [4] In preparation for shipping or status [5] Cleared for shipping.

  5. Add the action Send order "Processing" to Metro.

Important: METRO event procedures do not support the event New Order.

Send invoice to METRO

This event procedure allows you to send an invoice to METRO.

Send return label to METRO

Go to Orders » Shipping centre to generate a Return Label for the Return Order and trigger this event procedure to send the document to Metro.

Send 'accept return request' to METRO

This event procedure notifies METRO that you accepted the return request.

Report 'returned order' to METRO

If the buyer does not accept or receive the shipped items, the order is automatically returned. Create a Return Order and trigger this event.

Send 'return request declined' to METRO

This event procedure sends a notification to METRO to decline the return request submitted by the customer.

Send credit note to METRO

Create a Credit Note Order from a Return Order that has been accepted and generate a credit note document on the Credit Note Order. Trigger this event to send the credit note to METRO.

7.3.2. Example: Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure.
    → The Create new event procedure window opens.

  3. Enter a name.

  4. Select an event, for example Order change: Outgoing items booked.

  5. Save the settings.

  6. Select the filter Order > Order type > Order.

  7. Select the filter Order > Referrer > METRO.

  8. Select a procedure from the area Plugin.

  9. Save the settings.

8. Using the plugin help

The PlentyONE back end provides the menu Setup » Markets » METRO » Help. The plugin help enables you to check the following:

8.1. Downloading a CSV file of the Item export

  1. Go to Setup » Markets » METRO » Help.

  2. Select a catalogue from the catalogue list.

  3. Click on Download CSV.

  4. Check the exported content for the selected catalogue.

8.2. Checking variation export conditions

  1. Go to Setup » Markets » METRO » Help.

  2. Enter a variation ID.

  3. Select the METRO catalogue that is relevant for the variation.

  4. Click on Check.
    → A list of the export conditions is shown.

    • OK = The requirement is met.

    • X = The requirement is missing.

8.3. Checking the plugin health

  1. Go to Setup » Markets » METRO » Help.

  2. Click on Check.
    The plugin checks the following:

    • Is the order referrer METRO active in the menu Setup » Orders » Order referrer?

    • Can PlentyONE connect to the METRO API?

    • Is more than one referrer METRO present and active in the menu Setup » Orders » Order referrer?

    • Is the highest available referrer ID active?