METRO Layer Integration (closed beta)

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.

Closed beta test phase

This METRO integration is currently in a closed beta testing phase and is only available to sellers who are already using the METRO plugin.
Are you already using the METRO plugin and interested in participating in the closed beta test phase? Then get in touch with your PlentyONE contact person (Business Development / Account Management).

What features are available during the closed beta testing phase?

During the closed beta testing phase, the following features are available with the new METRO integration:

  • Order import

  • Import of return requests

  • Management of cancellations, returns, and refunds

  • Automation of order processing via PlentyONE Flow

Item export as well as price and stock synchronisation are currently only possible via the existing METRO plugin.

Note: You can use the METRO plugin alongside the new METRO Layer Integration. This allows you to continue exporting items to METRO via the plugin while importing orders through the new integration.
Note that you cannot use the flows of the METRO Layer Integration for orders that have been imported via the METRO plugin. Likewise, event procedures of the METRO plugin will not apply to orders imported via the METRO Layer Integration.

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

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

Order import

every 15 minutes

Cancellation import

hourly

Return request import

hourly

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

Order import

Basic settings for the sales channel

  • An account for METRO is created.

  • 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 toggle button 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 account is activated.

Cancellation Import
Cancellations are imported automatically if the Order import cron is activated.

Return request import

Basic settings for the sales channel

  • An account for METRO is created.

  • 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 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 account is activated.

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

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

5. Setting up METRO in PlentyONE:

First, create an account and carry out the basic settings to set up the sales channel in PlentyONE. To do so, proceed as described below.

5.1. Creating an account

In the Sales Channels » Accounts menu, create an account for METRO.

Creating an account:

  1. Open the Sales Channels » Accounts menu.

  2. Click on Create account (add).
    → The window Create account opens.

  3. Select METRO from the drop-down list Platform.

  4. Select the Client (Shop) from the drop-down list.

  5. Enter a name for the account.

  6. Click on add CREATE.
    → The account for METRO is created.

5.2. Account overview

In the Sales Channels » Accounts menu, you can create your METRO account. In addition, you can find an overview of the account here.

Table 3 contains an overview of the accounts in the Sales Channels » Accounts menu.

Table 3. Accounts in the Sales Channels » Accounts menu.
Setting Explanation

bigtop_updates Connection

Connection status of the account.
Accounts can have the following connection statuses:

  • Connected (bigtop_updates) = The account is connected to the sales channel.

  • Disconnected (signal_disconnected) = The account is not connected to the sales channel.
    Note: If the account is Disconnected, this may be due to missing or incorrect basic settings for the sales channel.

Name

Account name.

more_vert More

Click here to display more actions.

settings Account settings

Open the account settings.

error Errors

Open errors for Product listings oder Offer listings. The number of errors for the product listings or offer listings for this account is shown in brackets.

list Product listings

Open the overview of product listings for this account.

toggle_off Activate account

Activate the account.

delete Delete account

Delete the account.

Listings online

Hover over Listings online to see the number of product listings and offer listings that are listed on sales channels for this account.

Errors

Hover over Errors to see the number of errors that occurred for product listings and offer listings.

5.3. Carrying out the channel settings for METRO

Next, carry out the channel settings for METRO.

Carrying out the channel settings for METRO:

  1. Open the Sales Channels » Accounts menu.

  2. Click on the METRO tile.
    → The tab Channel settings opens.

  3. Carry out the settings. Pay attention to the explanations given in [grundeinstellungen-metro].
    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.

  4. Save () the settings.

Note: You need to create a separate METRO account for each METRO sales channel on which you offer items.

Table 4. Channel settings for the sales channel METRO
Setting Explanation

CONNECT (link)

Click here to connect to METRO. Enter your client key and your secret key and click CONNECT (link).

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 a date via the calendar (today).
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.

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 has been rejected.

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 service providers

Map shipping service providers

Map your PlentyONE shipping profiles with the METRO carriers from the drop-down list.

Mapping shipping profiles:

  1. Click Add mapping.

  2. Select the PlentyONE shipping profile.

  3. Select the sales channel.

  4. Select the Metro carrier.

5.4. Modifying the account settings

In the Account settings tab, you can adjust the account’s name.

Carrying out account settings:

  1. Open the Sales Channels » Accounts menu.

  2. Open the account for METRO.

  3. Open the settings Account settings tab.

  4. Enter the name.

  5. Save () the settings.

5.5. Activating the account

In the Sales Channels » Accounts menu, activate the account to enable the data exchange with METRO.

Activating the account for METRO:

  1. Open the Sales Channels » Accounts menu.

  2. Click More (more_vert) in the tile for METRO.
    → A drop-down list with further options appears.

  3. Select the Activate account (toggle_on) option from the drop-down list.
    → The account is activated and data can be exchanged with METRO.

