eMAG (Setup via Channel Control Centre)

The Romanian market eMAG is the largest market in Southeast Europe.

eMAG offers 3 country-specific markets. Each of these markets is a stand-alone platform.

Romania
Bulgaria
Hungary

Sales Channels » Channel Control Centre

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

1. Registering with eMAG

First, register as a seller with eMAG. You can register on the eMAG website.
Tip: Click on the arrow next to the Romanian flag to change the language to English.

2. Frequency of data exchange

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

Table 1. Frequency of data exchange
Data	Interval	Explanation
Item export	once a day
Offer export	once a day	Only new offers are exported. New offers are variations for which no PNK is saved in the SKU data field yet. The process exports the new offers and saves the PNK as an SKU.
Offer update	every 15 minutes	Offers are exported if either the price or the stock has changed since the last run.
Offer removal	once a day	Offers are removed from eMAG under the following conditions: The variation was deleted from PlentyONE The variation is no longer active This variation is no longer enabled for eMAG The client used for eMAG was removed from the variation
Order import	every 20 minutes
Catalogue templates	every two weeks	The catalogue templates are updated every two weeks on Monday. The update takes place in even calendar weeks.

3. Products vs. Offers

Whoever lists item data for a product first on eMAG becomes the owner of this product. Only owners can update the item data of the product. The owner’s price is displayed to the right of the item description.
All other merchants can only publish prices and stocks for the product. As such, they do not publish a product. Instead, they publish an offer. This information is shown below the item description as "other offers".

Important: eMAG checks all product and offer data manually before publication on the market.

emag owner vs offer

4. Workflow of the item data export

Scenario 1: You want to list a product on eMAG that no one else is offering on the market.

You export the item data for the first time. To do so, you use the catalogue format eMAG Products.
eMAG checks all item data manually. Patience is a virtue.
eMAG assigns a unique Part Number Key to the product. eMAG also calls this key a PNK code. The PNK is automatically saved in PlentyONE as an SKU and now serves as the unique identification key.
You become the owner of the product page. This means that only you are allowed to update the item data of this product. All other sellers can only publish offers for this product. As such, they can only export prices and stock information.
Every time you update the item data, someone at eMAG manually checks the data again.

emag owner

Scenario 2: You want to list a product on eMAG that is already offered on the market.

You export the item data for the first time. To do so, you use the catalogue format eMAG Offers.
When you export an offer for the first time, eMAG uses the EAN to match the offer to the correct product. Afterwards, the PNK is automatically saved as an SKU in PlentyONE and now serves as the unique identification key.
Your offer is published on the product page below the item description as an additional offer.

emag offer

5. Workflow of an order

This is the order workflow for eMAG:

Your products are listed on eMAG.
Customers place an order on eMAG.
Customers make their payments to eMAG.
The order is imported into PlentyONE.
Note: Customers make their payments to eMAG. As such, orders are imported with Status [5] Cleared for shipping.
You ship the order.
You notify eMAG of the shipment via Flow.

6. Setting up eMAG in PlentyONE

First, add eMAG 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.

6.1. Sales channel overview

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

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

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

Component

Explanation

Name

The name of the sales channel.

More

Click here to display more actions for a sales channel.

Listings

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

Settings

Opens the respective Settings menu of the sales channel.

Delete sales channel

Deletes the sales channel from the overview.

6.2. Adding the sales channel

First, add eMAG 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 eMAG.
Enter a name for the sales channel.
If asked to, select the Client (Shop) from the drop-down list.
Click Add eMAG.
→ The sales channel for eMAG is added.

6.3. Carrying out the basic settings for eMAG

Next, carry out the basic settings for eMAG.

First, add a new account for eMAG.

Adding an account for eMAG:

Go to Sales Channels » Channel Control Centre.
Click on the eMAG tile.
→ The tab Settings opens.
Click Add account ().
→ The Add account window opens.
From the Marketplace drop-down list, select the desired marketplace.
From the Client drop-down list, select the desired client.
Click SAVE (save).
→ A view with account settings opens.
Carry out the additional settings. Pay attention to the explanations given in Table 3.
Click Save (save).
→ The settings are saved.

Table 3. Settings for the sales channel eMAG

Column

Explanation

Save

