MediaMarktSaturn Core Integration
MediaMarkt and Saturn offer customers a wide range of technology, electronics and multimedia products.
Parallel use of both MediaMarktSaturn integrations
It is not possible to use the MediaMarkt plugin and the MediaMarktSaturn Core Integration at the same time. This also applies if you connect different country platforms via the plugin and the Core Integration (e.g. if you connect your German shop via the plugin and your Spanish shop via the Core Integration). |
Switch from MediaMarkt plugin to MediaMarktSaturn Core Integration
If you want to switch from the MediaMarkt plugin to the MediaMarktSaturn Core Integration, you can transfer your existing settings and SKUs to the new MediaMarktSaturn Core Integration. You can find instructions on how to do this here. |
1. Becoming a seller at MediaMarktSaturn
First, register as a seller with MediaMarktSaturn to start selling items on MediaMarktSaturn.
After registering, you will receive login details from MediaMarktSaturn. You need these login details to set up MediaMarktSaturn in PlentyONE.
2. Frequency of data exchange
After you have set up MediaMarktSaturn in PlentyONE, data is exchanged with the market in the intervals described in Table 1.
Data | Interval |
---|---|
Item export |
once a day |
full item export (creating + and updating offers) |
once a day |
Stock synchronisation |
every 15 minutes |
Price synchronisation |
hourly |
Order import |
every 15 minutes |
Importing refunds |
every 15 minutes |
3. Setting up the data exchange
In order for the interface to successfully carry out the item export, the offer export, the stock and price synchronisation, the order import and the import of refunds, certain settings are mandatory. Pay attention to the following list.
Settings section | Settings |
---|---|
Item export |
|
Basic settings for the market |
|
Catalogue settings |
|
Variation settings |
|
Offer export |
|
Basic settings for the market |
|
Catalogue settings |
|
Variation settings |
|
Stock synchronisation / Price synchronisation |
|
Basic settings for the market |
|
Catalogue settings |
|
Variation settings |
|
Order import |
|
Basic settings for the market |
|
4. Workflow of the item data and offer export to MediaMarktSaturn
Workflow of the item data export
-
If you want to offer a product that is not yet listed on MediaMarktSaturn, create an item data catalogue with the following mandatory information:
-
Shop SKU
-
Title (DE)
-
EAN
-
Main Product Image
-
Brand
Depending on the product category, further mandatory information may be required.
Note: Pay attention to the information on recommended data field mappings.
-
-
The item data catalogue is exported to MediaMarktSaturn.
Important: If the item data catalogue contains a product that does not yet exist on MediaMarktSaturn, MediaMarktSaturn must first approve this product. The report for the item data catalogue remains in PENDING status until the product is approved.
Workflow of the offer export to MediaMarktSaturn
Do I always have to create a product catalogue and an offer catalogue?
If you only want to offer products that already exist on MediaMarktSaturn, you do not need to create an item data catalogue beforehand. You can directly create an offer catalogue. |
-
Create an offer catalogue with the following mandatory information:
-
Offer SKU
-
Offer Price
-
Product ID Type
Tip: Use the EAN as primary identifier.
Alternatively, you can enter the SHOP-SKU. Make sure to select the same source for the SHOP-SKU that you used for the Shop SKU field in the item data catalogue. -
Offer State
-
Price type for strikethrough prices
-
-
The offer catalogue is exported to MediaMarktSaturn.
5. Workflow of an order
-
Your items are listed on MediaMarktSaturn.
-
Customers place an order on MediaMarktSaturn.
-
The incomplete order is imported into PlentyONE.
→ At this point, the invoice and delivery address for the order are still missing and the order has not yet been paid for. -
If the order is accepted, customers make their payments to MediaMarktSaturn.
-
With the payment confirmation, the invoice and delivery address on the order are updated in PlentyONE.
→ The order is complete. -
The order is shipped.
-
The shipping confirmation must be uploaded to MediaMarktSaturn by event procedure.
Note: For this, you must first map the shipping profiles in PlentyONE with the shipping profiles from MediaMarktSaturn. -
The invoice must be uploaded to MediaMarktSaturn by event procedure.
→ The invoice is sent to the customer via event procedure.
No cancellations possible
At MediaMarktSaturn, customers cannot cancel orders. The items need to be returned instead. |
6. Setting up MediaMarktSaturn in PlentyONE
Now set up the market in PlentyONE.
6.1. Account overview
The Setup » Markets » MediaMarktSaturn » Settings menu provides an overview of your MediaMarktSaturn accounts. Table 3 lists the columns and available actions in the account overview.
Configuring columns
Click on Configure columns (settings) to define which settings should be displayed in the account overview. |
Note: The account overview looks different depending on which columns you add or hide via Configure columns (settings). The following table only lists the columns which are displayed in the overview by default.
Column | Explanation | ||
---|---|---|---|
ID |
The ID of your MediaMarktSaturn account. The ID is assigned automatically when you create a new account. |
||
Name |
The name of your MediaMarktSaturn account. |
||
Active |
circle = The account is active and data is exchanged with MediaMarktSaturn. Note: Data is only exchanged with MediaMarktSaturn if the account is both connected with MediaMarktSaturn and active. In addition, a MediaMarktSaturn API key must be saved for the account. Click on Test connection in the account settings in order to connect to MediaMarktSaturn. |
||
Client |
The client (plentyShop) that orders of this MediaMarktSaturn account are assigned to. |
||
Order import |
done = The order import for this account is active. Orders are imported into PlentyONE every 15 minutes. close = Orders are not imported. |
||
Item export |
done = The item export for this account is active. Items are exported to MediaMarktSaturn once per day. close = Items are not exported. |
||
Offer export |
done = The offer export for this account is active. A full offer export is carried out once per day. This means that new offers are created and existing offers are updated. close = Offers are not exported. |
||
more_vert More |
Click here to display more actions.
|
6.2. Carrying out the basic settings
Carry out the basic settings for the market in the Setup » Markets » MediaMarktSaturn » Settings menu.
First, add a new account for MediaMarktSaturn.
Adding a new account:
-
Go to Setup » Markets » MediaMarktSaturn » Settings.
-
Click on Add account (add).
→ The Add account window opens. -
Enter an account name.
-
Save () the settings.
→ A view with account settings opens. -
Carry out the additional settings. Pay attention to the explanations given in Table 4.
-
Save () the settings.
Setting | Explanation | ||
---|---|---|---|
Save |
Save the settings. |
||
more_vert More |
Click here to display more actions.
|
||
Test connection |
Click here to test whether a connection to MediaMarktSaturn could be established. In this step, the API key is checked. Note: You have to test the connection again if you change the API key. |
||
General |
|||
Account |
The name of your MediaMarktSaturn account. You entered the name when you created the account. |
||
Active |
Activate the MediaMarktSaturn account. The data exchange with MediaMarktSaturn is started. We recommend to only activate the account after you carried out all settings. Note: The account has to be connected to a MediaMarktSaturn account so that data can be exchanged between PlentyONE and MediaMarktSaturn. The MediaMarktSaturn API key must be saved in PlentyONE. |
||
MediaMarktSaturn API key |
Enter the API key. You have received the API key from MediaMarktSaturn. |
||
Client |
Select a client (shop). The orders of this MediaMarktSaturn account will be assigned to this client. |
||
Item |
|||
Item export |
Activate to export items to MediaMarktSaturn once per day. |
||
Map shipping profiles |
Map your PlentyONE shipping profiles with shipping profiles from MediaMarktSaturn. Mapping shipping profiles:
|
||
Orders |
|||
Order import |
Activate to import MediaMarktSaturn orders into PlentyONE every 15 minutes. |
||
Order import start date |
Enter a date in the format D.M.YYYY or select a date via the calendar (today). |
||
Allow cancellations for orders with invoice |
Should customers be able to cancel an order if an invoice was already created? Note: At MediaMarktSaturn, customers cannot cancel orders. |
||
Status for shipped orders |
Select the order status for orders that were shipped. |
||
Status for credit notes |
Select the order status for orders that were refunded by MediaMarktSaturn. |
||
Status for cancelled orders |
Select the order status for orders that were cancelled. Note: At MediaMarktSaturn, customers cannot cancel orders. |
||
Offers |
|||
Offer export |
Activate to export offers to MediaMarktSaturn once per day. Note: Offers can only be exported if an item has already been activated. If an item has not been activated by Saturn, then the offer cannot be exported. |
6.3. 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.
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 MediaMarktSaturn:
-
Go to Setup » Orders » Order referrer.
-
Click Search (search).
-
In the list, navigate to the option MediaMarktSaturn with the ID 178.00.
-
On the right of the referrer’s line, click on Edit (edit).
→ The window Edit referrer opens. -
Activate the option Visible in selection (toggle_on).
-
Click on Save (save).
→ The referrer is active.
Note: If you want to sell your items on MediaMarktSaturn, then the parent referrer for MediaMarktSaturn must also be activated (178.00 MediaMarktSaturn). In addition, you have to activate the referrer for the MediaMarkt or Saturn country platform on which you want to sell your items. The following order referrers are available for MediaMarkt and Saturn:-
178.00 MediaMarktSaturn = Parent referrer for MediaMarktSaturn
-
178.01 MediaMarkt Germany = MediaMarkt Germany
-
178.02 MediaMarkt Austria = MediaMarkt Austria
-
178.03 MediaMarkt Spain = MediaMarkt Spain
-
178.04 MediaMarkt Netherlands = MediaMarkt Netherlands
-
178.05 Saturn Germany = Saturn Germany
-
178.06 MediaMarkt Italy = MediaMarkt Italy
-
178.07 MediaMarkt Belgium = MediaMarkt Belgium
-
178.08 MediaMarkt Poland = MediaMarkt Poland
-
Example 1: If you want to sell your items on MediaMarkt Germany, you have to activate the parent referrer for MediaMarktSaturn (178.00 MediaMarktSaturn) and the referrer for MediaMarkt Germany (178.01 MediaMarkt Germany).
Example 2: If you want to sell your items on MediaMarkt Germany and MediaMarkt Netherlands, then activate the parent referrer for MediaMarktSaturn (178.00 MediaMarktSaturn) as well as the referrer for MediaMarkt Germany (178.01 MediaMarkt Germany) and the referrer for MediaMarkt Netherlands (178.04 MediaMarkt Netherlands).
7. Preparing variations
Now, prepare your variations.
7.1. Setting the variation availability
You need to activate the variations that you want to sell on MediaMarktSaturn. This is done in the Availability and visibility section of a variation within the Item » Items » [Open item] » [Open variation] menu.
Making a variation available for MediaMarktSaturn:
-
Go to Item » Items » [Open item] » [Open variation].
Tip: To sell all variations of an item on MediaMarktSaturn, 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, activate the option Active.
-
In the Sales channels section, click Add sales channels (add).
→ The window Add sales channels opens. -
In the drop-down list Sales channels, select the option MediaMarktSaturn.
-
Click Apply.
→ The sales channel is added. -
Save () the settings.
→ The variation is available for MediaMarktSaturn.
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 MediaMarktSaturn using the variation group function:
-
Go to Item » Items.
-
Select () the variations to be edited.
-
In the toolbar, click on layers » layers 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. -
In the drop-down list Sales channels, select the option MediaMarktSaturn.
-
Select the action Active from the drop-down list Actions.
→ The action is added to the lower part of the window. -
Activate the option Active.
-
Navigate to the area Availability.
-
Click Execute to apply the settings.
Batch processing allows you to edit several variations at once. You use filters to limit which variations are edited.
Making several variations available for MediaMarktSaturn using batch processing:
-
Go to Item » Batch processing.
-
Click on the tab Variations in the upper left corner.
-
Use the filters on the left to specify which variations should be processed.
-
Navigate to the area Market availability.
-
Activate the checkbox to the left of the option MediaMarktSaturn.
-
Activate the checkbox to the right of the option MediaMarktSaturn.
-
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.
8. Exporting item data
Item data is exported to MediaMarktSaturn using catalogues. Go to Data » Catalogues to create catalogues for MediaMarktSaturn.
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.
8.1. Adding product categories
Before you can create catalogues for MediaMarktSaturn, you have to add the product categories in which you want to offer your items on MediaMarktSaturn. This is done in the Setup » Markets » MediaMarktSaturn » Add catalogue templates menu.
After you added a product category in the Add catalogue templates menu, you can create a catalogue for this product category in the Data » Catalogues menu.
Adding product categories:
-
Go to Setup » Markets »MediaMarktSaturn » Add catalogue templates.
-
Click on Add categories (add).
-
Select a category for offering your items.
Tip: You can either search the category by entering the name in the input field or you can expand the category tree to browse the available categories. -
Save () the settings.
→ The category was added. You can now create a catalogue for this category in the Data » Catalogues menu.
8.2. Linking variations to a MediaMarktSaturn product category
Which variations are exported to MediaMarktSaturn?
You can use catalogue filters in the menu Data » Catalogues » [Open catalogue] » Filters to define which variations should be exported to MediaMarktSaturn. The filters MediaMarktSaturn and Active are already set by default. This means that all variations which are active and which have the market availability for MediaMarktSaturn in the Availability tab will be exported to MediaMarktSaturn. |
You can use properties to define in which product category on MediaMarktSaturn a variation should be listed. For example, you can create the property MediaMarktSaturn product categories of the type selection and use the MediaMarktSaturn product categories as selection values. You can then use the filters in the catalogue and filter for the property to define into which product category on MediaMarktSaturn the variations should be exported.
Creating a property of the type selection:
-
Go to Setup » Settings » Properties » Configuration.
-
Click on add Create property.
→ The settings for the new property are displayed. -
In the area Details, select the type selection.
-
In the area Details, select the section Items.
-
Carry out the additional settings.
→ Tip: For example, you can use MediaMarktSaturn product category as name for the property. -
Save (save) the settings.
→ The property is created. -
In the area Selection values, click on Create selection value.
-
Enter a name for the selection value.
→ Tip: You can enter the different MediaMarktSaturn product categories as names for the selection values. -
Save (save) the settings.
→ The selection value is created and displayed in the overview. The value automatically receives a consecutive and unique ID that cannot be changed. You need this ID to only export specific variations in a catalogue.
Next, link the desired variations with the selection property that you created.
Link variation with property:
-
Go to Item » Edit item » [Open item].
-
Click on the Variations tab.
-
Open the variation that should be linked.
-
Open the Properties tab.
-
In the Variation properties area, select the property you created from the Properties drop-down list and click on Add ().
→ The property is added. -
Select the desired product category from the drop-down list Value.
-
Save () the settings.
Afterwards, add the ID of the selection value as filter in the desired MediaMarktSaturn catalogue.
Tip: Open the property in the menu Setup » Settings » Properties » Configuration to see the IDs of the selection values.
Apply filters in the catalogue:
-
Go to Data » Catalogues.
-
Open the MediaMarktSaturn catalogue.
-
On the left-hand side, open the tab Filters.
-
In the area Custom filters, select the filter Linked to at least one property selection value.
-
Enter the ID of the selection value of the property.
Tip: Open the property in the menu Setup » Settings » Properties » Configuration to see the IDs of the selection values. -
Save (save) the settings.
8.3. Creating a catalogue
Item data is exported to MediaMarktSaturn using catalogues. To export your items to MediaMarktSaturn, create a catalogue in the Data » Catalogue menu. Afterwards, link the MediaMarktSaturn data fields with item data saved in PlentyONE in the catalogue.
After you activate the catalogue, the catalogue data is automatically exported to MediaMarktSaturn in regular intervals.
Note: There is a separate catalogue format for each MediaMarktSaturn product category. Different item data is exported in the different catalogue formats, depending on which information MediaMarktSaturn requires for each product category.
This means that you have to create a separate catalogue for each MediaMarktSaturn product category that you want to sell your items in. Go to Setup » Markets » MediaMarktSaturn » Add catalogue templates to add product categories.
Create a catalogue for offers
For MediaMarktSaturn, you always have to create a catalogue for offers. To do so, select the format Offer when you create a catalogue in the Data » Catalogues menu. |
Creating a catalogue:
-
Go to Data » Catalogues.
-
Click on Create catalogue (add).
-
Enter a name for the catalogue.
-
In the drop-down list Marketplace, select the option MediaMarktSaturn.
-
In the drop-down list Export type, select the option Item (new).
-
In the drop-down list Category, select a category of the sales channel.
-
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 MediaMarktSaturn. 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 MediaMarktSaturn was successful.
You should 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.3.1. Mapping data fields in the catalogue
After you have created a catalogue, map the market’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 MediaMarktSaturn.
-
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.