5.6. 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 Germany Mainland:

  1. Go to Setup » Orders » Order referrer.

  2. Click Search (search).

  3. In the list, navigate to the option Metro Germany Mainland with the ID 185.01.

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

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

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

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

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

  1. Open the Setup » Documents » DocumentBuilder menu.

  2. Open the template you use for METRO invoices.

  3. Click on Open Editor (edit).
    → The editor opens and the widgets are loaded.

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

  5. Click Text (edit) in the section with the bank details.
    → You can now edit the content of the widget.

  6. Remove the variables for the bank details.

  7. Save () the settings.
    → Your bank details are no longer displayed on the invoice template.

6.2. Entering payment information

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

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

Thank you very much! We have received your payment.

Text: Information for the payment method direct debit (only for the German market)

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 / Impressum

Ratepay GmbH | Franklinstr. 28-29 | 10587 Berlin
Management: Miriam Wohlfarth | Luise Linden
Local Court Berlin Charlottenburg | HRB 124156 B | VAT ID No. DE270098222

Text: 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]

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 / Impressum

Ratepay GmbH | Franklinstr. 28-29 | 10587 Berlin
Management: Miriam Wohlfarth | Luise Linden
Local Court Berlin Charlottenburg | HRB 124156 B | VAT ID No. DE270098222

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

  1. One template for the payment methods credit card, PayPal and SOFORT.

  2. One template for the payment method direct debit.

  3. One template for the payment method purchase on account.

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

Entering payment information:

  1. Expand the info box "Text:" for the respective payment method (e.g. credit card, PayPal and SOFORT) above this description.

  2. Copy the text to the clipboard.

  3. Open the Setup » Documents » DocumentBuilder menu.

  4. Open the template for METRO invoices and the relevant payment method.

  5. Click on Open Editor (edit).
    → The editor opens and the widgets are loaded.

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

  7. Click on Text (New) (edit) in the text widget you just added.

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

  9. Save () the settings.

  10. Repeat steps 1 to 9 for the other payment methods by selecting the relevant templates.

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

  1. Open the Setup » Documents » DocumentBuilder menu.

  2. Open the template for METRO invoices.

  3. Click Referrer in the Order settings section.
    → A drop-down list with all active referrers opens.

  4. Deselect all referrers except the referrers you use for Metro .

  5. Click Payment method in the Order settings section.
    → A drop-down list with all available payment methods opens.

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

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

7. 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 flow types: event-based, time-based or manual.

  • In the Flow Tracker, you can monitor ongoing or finished 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.

7.1. Sending order confirmation to METRO

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

Creating an event-based flow

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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 5.
        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.

  3. Configure the new flow according to Table 5.

  4. Save ​​() the settings.

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

Table 5. Event-based flow to send an order confirmation to METRO
Setting Option Selection

Trigger selection

Select an event, 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.

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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 6.
        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.

  3. Configure the new flow according to Table 6.

  4. Save ​​() the settings.

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

Table 6. Event-based flow to send an order cancellation to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

Select an order status, for example:

  • [8] Cancelled

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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 7.
        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.

  3. Configure the new flow according to Table 7.

  4. Save ​​() the settings.

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

Table 7. Event-based flow for sending shipping confirmations to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

or

  • Order > Book outgoing items

Select an order status, for example:

  • [7] Outgoing items booked

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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 fulfillment to METRO

7.4. Uploading invoices to METRO

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

Creating an event-based flow

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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 8.
        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.

  3. Configure the new flow according to Table 8.

  4. Save ​​() the settings.

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

Table 8. Event-based flow for uploading invoices to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Document > Document created

Select a document type, for example:

  • Invoice

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

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

7.5. Uploading return labels to METRO

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

Creating an event-based flow

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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 9.
        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.

  3. Configure the new flow according to Table 9.

  4. Save ​​() the settings.

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

Table 9. Event-based flow for uploading return labels to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Document > Return label saved

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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.

  3. Configure the new flow according to Table 10.

  4. Save ​​() the settings.

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

Table 10. Event-based flow to report acceptance of a return request to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

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

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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.

  3. Configure the new flow according to Table 11.

  4. Save ​​() the settings.

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

Table 11. Event-based flow to report rejection of a return request to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

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

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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

7.8. Uploading credit notes to METRO

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

Creating an event-based flow

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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.

  3. Configure the new flow according to Table 12.

  4. Save ​​() the settings.

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

Table 12. Event-based flow for uploading credit notes to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Document > Document created

or

  • Order > Order status changed

Select a document type, for example:

  • Credit note

or

Select an order status, for example:

  • [9.5] Credit note created

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → 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.

  3. Configure the new flow according to Table 13.

  4. Save ​​() the settings.

Note: The selected statuses, controls and filters in Table 13 only serve as an example. Select the status, 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 13. Event-based flow for reporting a returned order to METRO
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

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

Control element

Branch

  • Object type: Order

  • Filter settings for the branch:
    Note: If you want to use multiple filters, add the additional filters as conditions (playlist_add). Select AND as the relationship between the conditions.

Filter Operator Input field

Order > Order type

Is in (IN)

Sales 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

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

Viewing the data log:

  1. Go to Data » Log.
    → The data log overview opens.

  2. At the top, click on Filter (tune).

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

  4. Click Search (search).
    → The error reports are shown according to the filter settings.