Save the settings.

More

Click here to display more actions.

open_in_new Check manual

Click here to open the eMAG manual page in a new browser tab.

Delete account

Delete the account.

CONNECT ()

Click here to connect to eMAG. Enter your user name and password and click SAVE (save).

General

Active

Activate the eMAG account (). The data exchange with eMAG is started.
We recommend to only activate the account after you carried out all settings.

Note: The account has to be connected to an eMAG account so that data can be exchanged between PlentyONE and eMAG.

Client

The client (Shop) that orders of this eMAG account are assigned to. The client was selected when the account was created and cannot be changed afterwards.

Marketplace

The marketplace your eMAG account is assigned to. The marketplace was selected when the account was created and cannot be changed afterwards.

Stock buffer

Enter a value that should be used as stock buffer. A stock buffer is the amount of an item that should not be sold, but kept as a buffer.
For example, if you enter the value 5 here, then the stock for eMAG is reduced by 5 items which are kept as a buffer.

Items

Items export

Activate () to export items to eMAG once a day.

Shipping service providers

Match your PlentyONE shipping profiles with the eMAG shipping service providers from the drop-down list.
Note: Your account has to be connected to eMAG. If the account is not connected, the eMAG shipping service providers might not be displayed.

Orders

Orders import

Activate () to import orders from eMAG into PlentyONE every 15 minutes.

Cancellation requests import

Activate() to automatically import cancellation requests into PlentyONE once per day.

Return requests import

Activate () to automatically import return requests into PlentyONE once per day.

Status for cancelled orders

Select the order status for orders that were cancelled.

Tip: Select a status higher than status 8.

Offers

Offers update

Activate () to export offers for which either the price or the stock has changed since the last run.

Offer update start date

Enter a date in the format D.M.YYYY or select a date via the calendar ().
Only offers starting from this date will be updated on eMAG.

6.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 eMAG.
→ The Settings menu opens.
Switch to the menu General settings.
Enter a new Channel name.
Click Save (save).
→ The new channel name is saved.

6.5. Activating the order referrer

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

What is an order referrer?

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

The following order referrers are available for eMAG:

169.00 eMAG = All eMAG sales channels
169.01 eMAG Romania = eMAG Romania
169.02 eMAG Bulgaria = eMAG Bulgaria
169.03 eMAG Hungary = eMAG Hungary

If you want to sell your items on all eMAG country platforms for which you have created an account in PlentyONE, activate only the parent referrer for eMAG (169.00 eMAG). Your items will then be available on all eMAG country platforms.
If you only want to sell your items on specific eMAG country platforms, then only activate those referrers.

Activating the order referrer for eMAG:

Go to Setup » Orders » Order referrer.
Click Search ().
In the list, navigate to the option eMAG or one of the sub-referrers.
On the right of the referrer’s line, click Edit ().
→ The window Edit referrer opens.
Note: If you want to sell your items on all eMAG country platforms for which you have created an account in PlentyONE, activate only the parent referrer for eMAG (169.00 eMAG). Your items will then be available on all eMAG country platforms.
If you only want to sell your items on specific eMAG country platforms, then only activate those referrers.
Activate the option Visible in selection ().
Click SAVE ().
→ The referrer is active.

6.6. Defining a sales price

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

What is a sales price?

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

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

eMAG expects a net sales price. You can export a price in Euros. eMAG then converts the price into the local currency. However, you can also create and use a sales price in the local currency for eMAG.

Defining a sales price for eMAG:

Go to Setup » Item » Sales prices » [Open sales price].
Tip: No sales prices? Then create a sales price first.
Activate the referrer eMAG.
Save () the settings.

7. Preparing variations

Now, prepare your variations for the export.

7.1. Setting the variation availability

You need to activate the variations you want to sell on eMAG 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 eMAG:

Go to Item » Items » [Open variation].
Tip: To sell all variations of an item on eMAG, 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 eMAG 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 eMAG.

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 eMAG 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 eMAG 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 eMAG using batch processing:

Navigate to the area Market availability.
Activate the checkbox to the left of the option eMAG.
Activate the checkbox to the right of the option eMAG.
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.2. Link sales price and save price

Now, link the sales price for eMAG to your variations and enter the actual monetary amounts.

