Conrad Core Integration (Setup via Channel Control Centre)

Conrad is a market specialised in consumer electronics, home technology, tools, and work safety.

Sales Channels » Channel Control Centre

This page explains the setup process for Conrad via the Sales Channels » Channel Control Centre menu. If this menu is not available in your system, then you can find instructions on how to set up Conrad via the Setup » Markets menu here.

1. Becoming a seller at Conrad

First, become a seller with Conrad to start selling items on Conrad.

After registering, you will receive login details from Conrad. You need these login details to set up Conrad in PlentyONE.

2. Frequency of data exchange

After you have set up Conrad in PlentyONE, data is exchanged with the market in the intervals described in Table 1.

Table 1. Frequency of data exchange
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.

Table 2. Mandatory settings for Conrad
Settings section	Settings
Item export
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	Conrad is added as a sales channel to your system. The following basic settings for Conrad are carried out: An account for Conrad is created. The Conrad API key is entered. The Item export is activated. The account for Conrad is activated.
Variation settings	The variation is active. The sales channel Conrad is enabled for the variation. At least one category which is linked with Conrad is saved for the item.
Catalogue settings	A product catalogue is created. The catalogue is linked to the account. The mappings for the product catalogue are carried out. The product catalogue is activated.
Listing settings	A product listing is created. The product listing is activated. The listing contains at least one variation.
Offer export
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	Conrad is added as a sales channel to your system. The following basic settings for Conrad are carried out: An account for Conrad is created. The Conrad API key is entered. The Offer export is activated. The account for Conrad is activated.
Variation settings	The variation is active. The sales channel Conrad is enabled for the variation. At least one category which is linked with Conrad is saved for the item.
Catalogue settings	An offer catalogue is created. The catalogue is linked to the account. The mappings for the offer catalogue are carried out. The offer catalogue is activated.
Listing settings	An offer listing is created. The offer listing is activated. The listing contains at least one variation.
Stock synchronisation / Price synchronisation
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	Conrad is added as a sales channel to your system. The following basic settings for Conrad are carried out: An account for Conrad is created. The Conrad API key is entered. The Offer export is activated. The account for Conrad is activated.
Variation settings	The variation is active. The sales channel Conrad is enabled for the variation. At least one category which is linked with Conrad is saved for the item.
Catalogue settings	An offer catalogue is created. The catalogue is linked to the account. The mappings for the offer catalogue are carried out. The offer catalogue is activated.
Listing settings	An offer listing is created. The offer listing is activated. The listing contains at least one variation.
Order import
Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:	Conrad is added as a sales channel to your system. The following basic settings for Conrad are carried out: An account for Conrad is created. The Conrad API key is entered. The Client is selected. The Order import is activated. The shipping profiles are mapped. The account for Conrad is activated.

4. Workflow of an order

Your items are listed on Conrad. The name of your company is shown with your items.
Customers place an order on Conrad.
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.
The order must be accepted or rejected via flow.
If the order is accepted, customers make their payments to Conrad.
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 sent to Conrad via flow.

Tax refunds for solar panels cannot be processed via PlentyONE

Customers who buy solar panels at Conrad and have them installed by companies with a specific certification can receive a certificate to have the value added tax refunded.
This process cannot be handled by PlentyONE at the moment, but it will be implemented in the future.

5. Setting up Conrad in PlentyONE

First, add Conrad as a sales channel in the Channel Control Centre and carry out the basic settings to set up the sales channel in PlentyONE. To do so, proceed as described below.

5.1. Sales channel overview

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

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

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

Component

Explanation

Name

The name of the sales channel.

More

Click here to display more actions for a sales channel.

Listings

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

Settings

Opens the respective Settings menu of the sales channel.

Delete sales channel

Deletes the sales channel from the overview.

5.2. Adding the sales channel

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

Adding a sales channel:

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

5.3. Carrying out the basic settings for Conrad

Next, carry out the basic settings for Conrad.

First, add a new account for Conrad.

Adding an account for Conrad:

Go to Sales Channels » Channel Control Centre.
Click on the Conrad tile.
→ The tab Settings opens.
Click Add account ().
→ The Add account window opens.
Enter an account name.
Click SAVE (save).
→ A view with account settings opens.
Carry out the additional settings. Pay attention to the explanations given in [grundeinstellungen-conrad].
Click Save (save).
→ The settings are saved.

Table 4. Settings for the sales channel Conrad

Setting

Explanation

Save

Save the settings.

More

Click here to display more actions.

Delete account

Delete the account.

TEST CONNECTION

Click here to test whether a connection to Conrad 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 Conrad account. You entered the name when you created the account.

Active

Activate the Conrad account (toggle_on). The data exchange with Conrad is started.

We recommend to only activate the account after you carried out all settings.

Note: The account has to be connected to a Conrad account so that data can be exchanged between PlentyONE and Conrad. The Conrad API key must be saved in PlentyONE.

Conrad API key

Enter the API key. You have received the API key from Conrad.

Client

Select a client (shop). The orders of this Conrad account will be assigned to this client.

Item

Item export

Activate (toggle_on) to export items to Conrad once per day.

Map shipping profiles

Shipping zone

Map your PlentyONE shipping profiles with the Conrad shipping profiles from the drop-down list.
Note: Click () to update the shipping zones.

Mapping shipping profiles:

Select the shipping zone from the drop-down list.
Note: You need to have a default mapping to prevent errors during the order import. Define a fallback for unassigned shipping zones.
Click Show mappings for the selected zone.
→ A new view for mapping shipping profiles opens.
Note: Your changes will not be saved. In order to save your changes first, click Save (save) in the top left corner before mapping the shipping profiles.
Click Add mapping.
→ The window Add new shipping profile mapping opens.
Select the Conrad shipping method.
Select the PlentyONE shipping profile.
Select the Conrad shipping service provider.
Click save Save.
→ The new mapping is shown in the menu.
Tip: You can edit the shipping profile mappings later on. To do so, click More () and then on Edit mapping ().

Orders

Order import

Activate (toggle_on) to import Conrad orders into PlentyONE every 15 minutes.
Note: Every order that was imported into PlentyONE will be billed.
Note: If the order import is active, it is mandatory to assign statuses for shipped orders, credit notes, and cancelled orders.

Order import start date

Enter a date in the format D.M.YYYY or select a date via the calendar ().
Only orders starting from this date will be imported into PlentyONE. Orders which were generated before this date will not be imported.
Note: When you create an account, the order import start date is automatically filled with the current date. If you want to import old orders, then enter the desired start date.

Allow cancellations for orders with invoice

Should customers be able to cancel an order if an invoice was already created?

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

Status for cancelled orders

Select the order status for orders that were cancelled.

Note: Select a status higher than status 8.

Offers

Offer export

Activate (toggle_on) to export offers to Conrad once per day.
A full offer export is carried out once per day. This means that new offers are created and existing offers are updated.
Stock is updated every 15 minutes.
Prices are updated every hour.