Availability | Explanation |
---|---|
Navigation |
When you open a catalogue, the view Mapping is shown. On the very left is the navigation.
|
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 (✱). |
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 Data » Catalogues.
-
Click on the catalogue.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column. -
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.
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:

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

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:
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:
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":
-
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":
-
To the left of the fallback data field, click on the cog ().
→ The window Data column settings is shown. -
For the setting Fallback condition, select the option Empty.
-
Click on Save.
→ The fallback data field is added with the fallback condition "empty". -
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.

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

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 (calculate).
→ 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 (add).
Tip: Use the search function. This helps you to find data fields quickly. -
Optional: If the symbol more_vert is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.-
Click on the icon more_vert.
-
In the window shown, select the assignments from the drop-down list.
-
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.3.2. Recommendations for data field mappings
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 standard format Item (new).
Note: You have to create a separate catalogue for each MediaMarktSaturn product category that you want to offer your items in.
Catalogues for different product categories contain different data fields. This is because different item data has to be specified in each MediaMarktSaturn product category.
However, some data fields are the same in each category. Only the recommended mappings for those data fields are described here.
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
General |
||
Shop SKU |
yes |
The variation number is a value that you can customise. Each variation number in your system is unique. |
Title (DE) |
yes |
or
or
|
EAN |
yes |
|
Main Product Image |
yes |
or
|
EU Responsible Person Name (DE) |
no |
|
EU Responsible Person City (DE) |
no |
|
EU Responsible Person Address Additional Details (DE) |
no |
Enter any additional adress information for the address in the EU Responsible Person Address Line (DE) field. This can be P.O. Box details, the floor, the appartment number or other localisation details, e.g. "1st floor, appartment 12a". |
EU Responsible Person Address Line (DE) |
no |
Combine the following data fields via Add data source (link):
Additionally select the separator Space in the Settings (settings). |
EU Responsible Person Zip Code (DE) |
no |
|
EU Responsible Person Email (DE) |
no |
|
EU Responsible Person Website URL (DE) |
no |
|
Required minimum power to enable USB-C charging |
no |
The required minimum power must be specified in watts. The power can be entered either as a whole number or as a decimal number with up to two decimal places. The number must be followed by a space, followed by the measurement unit. Allowed specifications for the measurement unit are W or Watt.
Example: 20 W |
Required power for maximum USB-C charging speed |
no |
The required power for maximum USB-C charging speed must be specified in watts. The power can be entered either as a whole number or as a decimal number with up to two decimal places. The number must be followed by a space, followed by the measurement unit. Allowed specifications for the measurement unit are W or Watt.
Example: 27 W |
Brand |
||
Brand |
yes |
This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your manufacturers. The values are then assigned to a PlentyONE data field. recommended mapping:
|
EU Responsible Person Country (DE) |
||
EU Responsible Person Country (DE) |
no |
The country ID of the manufacturer’s EU-responsible person according to ISO-3166, for example DE or GB. recommended mapping:
Enter the name of the country in the Comparative value field. Example: |
Supports charging via USB-C port |
||
Supports charging via USB-C port |
no |
Allowed values: |
Supports USB Power Delivery (PD) Charging Protocol |
||
Supports USB Power Delivery (PD) Charging Protocol |
no |
Allowed values: |
Charger included |
||
Charger included |
no |
Allowed values: Tip: If the scope of delivery includes an USB-C charger, you can also add this information in the Scope of delivery data field. Use a property of the type Text for this data field. |
-
You need more information on how to map items? Here are two examples of item mappings for different product categories. Only the mandatory fields are mapped in the examples. Note that these examples are recommendations only. Depending on how you manage your item data, other mappings may be more appropriate than the recommendations given here.
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
General |
||
Category |
yes |
The MediaMarktSaturn product category. |
ItemID |
yes |
|
VariationID |
yes |
|
active channels |
yes |
|
Shop SKU |
yes |
|
Title (DE) |
yes |
|
EAN |
yes |
|
Main Product Image |
yes |
|
Scope of delivery (DE) |
yes |
|
Capacity (DE) |
yes |
|
Width |
yes |
Combine the following data fields via Add data source (link):
Additionally select the separator Space in the Settings (settings). Note: When mapping the Width field, the size unit is not automatically exported to MediaMarktSaturn. As the marketplace requires a size unit, add the size unit mm or cm or m separately using an own value. To ensure that the value of the width and the size unit are not directly next to each other, separate the fields with a Space. |
Depth |
yes |
Combine the following data fields via Add data source (link):
Additionally select the separator Space in the Settings (settings). Note: When mapping the Depth field, the size unit is not automatically exported to MediaMarktSaturn. As the marketplace requires a size unit, add the size unit mm or cm or m separately using an own value. To ensure that the value of the depth and the size unit are not directly next to each other, separate the fields with a Space. |
Height |
yes |
Combine the following data fields via Add data source (link):
Additionally select the separator Space in the Settings (settings). Note: When mapping the Height field, the size unit is not automatically exported to MediaMarktSaturn. As the marketplace requires a size unit, add the size unit mm or cm or m separately using an own value. To ensure that the value of the height and the size unit are not directly next to each other, separate the fields with a Space. |
Device type (DE) |
yes |
|
Color (DE) |
yes |
or
|
Connections (DE) |
yes |
|
Brand |
||
Brand |
yes |
Here you assign manufacturers. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your manufacturers. The values are then assigned to a PlentyONE data field. Example:
|
Color (basic) |
||
Color (basic) |
yes |
Here you assign colours. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your colours. The values are then assigned to a PlentyONE data field. Example:
|
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
General |
||
Category |
yes |
The MediaMarktSaturn product category. |
ItemID |
yes |
|
VariationID |
yes |
|
active channels |
yes |
|
Shop SKU |
yes |
|
Title (DE) |
yes |
|
EAN |
yes |
|
Main Product Image |
yes |
|
Scope of delivery (DE) |
yes |
|
Device type (DE) |
yes |
|
Age recommendation manufacturer (from) |
yes |
Combine the following data fields via Add data source (link):
Additionally select the separator Space in the Settings (settings). Note: MediaMarktSaturn requires the unit year/s or month/s after the age specification. |
Brand |
||
Brand |
yes |
Here you assign manufacturers. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your manufacturers. The values are then assigned to a PlentyONE data field. Example:
|
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
fields |
||
Offer SKU |
yes |
This data field is assigned automatically. |
Offer SKU status |
no |
This data field is assigned automatically. |
Offer SKU base |
no |
|
ItemID |
no |
This data field is assigned automatically. |
VariationID |
no |
This data field is assigned automatically. |
Offer Description |
no |
|
Offer Internal Description |
no |
The internal offer description. This description will not be shown on MediaMarktSaturn.
|
Offer Price |
yes |
The sales price of the item.
|
Offer Price Additional Info |
no |
Additional information about the sales price. |
Offer Quantity |
no |
The stock of the variation.
Tip: Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses. |
Minimum Quantity Alert |
no |
You will be informed via email when the stock reaches the defined minimum quantity. If you do not enter a quantity here, then you will not receive an email. |
Availability Start Date |
no |
When will the item be available?
|
Availability End Date |
no |
Until when will the item be available?
|
Discount Price |
no |
The offer price. |
Discount Start Date |
no |
When will the discount start? |
Discount End Date |
no |
When will the discount end? |
Lead Time to Ship (in days) |
no |
The processing time in days until the item can be shipped.
|
Update/Delete |
no |
This data field is automatically mapped with UPDATE so that items can be updated on MediaMarktSaturn. |
Active channels |
no |
This data field is assigned automatically. |
Cut Off Time (NL only) |
no |
Until when are customers shown that their item will be dispatched on the same day if they order within the next 30 minutes?
Example: 17:00 (HH:MM) |
Product ID Type |
||
Product ID Type |
yes |
EAN should be used as the primary identifier, as MediaMarktSaturn can locate the product using the EAN. If the product already exists in MediaMarktSaturn, the system will automatically link the product to its corresponding MediaMarktSaturn SKU.
The SKU in MediaMarktSaturn is different from the PlentyONE SKU. The MediaMarktSaturn SKU is a unique identifier assigned by MediaMarktSaturn to each product. If you want to add items to existing offers with content provided by MediaMarktSaturn, you can map the relevant MediaMarktSaturn SKU.
Instead of the EAN, you can also use the SHOP-SKU as identifier. Ensure that the mapping for the SHOP-SKU is the same as in the item catalogue. Example: If you have mapped the variation number to the Shop SKU in the item catalogue, also use the variation number for the SHOP SKU here. |
Offer State |
||
Offer State |
yes |
The item’s condition, for example new or used.
|
Logistics Class |
||
Logistics Class |
no |
MediaMarktSaturn calculates the shipping costs of an item with the item’s logistic class. |
Free return |
||
Free return |
no |
Can the item be returned free of charge?
Allowed values: |
Reverse charge |
||
Reverse charge |
no |
This value is derived from the seller profile in Mirakl.
Allowed values: |
Customer group availability |
||
Customer group availability |
no |
Allowed values: |
Take-back obligation |
||
Take-back obligation |
no |
Allowed values: |
Price type for strikethrough prices |
||
Price type for strikethrough prices |
yes |
Allowed values: |
8.3.3. Notes on mapping data fields
Adding a brand
If you want to map a brand in a product catalogue for which no MediaMarktSaturn data field exists yet, report this brand to MediaMarktSaturn. MediaMarktSaturn then adds this brand to the data field selection.
Exporting an image list
You can export a list of item or variation images to MediaMarktSaturn via the data fields for images. The following data fields are available for image mapping:
-
Main Product Image
-
Additional Product Image 1
-
Additional Product Image 2
-
Product Detail View 1
-
Product Detail View 2
-
Product Detail View 3
-
Lifestyle Image 1
-
Lifestyle Image 2
-
Lifestyle Image 3
To export an image list, select one of the above data fields and map the image list as follows:
-
Image » Variation images » Image list, image information Full image URL
or
Image » Item images » Image list, image information Full image URL -
Under Maximum number of images, enter the number of images you want to export from the image list.
The URLs of the images from the image list are automatically mapped to the next available image data fields in order.
Example: If the image list is mapped to the data field Additional Product Image 1 and contains three images:
-
The URL of the first image is mapped to the data field Additional Product Image 1,
-
the URL of the second image to Additional Product Image 2,
-
the URL of the third image to Product Detail View 1.
Note: If a subsequent data field is already mapped, this data field is skipped. The image URL is then mapped to the next available empty image data field instead.
Important: Only as many images are mapped as the number of available following data fields for images. Excess images from the image list are not added.
Data fields with different mapping options
In the catalogues, you will find data fields that allow both simple and complex 1:1 mapping. This selection gives you the flexibility to adapt the mapping to the nature of your data.
Example: The data field Offer state in the offer catalogue
For the data field Offer state, both the simple and the complex mapping are marked as mandatory. You only have to configure one of these two options.
-
Simple 1:1 mapping: Select this option if the value for the data field should be the same for all your offers in the catalogue. For example, if you only offer new products and the status New (value 11) applies to all items.
-
Complex 1:1 mapping: This option is useful if you want to transmit different values for the data field. For example, if you offer new and used products at the same time and therefore need to transmit the status New (value 11) as well as the status Very good (value 8). The complex mapping allows you to react flexibly to different values for item settings or properties.
If you want to transmit the status New for all items:
-
Next to the marketplace data field, click on + Add data source.
→ 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 the value 11 into the input field.
→ This value is exported for all variations.
Note: Make sure that the value corresponds to the marketplace standard. In this case, 11 corresponds to the status New at MediaMarktSaturn. You can find the list of valid values in the Mirakl backend.