Linking the sales price and saving a price:

Go to Item » Items » [Open variation].
Click the Pricing tab.
In the Sales prices section, click More () and then Add sales prices ().
Select the sales price for eMAG from the drop-down list on the left.
Click APPLY.
→ The sales price is added and displayed in the list.
Enter the monetary price into the Price field.
Click Save (save).

8. Setting up the item export

Item data is exported to eMAG using catalogues. Catalogues for eMAG are usually managed via the Data » Catalogues menu. However, you can also create catalogues for eMAG 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.

8.1. Creating a catalogue

To export your items to eMAG, create catalogues in the Channel Control Centre. In each product catalogue, you map the eMAG data fields to the corresponding item data saved in PlentyONE. Once you have activated the catalogue, account, listing and variations, the item data is automatically exported to eMAG at regular intervals.

There are three export types for eMAG: The export type eMAG Offers, the export type eMAG Products and the export type eMAG Generic Products.

Categories for eMAG Products

eMAG must activate you for each category in which you want to offer items. You can only create an eMAG Products catalogue after eMAG has activated you for the desired category. If you are not activated for a category, your products will not be published in the category.

eMAG offers the possibility to export items without a specific category (e.g. electronics, books or gardening) as well as in a language other than Romanian, Hungarian or Bulgarian. The items exported via the eMAG Generic Products catalogue are translated by eMAG in a semi-automated process and assigned to a corresponding category.

Note: The eMAG Generic Products catalogue currently only works for eMAG Romania, but will also be activated for eMAG Bulgaria and eMAG Hungary in the future.

Creating a catalogue for offers
Creating a catalogue for products
Creating a catalogue for generic products

Offers are exported using the export type eMAG Offers. There is only one category for this export type. All offers are therefore exported with only one catalogue.

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the eMAG 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 eMAG Offers.
In the drop-down list Export type, select the option Item (new).
From the drop-down list Category, select the option Offers.
Click Save (save).
→ The catalogue is created.
→ The catalogue is opened for editing.
On the left-hand side of the menu, click on Settings.
In the Basic settings, select the account that you want to use this catalogue for.
Click Save (save).

Products are exported using the export type eMAG Products. As the category, you select the category in which you want to publish the products of the catalogue. Note that eMAG has to activate you for each category. If you are not activated for a category, your products will not be published in the category.

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the eMAG tile.
Go to Mapping » Product mapping.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option eMAG Products.
In the drop-down list Export type, select the option Item (new).
In the drop-down list Category, select a category of the sales channel for which you want to create a catalogue.
Click Save (save).
→ The catalogue is created.
→ The catalogue is opened for editing.
On the left-hand side of the menu, click on Settings.
In the Basic settings, select the account that you want to use this catalogue for.
Click Save (save).

Products without a specific category and in a language other than Romanian, Hungarian or Bulgarian are exported using the eMAG Generic Products export type. The items exported via the eMAG Generic Products catalogue are translated by eMAG in a semi-automated process and assigned to a corresponding category.

Note: The eMAG Generic Products catalogue currently only works for eMAG Romania, but will also be activated for eMAG Bulgaria and eMAG Hungary in the future.

Creating a catalogue:

Go to Sales Channels » Channel Control Centre.
Click on the eMAG tile.
Go to Mapping » Product mapping.
Click Create catalogue (add).
Enter a name for the catalogue.
In the drop-down list Marketplace, select the option eMAG Generic Products.
In the drop-down list Export type, select the option Item (new).
In the drop-down list Category, select the option Generic Product.
Click Save (save).
→ The catalogue is created.
→ The catalogue is opened for editing.
On the left-hand side of the menu, click on Settings.
In the Basic settings, select the account that you want to use this catalogue for.
Click Save (save).

Other catalogue settings

Other catalogue settings are optional. Once you carried out the settings described on this page, your catalogue is automatically exported to eMAG. 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 eMAG 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.2. Mapping data fields in the catalogue

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

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

Getting to know the catalogue menu for marketplace formats

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

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

eMAG products: List of recommended data field mappings

