METRO (closed beta) (Setup via Channel Control Centre)

METRO is an international food wholesaler headquartered in Düsseldorf, Germany, operating over 620 stores in 21 countries. Its product range is primarily aimed at business customers in the hotel, restaurant and catering industries, as well as food retailers (HoReCa & Trader). The METRO MARKETS online marketplace offers a wide selection of professional equipment, especially for HoReCa customers.

Channel Control Centre

This page explains the setup process for METRO via the menu Sales Channels » Channel Control Centre. If your system features the Sales Channels » Accounts menu instead, then you can find instructions on how to set up METRO via this menu here.

This METRO integration is currently in a closed beta testing phase. Are you interested in participating in the closed beta testing phase? Then get in touch with your PlentyONE contact person (Business Development / Account Management).

1. Switching from the METRO plugin to the core integration

If you have been using the METRO plugin and now want to switch to the METRO core integration, you will find detailed instructions on how to do so directly within your PlentyONE system.
Go to Sales Channels » Channel Control Centre, open your METRO account and open the Channel settings. At the top, click Schedule switch to open a guide with settings and useful tips for switching to the core integration.

2. Registering with METRO

First, register as a seller with METRO to start selling items on METRO.

Afterwards, you will receive your access data that are required for the setup in PlentyONE.

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
Product export	daily
Offer creation	daily
Offer updates	hourly
Deactivation of offers	daily
Stock synchronisation	every 15 minutes
Price synchronisation	hourly
Order import	every 15 minutes
Import of cancellations	hourly
Return requests import	hourly

4. Setting up the data exchange

In order for the interface to successfully carry out the order import and the import of return requests, at least the settings in the following table are required.

Table 2. Mandatory settings for METRO
Settings section	Settings
Creating and updating offers on METRO (price and stock synchronisation)
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	METRO is added as a sales channel to your system. The following channel settings for METRO are carried out: The account has been connected via the CONNECT button by entering the client key and the secret key. One or more sales channels for METRO are selected. The Offer export cron is activated. The data exchange is activated.
Catalogue settings	An offer catalogue is created. The mappings for the offer catalogue are carried out. The offer catalogue is activated.
Variation settings	The desired sales channel for METRO must be saved at the variation.
Listing settings	An offer listing is created. The offer listing is activated. The listing contains at least one variation.
Product export
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	METRO is added as a sales channel to your system. The following channel settings for METRO are carried out: The account has been connected via the CONNECT button by entering the client key and the secret key. The Products export cron is activated. The data exchange is activated.
Catalogue settings	The desired product categories were added. A product catalogue is created. The mappings for the product catalogue have been created. The product catalogue is activated.
Listing settings	A product listing is created. The product listing is activated.
Variation settings	The desired sales channel for METRO must be saved at the variation.
Order import
Basic settings for the sales channel	METRO is added as a sales channel to your system. The following channel settings for METRO are carried out: The account has been connected via the CONNECT button by entering the client key and the secret key. The toggle Order import cron is activated. The start date for the order import is entered. The start time for the order import is entered. The Status for cancelled orders is selected. The status for Automatically reject cancel requests from this status is selected. The shipping profiles are mapped. The following general settings are carried out: The data exchange is activated.
Import of cancellations Cancellations are imported automatically if the Order import cron is activated.
Return requests import
Basic settings for the sales channel	METRO is added as a sales channel to your system. The following channel settings for METRO are carried out: The account has been connected via the CONNECT button by entering the client key and the secret key. The toggle button Return request import cron is activated. The Status for accepted return requests is selected The Status for return requests cancelled by customer is selected. The Metro return reasons are mapped. The shipping profiles are mapped. The following general settings are carried out: The data exchange is activated.

5. Workflow of an order

Your items are listed on METRO.
Customers place an order on METRO.
Customers make their payments to METRO.
The order is imported in PlentyONE and already contains all data.
You confirm or cancel the order via flow.
Once you have confirmed the order, you ship it.
You send the shipping confirmation to METRO via flow.
You send the invoice to METRO via flow.
Note: You need to create the invoice as a PDF file in the DocumentBuilder.

5.1. Workflow of a return

Your items are listed on METRO.
Customers place an order on METRO.
Customers make their payments to METRO.
The order is imported in PlentyONE and already contains all data.
You confirm the order via flow.
You ship the order.
You send the shipping confirmation to METRO via flow.
You send the invoice to METRO via flow.
Note: You need to create the invoice as a PDF file in the DocumentBuilder.
Customers receive the order.
Customers can return the entire order or individual items.
Note: Customers must request returns in their METRO account.
The return request is imported into PlentyONE.
- The return is added to the main order in PlentyONE.
You create a return label in the shipping centre.
You send the return label to METRO via flow.
Customers send the return back to you.
Once you have received the return, you accept or reject the return request via flow.
If you have accepted the return request, you create a credit note.
You send the credit note to METRO via Flow.
The refund is initiated.

6. Setting up METRO in PlentyONE

First, add METRO as a sales channel in the Channel Control Centre and carry out the basic settings to set up the sales channel in PlentyONE.

In which countries can I sell with METRO?

With METRO, you can offer your items in France, Germany, Italy, the Netherlands, Portugal, and Spain.

6.1. Adding the sales channel

Add METRO as a sales channel in the Channel Control Centre.

Adding a sales channel:

Open the Sales Channels » Channel Control Centre menu.
Click on Add sales channel ().
→ The menu Add sales channel opens.
Click on Continue in the tile of METRO.
Enter a name for the sales channel.
If asked to, select the Client (Shop) from the drop-down list.
Click on Add METRO.
→ The sales channel for METRO is added.

6.2. Sales channel overview

In the Channel Control Centre you can find an overview of the sales channels set up in your system.

Table 3 explains the different tiles visible in the Sales Channels » Channel Control Centre menu.

Table 3. Tile components in the Sales Channels » Channel Control Centre menu

Component

Explanation

Name

The name of the sales channel.

More

Click here to display more actions for a sales channel.

Listings

Opens the overview of the product and offer listings for this sales channel.

Settings

Opens the respective Settings menu of the sales channel.

Delete sales channel

Deletes the sales channel from the overview.

6.3. Carrying out the channel settings for METRO

Next, carry out the channel settings for METRO.

Carrying out the channel settings for METRO:

Go to Sales Channels » Channel Control Centre.
Click on the METRO tile.
→ The tab Channel settings opens.
Carry out the settings. Pay attention to the explanations given in Table 4.
Note: You can only carry out the settings in the General, Orders, Returns and Map shipping profiles sections once you have correctly entered the client secret and the secret key in the CONNECT section and clicked CONNECT.
Save () the settings.