Note: Offers can only be exported if an item has already been activated. If an item has not been activated by Conrad, then the offer cannot be exported.

5.4. Adjusting the general settings

In the menu General settings you can rename the sales channel. To do so, proceed as follows.

Renaming a sales channel:

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

5.5. Activating the order referrer

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

What is an order referrer?

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

Activating the order referrer for Conrad:

Go to Setup » Orders » Order referrer.
Click Search ().
In the list, navigate to the option Conrad with the ID 176.00.
On the right of the referrer’s line, click Edit ().
→ The window Edit referrer opens.
Activate the option Visible in selection ().
Click SAVE ().
→ The referrer is active.

6. Preparing variations

Now, prepare your variations.

6.1. Setting the variation availability

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

For one variation
Using variation group function
Using batch processing

Making a variation available for Conrad:

Go to Item » Items » [Open variation].
Tip: To sell all variations of an item on Conrad, carry out the settings for the item’s main variation. If the inheritance function is active for the variations, then this activates the availability of all variations of the item.
In the Availability and visibility section, enable the option Active ().
Click the Sales channels tab.
In the Sales channels section, activate the sales channel Conrad in the Status column ().
Tip: You can activate multiple sales channels at once. To do so, activate the checkboxes to the left of the desired sales channels. Then activate the toggle above the checkbox column (). Click ACTIVATE to confirm the activation.
Save () the settings.
→ The variation is available for Conrad.

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 Conrad using the variation group function:

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

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

Making several variations available for Conrad using batch processing:

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

7. Exporting product data

Product data is exported to Conrad using catalogues. Catalogues for Conrad are usually managed via the Data » Catalogues menu. However, you can also create catalogues for Conrad directly in the Channel Control Centre.

What is a catalogue?

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

Marketplace formats are used to export item data to markets.
Standard formats are used to export data from your PlentyONE system into a file.

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

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

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

You can find more information on how to create Channel maps in the Channel maps section.

7.1. Adding product categories

Before you can create product catalogues for Conrad, you have to add the product categories in which you want to offer your items on Conrad. This is done in the Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Category whitelist menu. After you added Conrad product categories, you can create product catalogues or Channel maps for for these product categories.

Adding product categories:

Go to Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Category whitelist.
Click Add categories ().
→ The Add categories window opens.
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. Click Show categories () in the category tree to expand the available subcategories.
Click SAVE ().
→ The category was added. You can now create a product catalogue for this category in the Data » Catalogues menu.
Tip: Once you have added at least two product categories, you can create a Channel map for these categories in the Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Mapping » Product mapping menu.

7.2. Linking variations to a Conrad product category

Which variations are exported to Conrad?

You can use catalogue filters in the menu Data » Catalogues » [Open catalogue] » Filters to define which variations should be exported to Conrad. The filters Conrad and Active are already set by default. This means that all variations which are active and enabled for Conrad in the Sales channels tab will be exported to Conrad.
You can use the custom filters in the catalogue to define in detail which variations should be exported to Conrad.

You can use properties to define in which product category on Conrad a variation should be listed. For example, you can create the property Conrad product categories of the type selection and use the Conrad 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 Conrad the variations should be exported.

Creating a property of the type selection:

Go to Setup » Settings » Properties » Configuration.
Click Create property.
→ The settings for the new property are displayed.
In the Details section, select the type selection.
In the Details section, select the section Items.
Carry out the additional settings.
→ Tip: For example, you can use Conrad product category as name for the property.
Click Save ().
→ The property is created.
In the section Selection values, click Create selection value.
Enter a name for the selection value.
→ Tip: You can enter the different Conrad product categories as names for the selection values.
Click Save ().
→ 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 » Items.
Open the variation that you want to link.
Click the Properties tab.
In the Properties section, click Add properties.
→ The window Add properties opens.
Select the newly created property ().
Tip: Use the search () or the filters () to search for the new property.
Click APPLY.
→ The property is added.
Select the desired product category from the drop-down list Value.
Click Save ().

Afterwards, add the ID of the selection value as filter in the desired Conrad 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 Conrad catalogue.
On the left-hand side, open the tab Filters.
In the Custom filters section, 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.
Click Save ().

7.3. Creating a product catalogue

Product data is exported to Conrad using product catalogues. In each product catalogue, you map the Conrad data fields to the corresponding product data saved in PlentyONE. To simplify product data mapping, you can create Channel maps for Conrad in the Channel Control Centre. Next, add the relevant product catalogues to these Channel maps and map the data fields required by Conrad to the product data saved in PlentyONE.
Once you have activated the Channel map, catalogue, account, listing and variations, the product data is automatically exported to Conrad once a day.

Note: There is a separate catalogue format for each Conrad product category. Different product data is exported in the different catalogue formats, depending on which information Conrad requires for each product category.
This means that you have to create a separate catalogue for each Conrad product category that you want to sell your items in.

Create a catalogue for offers

For Conrad, you always have to create an additional catalogue for offers. The offer catalogue is required in addition to the catalogues for the different Conrad product categories so that offers can be created on Conrad.
You can find information on creating an offer catalogue here.
Note: Offers can only be exported for items that have already been activated by Conrad. As long as an item has not yet been activated by Conrad, the offer cannot be exported.

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

Creating a product channel map:

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

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

Linking a product catalogue to the channel map:

Go to Sales Channels » Channel Control Centre » [Name of your Conrad sales channel] » Mapping » Product mapping.
In the row of the channel map you want to edit, click on More and select Connect catalogues.
In the drop-down list Select catalogues, click Create catalogue.
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Conrad.
In the drop-down list Export type, select the option Item (New).
In the drop-down list Categories, select the product categories in which you want to sell on Conrad.
Click CREATE AND CONNECT TO CHANNEL MAP.
→ The catalogue is created and connected to the channel map.

7.3.1. Mapping data fields in the product 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 product exports to Conrad.

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

Getting to know the catalogue menu for marketplace formats

Availability	Explanation
Navigation	When you open a catalogue, the view Mapping is shown. On the very left is the navigation. Switch to other views of the catalogue. Open the catalogue settings. Use filters that limit the data that is exported. Go back to the list of catalogues. Create a new catalogue.
Toolbar	The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.
Marketplace data field	To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱). *Tip:* Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions ().
PlentyONE data fields	On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Availability

Explanation

Navigation

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

Switch to other views of the catalogue.
Open the catalogue settings.
Use filters that limit the data that is exported.
Go back to the list of catalogues.
Create a new catalogue.

Toolbar

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

Marketplace data field

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

PlentyONE data fields

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

Mapping catalogue fields:

Go to Sales Channels » Channel Control Centre.
Click on the tile of your Conrad Sales Channel.
Click on the catalogue you want to edit.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.
Map suitable PlentyONE data fields to the market data fields.
For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.
- Simple 1:1 mapping
- Simple 1:1 mapping with properties
- Complex 1:1 mapping
- 1:1 mapping with fallback data fields
- 1:n mapping
- Own value mapping
- Mapping with mathematical calculations
Save () the catalogue.
→ The mappings are saved.

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

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

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