Marketplace field	Mandatory?	Recommended PlentyONE mapping
ID	yes	The variation ID is mapped automatically.
Part Number Key	yes	SKU » SKU » [referrer eMAG] » [select account]
Name	yes	Item text » Name 1 or Item text » Name 2 or Item text » Name 3 or Property linked to variation
Part number/manufacturer code	yes	The variation ID is mapped automatically.
Description	no	Item text » Item text, language German or Property of the type Text, language German
Brand	no	Item » Manufacturer name
Weight (g)	no	Variation » Net weight g
URL	no	Variation » Ceres Product URL
EAN	yes	Barcode » [Select barcode of the type GTIN]
Sale price without VAT	yes	Sales price » [Sales price for eMAG]
Recommended price without VAT	no	Sales price » [Sales price of the type RRP]
Min. offer sale price without VAT	yes	Sales price » [Min. offer price for eMAG] The minimum offer price must fulfil the following requirements: It must be lower or equal to the Sale price without VAT. It must be lower than the Max. offer sale price without VAT. The minimum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price. *Note:* Theoretically, you can map the same sales price that you also mapped to the marketplace data field Sale price without VAT. However, by doing this, you will bypass the validation. So you might not notice if your price for a variation is too low.
Max. offer sale price without VAT	yes	Sales price » [Max. offer price for eMAG] The maximum offer price must fulfil the following requirements: It must be equal to or higher than the Sale price without VAT. It must be higher than the Min. offer sale price without VAT. The maximum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price. *Note:* Theoretically, you can map the same sales price that you also mapped to the marketplace data field Sale price without VAT. However, by doing this, you will bypass the validation. So you might not notice if your price for a variation is too high.
Currency type	no	???
Stock	yes	Stock » [Select 1 or more warehouses] *Tip:* Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses.
Warranty	depending on category	Property of the type Whole number, Decimal number or Selection *Tip:* For the variation, save the warranty duration in months.
Start date	no	Variation » Release date or Property of the type Date
VAT rate	yes	Map a PlentyONE VAT rate for each VAT rate of the account. You can map the VAT rates of your country if your products fall into the same VAT class in both the country of the market and in your home country.
Processing time	no	Variation » Availability days or Property of the type Selection, selection values corresponding to the eMAG handling times This is the time until shipping in days. *Important:* If the order is not shipped after the specified number of days has elapsed, the order is cancelled automatically. *Example:* If the handling time is 0, the order is shipped on the day of the order. As such, the order is cancelled if eMAG is not notified of shipping on the same day.

Marketplace field

Mandatory?

Recommended PlentyONE mapping

yes

The variation ID is mapped automatically.

Part Number Key

yes

SKU » SKU » [referrer eMAG] » [select account]

Name

yes

Item text » Name 1

Item text » Name 2

Item text » Name 3

Property linked to variation

Part number/manufacturer code

yes

The variation ID is mapped automatically.

Description

Item text » Item text, language German

Property of the type Text, language German

Brand

Item » Manufacturer name

Weight (g)

Variation » Net weight g

URL

Variation » Ceres Product URL

EAN

yes

Barcode » [Select barcode of the type GTIN]

Sale price without VAT

yes

Sales price » [Sales price for eMAG]

Recommended price without VAT

Sales price » [Sales price of the type RRP]

Min. offer sale price without VAT

yes

Sales price » [Min. offer price for eMAG]

The minimum offer price must fulfil the following requirements:

It must be lower or equal to the Sale price without VAT.
It must be lower than the Max. offer sale price without VAT.

The minimum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price.

Note: Theoretically, you can map the same sales price that you also mapped to the marketplace data field Sale price without VAT. However, by doing this, you will bypass the validation. So you might not notice if your price for a variation is too low.

Max. offer sale price without VAT

yes

Sales price » [Max. offer price for eMAG]

The maximum offer price must fulfil the following requirements:

It must be equal to or higher than the Sale price without VAT.
It must be higher than the Min. offer sale price without VAT.

The maximum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price.

Currency type

???

Stock

yes

Stock » [Select 1 or more warehouses]
Tip: Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses.

Warranty

depending on category

Property of the type Whole number, Decimal number or Selection

Tip: For the variation, save the warranty duration in months.

Start date

Variation » Release date

Property of the type Date

VAT rate

yes

Map a PlentyONE VAT rate for each VAT rate of the account. You can map the VAT rates of your country if your products fall into the same VAT class in both the country of the market and in your home country.