Table 4. Channel settings for the sales channel METRO
Setting	Explanation
CONNECT ()	Click here to connect to METRO. Enter your client key and your secret key and click CONNECT ().
Schedule switch	If you have already been using the METRO plugin, then you can schedule the switch to the METRO core integration here. Click the button to open detailed instructions and settings for the switch to the METRO core integration.
General
Sales channels	Select the sales channels you want to use on METRO. The following sales channels are currently available for METRO: Metro Germany Mainland Metro Balearic Islands Metro Spain Mainland Metro France Mainland Metro Italy Mainland Metro Netherlands Mainland Metro Portugal Mainland
Orders
Cron for order import	Activate this option to automatically import METRO orders into PlentyONE every 15 minutes.
Order import start date	Enter the desired start date in the format DD.MM.YYYY or select it via the calendar (). Only orders starting from this date will be imported into PlentyONE. Orders which were generated before this time will not be imported.
Order import start time	Enter the desired start time in the format HH:MM. Only orders starting from this time will be imported into PlentyONE. Orders which were generated before this time will not be imported.
Status for cancelled orders	Select the order status for orders that were cancelled. *Note:* The default status of the system is used as standard setting. You can also set a specific METRO cancellation status. *Important:* This field is mandatory once the cron for order import is activated.
Automatically reject cancel requests from this status	From which order status do you want to reject cancellation requests automatically? *Important:* This field is mandatory once the cron for order import is activated.
Products & offers
Product export cron	Activate to export products to METRO once per day.
Offer export cron	Activate to create, update, and deactivate offers on METRO. Creation of new offers: daily Updating offers, including prices: hourly Stock updates: every 15 minutes Deactivation of offers: daily
Returns
Return requests import cron	Activate this option to automatically import METRO return requests into PlentyONE every hour.
Status for accepted return requests	Select the order status for orders for which a return request has been accepted. *Note:* The default status of the system is used as standard setting. You can also set a specific METRO return status.
Status for return requests cancelled by customer	Select the order status for orders for which a return request was withdrawn by the customer.
Map return reasons	Map each METRO return reason to a PlentyONE return reason from the drop-down list. Returns can only be imported if a return reason has been mapped. *Tip:* You can save return reasons in the menu Setup » Orders » Order types » Return. METRO currently has the following reasons for return: Have changed my mind Delivery is not possible Product shelf life exceeded Foreign body in the product Moulds found Strange smell/taste Product label missing/damaged or not legible Delivery failed Delivery rejected Delayed delivery It does not work Packaging intact, contents damaged Packaging and contents damaged Wrong delivery Parts of the order are missing Does not correspond to the description / the photos I found a better price
Map shipping profiles
Map shipping profiles	Map your PlentyONE shipping profiles with the METRO carriers from the drop-down list. The mapping is used in the fulfiment process. Mapping shipping profiles: Click Add mapping. Select the PlentyONE shipping profile. Select the sales channel. Select the Metro carrier.

6.4. Adjusting the general settings

In the menu General settings you may adjust how the sales channel appears and behaves in your system. The functions in this menu are explained in detail in this chapter.

6.4.1. Renaming the sales channel

You can rename the sales channel at any time via the general settings. To do so, proceed as follows.

Renaming a sales channel:

Go to Sales Channels » Channel Control Centre.
Open the sales channel for METRO.
→ The General settings menu opens.
Enter a new Channel name.
Click Save (save).
→ The new channel name is saved.

6.4.2. (De)activating the data exchange

You can completely activate or deactivate the data exchange of a sales channel with its respective marketplace via a single toggle in the general settings. To do so, proceed as follows.

(De)activating the data exchange:

Go to Sales Channels » Channel Control Centre.
Open the sales channel for METRO.
Switch to the menu settings General settings.
Activate the Data exchange active toggle to activate the data exchange between your PlentyONE system and the marketplace.
OR: Deactivate the Data exchange active toggle to deactivate the data exchange between your PlentyONE system and the marketplace.
Click Save (save) to save your settings.

6.5. Activating the 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:

Go to Setup » Orders » Order referrer.
Click Search ().
In the list, navigate to the the desired METRO platform, for example Metro Germany Mainland with the ID 185.01.
Note: If you want to sell your items on METRO, then the parent referrer for METRO must also be activated (185.00 Metro). In addition, you have to activate the referrer for the METRO sales channel on which you want to sell your items.
On the right of the referrer’s line, click Edit ().
→ The window Edit referrer opens.
Activate the option Visible in selection ().
Click SAVE ().
→ The referrer is active.

Note: If you want to sell your items on another METRO sales channel, activate the corresponding order referrer for that sales channel instead. You can also activate multiple order referrers at the same time to offer your items on several or all METRO sales channels.

The following order referrers are available for METRO:

185.00 Metro = Parent referrer for Metro
185.01 Metro Germany Mainland = Metro Germany (mainland)
185.02 Metro France Mainland = Metro France (mainland)
185.03 Metro Italy Mainland = Metro Italy (mainland)
185.04 Metro Spain Mainland = Metro Spain (mainland)
185.05 Metro Netherlands Mainland = Metro Netherlands (mainland)
185.06 Metro Portugal Mainland = Metro Portugal (mainland)
185.07 Metro Balearic Islands = Metro Balearic Islands

6.6. Setting the variation availability

You need to activate the variations you want to sell on METRO and enable them for the relevant sales channel. This is done in the Item » Items » [Open variation] menu.

For one variation
Using variation group function
Using batch processing

Making a variation available for METRO:

Go to Item » Items » [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.
In the Availability and visibility section, enable the option Active ().
Click the Sales channels tab.
In the Sales channels section, activate the sales channel METRO in the Status column ().
Tip: You can activate multiple sales channels at once. To do so, activate the checkboxes to the left of the desired sales channels. Then activate the toggle above the checkbox column (). Click ACTIVATE to confirm the activation.
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:

Go to Item » Items.
Set search filters as needed and start the search.
Select () the variations to be edited.
In the toolbar, click on » Variation group function.
→ The Variation group function window opens.
Select the action Sales channels from the drop-down list Actions.
→ The action is added to the lower part of the window.
Select () the option METRO from the drop-down list Sales channels.
→ The sales channel is added below the Sales channels drop-down list.
Activate () the toggles to the left of the sales channels.
Click EXECUTE & CLOSE 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:

Navigate to the area Market availability.
Activate the checkbox to the left of the option METRO.
Activate the checkbox to the right of the option METRO.
Navigate to the area Availability.
Activate the checkbox to the left of the option Active.
Activate the checkbox to the right of the option Active.
Click on Apply to apply the settings to the variations.

7. Exporting product data

Product data is exported to METRO via catalogues. Catalogues are usually managed via the Data » Catalogues menu. However, you can create catalogues for METRO via the Channel Control Centre as well.

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.

Is this your first time working with catalogues? Then read up on the basic concept of catalogues first.

7.1. Adding product categories

Before you create catalogues for METRO, you have to add the product categories in which you want to offer your items on METRO. This is done in the Sales Channels » Channel Control Centre » [Open sales channel for METRO] » Category whitelist menu.
After you added a METRO product category in the Category whitelist menu, you can create a catalogue for this product category in the Data » Catalogues menu or in the Mapping » Product mapping menu.

Adding product categories:

Go to Sales Channels » Channel Control Centre » [Open sales channel for METRO] » Category whitelist.
Click Add categories (add).
→ The Add categories window opens.
Select a category for offering your items.
Tip: You can search for the category using the input field.
Click SAVE (save).
→ The category was added. You can now create a catalogue for this product category in the Data » Catalogues menu.

7.2. Creating a channel map for products

The sales channel METRO supports Channel maps for a quick mapping of your product data. With Channel maps, you can create cross-category mappings for a sales channel and apply them to catalogues afterwards. All linked catalogues automatically inherit the mapping from the Channel map. This will save you a lot of time as you don’t need to carry out the mappings for each catalogue.
You can find more information on how to create Channel maps in the Channel maps section.

Product data is exported to METRO via Channel maps. You can create channel maps for product data for METRO directly in the Channel Control Centre. Next, add the relevant product catalogues to these Channel maps and map the data fields required by METRO to the product data saved in PlentyONE.

If you have activated the catalogue, the data exchange, the listing and the variations, the product data is automatically exported to METRO once a day.

First, create a Channel map to map product data for METRO. To do so, proceed as follows:

Creating a product channel map:

Open the menu Sales Channels » Channel Control Centre » [Name of your METRO Sales Channel] » Mapping » Product mapping.
Click on Create Channel map ().
Enter a name for the channel map.
In the drop-down list Marketplace, select the option Metro Products.
In the drop-down list Catalogue type, select the option Product.
In the drop-down list Categories, select the product categories you want to sell on METRO.
Click on CREATE CHANNEL MAP.
→ The channel map is created.

7.3. Creating a product catalogue

Once you have created a product Channel map for METRO, you can proceed to create catalogues for the different product categories in which you want to sell on METRO and link them to the Channel map. To do so, proceed as follows:

Linking a product catalogue to the channel map:

Go to Sales Channels » Channel Control Centre » [Name of your METRO sales channel] » Mapping » Product mapping.
In the row of the channel map you want to edit, click on More and select Connect catalogues.
In the drop-down list Select catalogues, click Create catalogue.
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Metro Products.
In the drop-down list Export type, select the option Listing.
In the drop-down list Categories, select the product categories in which you want to sell on METRO.
Note: The catalogues for product listings are created for each sales channel. This means that if you want to list your items in the “T-shirts” product category in Germany and France, you will need to create a catalogue for T-shirts DE and a catalogue for T-shirts FR.
Click CREATE AND CONNECT TO CHANNEL MAP.
→ The catalogue is created and connected to the channel map.

Note: This means that you have to create a separate product catalogue for each METRO product category and for each sales channel (= each country) that you want to sell your items in.
Fo which sales channels (i.e. countries) you can create product catalogues depends on which sales channels you have selected in the Channel settings for METRO.

7.3.1. Mapping data fields in the catalogue

After you have created a Channel map for products, map the sales channel’s data fields to item data saved in PlentyONE. This chapter describes how you map data fields and which particularities apply for item exports to METRO.

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 channel map detail view

Table 5. The channel map detail view

Availability

Explanation

Navigation bar

You can use the navigation at the left edge of the menu to switch to the catalogue or channel map overviews, or to switch to other channel maps you opened previously.

Toolbar

The toolbar contains useful actions for your channel maps:

Save

Saves your changes to the Channel Map.

Vorschau

Opens a preview of the currently set mappings.

Live-Download

Prepares a local record of the currently set mappings for downloading.

Tabs

While common mappings appear in several catalogues and are carried out for all of them at once, catalogue-specific mappings are only done for one specific catalogue. You can use the two tabs at the top of the detail view to switch between views of the different mapping types. Any changes are applied automatically to all catalogues with the respective mapping types.

Sales Channel data fields

On the left-hand side of the mapping list all data fields available for the sales channel are listed. Mandatory fields are labeled with an asterisk (✱).
Tip: You can hide all non-mandatory fields in the detail view by activating the Show only mandatory fields toggle at the top of the mapping list.

PlentyONE data fields

On the right-hand side of the mapping list you can map suitable PlentyONE data fields to the sales channel data fields.

As soon as you have created a Channel map and the status Ready to use is shown in the overview, you can open the Channel map for further editing. A Channel map identifies all common fields, which are all fields that exist in at least two of the selected categories. The mapping of these fields only needs to be done once and automatically applies to all categories.

In order to carry out data field mappings, proceed as follows.

Mapping data fields in a Channel map:

Go to Sales Channels » Channel Control Centre.
Click on the tile of your METRO Sales Channel.
Navigate to Mapping » Product mapping.
→ The catalogue overview opens.
In the side navigation on the left, click Channel maps.
→ The Channel maps overview for that sales channel opens.
Click on the Channel map that you want to edit.
→ The detail view of the Channel map opens.
Next to a data field, click Add data source +.
Select the desired data field from the available categories on the left.
Or: Select an Own value () and enter the respective value.
At the bottom left, click CONFIRM to apply the mappings.
At the top, click Save ().
→ The changes are saved and all connected catalogues with this mapping are adjusted accordingly.
Note: A blue dot in the side navigation on the left indicates unsaved changes.

Mapping key as distinctive feature

Via the so-called mapping keys that are available in the tooltip next to the data field names in the mapping, it is possible to differentiate between data fields with the same name. Thus, the individual mapping key shows to which catalogue the data field belongs so the respective mapping can be carried out.

Changes in mapping affect all connected catalogues

If you change mappings in a Channel map, all connected catalogues with this mapping are updated accordingly.

Removing inherited mapping from a catalogue

If a catalogue is connected to a channel map and there are common fields in the mapping, you can still adjust the mapping for this catalogue and remove the mapping from the Channel map for specific data fields. After the changes, the catalogue is still connected to the Channel map. The changes that have been carried out will only apply to the modified catalogue.

Remove inherited mapping from catalogue:

Go to Data » Catalogues.
→ The catalogue overview opens.
Open the catalogue for which you want to remove the mapping.
Go to the line of the data field for which you want to remove the mapping from the Channel map.
Note: All common fields that have been transferred from the Channel map show the label Inherited from Channel map at the right of the data field column.
Deactivate () the toggle button Inherited from Channel map in order to remove the mapping that has been transferred from the Channel map.
Carry out a new mapping for the data field.
At the bottom left, click CONFIRM to apply the changes.
At the top, click Save ().
→ The changes are saved.
Note: You can reapply the mapping from the Channel map at any time by activating the toggle button Re-inherit from Channel map () once again.

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:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
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:

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.

Is this your first time working with properties? Then read up on the principles of properties first.

Creating a property:

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

Creating a simple 1:1 mapping with properties:

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.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
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.

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:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
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.
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:

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:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
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".
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.
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.

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:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
Click on Confirm.
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.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
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:

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.
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.
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:

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:

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.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol 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 .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

7.3.2. Activating the product export

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the METRO tile.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Metro Products.
In the drop-down list Export type, select the option Listing.
In the drop-down list Category, select a category of the sales channel for which you want to create a catalogue.
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.

Other catalogue settings

Other catalogue settings are optional. Once you carried out the settings described on this page, your catalogue is automatically exported to METRO. That means you can ignore the catalogue settings for Format settings, Export settings and Download settings.

The Format settings, Export settings, and Download settings allow you to create a file with the variation data contained in the catalogue. However, this file does not contain information about whether the data export to METRO was successful.

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

8. Exporting offer data

Offer data is exported to METRO via catalogues. Catalogues are usually managed via the Data » Catalogues menu. However, you can create catalogues for METRO via the Channel Control Centre as well.

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.

Is this your first time working with catalogues? Then read up on the basic concept of catalogues first.

8.1. Creating an offer catalogue

Offer data is exported to METRO via a catalogue. You can create catalogues for METRO directly in the Channel Control Centre. Afterwards, link the METRO data fields with offer data saved in PlentyONE in the catalogue you created. If you have activated the catalogue, the data exchange, the listing and the variations, offer data is automatically exported to METRO once per hour.

Do I always have to create a product catalogue and an offer catalogue?

If you only want to offer products that already exist on METRO, you do not need to create a product catalogue beforehand. You can directly create an offer catalogue.

Offer catalogues for combination of origin and destination

For METRO, you always have to create offer catalogues for the combination of the origin and destination of the items.
The origin is the region in which the items are stored. The destination is the region in which the items are sold. For example, you store your items in Spain and list them on the platform METRO DE.
Depending on where the items are stored and where they are sold, the offer’s stock, prices, shipping costs etc. can differ. Therefore, you have to create separate offer catalogues for the different combinations of origin and destination.
Note that the destination comprises the markets on which the items are sold, and not the countries. For example, if customers from France can shop on Metro.de, then you also can ship your items to France via Metro.de.
Which combinations of origin and destination are available depends on which sales channels you selected in the Channel settings for METRO.

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the METRO tile.
Go to Mapping » Offer mapping.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Metro Offers.
In the drop-down list Export type, select the option Listing.
In the drop-down list Category, select the combination of origin and destination for which you want to create a catalogue.
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.

Other catalogue settings

8.1.1. Mapping data fields in the offer catalogue

After you have created an offer catalogue, map the channel’s data fields to item data saved in PlentyONE. This chapter describes how you map data fields and what particularities apply for item exports to METRO.

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

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 ().
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.

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 ().

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:

Go to Sales Channels » Channel Control Centre.
Click on the tile of your METRO Sales Channel.
Click on the catalogue you want to edit.
→ 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.
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
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:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
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:

Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

Is this your first time working with properties? Then read up on the principles of properties first.

Creating a property:

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

Creating a simple 1:1 mapping with properties:

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.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
Click on Confirm.
→ The property is mapped to the marketplace data field.

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

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.

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:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
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.
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:

1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

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.

Creating a 1:1 mapping with fallback data fields:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
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".
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.
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

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

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:

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.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
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.
Click on Confirm.
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.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
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:

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.
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.
Enter a value into the input field.
→ This value is exported for all variations.

Example: Diameter information

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

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:

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.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol 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 .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

8.1.2. Recommended mappings for offer catalogues

To help you with mapping your data fields for the catalogue, we have created a list of recommended data field mappings. Note that these mappings are recommendations only. Depending on how you manage your item data, other mappings may be more appropriate than the recommendation given here.

Need more information about the PlentyONE data fields? All data fields are described on the manual page for the export type Listing.

List of recommended data field mappings for METRO offer catalogues

Marketplace field	Mandatory?	Recommended PlentyONE mapping
Origin & Destination
Destination	yes	This data field is assigned automatically. Region in which the item is sold.
Origin	yes	This data field is assigned automatically. Region from which the item is shipped.
Stock and prices (EUR)
Quantity	yes	The quantity in stock in the region of origin. If you only use one warehouse for the region of origin, select Stock » [Select warehouse] » Net stock. If you use multiple warehouses for the region of origin, assign a formula and have the sum of net stock levels of the warehouses calculated.
Net price	yes	Assign a formula and use the following formula to have the net price calculated: 100 sales price : (100 + VAT)*.
Net volume price list	no	Price which applies once a certain quantity of items has been purchased. You have to assign two data fields here: The price and the Min quantity of items (a minimum of 2 items) that has to be purchased in order to qualify for this price. Recommended mappings: Export as = This data field contains several price levels. Select a price level to be assigned to this quantity price level. Price = Assign the net price. Assign a formula and use the following formula to have the net price calculated: 100 sales price : (100 + VAT). Min quantity* = Own value, enter the amount that has to be purchased to qualify for this price.
General
GTIN	no	Barcode » GTIN 13
MPN	no	The manufacturer part number. Barcode » [Select barcode] or Property
Manufacturer	no	Item » Manufacturer name or Item » External manufacturer name
Processing time	yes	Time required to process and dispatch the order (in days). Variation » Availability days or Formula to have availability days calculated
Max processing time	no	Maximum time required to process and dispatch the order (in days). Assign a formula which considers processing time and buffer or Own value, a maximum of 99 days
Freight forwarding	no	Use this data field to specify whether items need to be sent via a freight forwarder because they are oversized or overweight. Own value, possible values: 'yes' = If all items should be sent via a freight forwarder. 'no' = If none of the offered items should be sent via a freight forwarder. Variation property if some, but not all items should be sent via a freight forwarder. *Note:* If you switch from the Metro plugin to the core integration, you should map the same property that was mapped in the Metro plugin configuration assistant.
Shipping group name	no	The name of the METRO shipping group. Shipping groups are created in the METRO Seller Office. There you also define which shipping costs apply for each country. In the offer catalogue, you have to assign the exact name of the METRO shipping group. If the METRO shipping group name is not assigned, then no shipping costs will be applied. Recommended mappings: For one shipping group: Own value, enter the name of the METRO shipping group For multiple shipping groups: Property of the type Selection, use the names of the METRO shipping groups as selection values
Business model	no	This data field specifies whether you sell to other businesses (B2B) or to private customers (B2C). Own value with the same value that was selected for Export as
Included fees
Included fees	no	This data field specifies which fees are already included in the net price. *Note:* Included fees only apply if you sell your items in France. Select a fee for Export as and assign the Fee type and the Fee amount. Fee type: Own value with the same value that was selected for Export as Fee amount: Own value with numerical value, a minimum of '0.01'
Internal
Variation ID	yes	This data field is assigned automatically.

Marketplace field

Mandatory?

Recommended PlentyONE mapping

Origin & Destination

Destination

yes

This data field is assigned automatically.
Region in which the item is sold.

Origin

yes

This data field is assigned automatically.
Region from which the item is shipped.

Stock and prices (EUR)

Quantity

yes

The quantity in stock in the region of origin.

If you only use one warehouse for the region of origin, select Stock » [Select warehouse] » Net stock.
If you use multiple warehouses for the region of origin, assign a formula and have the sum of net stock levels of the warehouses calculated.

Net price

yes

Assign a formula and use the following formula to have the net price calculated: 100 * sales price : (100 + VAT).

Net volume price list

Price which applies once a certain quantity of items has been purchased.
You have to assign two data fields here: The price and the Min quantity of items (a minimum of 2 items) that has to be purchased in order to qualify for this price. Recommended mappings:

Export as = This data field contains several price levels. Select a price level to be assigned to this quantity price level.
Price = Assign the net price. Assign a formula and use the following formula to have the net price calculated: 100 * sales price : (100 + VAT).
Min quantity = Own value, enter the amount that has to be purchased to qualify for this price.

General

GTIN

Barcode » GTIN 13

MPN

The manufacturer part number.

Barcode » [Select barcode]

Property

Manufacturer

Item » Manufacturer name

Item » External manufacturer name

Processing time

yes

Time required to process and dispatch the order (in days).

Variation » Availability days

Formula to have availability days calculated

Max processing time

Maximum time required to process and dispatch the order (in days).

Assign a formula which considers processing time and buffer

Own value, a maximum of 99 days

Freight forwarding

Use this data field to specify whether items need to be sent via a freight forwarder because they are oversized or overweight.

Own value, possible values:
- 'yes' = If all items should be sent via a freight forwarder.
- 'no' = If none of the offered items should be sent via a freight forwarder.
Variation property if some, but not all items should be sent via a freight forwarder.

Note: If you switch from the Metro plugin to the core integration, you should map the same property that was mapped in the Metro plugin configuration assistant.

Shipping group name

The name of the METRO shipping group. Shipping groups are created in the METRO Seller Office. There you also define which shipping costs apply for each country. In the offer catalogue, you have to assign the exact name of the METRO shipping group.
If the METRO shipping group name is not assigned, then no shipping costs will be applied.

Recommended mappings:

For one shipping group:

Own value, enter the name of the METRO shipping group

For multiple shipping groups:

Property of the type Selection, use the names of the METRO shipping groups as selection values

Business model

This data field specifies whether you sell to other businesses (B2B) or to private customers (B2C).

Own value with the same value that was selected for Export as

Included fees

This data field specifies which fees are already included in the net price.
Note: Included fees only apply if you sell your items in France.
Select a fee for Export as and assign the Fee type and the Fee amount.

Fee type: Own value with the same value that was selected for Export as
Fee amount: Own value with numerical value, a minimum of '0.01'

Internal

Variation ID

yes

This data field is assigned automatically.

8.1.3. Activating the offer export

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the METRO tile.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Metro Offers.
In the drop-down list Export type, select the option Listing.
In the drop-down list Category, select the combination of origin and destination for which you want to create a catalogue.
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.

Other catalogue settings

9. Managing listings

You create and manage offers for METRO via listings. You can access the product and offer listings for METRO by navigating to Sales Channels » Channel Control Centre » [Open METRO sales channel] and then opening the Offer listings or Product listings menu.

9.1. Offer listings

In the Offer listings menu of the account you gain an overview of your offer listings.

Tip: You can switch between specific views of offers and the listing group view via the button and .

gives you an overview of all the offer listings.
shows you the listing groups of the offer listings. Extend a listing group by clicking , to see all listings within the group.

Applying search filters

If you only want to take a look at certain offer listings, apply filters and narrow down the listings which are displayed. To do so, click on Filters () at the top of the menu.

Applying filters:

Go to Sales Channels » Channel Control Centre » [Open sales channel] » Offer listings.
Click Filters () at the top of the menu.
Select one or multiple filters.
Click Search ().
→ The selected filters are applied and the appropriate offer listings are displayed.
→ The filters that were applied are displayed at the top of the menu.

Tip: You can also reset () the selected filters. Then all offer listings will be displayed again.

Single listing view
Group view

Table 6 offers an overview of the single listing view of offer listings.

Table 6. Offer listings overview

Column

Explanation

Data sync

This column indicates whether data exchange for the offer listing is active or paused.
Tip: You can activate the data exchange in the listing’s line via » toggle_on Activate data sync .

Group ID

The ID of the listing group to which the offer listing is assigned. By clicking on the ID, you can open the listing group view.

Listing Name

Name of the offer listing.

SKU

SKU of the offer listing.
At METRO, an SKU is automatically assigned to the listing. This SKU is assigned by METRO and cannot be changed.

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Status on Channel

Displays the listing status on the sales channel, for example if the listing is already listed on the sales channel. Possible status are:

help = Unknown
progress_activity = Outstanding
progress_activity = Creation pending
cancel = Failed (before creation)
check_circle = Online
cancel = Failed (on update)
pause_circle = Paused
unpublished = Offline

List on

The sales channels on which the offer listing is to be offered are displayed here.

Errors

Indicates whether the listing is incorrect. Click to open the overview of listing errors.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing.
Note: Even if the Activate data sync option is activated, the listing will not be immediately listed on the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when a listing is online.

Delete listing

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

Table 7 offers an overview of the group view of offer listings.

Table 7. Group view of the offer listings

Column

Explanation

Data sync

This column indicates whether data exchange for the listing group is active or paused.
Tip: You can activate the data exchange in the listing group’s line via » toggle_on Activate data sync.

Group name

Name of the listing group

SKU

SKU of the listing group.

Channel

The sales channel to which the listing group is exported.

Errors

The error overview.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

The date and time on which the listing group was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing group.
Note: The data sync must also be activated for the single listing to list an offer listing on a sales channel.
Even if the Activate data sync option is activated in a listing group, the listings in this group will not be immediately listed on the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when the listings are online.

Delete listing group

Delete listing group.

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

9.2. Product listings

In the Product listings menu of the account you gain an overview of your product listings.

Tip: You can switch between specific views of product listings and the listing group view via the button.

gives you an overview of all the product listings.
shows you the listing groups of the product listings. Extend a listing group by clicking , to see all listings within the group.

Applying search filters

If you only want to take a look at certain product listings, apply filters and narrow down the listings which are displayed. To do so, click on Filters () at the top of the menu.

Applying filters:

Go to Sales Channels » Channel Control Centre » [Open sales channel] »Product listings.
Click Filters () at the top of the menu.
Select one or multiple filters.
Click Search ().
→ The selected filters are applied and the appropriate product listings are displayed.
→ The filters that were applied are displayed at the top of the menu.

Tip: You can also reset () the selected filters. Then all product listings will be displayed again.

Single listing view
Group view

Table 8 offers an overview of the single listing view of product listings.

Table 8. Overview of product listings

Column

Explanation

Data sync

This column indicates whether data exchange for the product listing is active or paused.
Tip: You can activate the data exchange in the listing’s line via » toggle_on Activate data sync .

Group ID

The ID of the listing group to which the product listing is assigned. By clicking on the ID, you can open the listing group view.

Listing Name

Name of the listing.

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Status on Channel

Displays the listing status on the sales channel, for example if the listing is already listed on the sales channel. Possible statuses are:

help = Unknown
progress_activity = Outstanding
progress_activity = Creation pending
cancel = Failed (Before creation)
check_circle = Online
cancel = Failed (On update)
pause_circle = Paused
unpublished = Offline

List on

The sales channels on which the product listing is to be offered are displayed here.

Errors

Indicates whether the listing is incorrect. Click to open the overview of listing errors.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

Click here to display more actions.

toggle_on Activate data sync

Delete listing

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

Table 9 offers an overview of the group view of product listings.

Table 9. Group view of the product listings

Column

Explanation

Data sync

Group name

Name of the listing group

Channel

The sales channel to which the listing group is exported.

Errors

The error overview.
No entry = No errors occurred.
= Errors occurred. The number indicates the number of errors.

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

The date and time on which the listing group was created.

Click here to display more actions.

toggle_on Activate data sync

Activate to permit the data exchange between the sales channel and the listing group.
Note: The data sync must be activated for the single listing to exchange product data with the sales channel.
Even if the Activate data sync option is activated for a listing group, the listing data will not be immediately exported to the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when the listings are online.

Delete listing group

Delete listing group.

Preview export results

Generates the preview of the export results. The preview opens in a separate window.

9.3. Creating listings

Products and offers are transferred to METRO as listings. Carry out the following steps to create listings for METRO.

What are product listings and offer listings used for?

If the item you want to sell is not listed on the sales channel yet you will need to create a product listing for it first. Creating a product listing sends the product data to the sales channel and allows for the item to be listed.
In order to actually be able to sell the item on the sales channel you will need to additionally create an offer listing. The offer listing contains data related to the sale of the item, such as its price and stock. In other words, a product listing allows you to list an item on a sales channel that did not previously exist on that sales channel, but in order to sell that item on that sales channel you also need an offer listing for that item.
If the item you want to sell is already listed on the sales channel you only need to create an offer listing. Offer listings send the data related to your offer, such as the price, stock, shipping costs etc., to the sales channel.
In most cases you will only need an offer listing in order to offer a product on a sales channel. Many sales channels do not differentiate between product and offer listings. You only need to send offer listings to these kinds of sales channels.

9.3.1. Creating offer listings

Offer listings are created in three steps:

First, you enter listing details, meaning you select the platform, template, and catalogue for the listing.
Next, you select the variations from which the offer listings are created.
Lastly, check and confirm your selection and create the listings.

You can also create offer listings directly from your product listings. Here you can learn how to do that.

Step 1: Specify listing details:

Go to Sales Channels » Channel Control Centre.
Open the sales channel for METRO.
→ The General settings menu opens.
Open the menu format_list_bulleted Offer listings.
Click arrow_drop_down and select Create offers.
→ The Create offers view opens.
Select the desired METRO platform.
Note: Select a country-specific sales channel, for example Metro Germany Mainland.
Select the template for the catalogue.
Tip: Only templates that are available for the desired METRO platform are displayed.
Select a catalogue with your mappings for offer data.
Tip: If you have no fitting catalogue yet, click on Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.
Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to METRO after the listing is created.
Click NEXT.
→ The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

Select the variations you want to create the offer listing for.
Tip: Use the search to filter for variations.
Note: Only variations that are linked to METRO in the Item » Items » [Open item] » [Open variation] menu are displayed.
Tip: If you want to create offer listings for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Offer listings can be created for a maximum of 50,000 variations at a time.
Click ADD TO SELECTED VARIATIONS.
→ The selected variations are displayed in the Selected variations section.
Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.
Click NEXT.
→ The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

Preview your settings in the Listing details section.
Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group () to see which variations are contained in the respective listing group.
If everything is set and done, click save CREATE OFFER LISTINGS.
Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click CONFIRM to create the offer listings.

9.3.2. Activating offer listings

If an offer listing was accepted by METRO, then an SKU is automatically added to the listing. This SKU is assigned by METRO and cannot be changed.

After you have created the offer listings, you have to activate the listings so that they can be transferred to METRO.
To do so, activate the individual listings and the listing group. The listing can only be transferred to the sales channel if both the listing and the listing group are activated.

Note: You can also activate listings immediately after creation by activating the option Automatically activate listings after creation. If you activate the option to automatically activate listings after creation, you still have to activate the data exchange for the listing group.

Activating offer listings:

Go to Sales Channels » Channel Control Centre » [Open METRO].
→ The General settings menu opens.
Open the Offer listings menu.
In the line of the offer listing you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple offer listings at once, place a check mark next to the desired offer listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

Go to Sales Channels » Channel Control Centre » [Open METRO].
→ The General settings menu opens.
Open the Offer listings menu.
Open the listing group view (folder).
In the line of the listing group you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing group is activated.

9.3.3. Deactivating offers on METRO

If you no longer want to offer an item on METRO, then deactivate the data exchange for the offer listing. If the data exchange is deactivated for an offer listing, a stock of 0 is transferred to METRO and the offer is no longer listed. Furthermore, prices and stock are no longer updated. Deactivated listings are transferred to METRO once per day. If you want to offer an item again, then reactivate the data exchange for the offer listing.

Deactivating an offer listing:

Go to Sales Channels » Channel Control Centre.
Click on the sales channel for METRO.
→ The menu Channel settings opens.
Switch to the menu list Offer listings.
Place a check mark next to the offer listing which should be deactivated (check_box).
At the top, click toggle_on Activate or pause data sync » Pause data sync.
or
Alternatively, you can pause the data exchange in the listing’s line via more_vert » toggle_on Pause data sync.
→ The data exchange for the offer listing is deactivated and it is no longer listed on METRO.
Note: Deactivated listings are transferred to METRO once per day. It can therefore take up to 24 hours for the listing to be taken offline.

9.3.4. Creating product listings

Product listings are created in three steps:

First, you enter listing details, meaning you select the platform, template, and catalogue for the listing.
Next, you select the variations from which the product listings are created.
Lastly, check and confirm your selection and create the listings.

Create product listings using the group function

You can also create product listings directly in the Items menu using the variation group function. You can find more information about the variation group function here.

Step 1: Specify listing details:

Go to Sales Channels » Channel Control Center.
Open the sales channel for METRO.
→ The General settings menu opens.
Open the menu format_list_bulleted Product listings.
Click on Create products.
→ The view Create products opens.
Select select the platform Metro and no country-specific sales channel.
Select the template for the catalogue.
Select a catalogue with your mapping for item data.
Tip: If you have no fitting catalogue yet, click on Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.
Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to METRO after the listing is created.
Click NEXT.
→ The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

Select the variations you want to create the product listing for.
Tip: Use the search to filter for variations.
Note: Only variations that are linked to METRO in the Item » Items » [Open item] » [Open variation] menu are displayed.
Tip: If you want to create a product listing for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Product listings can be created for a maximum of 50,000 variations at a time.
Click ADD TO SELECTED VARIATIONS.
→ The selected variations are displayed in the Selected variations section.
Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.
Click NEXT.
→ The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

Preview your settings in the Listing details section.
Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group () to see which variations are contained in the respective listing group.
If everything is set and done, click save CREATE PRODUCT LISTINGS.
Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click CONFIRM to create the product listings.

9.3.5. Activating product listings

METRO carries out an error validation before the product listing is transferred. All mandatory fields are checked. As the listings are first checked automatically and then by a member of staff at METRO, it may take some time for them to go live.
You can view errors either directly on the listing in the Product Listings menu in the Errors column, or via the Product Listings » Errors menu.

After you have created the product listings, you have to activate the listings so that they can be transferred to METRO.
To do so, activate the individual listings and the listing group. The listing can only be transferred to the sales channel if both the listing and the listing group are activated.

Activating product listings:

Go to Sales Channels » Channel Control Center » [Open METRO].
→ The General settings menu opens.
Open the Product listings menu.
In the line of the product listing you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple product listings at once, place a check mark next to the desired product listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

Go to Sales Channels » Channel Control Center » [Open METRO].
→ The General settings menu opens.
Open the Product listings menu.
Open the listing group view (folder).
In the line of the listing group you want to activate, click more_vert.
Click toggle_on Activate data sync.
Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
→ The data exchange for the listing group is activated.

10. Adjusting the invoice template

You need to make two adjustments to the invoice template for METRO invoices.

Remove your bank details from invoices for METRO. (How?)
Enter payment information depending on the selected payment method. (How?)

We recommend to create a separate invoice template for METRO in the DocumentBuilder. Copy a default template or an existing invoice template and adjust it as described in the following chapters.

Note: You can find more information about the content of customer invoices directly in the METRO Seller Office.

10.1. Removing bank details from invoices

Since customers make payments directly to METRO, your bank details must not appear on invoices for METRO. Otherwise, customers might accidentally send the payment to you.

Removing bank details from invoices for METRO:

Go to Setup » Documents » DocumentBuilder.
Open the template you use for METRO invoices.
Click Open Editor ().
→ The editor opens and the widgets are loaded.
Click on the section where your bank details are shown.
Note: If your bank details are in the footer, click on this section again to display the content.
Click Text () in the section with the bank details.
→ You can now edit the content of the widget.
Remove the variables for the bank details.
Save () the settings.
→ Your bank details are no longer displayed on the invoice template.

10.2. Entering payment information

Depending on the selected payment method, different payment information must appear on the invoices for METRO:

Template: Information for the payment methods credit card, PayPal, and SOFORT

Thank you very much! We have received your payment.

Template: Information for the payment method direct debit

Payment details:

RatePAY direct debit

The invoice amount of € xxxx.xx will be automatically debited from the account you specified in the order process.

RatePAY will inform you of the impending collection at least one day before the direct debit is due.

The seller has assigned the due purchase price claim from your order, including any ancillary claims, to RatePAY GmbH. The holder of the claim is therefore RatePAY GmbH. A debt-discharging payment by you is only possible to RatePAY GmbH. The terms of payment and data protection provisions of Ratepay GmbH apply: www.ratepay.com/legal

Imprint

Template: Information for the payment method purchase on account

Payment details:

RatePAY invoice

The selected payment method: RatePAY invoice

Please transfer the invoice amount due within the next 14 days to the following account:

IBAN: DE50100400000201630100
BIC: COBADEBBXXX
Bank: Commerzbank AG Berlin
Recipient: RatePAY GmbH
Reason for payment: RatePay-ID [RATEPAY-ID]

Imprint

To make management easier, we recommend creating three separate invoice templates for METRO:

One template for the payment methods credit card, PayPal and SOFORT.
One template for the payment method direct debit.
One template for the payment method purchase on account.

Copy the invoice template where you have already removed the bank details.

Entering payment information:

Expand the info box "Text:" for the respective payment method (e.g. credit card, PayPal and SOFORT) above this description.
Copy the text to the clipboard.
Go to Setup » Documents » DocumentBuilder.
Open the template for METRO invoices and the relevant payment method.
Click Open Editor ().
→ The editor opens and the widgets are loaded.
Click on the Text (new) widget on the left and drag and drop it into the section where you want the note to appear.
Tip: A section below the order items or the invoice total is suitable for this purpose. In the default template for invoices, you can also use the section under Manual Comment.
Click Text (New) () in the text widget you just added.
Paste the payment information for the selected method into the input field.
Important: For the payment method direct debit, you also need to replace the placeholder "xxxx.xx" with the variable for the invoice total. You can find this variable on the left under Variables > Order > Order system amounts > Invoice total.
Important: For the payment method purchase on account, you also need to replace the placeholder "[RATEPAY-ID]" with the corresponding ID.
Save () the settings.
Repeat steps 1 to 9 for the other payment methods by selecting the relevant templates.

10.3. Enabling the invoice template for METRO

To ensure that the adjusted invoice template is only used for METRO invoices and the respective payment method, you only enable it for METRO referrers and specific payment methods.

Enabling the invoice template for METRO:

Go to Setup » Documents » DocumentBuilder.
Open the template for METRO invoices.
Click Referrer in the Order settings section.
→ A drop-down list with all active referrers opens.
Deselect all referrers except the referrers you use for Metro.
Click Payment method in the Order settings section.
→ A drop-down list with all available payment methods opens.
Deselect all payment methods except the Metro payment methods you want to use this template for:
- Metro Direct Debit: Payment by direct debit
- Metro Open Invoice: Purchase on account
- Metro SOFORT: Payment by SOFORT (Klarna)
- Metro PayPal: Payment by PayPal
- Metro Credit Card: Payment by credit card
- Metro iDEAL: Payment by iDEAL
- Metro Direct Checkout: Other Metro payment methods
Save () the settings.
→ The invoice template is only used for invoices with the referrers of the selected METRO platforms and the selected METRO payment methods.

Note: To use the invoice template for METRO invoices, you also need to activate it. You can preview the template beforehand to make sure your adjustments are correct. To do this, open the invoice template and click Show preview ().

11. Automating order processing

Create event-based flows to automatically inform METRO about changes to the order status. The following actions are available for METRO in the PlentyONE Flow Studio:

Automatically inform METRO that the order was confirmed. (How?)
Automatically inform METRO that the order was cancelled. (How?)
Automatically inform METRO that the items have been shipped. (How?)
Automatically upload invoices to METRO. (How?)
Automatically upload return labels to METRO. (How?)
Automatically inform METRO that a return request has been accepted. (How?)
Automatically inform METRO that a return request has been rejected. (How?)
Automatically upload credit notes to METRO. (How?)
Automatically inform METRO that a customer has refused a return and the shipment has been sent back to you. (How?)

What is PlentyONE Flow?

With PlentyONE Flow (short: "Flow"), you can automate workflows for your business processes. Flow provides you with two functions in the Automation menu:

In Flow Studio, you create and configure automated workflows. Depending on the trigger type, there are three types of flows: event-based, time-based or manual.
In the Flow Tracker, you can monitor running or completed workflows.

The central element in both functions is the Canvas – a graphical interface on which the workflows are visualised with Actions and Controls. In Flow Studio the canvas can be edited, in Flow Tracker it is only used for visualisation and is therefore read-only.

Is this your first time working with PlentyONE Flow? Then read up on the basic concept of Flow first.

11.1. Sending order confirmations to METRO

Create an event-based flow to automatically inform METRO about the order confirmation.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 10.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 10.
Save () the settings.

Note: The selected statuses, controls and filters in Table 10 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 10. Event-based flow to send an order confirmation to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

For Order status, select a status between Status 4 and Status 5, for example:

[5] Cleared for shipping

You can create a new status for this.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send order confirmation to METRO

11.2. Sending order cancellation to METRO

Create an event-based flow to automatically inform METRO about the cancellation of an order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 11.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 11.
Save () the settings.

Note: The selected statuses, controls and filters in Table 11 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 11. Event-based flow to send an order cancellation to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select an order status, for example:

[8] Cancelled

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send order cancellation to METRO

11.3. Sending shipping confirmation to METRO

Create an event-based flow to automatically inform METRO when you have shipped the items of an order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 12.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 12.
Save () the settings.

Note: The selected statuses, controls and filters in Table 12 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 12. Event-based flow for sending shipping confirmations to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Order > Book outgoing items

Select an order status, for example:

[7] Outgoing items booked

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send fulfilment notification to METRO

11.4. Uploading invoices to METRO

Create an event-based flow to automatically upload invoices to METRO.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 13.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 13.
Save () the settings.

Note: The selected statuses, controls and filters in Table 13 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 13. Event-based flow for uploading invoices to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Document > Document created

Select a document type, for example:

Invoice

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send invoice to METRO

11.5. Uploading return labels to METRO

Create an event-based flow to automatically upload return labels to METRO.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 14.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 14.
Save () the settings.

Note: The selected statuses, controls and filters in Table 14 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 14. Event-based flow for uploading return labels to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Document > Return label saved

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send return label to METRO

11.6. Reporting acceptance of a return request to METRO

Create an event-based flow to automatically inform METRO when you have accepted a return request.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 15.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 15.
Save () the settings.

Note: The selected statuses, controls and filters in Table 15 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 15. Event-based flow to report acceptance of a return request to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select the status that you specified in the channel settings as Status for accepted return requests.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send “accept return request” to METRO

11.7. Reporting rejection of a return request to METRO

Create an event-based flow to automatically inform METRO when you have rejected a return request.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 16.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 16.
Save () the settings.

Note: The selected statuses, controls and filters in Table 16 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 16. Event-based flow to report rejection of a return request to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select the status that you specified in the channel settings as Status for return requests cancelled by customer.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send “decline return request” to METRO

11.8. Uploading credit notes to METRO

Create an event-based flow to automatically upload credit notes to METRO.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 17.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 17.
Save () the settings.

Note: The selected statuses, controls and filters in Table 17 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

Table 17. Event-based flow for uploading credit notes to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Document > Document created

Order > Order status changed

Select a document type, for example:

Credit Note

Select an order status, for example:

[9.5] Credit note created

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Send credit note to METRO

11.9. Reporting receipt of a return to METRO

Create an event-based flow to automatically inform METRO that a customer has refused a return and the shipment has been sent back to you.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 18.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 18.
Save () the settings.

Note: The selected statuses, controls and filters in Table 18 only serve as an example. Select the statuses, controls and filters for the flow which best suit your workflow.

For this flow, we recommend creating a dedicated status for returned orders beforehand.

Table 18. Event-based flow for reporting a returned order to METRO

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select an appropriate order status. For example, you can create a new status for returned orders.

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If there is more than one filter, add the others as conditions (). Select AND as the relationship between the conditions.

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Select the order referrers for the METRO sales channels that you want to use this flow for.

Actions

Multichannel > Metro

Report “returned order” to METRO

12. Viewing the data log

Error reports of the export are logged in the Data » Log menu. In order to view the data log and search for specific errors, proceed as follows.

For METRO, reports specify the account and the catalogue name. This way, you can see at a glance which catalogue the report is for.

Viewing the data log:

Go to Data » Log.
→ The data log overview opens.
At the top, click on Filter ().
For the Identifier filter, select the option Metro.
Tip: For a more detailed search, you can additionally use the Integration filter in order to search for a specific path.
Click Search ().
→ The error reports are shown according to the filter settings.

METRO (closed beta) (Setup via Channel Control Centre)

1. Switching from the METRO plugin to the core integration

2. Registering with METRO

3. Frequency of data exchange

4. Setting up the data exchange

5. Workflow of an order

5.1. Workflow of a return

6. Setting up METRO in PlentyONE

6.1. Adding the sales channel

6.2. Sales channel overview

6.3. Carrying out the channel settings for METRO

6.4. Adjusting the general settings

6.4.1. Renaming the sales channel

6.4.2. (De)activating the data exchange

6.5. Activating the order referrer

6.6. Setting the variation availability

7. Exporting product data

7.1. Adding product categories

7.2. Creating a channel map for products

7.3. Creating a product catalogue

7.3.1. Mapping data fields in the catalogue

7.3.2. Activating the product export

Other catalogue settings

8. Exporting offer data

8.1. Creating an offer catalogue

Other catalogue settings

8.1.1. Mapping data fields in the offer catalogue

8.1.2. Recommended mappings for offer catalogues

8.1.3. Activating the offer export

Other catalogue settings

9. Managing listings

9.1. Offer listings

9.2. Product listings

9.3. Creating listings

9.3.1. Creating offer listings

9.3.2. Activating offer listings

9.3.3. Deactivating offers on METRO

9.3.4. Creating product listings

9.3.5. Activating product listings

10. Adjusting the invoice template

10.1. Removing bank details from invoices

10.2. Entering payment information

10.3. Enabling the invoice template for METRO

11. Automating order processing

11.1. Sending order confirmations to METRO

11.2. Sending order cancellation to METRO

11.3. Sending shipping confirmation to METRO

11.4. Uploading invoices to METRO

11.5. Uploading return labels to METRO

11.6. Reporting acceptance of a return request to METRO

11.7. Reporting rejection of a return request to METRO

11.8. Uploading credit notes to METRO

11.9. Reporting receipt of a return to METRO

12. Viewing the data log

Is this page helpful?

Is this page helpful?