I want to fill this marketplace data field with the data from this PlentyONE setting.
If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.

Example: Sales price and RRP for Otto Market

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

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

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

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

Creating a property:

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

Creating a simple 1:1 mapping with properties:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
Click on Confirm.
→ The property is mapped to the marketplace data field.

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

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

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

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

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

Examples for complex 1:1 mappings are:

Categories
Brands
Shipping setting

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

Creating a complex 1:1:n mapping:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
Click on the PlentyONE data field for which you want to map values.
Important: Do not map own values or properties of the type None.
Your next steps depend on the PlentyONE data field you selected:
- Alternative 1: The available values for the PlentyONE data value are shown on the left.
  - Next to the value you want to select, click on the plus.
    → The value is added to the field on the right.
  - Click on Confirm.
- Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.
  - In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.
  - Click on Confirm.
- Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.
  - Select a value from the drop-down list.
  - Click on Confirm.
    → The value of the marketplace data field is exported, not the value of the PlentyONE data field.
    Exception: Only when you map an own value, the own value that you enter is exported.

Example: Delivery time in days for Otto Market

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

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

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

So this mapping specifies:

I want to fill the marketplace data field with the data from the selected PlentyONE setting.
If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.
If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

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

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

SKU
Barcodes
Sales prices
Properties

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

Empty

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

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

PlentyONE data fields that are available for variations by default

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

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

Creating a 1:1 mapping with fallback data fields:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
→ The fallback data field is added with the fallback condition "null".
Alternative 1: To add the fallback data field with the fallback condition "null":
1. Click on Confirm.
  → The fallback data field is exported if the data field above is not linked to the variation.
Alternative 2: To add the fallback data field with the fallback condition "empty":
1. To the left of the fallback data field, click on the cog ().
  → The window Data column settings is shown.
2. For the setting Fallback condition, select the option Empty.
3. Click on Save.
  → The fallback data field is added with the fallback condition "empty".
4. Click on Confirm.
  → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

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

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

1:n mapping: 1 marketplace data field, several PlentyONE data fields

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

So this mapping specifies:

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

Creating a 1:n mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.
To the right of the mapped PlentyONE data field, click on Add data field ().
→ To the left, the list of available PlentyONE data fields again are shown in groups.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
Save () the catalogue.
→ The mappings are saved.
→ During the export, the content of the PlentyONE data fields is combined and exported as one field.

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

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

So this mapping specifies:

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

Creating an own value mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view.
Enter a value into the input field.
→ This value is exported for all variations.

Example: Diameter information

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

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

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

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

This function only works for data fields that contain numerical values.
This functionality is new and not available for all catalogue formats.

So this mapping specifies:

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

Recalculating numerical values:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.
1. Click on the icon .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

7.3.2. 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 recommendations 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 Conrad product category that you want to offer your items in.
Catalogues for different product categories contain different data fields. This is because different product data has to be specified in each Conrad product category.
However, some data fields are the same in each category. Only the recommended mappings for those data fields are described here.

List of recommended item mappings

Marketplace field Mandatory? Recommended PlentyONE mapping

Marketplace field	Mandatory?	Recommended PlentyONE mapping
General
Product-ID (of the seller)	yes	The unique item ID in the system of the seller. This ID is used to match the offers later on. Variation » Variation ID
Product title	yes	Item text » Name 1, languages English
Content units per selling unit	yes	Here you provide information about the content of the item, for example `1 piece` or `100 g`. You have to enter at least `0.0001` here. Enter a period as decimal separator. Variation » Content value
Charging capacity (min.)	no	The required power for minimum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed. Property of the type Text *Example:* 20
Charging capacity (max.)	no	The required power for maximum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed. Property of the type Text *Example:* 27
Brandname
Brandname	yes	Here you map 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. For Brandname, first select the manufacturer as it is called at Conrad. Then assign the field to the corresponding manufacturer in PlentyONE. *Example:* Brand.0002 Manufacturer » [Select manufacturer]
Selling unit of measure
Selling unit of measure	yes	Here you map the sales quantity unit. Enter the smallest amount of the item that can be sold individually. This unit is independent of the unit that you want to use to price or store the item. 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 sales quantity units. The values are then assigned to a PlentyONE data field. For Selling unit of measure, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE. *Example:* ST Variation » Content unit » Piece
Content units
Content units	yes	Here you map the content unit. 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 content units. The values are then assigned to a PlentyONE data field. For Content units, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE. *Example:* unece.unit.C62 Variation » Content unit » Piece
VAT rate
VAT rate	yes	Here you map the VAT class. 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 VAT classes. The values are then assigned to a PlentyONE data field. For VAT rate, first select the VAT class as it is called at Conrad. Then assign the field to the corresponding VAT class in PlentyONE. *Example:* 1 VAT rate » [VAT rate in per cent]
Charging capacity (max.) UNIT
Charging capacity (max.) UNIT	no	The required power for maximum charging capacity must be specified in watts. Property of the type Selection *Allowed values:* `W` = Watts
Charging method (Power Delivery)
Charging method (Power Delivery)	no	Is the USB Power Delivery (PD) charging protocol supported? Property of the type Selection *Allowed values:* `mit USB Power Delivery` = The appliance supports the USB Power Delivery (PD) charging protocol. `ohne USB Power Delivery` = The appliance does not support the USB Power Delivery (PD) charging protocol.
RED-compliant charger available
RED-compliant charger available	no	Is a charger included in the scope of delivery? Property of the type Selection *Allowed values:* `Yes` = The scope of delivery includes a charger. `No` = The scope of delivery does not include a charger. `Product not governed by RED` = The product is not subject to the RED (Radio Equipment Directive).
Charging capacity (min.) UNIT
Charging capacity (min.) UNIT	no	The required minimum charging capacity must be specified in watts. Property of the type Selection *Allowed values:* `W` = Watts

General

Product-ID (of the seller)

yes

The unique item ID in the system of the seller. This ID is used to match the offers later on.

Variation » Variation ID

Product title

yes

Item text » Name 1, languages English

Content units per selling unit

yes

Here you provide information about the content of the item, for example 1 piece or 100 g. You have to enter at least 0.0001 here. Enter a period as decimal separator.

Variation » Content value

Charging capacity (min.)

The required power for minimum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed.

Property of the type Text

Example: 20

Charging capacity (max.)

The required power for maximum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed.

Property of the type Text

Example: 27

Brandname

yes

Here you map 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.
For Brandname, first select the manufacturer as it is called at Conrad. Then assign the field to the corresponding manufacturer in PlentyONE.

Example:

Brand.0002
Manufacturer » [Select manufacturer]

Selling unit of measure

yes

Here you map the sales quantity unit. Enter the smallest amount of the item that can be sold individually. This unit is independent of the unit that you want to use to price or store the item.
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 sales quantity units. The values are then assigned to a PlentyONE data field.
For Selling unit of measure, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE.