Processing time

Variation » Availability days

Property of the type Selection, selection values corresponding to the eMAG handling times

This is the time until shipping in days.

Important: If the order is not shipped after the specified number of days has elapsed, the order is cancelled automatically.

Example: If the handling time is 0, the order is shipped on the day of the order. As such, the order is cancelled if eMAG is not notified of shipping on the same day.

eMAG offers: list of recommended data field mappings

Marketplace field	Mandatory?	Recommended PlentyONE mapping
ID	yes	The variation ID is mapped automatically.
Name	yes	Item text » Name 1 or Item text » Name 2 or Item text » Name 3 or Property linked to variation
EAN	yes	Barcode » [Select barcode of the type GTIN]
Part number/manufacturer code	yes	The variation ID is mapped automatically.
Sale price without VAT	yes	Sales price » [Sales price for eMAG]
Min. offer sale price without VAT	yes	Sales price » [Min. offer price for eMAG] The minimum offer price must fulfil the following requirements: It must be lower or equal to the Sale price without VAT. It must be lower than the Max. offer sale price without VAT. The minimum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price. *Note:* Theoretically, you can map the same sales price that you also mapped to the marketplace data field Sale price without VAT. However, by doing this, you will bypass the validation. So you might not notice if your price for a variation is too low.
Max. offer sale price without VAT	yes	Sales price » [Max. offer price for eMAG] The maximum offer price must fulfil the following requirements: It must be equal to or higher than the Sale price without VAT. It must be higher than the Min. offer sale price without VAT. The maximum offer price is used to validate the sales price. During export, the Sale price without VAT is checked against the minimum and maximum offer sales prices. If the Sale price without VAT is not within the range resulting from the minimum and maximum offer sales prices, eMAG returns an error to allow you to correct the price. *Note:* Theoretically, you can map the same sales price that you also mapped to the marketplace data field Sale price without VAT. However, by doing this, you will bypass the validation. So you might not notice if your price for a variation is too high.
Currency type	no	If no data field is mapped, the currency of the marketplace is exported.
Stock	yes	Stock » [Select 1 or more warehouses] *Tip:* Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses.
Warranty	no	Property of the type Whole number, Decimal number or Selection *Tip:* For the variation, save the warranty duration in months.
Start date	no	Variation » Release date or Property of the type Date
Status	yes	The status is used to activate or deactivate offers for the marketplace. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. The values are then assigned to a PlentyONE data field. Recommended mapping: Variation » Active *Important:* If an offer with the status 0: Inactive is exported, this offer is deactivated on the marketplace.
VAT	yes	Map a PlentyONE VAT rate for each VAT rate of the account. You can map the VAT rates of your country if your products fall into the same VAT class in both the country of the market and in your home country.
Processing time	no	Variation » Availability days or Property of the type Selection, selection values corresponding to the eMAG handling times This is the time until shipping in days. *Important:* If the order is not shipped after the specified number of days has elapsed, the order is cancelled automatically. *Example:* If the handling time is 0, the order is shipped on the day of the order. As such, the order is cancelled if eMAG is not notified of shipping on the same day.

Marketplace field

Mandatory?

Recommended PlentyONE mapping

yes

The variation ID is mapped automatically.

Name

yes

Item text » Name 1

Item text » Name 2

Item text » Name 3

Property linked to variation

EAN

yes

Barcode » [Select barcode of the type GTIN]

Part number/manufacturer code

yes

The variation ID is mapped automatically.

Sale price without VAT

yes

Sales price » [Sales price for eMAG]

Min. offer sale price without VAT

yes

Sales price » [Min. offer price for eMAG]

The minimum offer price must fulfil the following requirements:

It must be lower or equal to the Sale price without VAT.
It must be lower than the Max. offer sale price without VAT.

Max. offer sale price without VAT

yes

Sales price » [Max. offer price for eMAG]

The maximum offer price must fulfil the following requirements:

It must be equal to or higher than the Sale price without VAT.
It must be higher than the Min. offer sale price without VAT.

Currency type

If no data field is mapped, the currency of the marketplace is exported.

Stock

yes

Stock » [Select 1 or more warehouses]
Tip: Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses.