If you want to transmit the condition New for some items and the condition Very good for other items:
Create mapping for new items:
-
Click on the field for Offer state.
→ A list of the available values is shown. -
Select the value New.
→ The value 11 is mapped. -
Next to the marketplace data field, click + Add data source.
→ To the left, the available PlentyONE data fields are listed in groups. -
Click on Item » Condition ID.
→ The PlentyONE data field is inserted and the field Comparative value is shown. -
In the field Comparative value, enter the value that is saved in the item settings for the selected status. For example 0 for New.
-
Click Confirm.
Create mapping for used items:
-
Click + Add offer state.
-
Click on the field for Offer state.
→ A list of the available values is shown. -
Select the value Very good.
→ The value 8 is mapped. -
Next to the marketplace data field, click + Add data source.
→ To the left, the available PlentyONE data fields are listed in groups. -
Click on Item » Condition ID.
→ The PlentyONE data field is inserted and the field Comparative value is shown. -
In the field Comparative value, enter the value that is saved in the item settings for the selected status. For example 1 for Used.
-
Click Confirm.

You can find further details on the configuration of simple and complex mapping in the chapter Mapping data fields in the catalogue.
8.3.4. Providing information on manufacturer and EU-responsible person (GPSR)
The General Product Safety Regulation of the EU (GPSR) requires manufacturers and sellers to ensure the product safety of certain goods and to provide certain information for this purpose. This information includes details about the manufacturer and, in the case of manufacturers without an establishment in the EU, details about the responsible person within the EU. The GPSR regulation ensures that products are safe and comply with consumer protection requirements before being placed on the market.
In this chapter, you will learn how to add information on the manufacturer and the responsible person within the EU in PlentyONE to comply with the GPSR regulation.
If you export your items to MediaMarktSaturn via catalogues, you can add the information on the manufacturer and the EU-responsible person directly via the data field mappings for items.
8.3.5. Providing information and images for chargers for electrical appliances with radio frequency (FuAG)
On 23rd November 2022 the EU directive 2022/2380 on the harmonisation of charger interfaces of radio equipment was passed.
This directive was realized in German law on the 6th May 2024 by changing the Funkanlagengesetz (FuAG). The new FuAG is in effect since the 28th December 2024 and contains new labeling requirements for electrical appliances with radio frequency and chargers, such as:
-
Mobile phones
-
Tablets
-
Digital cameras (all digital cameras except: security cameras and digital cameras that are exclusively used in the audiovisual sector)
-
Headphones
-
Headsets
-
Handheld gaming consoles
-
Portable speakers
-
E-readers
-
Keyboards
-
Mice
-
Portable navigation systems
-
Earbuds
-
Laptops
The following information has to be indicated in the product details for the mentioned electrical appliances that are put into circulation from 28th December 2024 (for laptops starting 28th April 2026) on:
-
Pictogram for charger included in the scope delivery:
-
The pictogram indicates if a charger is included (charger plug is not crossed out) or not (charger plug is crossed out).
-
The mandatory pictogram is described and displayed in Appendix I Part 3 of the directive 2022/2380
-
-
Label about charging properties of compatible chargers:
-
The label offers all necessary charging properties of the charger that are compatible with the electrical appliance.
-
The mandatory label is described and displayed in Appendix I Part 4 of the directive 2022/2380.
-
Note: The labelling requirement applies to the B2B and B2C section.
In this chapter you learn how to provide the mandatory information and images for chargers to comply with the FuAG requirements.
If you export your items to MediaMarktSaturn via catalogues, you can add the information on chargers directly via the data field mappings for items. MediaMarktSaturn automatically generates the required images from your details in the following data fields and provides them on the product detail page:
-
Required minimum power to enable USB-C charging
-
Required power for maximum USB-C charging speed
-
Supports charging via USB-C port
-
Supports USB Power Delivery (PD) Charging Protocol
-
Charger included
For further information on these data fields, see the recommendations for data field mappings.
8.3.6. Activating the catalogue export
You have set up MediaMarktSaturn in PlentyONE and created a catalogue for exporting your item data? Then start the export of your item data. To do so, activate the catalogues which should be exported to MediaMarktSaturn in the Data » Catalogues menu.
Activating the catalogue export to MediaMarktSaturn:
-
Go to Data » Catalogues.
→ The catalogues are listed. -
Scroll to the MediaMarktSaturn catalogue.
-
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to MediaMarktSaturn once a day.
Tip: Go to Data » Catalogue export status for information about the status of the export.
9. Deactivating an offer
You have two options for deactivating offers on MediaMarktSaturn:
-
Option 1: Deactivating the corresponding variation
-
Option 2: Removing the availability for MediaMarktSaturn on the variation
Option 1: Deactivating the variation
In the chapter on variation availability you learn that variations must be activated in the Availability and visibility section to sell them on MediaMarktSaturn. If you deactivate the variation of an offer, a stock of 0 is sent to MediaMarktSaturn. This deactivates the offer.
Deactivating a variation:
-
Go to Item » Items » [Open item] » [Open variation].
Tip: To deactivate all variations of an item, carry out these settings for the main variation. If the inheritance function is active for the variations, then this deactivates the availability of all variations of the item. -
Deactivate toggle_off the variation in the Availability and visibility section.
-
Save (save) the settings.
→ The variation is deactivated.
Note: Stock synchronisation is only carried out for activated variations. Even if you update the stock, no stock is transmitted for deactivated variations.
Do you want to reactivate the offer? Then activate the variation again.
Option 2: Removing the availability for MediaMarktSaturn
In the chapter on variation availability you also learn that you can only sell a variation on MediaMarktSaturn if the sales channel MediaMarktSaturn has been added in the Sales channels section. If you remove the sales channel MediaMarktSaturn from the variation of an offer, a stock of 0 is sent to MediaMarktSaturn. This deactivates the offer.
Removing the sales channel from a variation:
-
Go to Item » Items » [Open item] » [Open variation].
Tip: To remove the sales channel from all variations of an item, carry out these settings for the main variation. If the inheritance function is active for the variations, then the sales channel is removed from all variations of the item. -
In the Sales channels section, click on Remove sales channel delete next to the MediaMarktSaturn entry.
-
Save (save) the settings.
→ The variation is no longer available for the sales channel.
Note: Stock synchronisation is only carried out for activated variations. Even if you update the stock, no stock is transmitted for deactivated variations.
Do you want to reactivate the offer? Then add the sales channel MediaMarktSaturn to the variation again.
10. Manually managing the data exchange
In the menu Setup » Markets » MediaMarktSaturn » Data exchange you can import and export data manually. This menu is mainly meant to test the export. For example, you can only export specific item and offer data or only import individual orders to PlentyONE. This can be helpful if you want to test the export or if you have to import missing orders.
10.1. Manually exporting item data
In the Setup » Markets » MediaMarktSaturn » Data exchange » Data export menu, you can export individual items and offers to MediaMarktSaturn. For example, this can be helpful if you want to test the export to MediaMarktSaturn or if you only want to export individual items.
Note: To appear in the drop-down list for manual export, the catalogue must be linked to an account under Data » Catalogues » [Open catalogue] » Tab: Basic settings » Section: Basic settings.
In the Data export menu, you can already export data even if the account has not been activated yet. This way, you can test the export with individual items and offers before you activate the account and exchange data with MediaMarktSaturn.
Manually exporting an item:
-
Go to Setup » Markets » MediaMarktSaturn » Data exchange » Data export.
-
Select the Account from the drop-down list.
-
Select a Catalogue from the drop-down list.
-
Enter one or more Item IDs separated by comma. Those items will then be exported to MediaMarktSaturn.
-
Click on file_upload Export.
Note: You can run this process every 30 minutes. Items cannot be exported manually between 24.00 - 6.00 CET.
Tip: Click on Preview to generate e preview of the export.
Manually exporting offers:
-
Go to Setup » Markets » MediaMarktSaturn » Data exchange » Data export.
-
Select the Account from the drop-down list.
-
Select a Catalogue from the drop-down list.
-
Enter one or more Item IDs separated by comma. The offers for those items will then be exported to MediaMarktSaturn.
-
Click on file_upload Export.
Note: You can run this process every 15 minutes.
Tip: Click on Preview to generate e preview of the export.
10.2. Manually importing orders
In the Setup » Markets » MediaMarktSaturn » Data exchange » Order import menu, you can manually import individual orders into PlentyONE.
You can either enter the order IDs of the orders you want to import, or you can import orders from a specific time frame.
Note: You can run this process every 15 minutes.
Import orders by ID:
-
Go to Setup » Markets » MediaMarktSaturn » Data exchange » Order import.
-
Open the tab Import orders by order ID.
-
Enter one or more order IDs into the input field Order IDs. Separate the IDs by comma if you enter more than one ID.
-
Click Import.
→ The orders are imported into PlentyONE.
Import orders by date:
-
Go to Setup » Markets » MediaMarktSaturn » Data exchange » Order import.
-
Open the tab Import orders by date.
-
Enter a start date in the format D.M.YYYY or select a date via the calendar (today).
-
Enter an end date in the format D.M.YYYY or select a date via the calendar (today).
-
Click Import.
→ Orders from the selected time frame are imported into PlentyONE.
11. Automating order processing
You can automatically inform MediaMarktSaturn about changes to the order status by using one of the following options:
-
Option 1: PlentyONE Flow (recommended)
-
Option 2: Event procedures (old method)
11.1. Option 1: PlentyONE Flow (recommended)
Create event-based Flows to automatically inform MediaMarktSaturn about changes to the order status. The following actions are available for MediaMarktSaturn in the PlentyONE Flow Studio:
-
Automatically inform MediaMarktSaturn that the order was confirmed. (How?)
-
Automatically inform MediaMarktSaturn that the order was rejected. (How?)
-
Automatically inform MediaMarktSaturn that the items have been shipped. (How?)
-
Automatically upload invoices to MediaMarktSaturn. (How?)
-
Automatically inform MediaMarktSaturn that an item was refunded. (How?)
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.
-
Is this your first time working with PlentyONE Flow? Then read up on the basic concept of Flow first.
11.1.1. Report order confirmation to MediaMarktSaturn
Create an event-based Flow to automatically inform MediaMarktSaturn about the order confirmation.
-
Go to Automation » Flow Studio.
-
Click Create flow (add).
→ A stepper opens and guides you through the following three steps.-
General
-
Enter a unique name and, if necessary, a description for the new flow.
-
Click Next.
-
-
Trigger
-
Select Event-based as the trigger.
-
Click Next.
-
-
Settings
-
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. -
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. -
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 5.
-
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.
Setting | Option | Selection | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Trigger selection |
Select an event, for example:
|
For Order types, select the type Incomplete order. |
|||||||||
Control element |
Branch |
|
|||||||||
Actions |
Plugin (Legacy) > Mediamarkt |
Accept incomplete order on MediamarktSaturn |
11.1.2. Report order rejection to MediaMarktSaturn
Create an event-based Flow to automatically inform MediaMarktSaturn about the rejection of an order.
-
Go to Automation » Flow Studio.
-
Click Create flow (add).
→ A stepper opens and guides you through the following three steps.-
General
-
Enter a unique name and, if necessary, a description for the new flow.
-
Click Next.
-
-
Trigger
-
Select Event-based as the trigger.
-
Click Next.
-
-
Settings
-
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. -
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. -
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 6.
-
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.
Setting | Option | Selection | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Trigger selection |
Select an event, for example:
|
For Order types, select the type Incomplete order. |
|||||||||
Control element |
Branch |
|
|||||||||
Actions |
Plugin (Legacy) > Mediamarkt |
Decline incomplete order on MediamarktSaturn |
11.1.3. Uploading shipping confirmations to MediaMarktSaturn
Create an event-based Flow to automatically inform MediaMarktSaturn when you have shipped the items of an order.
-
Go to Automation » Flow Studio.
-
Click Create flow (add).
→ A stepper opens and guides you through the following three steps.-
General
-
Enter a unique name and, if necessary, a description for the new flow.
-
Click Next.
-
-
Trigger
-
Select Event-based as the trigger.
-
Click Next.
-
-
Settings
-
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. -
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. -
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 7.
-
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.
Setting | Option | Selection | ||||||
---|---|---|---|---|---|---|---|---|
Trigger selection |
Select an event, for example:
or
|
Select an order status, for example:
|
||||||
Control element |
Branch |
|
||||||
Actions |
Plugin (Legacy) > Mediamarkt |
Upload shipping confirmation to MediamarktSaturn |
11.1.4. Uploading invoices to MediamarktSaturn
Create an event-based Flow to automatically upload invoices to MediaMarktSaturn.
-
Go to Automation » Flow Studio.
-
Click Create flow (add).
→ A stepper opens and guides you through the following three steps.-
General
-
Enter a unique name and, if necessary, a description for the new flow.
-
Click Next.
-
-
Trigger
-
Select Event-based as the trigger.
-
Click Next.
-
-
Settings
-
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. -
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. -
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 8.
-
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.
Setting | Option | Selection | ||||||
---|---|---|---|---|---|---|---|---|
Trigger selection |
Select an event, for example:
Note: Select an event after which the items have already been shipped. |
Select a document type, for example:
|
||||||
Control element |
Branch |
|
||||||
Actions |
Plugin (Legacy) > Mediamarkt |
Upload invoice to MediamarktSaturn |
11.1.5. Reporting refunds to MediaMarktSaturn
Create an event-based Flow to automatically inform MediaMarktSaturn that an item was refunded.
Different flows can be created, depending on the reason for the refund. The following actions are available for MediaMarktSaturn to report a refund:
-
Report refund to MediamarktSaturn: Item not received
-
Report refund to MediamarktSaturn: Item returned
-
Report refund to MediamarktSaturn: Chargeback by the customer’s bank
-
Report refund to MediamarktSaturn: Agreement with vendor
-
Report refund to MediamarktSaturn: No response from the shop
-
Report refund to MediamarktSaturn: Out of stock
-
Report refund to MediamarktSaturn: PayPal decision in favor of the customer
-
Report refund to MediamarktSaturn: Agreement found between customer and seller
-
Report refund to MediamarktSaturn: Cancelled before shipping
To report refunds to MediaMarktSaturn, a credit note must be created. If it is a full refund, a credit note for all order items of the parent order must be created. For a partial refund, a partial credit note that only contains the affected order items must be created. In a partial credit note, you can also specify that only a certain amount is refunded.
Carry out the flows listed in this section for the credit note you have created.
-
Go to Orders » Orders.
-
Carry out the search (search) to display orders.
-
Open the order for which a credit note should be created.
-
At the top, click on Create orders (shopping_cart) > Credit note.
-
Select the option For all order items.
-
Save (save) the settings.
→ The credit note order is created. -
Carry out the appropriate flow for this order.
-
Go to Orders » Orders.
-
Carry out the search (search) to display orders.
-
Open the order for which a credit note should be created.
-
At the top, click on Create orders (shopping_cart) > Credit note.
-
Select the option For specific order items.
-
Under Quantity, enter the quantity of order items for which a credit note should be created.
-
Click Add items to shopping cart (add_shopping_cart) to the right of the relevant item.
-
Under Price, enter the amount to be refunded for the order item.
-
Save (save) the settings.
→ The credit note order is created. -
Carry out the appropriate flow for this order.
-
Go to Automation » Flow Studio.
-
Click Create flow (add).
→ A stepper opens and guides you through the following three steps.-
General
-
Enter a unique name and, if necessary, a description for the new flow.
-
Click Next.
-
-
Trigger
-
Select Event-based as the trigger.
-
Click Next.
-
-
Settings
-
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. -
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. -
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 9.
-
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.
Setting | Option | Selection | ||||||
---|---|---|---|---|---|---|---|---|
Trigger selection |
Select an event, for example:
|
Select an order type, for example:
|
||||||
Control element |
Branch |
|
||||||
Actions |
Plugin (Legacy) > Mediamarkt |
Select an action for Report refund to MediamarktSaturn with the appropriate reason. |
11.2. Option 2: Event procedures (old method)
Set up event procedures to automatically inform MediaMarktSaturn about changes to the order status. The following event procedures are available for MediaMarktSaturn:
-
Automatically inform MediaMarktSaturn that the order was confirmed. (How?)
-
Automatically inform MediaMarktSaturn that the order was rejected. (How?)
-
Automatically inform MediaMarktSaturn that the items have been shipped. (How?)
-
Automatically upload invoices to MediaMarktSaturn. (How?)
-
Automatically inform MediaMarktSaturn that an item was refunded. (How?)
11.2.1. Report order confirmation to MediaMarktSaturn
Set up an event procedure to automatically inform MediaMarktSaturn about the order confirmation.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 10.
-
Save () the settings.
-
Carry out the additional settings according to Table 10.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 10 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
|
|
Filter 1 |
Order > Order type |
Order |
Filter 2 |
Order > Referrer |
Select the order referrers for the MediaMarktSaturn country platforms that you want to use this event procedure for. |
Procedure |
Plugin |
Accept incomplete order on MediamarktSaturn |
11.2.2. Report order rejection to MediaMarktSaturn
Set up an event procedure to automatically inform MediaMarktSaturn about the rejection of an order.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 11.
-
Save () the settings.
-
Carry out the additional settings according to Table 11.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 11 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
|
|
Filter 1 |
Order > Order type |
Order |
Filter 2 |
Order > Referrer |
Select the order referrers for the MediaMarktSaturn country platforms that you want to use this event procedure for. |
Procedure |
Plugin |
Decline incomplete order on MediamarktSaturn |
11.2.3. Uploading shipping confirmations to MediaMarktSaturn
Set up an event procedure to automatically inform MediaMarktSaturn when you have shipped the items of an order.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 12.
-
Save () the settings.
-
Carry out the additional settings according to Table 12.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 12 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
|
Select an event, for example [7] Shipped. |
Filter 1 |
Order > Order type |
Order |
Filter 2 |
Order > Referrer |
Select the order referrers for the MediaMarktSaturn country platforms that you want to use this event procedure for. |
Procedure |
Plugin |
Upload shipping confirmation to MediamarktSaturn |
11.2.4. Automatically uploading invoices to MediaMarktSaturn
Set up an event procedure to automatically upload invoices to MediaMarktSaturn.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 13.
-
Save () the settings.
-
Carry out the additional settings according to Table 13.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 13 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
Note: Select an event after which the items have already been shipped. |
|
Filter |
Order > Referrer |
Select the order referrers for the MediaMarktSaturn country platforms that you want to use this event procedure for. |
Procedure |
Plugin |
Upload invoice to MediamarktSaturn |
11.2.5. Reporting refunds to MediaMarktSaturn
Set up an event procedure to automatically inform MediaMarktSaturn that an item was refunded.
Different event procedures can be created, depending on the reason for the refund. The following event procedures are available for MediaMarktSaturn to report a refund:
-
Report refund to MediamarktSaturn: Agreement with vendor
-
Report refund to MediamarktSaturn: Cancelled before shipping
-
Report refund to MediamarktSaturn: Item not received
-
Report refund to MediamarktSaturn: Item returned
-
Report refund to MediamarktSaturn: Out of stock
-
Report refund to MediamarktSaturn: Agreement found between customer and seller
-
Report refund to MediamarktSaturn: Chargeback by the customer’s bank
-
Report refund to MediamarktSaturn: No response from the shop
-
Report refund to MediamarktSaturn: PayPal decision in favor of the customer
To report refunds to MediaMarktSaturn, a credit note must be created. If it is a full refund, a credit note for all order items of the parent order must be created. For a partial refund, a partial credit note that only contains the affected order items must be created. In a partial credit note, you can also specify that only a certain amount is refunded.
Carry out the event procedures listed in this section for the credit note you have created.
-
Go to Orders » Orders.
-
Carry out the search (search) to display orders.
-
Open the order for which a credit note should be created.
-
At the top, click on Create orders (shopping_cart) > Credit note.
-
Select the option For all order items.
-
Save (save) the settings.
→ The credit note order is created. -
Carry out the appropriate event procedure for this order.
-
Go to Orders » Orders.
-
Carry out the search (search) to display orders.
-
Open the order for which a credit note should be created.
-
At the top, click on Create orders (shopping_cart) > Credit note.
-
Select the option For specific order items.
-
Under Quantity, enter the quantity of order items for which a credit note should be created.
-
Click Add items to shopping cart (add_shopping_cart) to the right of the relevant item.
-
Under Price, enter the amount to be refunded for the order item.
-
Save (save) the settings.
→ The credit note order is created. -
Carry out the appropriate event procedure for this order.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 14.
-
Save () the settings.
-
Carry out the additional settings according to Table 14.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 14 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example: Order generation: New credit note |
|
Filter |
Order > Referrer |
Select the order referrers for the MediaMarktSaturn country platforms that you want to use this event procedure for. |
Procedure |
Plugin |
Select an event procedure for Report refund to MediamarktSaturn with the appropriate reason. |
12. Download reports
In the Setup » Markets » MediaMarktSaturn » Reports menu, you can download reports for offer export and item export. These reports are generated after an offer or item export to MediaMarktSaturn.
Table 15 contains an overview of the reports in the Setup » Markets » MediaMarktSaturn » Reports menu.
Column | Explanation |
---|---|
Date |
Creation date of the report in the format YYYY.MM.DD hh:mm:ss |
Status |
The processing status of the report.
|
Integration Details |
The number of imported products or offers. |
Transform Lines |
The number of rows in the report in which no errors occurred and the number of rows in which errors occurred. |
Download |
Download report (file_download): The report is downloaded. |
Downloading a report:
-
Go to Setup » Markets » MediaMarktSaturn » Reports.
-
Click on Filters (tune) at the top of the menu.
-
Select a report type. The available report types are listed in Table 16.
-
Click Search (search).
→ The selected filter is applied and the appropriate reports are displayed.
→ The active filter is displayed at the top of the menu.
Tip: If you want to change the filter, you can reset (refresh) it. Then select the desired filter as described above. -
Click Download report (file_download).
→ The report is downloaded.
Report type | Explanation |
---|---|
Offers |
The offer report contains information on the offer export to MediaMarktSaturn. |
Products |
The product report contains information on the item export to MediaMarktSaturn. |
13. Viewing the data log
Events in your system are logged in the menu Data » Log. This allows you to check the data log for errors without relying on our support.
Viewing the data log:
-
Go to Data » Log.
-
Click on Filters (tune) at the top of the menu.
-
In the Identifier field, enter the option MediaMarktSaturn.
-
Optional: Select a date if you only want to see entries for a specific day.
-
Click on Search () to display the results.
14. Switching from the MediaMarkt plugin to the MediaMarktSaturn Core Integration
If you are using the MediaMarkt plugin, you can transfer your settings and SKUs to the new MediaMarktSaturn Core Integration.
14.1. Transferring settings to the Core Integration
To migrate your settings from the MediaMarkt plugin, you have to manually configure them in the MediaMarktSaturn Core Integration. The following table shows which settings from the plugin assistant need to be transferred, along with their corresponding locations in the Core Integration.
Settings in the plugin assistant | Settings section of the MediaMarktSaturn Core Integration |
---|---|
Authentication |
|
API key |
Setup » Markets » MediaMarktSaturn » Settings » [Open account]
|
Data exchange |
|
Configuration for automated order import, item and offer export |
Setup » Markets » MediaMarktSaturn » Settings » [Open account]
|
Options for the offer export |
The setting for the offer export is omitted. |
Refunds |
|
Mapping of refund reasons |
You don’t need to map refund reasons. Instead, event-based Flows or event procedures with different refund reasons are used. |
Cancellations |
|
Mapping of cancellation reasons |
At MediaMarktSaturn, customers cannot cancel orders. The item needs to be returned instead. |
Warehouse selection |
|
Warehouse selection |
You directly map your warehouses via the offer quantity data field in the corresponding offer catalogue. Pay attention to the recommendations for data field mappings. |
Shipping profiles |
|
Shipping profile mapping |
Setup » Markets » MediaMarktSaturn » Settings » [Open account]
|
Offer properties |
|
Offer properties mapping |
You specify which offer data is transferred via the data field mapping in the corresponding offer catalogue. |
14.2. Transferring SKUs
Follow the steps below to transfer the SKUs from your MediaMarkt plugin account to your MediaMarktSaturn Core Integration account.
Transferring SKUs for product catalogues:
Important: This process can only be carried out once per account. Therefore, you should only transfer your SKUs when you know that you will no longer be creating new products on MediaMarktSaturn via the MediaMarkt plugin.
-
Go to Setup » Markets » MediaMarktSaturn » Settings » [Open account].
-
Click Migrate plugin SKUs in the Offers section.
→ The plugin SKUs will be transferred to your MediaMarktSaturn Core Integration account.
→ You can now manage your existing products and offers via the MediaMarktSaturn Core Integration catalogues.
Note: Your plugin product catalogues cannot be migrated to the Core Integration product catalogues. Instead, create new product catalogues and then map the data fields accordingly.
To manage your offers, no SKU transfer is required. Instead, you manage your offers via offer catalogues. In these catalogues you map the data fields from MediaMarktSaturn to the corresponding fields in your system. Pay attention to the recommendations for data field mappings.