Example:

ST
Variation » Content unit » Piece

Content units

yes

Here you map the content unit. 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 content units. The values are then assigned to a PlentyONE data field.
For Content units, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE.

Example:

unece.unit.C62
Variation » Content unit » Piece

VAT rate

yes

Here you map the VAT class. 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 VAT classes. The values are then assigned to a PlentyONE data field.
For VAT rate, first select the VAT class as it is called at Conrad. Then assign the field to the corresponding VAT class in PlentyONE.

Example:

1
VAT rate » [VAT rate in per cent]

Charging capacity (max.) UNIT

The required power for maximum charging capacity must be specified in watts.

Property of the type Selection

Allowed values: W = Watts

Charging method (Power Delivery)

Is the USB Power Delivery (PD) charging protocol supported?

Property of the type Selection

Allowed values: mit USB Power Delivery = The appliance supports the USB Power Delivery (PD) charging protocol.
ohne USB Power Delivery = The appliance does not support the USB Power Delivery (PD) charging protocol.

RED-compliant charger available

Is a charger included in the scope of delivery?

Property of the type Selection

Allowed values: Yes = The scope of delivery includes a charger.
No = The scope of delivery does not include a charger.
Product not governed by RED = The product is not subject to the RED (Radio Equipment Directive).

Charging capacity (min.) UNIT

The required minimum charging capacity must be specified in watts.

Property of the type Selection

Allowed values: W = Watts

You need more information on how to map items? Here is an example of item mappings for the product category PC systems. Only the mandatory fields are mapped in this example. Note that the mappings are recommendations only. Depending on how you manage your product data, other mappings may be more appropriate than the recommendation given here.

Example: Recommended mappings of mandatory fields for the category PC systems

Marketplace field Mandatory? Recommended PlentyONE mapping

Marketplace field	Mandatory?	Recommended PlentyONE mapping
General
Product-ID (of the seller)	yes	The unique item ID in the system of the seller. This ID is used to match the offers later on. Variation » Variation ID
Product title	yes	Item text » Name 1, languages English
Content units per selling unit	yes	Here you provide information about the content of the item, for example `1 piece` or `100 g`. You have to enter at least `0.0001` here. Enter a period as decimal separator. Variation » Content quantity
Brandname
Brandname	yes	Here you map 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. For Brandname, first select the manufacturer as it is called at Conrad. Then assign the field to the corresponding manufacturer in PlentyONE. *Example:* Brand.0002 Manufacturer » [Select manufacturer]
Selling unit of measure
Selling unit of measure	yes	Here you map the sales quantity unit. Enter the smallest amount of the item that can be sold individually. This unit is independent of the unit that you want to use to price or store the item. 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 sales quantity units. The values are then assigned to a PlentyONE data field. For Selling unit of measure, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE. *Example:* ST Variation » Content unit » Piece
Content units
Content units	yes	Here you map the content unit. 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 content units. The values are then assigned to a PlentyONE data field. For Content units, first select the unit as it is called at Conrad. Then assign the field to the corresponding unit in PlentyONE. *Example:* unece.unit.C62 Variation » Content unit » Piece
VAT rate
VAT rate	yes	Here you map the VAT class. 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 VAT classes. The values are then assigned to a PlentyONE data field. For VAT rate, first select the VAT class as it is called at Conrad. Then assign the field to the corresponding VAT class in PlentyONE. *Example:* 1 VAT rate » [VAT rate in per cent]

General

Product-ID (of the seller)

yes

The unique item ID in the system of the seller. This ID is used to match the offers later on.

Variation » Variation ID

Product title

yes

Item text » Name 1, languages English

Content units per selling unit

yes

Here you provide information about the content of the item, for example 1 piece or 100 g. You have to enter at least 0.0001 here. Enter a period as decimal separator.

Variation » Content quantity

Brandname

yes

Example:

Brand.0002
Manufacturer » [Select manufacturer]

Selling unit of measure

yes

Example:

ST
Variation » Content unit » Piece

Content units

yes

Example:

unece.unit.C62
Variation » Content unit » Piece

VAT rate

yes

Example:

1
VAT rate » [VAT rate in per cent]

7.3.3. Notes on mapping data fields

Adding a brand

If you want to map a brandname in a product catalogue for which no Conrad data field exists yet, report this brand to Conrad. Conrad then adds this brand to the data field selection.

Exporting an image list

You can export a list of item or variation images to Conrad via the data fields for images. The following data fields are available for image mapping:

Data fields for image export to Conrad

Main Product image URL
Product image 2 URL
Product image 3 URL
Product image 4 URL
Product image 5 URL

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 Main Product image URL and contains three images:

The URL of the first image is mapped to the data field Main Product image URL,
the URL of the second image to Product image 2 URL,
the URL of the third image to Product image 3 URL.

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 13). The complex mapping allows you to react flexibly to different values for item settings or properties.

How does the simple mapping look like in this example?

If you want to transmit the status New for all items:

Next to the marketplace data field, click 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 Conrad. You can find the list of valid values in the Mirakl backend.

How does the complex mapping look like in this example?

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 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 13 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 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 product catalogue.

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

Providing information and images for chargers via the product catalogue

If you export your items to Conrad via catalogues, you can add the information on chargers directly via the data field mappings for items. Conrad automatically generates the required images from your details in the following data fields and provides them on the product detail page:

Charging capacity (min.)
Charging capacity (max.)
Charging method (PD)
RED-compliant charger available
Charging capacity (max.) UNIT
Charging capacity (min.) UNIT
Charging method (Power Delivery)

For further information on these data fields, see the recommendations for data field mappings.

Which Conrad product categories require FuAG information?

0611041 Action cams
1805010 Bluetooth® hands-free sets
1310040 Bluetooth® speakers
0417038 Camcorders
3620048 Digital cameras
0417009 Visualisers
0415035 eBook readers
0413098 eBook reader accessories
3620049 Disposable cameras, non-digital photography
1801021 EX-proof mobile phones
1801040 Mobile phones
1312021 Headphones
0415223 Laptop keyboards
0413102 Beginner’s PC
0411022 PC mice
1310038 Mini speakers
1407014 Portable PA speakers
0715024 Motorbike headsets
0319011 Satnavs
3600038 Nintendo consoles
0609050 Outdoor satnavs
0403047 Outdoor and industry-grade tablets
1407020 Party speakers
1413185 PC complete sets
0416010 PC speakers
0413178 PC systems
0411033 Pen displays
1801022 Satellite phones
3600016 Chess computers
1801050 Big button mobile phones
1801015 Smartphones
1801014 Smartphones (contract)
3620047 Instant cameras
3620020 DSLR cameras
3620050 System cameras
0403040 Tablets
0413122 Tablet keyboards
0420013 Keyboard-mouse combos (desktops)
0420012 Keyboards
1009014 Phone headset cables
0413047 USB-keypads, keypads
0601013 Wearables
0611046 Wildlife cameras

7.3.5. Activating the catalogue export