Warranty

Property of the type Whole number, Decimal number or Selection

Tip: For the variation, save the warranty duration in months.

Start date

Variation » Release date

Property of the type Date

Status

yes

The status is used to activate or deactivate offers for the marketplace. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. The values are then assigned to a PlentyONE data field.
Recommended mapping:

Variation » Active

Important: If an offer with the status 0: Inactive is exported, this offer is deactivated on the marketplace.

VAT

yes

Processing time

Variation » Availability days

Property of the type Selection, selection values corresponding to the eMAG handling times

This is the time until shipping in days.

Important: If the order is not shipped after the specified number of days has elapsed, the order is cancelled automatically.

Example: If the handling time is 0, the order is shipped on the day of the order. As such, the order is cancelled if eMAG is not notified of shipping on the same day.

8.4. Customise item export via filters

The eMAG product catalogues export all items and variations that are enabled for the sales channel eMAG. To avoid that every eMAG product catalogue exports all items and variations enabled for eMAG, you can create tags for each product category. These tags need to be linked to the corresponding items and variations. In the *Data » Catalogues » [Open catalogue] » Filters*menu, you can then add the tags as filters for the respective catalogues.

Apply filters in the catalogue:

Go to Data » Catalogues.
Click on the eMAG catalogue.
→ The catalogue opens.
On the left-hand side of the menu, click Filters.
→ The Filters tab opens.
In the Custom filters section, select the option Has tags from the Select filter drop-down list.
Click ADD FILTER.
→ The filter is added.
For the Has tags filter, select the tag from the drop-down list for which the catalogue should filter.
Click Save (save).

8.5. Activating the catalogue export

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

Activating the catalogue export to eMAG:

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

In the menu Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange you can manually import and export data. This menu is mainly meant to test the export. For example, you can only export specific item and offer data or only import individual orders to PlentyONE. This can be helpful if you want to test the export or if you have to import missing orders.

9.1. Manually exporting item data

In the Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export menu, you can export individual items to eMAG. For example, this can be helpful if you want to test the export to eMAG or if you only want to export individual items. In addition, you can have the status of your product documentation checked here and you can retrieve variation IDs and eMAG product IDs.

9.1.1. Manually exporting items

Manually exporting an item:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export.
In the Item export section, select the Account from the drop-down list.
Select a catalogue from the drop-down list.
Enter one or more Variation IDs separated by comma. These variations will be exported to eMAG.
Click upload EXPORT.
Tip: Click PREVIEW to generate a preview of the export.

9.1.2. Manually executing a generic item export

Products without a specific category and in a language other than Romanian, Hungarian or Bulgarian are exported using the generic item export. The items exported via the generic item export are translated by eMAG in a semi-automated process and assigned to a corresponding category.
In the Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export menu, you can export individual items to eMAG via the generic item export. To do so, enter the variation IDs of the variations that you want to export.

Manually exporting items via the generic item export:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export.
In the Generic item export section, select the Account from the drop-down list.
Select a catalogue from the drop-down list.
Enter one or more Variation IDs separated by comma. These variations will be exported to eMAG.
Click upload EXPORT.

9.1.3. Checking the product documentation

In the Product documentation check section, you can have your items checked by eMAG. eMAG will check the items and either approve or reject the product documentation. If an item is rejected, the errors will be shown here and you can adjust the item.

Checking the product documentation status:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export.
In the section Product documentation check, select the Account from the drop-down list.
Enter a variation ID.
Click CHECK.
→ The product documentation for this variation is checked. If the variation is rejected, the errors will be shown here and you can adjust the variation.

9.1.4. Retrieving variation IDs

In the Get variations IDs by eMAG products IDs section, you can enter the eMAG product IDs of your items to retrieve the variation IDs of those items in PlentyONE. This function can be useful if you already listed items on eMAG before using PlentyONE.

Retrieving variation IDs via eMAG product IDs:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export.
In the Get variations IDs by eMAG products IDs section, select the Account from the drop-down list.
Enter one or more eMAG product IDs separated by comma.
Click CHECK.
→ The variation IDs for those eMAG product IDs are displayed.

9.1.5. Retrieving eMAG product IDs

In the Get eMAG products IDs by variations IDs section, you can enter the variation IDs of your items to retrieve the eMAG product IDs of those items. This function can be useful if you already listed items on eMAG before setting up the eMAG interface in PlentyONE.

Retrieving eMAG product IDs via variation IDs:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Item export.
In the Get eMAG products IDs by variations IDs section, select the Account from the drop-down list.
Enter one or more variation IDs separated by comma.
Click CHECK.
→ The eMAG product IDs for those variation IDs are displayed.

9.2. Manually exporting offers

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

Manually exporting offers:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Offer update.
Select the Account from the drop-down list.
Select a catalogue from the drop-down list.
Enter one or more Variation IDs separated by comma. The offers for these variations will be exported to eMAG.
Click upload EXPORT.
Tip: Click PREVIEW to generate a preview of the export.

9.3. Manually importing orders

In the Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Order import menu, you can manually import individual orders into PlentyONE.

Manually importing orders:

Go to Sales Channels » Channel Control Centre » [Open sales channel for eMAG] » Settings » Data exchange » Order import.
Select the Account from the drop-down list.
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 download IMPORT.
→ The orders are imported into PlentyONE.

10. Managing listings

You create and manage offers for eMAG via listings. You can access the product and offer listings for eMAG by navigating to Sales Channels » Channel Control Centre » [Open eMAG 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 4 offers an overview of the single listing view of offer listings.

Table 4. 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 5 offers an overview of the group view of offer listings.

Table 5. 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 eMAG as listings. Carry out the following steps to create listings for eMAG.

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 eMAG.
→ The Settings menu opens.
Open the menu format_list_bulleted Product listings.
Click on Create products.
→ The view Create products opens.
Select the platform eMAG.
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 eMAG 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 eMAG 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 eMAG.
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 eMAG].
→ 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 eMAG].
→ 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 eMAG.
→ 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 eMAG.
Select the template for the catalogue.
Tip: Only templates that are available for the platform eMAG 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 eMAG 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 eMAG 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 eMAG.
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 eMAG].
→ 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 eMAG].
→ 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 6 contains an overview of listing errors.

Table 6. 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. Automating order processing

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

Automatically inform eMAG that the items have been shipped. (How?)
Automatically send invoice notifications to eMAG. (How?)
Automatically inform eMAG that a cancellation request has been accepted. (How?)
Automatically inform eMAG that a return request has been accepted. (How?)
Automatically inform eMAG that a return request has been rejected. (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.

11.1. Sending shipping confirmations to eMAG

Create an event-based flow to automatically inform eMAG 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 7.
    Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.
  3. Save () the settings.
    → The flow is created.
    → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
    Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.
Configure the new flow according to Table 7.
Save () the settings.

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

Table 7. Event-based flow for sending shipping confirmations to eMAG

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 type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

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

Actions

Plugin (Legacy) > Emag

eMAG: Send fulfillment notification to eMAG

11.2. Sending invoice notifications to eMAG

Create an event-based flow to notify eMAG that an invoice has been created for 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 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 send invoice notifications to eMAG

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Document > Document created

Select a document type, for example:

Invoice

Controls

Branch

Object type: Order
Filter settings for the branch:
Note: If 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)

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

Actions

Plugin (Legacy) > Emag

eMAG: Send invoice notification to eMAG

11.3. Reporting the acceptance of a cancellation request to eMAG

Create an event-based flow to automatically inform eMAG when you have accepted a cancellation request. Note that orders marked as shipped can no longer be cancelled.

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 the acceptance of a cancellation request to eMAG

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)

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

Actions

Plugin (Legacy) > Emag

eMAG: Send Cancel request accepted to eMAG

11.4. Reporting the acceptance of a return request to eMAG

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

Creating an event-based flow

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

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

Table 10. Event-based flow to report the acceptance of a return request to eMAG

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select an order status, for example:

[9] Return

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)

Return

Order > Order referrer

Is in (IN)

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

Actions

Plugin (Legacy) > Emag

eMAG: Send Return request accepted to eMAG

11.5. Reporting the rejection of a return request to eMAG

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

Creating an event-based flow

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

Setting

Option

Selection

Trigger selection

Select a trigger, for example:

Order > Order status changed

Select a suitable order status. For example, you can create a new status for rejected return requests.

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)