You have set up Conrad 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 Conrad in the Data » Catalogues menu.

Activating the catalogue export to Conrad:

Go to Data » Catalogues.
→ The catalogues are listed.
Scroll to the Conrad catalogue.
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to Conrad once a day.
Tip: Go to Data » Catalogue export status for information about the status of the export.

8. Exporting offer data

Offer data is exported to Conrad using catalogues. Catalogues for Conrad are usually managed via the Data » Catalogues menu. However, you can also create catalogues for Conrad directly in the Channel Control Centre.

What is a catalogue?

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

Marketplace formats are used to export item data to markets.
Standard formats are used to export data from your PlentyONE system into a file.

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

8.1. Creating an offer catalogue

Offer data is exported to Conrad via a catalogue. You can create catalogues for Conrad directly in the Channel Control Centre. Then, map the Conrad data fields to offer data saved in PlentyONE in the catalogue you created.
Once you have activated the catalogue, the account, the listing and the variations, the offer data is automatically exported to Conrad once a day.

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the Conrad tile.
Go to Mapping » Offer mapping.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option Conrad.
In the drop-down list Export type, select the option Item (New).
In the drop-down list Category, select Offer.
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 Conrad. 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 Conrad was successful.

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

8.1.1. Mapping data fields in the offer catalogue

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

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

Getting to know the catalogue menu for marketplace formats

Availability	Explanation
Navigation	When you open a catalogue, the view Mapping is shown. On the very left is the navigation. Switch to other views of the catalogue. Open the catalogue settings. Use filters that limit the data that is exported. Go back to the list of catalogues. Create a new catalogue.
Toolbar	The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields.
Marketplace data field	To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱). *Tip:* Show or hide optional marketplace data fields in the toolbar. To do so, click on the further actions ().
PlentyONE data fields	On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped.

Availability

Explanation

Navigation

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

Switch to other views of the catalogue.
Open the catalogue settings.
Use filters that limit the data that is exported.
Go back to the list of catalogues.
Create a new catalogue.

Toolbar

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

Marketplace data field

PlentyONE data fields

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

Mapping catalogue fields:

Go to Sales Channels » Channel Control Centre.
Click on the tile of your Conrad Sales Channel.
Click on the catalogue you want to edit.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.
Map suitable PlentyONE data fields to the market data fields.
For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.
- Simple 1:1 mapping
- Simple 1:1 mapping with properties
- Complex 1:1 mapping
- 1:1 mapping with fallback data fields
- 1:n mapping
- Own value mapping
- Mapping with mathematical calculations
Save () the catalogue.
→ The mappings are saved.

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

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

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

I want to fill this marketplace data field with the data from this PlentyONE setting.
If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.

Example: Sales price and RRP for Otto Market

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

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

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

Creating a property:

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

Creating a simple 1:1 mapping with properties:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Expand the group Property.
→ The property groups are shown.
Expand the group you need.
Click on the Plus sign on the right of the property you want.
From the drop-down list Language, select the language in which you send the data to the market.
Click on Confirm.
→ The property is mapped to the marketplace data field.

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

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

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

Examples for complex 1:1 mappings are:

Categories
Brands
Shipping setting

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

Creating a complex 1:1:n mapping:

Click on the field for the marketplace data field.
→ A list of the available values is shown.
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped.
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups.
Click on a group.
→ The PlentyONE data fields of the group are shown.
Click on the PlentyONE data field for which you want to map values.
Important: Do not map own values or properties of the type None.
Your next steps depend on the PlentyONE data field you selected:
- Alternative 1: The available values for the PlentyONE data value are shown on the left.
  - Next to the value you want to select, click on the plus.
    → The value is added to the field on the right.
  - Click on Confirm.
- Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.
  - In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.
  - Click on Confirm.
- Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.
  - Select a value from the drop-down list.
  - Click on Confirm.
    → The value of the marketplace data field is exported, not the value of the PlentyONE data field.
    Exception: Only when you map an own value, the own value that you enter is exported.

Example: Delivery time in days for Otto Market

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

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

So this mapping specifies:

I want to fill the marketplace data field with the data from the selected PlentyONE setting.
If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.
If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

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

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

SKU
Barcodes
Sales prices
Properties

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

Empty

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

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

PlentyONE data fields that are available for variations by default

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

Creating a 1:1 mapping with fallback data fields:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
→ The fallback data field is added with the fallback condition "null".
Alternative 1: To add the fallback data field with the fallback condition "null":
1. Click on Confirm.
  → The fallback data field is exported if the data field above is not linked to the variation.
Alternative 2: To add the fallback data field with the fallback condition "empty":
1. To the left of the fallback data field, click on the cog ().
  → The window Data column settings is shown.
2. For the setting Fallback condition, select the option Empty.
3. Click on Save.
  → The fallback data field is added with the fallback condition "empty".
4. Click on Confirm.
  → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

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

1:n mapping: 1 marketplace data field, several PlentyONE data fields

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

So this mapping specifies:

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

Creating a 1:n mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the group you need.
→ The PlentyONE data fields of the group are shown.
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right.
Click on Confirm.
To the right of the mapped PlentyONE data field, click on Add data field ().
→ To the left, the list of available PlentyONE data fields again are shown in groups.
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
Click on Confirm.
To the very right of the row, click on Settings ().
Select a separator from the drop-down list Separator or add a custom separator.
Click on Save.
Save () the catalogue.
→ The mappings are saved.
→ During the export, the content of the PlentyONE data fields is combined and exported as one field.

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

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

So this mapping specifies:

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

Creating an own value mapping:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view.
Enter a value into the input field.
→ This value is exported for all variations.

Example: Diameter information

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

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

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

This function only works for data fields that contain numerical values.
This functionality is new and not available for all catalogue formats.

So this mapping specifies:

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

Recalculating numerical values:

Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups.
At the very top of the list, click on the plus icon next to Formula ().
→ The data field Formula is added to the field on the right.
Click into the data field.
→ The window Modify value is shown.
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation ().
Tip: Use the search function. This helps you to find data fields quickly.
Optional: If the symbol is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.
1. Click on the icon .
2. In the window shown, select the assignments from the drop-down list.
3. Save the settings.
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.

8.1.2. Recommendations for data field mappings

Need more information about the PlentyONE data fields? All data fields are described on the manual page for the standard format Item (new).

List of recommended data field mappings for the format Offer

Marketplace field Mandatory? Recommended PlentyONE mapping

Marketplace field	Mandatory?	Recommended PlentyONE mapping
Offer SKU	yes	This data field is assigned automatically.
Offer SKU status	no	This data field is assigned automatically.
Offer SKU base	no	Variation » Variation ID
ItemID	no	This data field is assigned automatically.
VariationID	no	This data field is assigned automatically.
Offer description	no	Property of the type Text
Offer internal description	no	The internal offer description. This description will not be shown on Conrad. Property of the type Text
Offer price	yes	The sales price of the item. Sales price » [Select sales price for Conrad]
Offer price additional info	no	Additional information about the sales price.
Offer quantity	no	The stock of the variation. Stock » Total virtual stock » Net stock *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? Variation » Release date
Availability end date	no	Until when will the item be available? Variation » Available until
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. Variation » Availability days
Update/delete	no	This data field is automatically mapped with UPDATE so that items can be updated on Conrad.
Active channels	no	This data field is assigned automatically.
Product ID Type
Product ID Type	yes	EAN Preferably use the EAN as the identifier, as Conrad can uniquely identify the product based on the EAN. If the product already exists at Conrad, the system will automatically link the product to its corresponding Conrad SKU. If you use EAN as the Product ID Type, map the data source Barcode » GTIN13 to Product ID. SKU The SKU at Conrad is different from the PlentyONE SKU. The Conrad SKU is a unique identifier assigned by Conrad to each product. If you want to add items to existing offers with content provided by Conrad, you can map the relevant Conrad SKU. If you use SKU as the Product ID Type, map a property of the type Text or Selection to Product ID. The value of this property must exactly match the Conrad SKU of the product. SHOP_SKU Instead of the EAN, you can also use the SHOP_SKU as the identifier. If you use SHOP_SKU as the Product ID Type, make sure that you use the same mapping for Product ID as in the item catalogue. *Example:* If you have mapped the Variation ID to Product ID in the item catalogue, also use the Variation ID for Product ID here.
Offer state
Offer state	yes	The item’s condition, for example new or used. Property of the type Text or Selection
Logistics class
Logistics class	no	Conrad 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? Property of the type Text or Selection *Allowed values:* `true` = The item can be returned free of charge. `false` = A free return is not allowed.
Return costs
Return costs	yes

Offer SKU

yes

This data field is assigned automatically.

Offer SKU status

This data field is assigned automatically.

Offer SKU base

Variation » Variation ID

ItemID

This data field is assigned automatically.

VariationID

This data field is assigned automatically.

Offer description

Property of the type Text

Offer internal description

The internal offer description. This description will not be shown on Conrad.

Property of the type Text

Offer price

yes

The sales price of the item.

Sales price » [Select sales price for Conrad]

Offer price additional info

Additional information about the sales price.

Offer quantity

The stock of the variation.

Stock » Total virtual stock » Net stock

Tip: Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses.

Minimum quantity alert

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

When will the item be available?

Variation » Release date

Availability end date

Until when will the item be available?

Variation » Available until

Discount price

The offer price.

Discount start date

When will the discount start?

Discount end date

When will the discount end?

Lead time to ship (in days)

The processing time in days until the item can be shipped.

Variation » Availability days

Update/delete

This data field is automatically mapped with UPDATE so that items can be updated on Conrad.

Active channels

This data field is assigned automatically.

Product ID Type

yes

EAN

Preferably use the EAN as the identifier, as Conrad can uniquely identify the product based on the EAN. If the product already exists at Conrad, the system will automatically link the product to its corresponding Conrad SKU.

If you use EAN as the Product ID Type, map the data source Barcode » GTIN13 to Product ID.

SKU

The SKU at Conrad is different from the PlentyONE SKU. The Conrad SKU is a unique identifier assigned by Conrad to each product. If you want to add items to existing offers with content provided by Conrad, you can map the relevant Conrad SKU.

If you use SKU as the Product ID Type, map a property of the type Text or Selection to Product ID. The value of this property must exactly match the Conrad SKU of the product.

SHOP_SKU

Instead of the EAN, you can also use the SHOP_SKU as the identifier.

If you use SHOP_SKU as the Product ID Type, make sure that you use the same mapping for Product ID as in the item catalogue.

Example: If you have mapped the Variation ID to Product ID in the item catalogue, also use the Variation ID for Product ID here.

Offer state

yes

The item’s condition, for example new or used.

Property of the type Text or Selection

Logistics class

Conrad calculates the shipping costs of an item with the item’s logistic class.

Free return

Can the item be returned free of charge?

Property of the type Text or Selection

Allowed values: true = The item can be returned free of charge.
false = A free return is not allowed.

Return costs

yes

8.1.3. Notes on mapping data fields

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 13). The complex mapping allows you to react flexibly to different values for item settings or properties.

How does the simple mapping look like in this example?

If you want to transmit the status New for all items:

Next to the marketplace data field, click 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 Conrad. You can find the list of valid values in the Mirakl backend.

How does the complex mapping look like in this example?

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 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 13 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 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 offer catalogue.

8.1.4. Activating the catalogue export

You have set up Conrad in PlentyONE and created a catalogue for exporting your offer data? Then activate the catalogues you want to export to Conrad in the Data » Catalogues menu and continue with creating offer listings.
Once you have activated the offer catalogue, the data exchange, the offer listing and the variations, the offer data will be automatically exported to Conrad once a day.

Activating the catalogue export to Conrad:

Go to Data » Catalogues.
→ The catalogues are listed.
Scroll to the Conrad catalogue.
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to Conrad once a day.
Tip: Go to Data » Catalogue export status for information about the status of the export.

9. Manually exporting product and offer data

In the Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » Data exchange » Data export menu, you can manually export individual items and offers to Conrad. For example, this can be helpful if you want to test the export to Conrad or if you only want to export individual items.

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

Manually exporting an item:

Go to Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » 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 Conrad.
Click Export.
Note: You can run this process every 30 minutes. Items cannot be exported manually between 24.00 - 6.00 CET.
Tip: Click Preview to generate e preview of the export.

Manually exporting offers:

Go to Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » 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 Conrad.
Click Export.
Note: You can run this process every 15 minutes.
Tip: Click Preview to generate e preview of the export.

10. Managing listings

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

10.1. Offer listings

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

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

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

Applying search filters

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

Applying filters:

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

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

Single listing view
Group view

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

Table 5. Offer listings overview

Column

Explanation

Data sync

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

Group ID

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

Listing Name

Name of the offer listing.

SKU

SKU of the offer listing.
Note: You can edit the SKU. To do so, click Activate editing mode (). Make the changes and click Save () to apply them. If you want to exit the editing mode, click Deactivate editing mode ().

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Status on Channel

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

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

Note: For platforms with multiple sales channels, the number after the status icon indicates on how many sales channels the offer listing has this status.

List on

The sales channels on which the offer listing is to be offered are displayed here.
Click the pencil icon (edit) to add or remove sales channels.

Errors

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

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

Click here to display more actions.

toggle_on Activate data sync

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

Delete listing

Preview export results

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

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

Table 6. Group view of the offer listings

Column

Explanation

Data sync

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

Group name

Name of the listing group

SKU

SKU of the listing group.

Channel

The sales channel to which the listing group is exported.

Errors

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

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

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

Click here to display more actions.

toggle_on Activate data sync

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

Delete listing group

Delete listing group.

Preview export results

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

10.2. Product listings

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

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

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

Applying search filters

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

Applying filters:

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

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

Single listing view
Group view

<<#table-product-listings-overview>> offers an overview of the single listing view of product listings.