Return

Order > Order referrer

Is in (IN)

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

Actions

Plugin (Legacy) > Emag

eMAG: Send Return request rejected to eMAG

12. Troubleshooting

12.1. Check list: Variation export

To export a variation to eMAG, this variation has to meet the following requirements:

Is the order referrer active?

Go to Setup » Orders » Order referrer.
Is the option eMAG or one of the sub-referrers active?
If necessary, activate this order referrer.
Click Save (save).

Have you enabled the variation for the sales channel?

The variation must be enabled for the sales channel.

Go to Item » Items » [Open variation].
Switch to the Sales channels tab.
In the section Sales channels, select the option eMAG (check_box).
Activate the toggle button Activate sales channel (toggle_on).
Confirm the pop-up by clicking ACTIVATE.
Click Save (save).
→ The variation is available for eMAG.

Have you activated the variation?

Go to Item » Items » [Open variation].
In the Availability and visibility section of the General tab, activate the option Active.
Click Save (save).

Does the variation have positive net stock?

Go to Item » Items » [Open variation].
Switch to the Stock tab.
Expand the Stock (arrow_forward_ios) section.
→ The net stock per warehouse is shown in the Net stock column.

Are the sales price and price settings correct?

Check the sales price:

Go to Setup » Item » Sales prices.
For the filter Referrer, select eMAG.
Click Search (search).
→ The sales price that is active for the referrer is shown.
Check the settings of the sales price.
Make any necessary corrections.

Check the price:

Go to Item » Items » [Open variation].
→ The sales prices are listed in the tab Pricing.
Check the following settings:
- Is the sales price for the referrer linked?
- Does the price for the referrer have the correct price?
Make any necessary corrections.

Does the variation have at least one image?

Go to Item » Items » [Open variation].
Switch to the Images tab.
Check if at least one image is linked to the variation.

Is each mandatory field for eMAG mapped to a PlentyONE data field?

At the least the mandatory fields for the sales channel have to be mapped to PlentyONE data fields. These mandatory fields are different for different product categories. In the catalogue, mandatory fields are marked with an asterisk.

Is the catalogue active?

The catalogue that the variation is associated with must be activated.

Go to Data » Catalogues.
→ The catalogues are listed.
Scroll to the eMAG catalogue.
In the column Active, activate the toggle (toggle_on).

Couldn’t find any errors?

You have confirmed that the above settings are correct but the variation is still not exported? Then check the data log.

Go to Data » Log.
Use the following filters:
- Integration = eMAG
Click Search (search).
Check all entries for the levels warning and error.
Open the logs containing the message Variation invalid.
→ The the variation ID and the reason for the rejection or the missing characteristic are shown.
Correct the variation data.

eMAG (Setup via Channel Control Centre)

1. Registering with eMAG

2. Frequency of data exchange

3. Products vs. Offers

4. Workflow of the item data export

5. Workflow of an order

6. Setting up eMAG in PlentyONE

6.1. Sales channel overview

6.2. Adding the sales channel

6.3. Carrying out the basic settings for eMAG

6.4. Adjusting the general settings

6.5. Activating the order referrer

6.6. Defining a sales price

7. Preparing variations

7.1. Setting the variation availability

7.2. Link sales price and save price

8. Setting up the item export

8.1. Creating a catalogue

Other catalogue settings

8.2. Mapping data fields in the catalogue

8.3. Recommendations for data field mappings

8.4. Customise item export via filters

8.5. Activating the catalogue export

9. Manually managing the data exchange

9.1. Manually exporting item data

9.1.1. Manually exporting items

9.1.2. Manually executing a generic item export

9.1.3. Checking the product documentation

9.1.4. Retrieving variation IDs

9.1.5. Retrieving eMAG product IDs

9.2. Manually exporting offers

9.3. Manually importing orders

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. Automating order processing

11.1. Sending shipping confirmations to eMAG

11.2. Sending invoice notifications to eMAG

11.3. Reporting the acceptance of a cancellation request to eMAG

11.4. Reporting the acceptance of a return request to eMAG

11.5. Reporting the rejection of a return request to eMAG

12. Troubleshooting

12.1. Check list: Variation export

Is this page helpful?

Is this page helpful?