//*_Tip:_* Click on material:edit[] in the columns *Listing name* and *Catalogue* to activate the editing mode and to edit the listing name or catalogues.//

[[table-product-listings-overview]]
.Overview of product listings
[cols="1,2a"]
|===
|Column |Explanation

| *Data sync*
| This column indicates whether data exchange for the product listing is active or paused. +
*_Tip:_* You can activate the data exchange in the listing’s line via *material:more_vert[] » matsymbol:toggle_on[] Activate data sync* .

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

| *Listing Name*
| Name of the listing.

| *Variation ID*
| ID of the variation.

| *Channel*
| The sales channel to which the listing is exported.

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

. matsymbol:help[role=white] = Unknown
. matsymbol:progress_activity[role=white] = Outstanding
. matsymbol:progress_activity[role=white] = Creation pending
. matsymbol:cancel[role=red] = Failed (Before creation)
. matsymbol:check_circle[role=green] = Online
. matsymbol:cancel[role=red] = Failed (On update)
. matsymbol:pause_circle[role=lightGrey] = Paused
. matsymbol:unpublished[role=lightGrey] = Offline

*_Note:_* For platforms with multiple sales channels, the number after the status icon indicates on how many sales channels the offer listing has this status.

| *List on*
| The sales channels on which the product listing is to be offered are displayed here. +
Click the pencil icon (matsymbol:edit[]) to add or remove sales channels.

| *Errors*
| Indicates whether the listing is incorrect. Click to open the overview of listing errors. +
No entry = No errors occurred. +
material:circle[role="red"] = Errors occurred. The number indicates the number of errors.

| *Template*
| The template selected for the listing.

| *Catalogue*
| The catalogue selected for the listing.

| *Creation date*
| The date and time on which the listing was created.

| material:more_vert[]
| Click here to display more actions.

[cols="1,3a"]
!====
! matsymbol:toggle_on[] *Activate data sync*
! Activate to permit the data transfer between the sales channel and the listing. +
*_Note:_* Even if the *Activate data sync* option is activated, the listing will not be immediately listed on the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when a listing is online.

! material:delete[] *Delete listing*
! material:delete[] *Delete listing*

! material:preview[] *Preview export results*
! Generates the preview of the export results. The preview opens in a separate window.
!====
|===

<<#table-product-listings-group-view>> offers an overview of the group view of product listings.

//*_Tip:_* Click on material:edit[] in the columns *Group name* and *Catalogue* to activate the editing mode and to edit the group name or catalogues.//

[[table-product-listings-group-view]]
.Group view of the product listings
[cols="1,2a"]
|===
|Column |Explanation

| *Data sync*
| This column indicates whether data exchange for the listing group is active or paused. +
*_Tip:_* You can activate the data exchange in the listing group’s line via *material:more_vert[] » matsymbol:toggle_on[] Activate data sync*.

| *Group name*
| Name of the listing group

| *Channel*
| The sales channel to which the listing group is exported.

| *Errors*
| The error overview. +
No entry = No errors occurred. +
material:circle[role="red"] = Errors occurred. The number indicates the number of errors.

| *Template*
| The template selected for the listing group.

| *Catalogue*
| The catalogue selected for the listing group.

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

| material:more_vert[]
| Click here to display more actions.

[cols="1,3a"]
!====
! matsymbol:toggle_on[] *Activate data sync*
! Activate to permit the data transfer between the sales channel and the listing group. +
*_Note:_* The data sync must be activated for the single listing to exchange product data with the sales channel. +
Even if the *Activate data sync* option is activated for a listing group, the listing data will not be immediately exported to the sales channel. The listing data is only permitted to be exported to the sales channel. It depends on the respective sales channels when the listings is online.

! material:delete[] *Delete listing group*
! Delete listing group.

! material:preview[] *Preview export results*
! Generates the preview of the export results. The preview opens in a separate window.
!====
|===

10.3. Creating listings

Offers are transferred to Conrad as listings. Carry out the following steps to create listings for Conrad.

What are product listings and offer listings used for?

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

10.3.1. Create product listings

Product listings are created in three steps:

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

Create product listings using the group function

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

Step 1: Specify listing details:

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

Step 2: Select variations:

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

Step 3: Preview and confirm selection:

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

10.3.2. Activating product listings

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

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

Activating product listings:

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

Activating a listing group:

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

10.3.3. Creating offer listings

Offer listings are created in three steps:

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

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

Step 1: Specify listing details:

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

Step 2: Select variations:

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

Step 3: Preview and confirm selection:

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

10.3.4. Activating offer listings

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

Activating offer listings:

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

Activating a listing group:

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

10.3.5. Viewing listing errors

The Errors tab of the Sales Channels » Channel Control Centre » [Open sales channel] » Offer listings / Product listings menu provides an overview of all errors that occurred in PlentyONE when exporting your product and offer listings.
Tip: The overview of listing errors is only displayed if at least one error has occurred when exporting the listings.

Here you can see:

the affected listings
error details

For each error, you can download a CSV file containing the affected listings by clicking the download button. You can correct the errors directly in the CSV file. You can then re-import the corrected CSV file.

Table 7 contains an overview of listing errors.

Table 7. Listing errors of offer listing and product listings
Column	Explanation
[Information about the error]	Information about the error is provided here. It contains the affected field of the data record, a brief description of the error and the number of listings for which this error has occurred. *Example:* "Field: gtin Error: Given data is not a string. (1)" → The error occurred in the gtin field of the data record. → The error occurred because no character string was entered as a value in the gtin field. → The error has occurred for one listing.
Download data as CSV	The CSV file with the data records is downloaded.
Listing name	The name of the listing.
Parent SKU	The parent SKU of the main variation.
SKU	The SKU of the sub-variation.
Variation ID	The ID of the variation.
Channel	The sales channel to which the listing is exported.
Export activity	Shows whether the variation is being exported. Active () = The variation is exported with the listing. Not active () = The variation is not exported with the listing.
Status	The listing’s status on the sales channel. Possible statuses are: help = Unknown progress_activity = Outstanding progress_activity = Creation pending cancel = Failed (before creation) check_circle = Online cancel = Failed (on update) pause_circle = Paused unpublished = Offline
Errors	The error overview. No entry = No errors occurred. = Errors occurred. The number indicates the number of errors.
Template	The template selected for the listing.
Catalogue	The catalogue selected for the listing.

11. Manually importing orders

In the Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » Data exchange » Order import menu, you can manually import individual orders into PlentyONE. This can be helpful if you have to import missing orders.
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.

Entering order IDs
Selecting a time frame

Import orders by ID:

Go to Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » Data exchange » Order import.
Click 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 Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Settings » Data exchange » Order import.
Click the tab Import orders by date.
Enter a start date in the format D.M.YYYY or select a date via the calendar ().
Enter an end date in the format D.M.YYYY or select a date via the calendar ().
Click Import.
→ Orders from the selected time frame are imported into PlentyONE.

12. Automating order processing

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

Automatically inform Conrad that the order was confirmed. (How?)
Automatically inform Conrad that the order was rejected. (How?)
Automatically inform Conrad that the items have been shipped. (How?)
Automatically inform Conrad about cancellations. (How?)
Automatically inform Conrad about refunds. (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 running or completed workflows.

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

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

12.1. Reporting order confirmation to Conrad

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

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 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.
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 statuses, controls and filters for the flow which best suit your workflow.

Table 8. Event-based flow to report an order confirmation to Conrad

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order created

For Order types, select the type Incomplete order.

Controls

Branch

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

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Conrad

Actions

Plugin (Legacy) > Conrad

Accept incomplete order on Conrad
Note: If you additionally use the action Order > Change order status, select a status between Status 1 and Status 2.

12.2. Reporting order rejection to Conrad

Create an event-based flow to automatically inform Conrad about the rejection of an order.

Creating an event-based flow

Go to Automation » Flow Studio.
Click Create flow ().
→ A stepper opens and guides you through the following three steps.
1. General
  1. Enter a unique name and, if necessary, a description for the new flow.
  2. Click Next.
2. Trigger
  1. Select Event-based as the trigger.
  2. Click Next.
3. Settings
  1. If desired, select a UI from the optional drop-down list Flow available in.
    → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
    Note: UIs currently selectable: Order UI.
  2. From the drop-down list Trigger selection, select the event according to Table 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.
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 statuses, controls and filters for the flow which best suit your workflow.

Table 9. Event-based flow to report an order rejection to Conrad

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order created

For Order types, select the type Incomplete order.

Controls

Branch

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

Filter

Operator

Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

Conrad

Actions

Plugin (Legacy) > Conrad

Reject incomplete order on Conrad
Note: If you additionally use the action Order > Change order status, select a status between Status 1 and Status 2.

12.3. Reporting shipping confirmation to Conrad

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

Creating an event-based flow

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

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

Table 10. Event-based Flow for sending shipping confirmations to Conrad

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Order > Book outgoing items

Select an order status, for example:

[7] Outgoing items booked

Controls

Branch

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

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Conrad

Actions

Plugin (Legacy) > Conrad

Report shipping confirmation to Conrad

12.4. Automatically reporting cancellations

Create an event-based flow to automatically inform Conrad about cancellations. Note that orders marked as shipped can no longer be cancelled.
Different flows can be created, depending on the reason for the cancellation. The following actions are available for Conrad to report a cancellation:

Report cancellation to Conrad: Item no longer available
Report cancellation to Conrad: Content error
Report cancellation to Conrad: Cancelled by the client prior to shipping
Report cancellation to Conrad: Customer complaint
Report cancellation to Conrad: Delivery address undeliverable / goods returned
Report cancellation to Conrad: Return
Report cancellation to Conrad: Cancellation request of the customer
Report cancellation to Conrad: Wrong payment term
Report cancellation to Conrad: Agreement reached between buyer and seller
Report cancellation to Conrad: Too long shipping time
Send cancellation to Conrad

Creating an event-based flow

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

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

Table 11. Event-based flow to send a cancellation to Conrad

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select a status, for example:

[8] Cancelled

[8.1] Cancelled by customer

Controls

Branch

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

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Conrad

Actions

Plugin (Legacy) > Conrad

Send cancellation to Conrad

Report cancellation to Conrad: (Select the appropriate option)

12.5. Reporting refunds to Conrad

Create an event-based flow to automatically inform Conrad about refunds.
Different flows can be created, depending on the reason for the refund request. The following actions are available for Conrad to report a refund:

Report refund to Conrad: Item not received
Report refund to Conrad: Item returned
Report refund to Conrad: Agreement with vendor
Report refund to Conrad: Out of stock
Report refund to Conrad: Cancelled before shipping

Creating an event-based flow

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

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

Table 12. Event-based flow to send a refund request to Conrad

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order created

Select an order type, for example:

Credit note

Controls

Branch

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

Filter

Operator

Input field

Order > Order referrer

Is in (IN)

Conrad

Actions

Plugin (Legacy) > Conrad

Report refund to Conrad: (Select the appropriate option)

13. Download reports

In the Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Reports menu, you can download reports for offer export and item export. These reports are generated after an offer or item export to Conrad.

Table 13 contains an overview of the reports in the Channel Control Centre.

Table 13. Reports for Conrad in the Channel Control Centre
Column	Explanation
Date	Creation date of the report in the format YYYY.MM.DD hh:mm:ss
Status	The processing status of the report. Reports can have the following statuses: PENDING = The report has not been processed yet. COMPLETE = The report was processed.
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 (): The report is downloaded.

Downloading a report:

Go to Sales Channels » Channel Control Centre » [Open sales channel for Conrad] » Reports.
Click Filters () at the top of the menu.
Select a report type. The available report types are listed in Table 14.
Click 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 () it. Then select the desired filter as described above.
Click Download report ().
→ The report is downloaded.

Table 14. Report types
Report type	Explanation
Offers	The offer report contains information on the offer export to Conrad.
Products	The product report contains information on the item export to Conrad.

Conrad Core Integration (Setup via Channel Control Centre)

1. Becoming a seller at Conrad

2. Frequency of data exchange

3. Setting up the data exchange

4. Workflow of an order

5. Setting up Conrad in PlentyONE

5.1. Sales channel overview

5.2. Adding the sales channel

5.3. Carrying out the basic settings for Conrad

5.4. Adjusting the general settings

5.5. Activating the order referrer

6. Preparing variations

6.1. Setting the variation availability

7. Exporting product data

7.1. Adding product categories

7.2. Linking variations to a Conrad product category

7.3. Creating a product catalogue

7.3.1. Mapping data fields in the product catalogue

7.3.2. Recommendations for data field mappings

7.3.3. Notes on mapping data fields

Adding a brand

Exporting an image list

Data fields with different mapping options

7.3.4. Providing information and images for chargers for electrical appliances with radio frequency (FuAG)

Providing information and images for chargers via the product catalogue

7.3.5. Activating the catalogue export

8. Exporting offer data

8.1. Creating an offer catalogue

Other catalogue settings

8.1.1. Mapping data fields in the offer catalogue

8.1.2. Recommendations for data field mappings

8.1.3. Notes on mapping data fields

Data fields with different mapping options

8.1.4. Activating the catalogue export

9. Manually exporting product and offer data

10. Managing listings

10.1. Offer listings

10.2. Product listings

10.3. Creating listings

10.3.1. Create product listings

10.3.2. Activating product listings

10.3.3. Creating offer listings

10.3.4. Activating offer listings

10.3.5. Viewing listing errors

11. Manually importing orders

12. Automating order processing

12.1. Reporting order confirmation to Conrad

12.2. Reporting order rejection to Conrad

12.3. Reporting shipping confirmation to Conrad

12.4. Automatically reporting cancellations

12.5. Reporting refunds to Conrad

13. Download reports

Is this page helpful?

Is this page helpful?