eMAG (Setup via Setup » Markets)

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

Setup » Markets

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

1. Registering with eMAG

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

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

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

4. 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 or event procedure.

5. Setting up eMAG in PlentyONE

Now set up the sales channel in PlentyONE.

5.1. Account overview

The Setup » Markets » eMAG » Settings menu provides an overview of your eMAG accounts. Table 1 lists the columns and available actions in the account overview.

Configuring columns

Click Configure columns (settings) to define which settings should be displayed in the account overview.
The columns ID, Active, Client, Marketplace, Item export, Order import, and Offer update are displayed in the overview by default.

Note: The account overview looks different depending on which columns you add or hide via Configure columns (settings). The following table only lists the columns which are displayed in the overview by default.

Table 1. eMAG account overview
Column Explanation

ID

The ID of your eMAG account. The ID is assigned automatically when you create a new account.

Active

circle = The account is active and data is exchanged with eMAG.
circle = The account is not active. Data is not exchanged with eMAG.

Client

The client (plentyShop) that orders of this eMAG account are assigned to.

Marketplace

The marketplace your eMAG account is assigned to. The following marketplaces are available:

  • Romania

  • Bulgaria

  • Hungary

Item export

done = The item export for this account is active. Items are exported to eMAG once per day.

close = Items are not exported.

Order import

done = The order import for this account is active. Orders are imported into PlentyONE every 15 minutes.

close = Orders are not imported.

Offer update

done = The offer export for this account is active. A full offer export is carried out once per day. This means that new offers are created and existing offers are updated.
Stock and prices are updated every 15 minutes.

close = Offers are not exported.

5.2. Carrying out the basic settings

Carry out the basic settings for the market in the Setup » Markets » eMAG » Settings menu.

First, add a new account for eMAG.

Adding a new account:

  1. Go to Setup » Markets » eMAG » Settings.

  2. Click Add account (add).
    → The Add account window opens.

  3. From the Marketplace drop-down list, select the desired marketplace.

  4. From the Client drop-down list, select the desired client.

  5. Click SAVE (save).
    → A view with account settings opens.

  6. Carry out the additional settings. Pay attention to the explanations given in Table 2.

  7. Click Save (save).

Table 2. Settings for the market eMAG
Setting Explanation

CONNECT (link)

Click here to connect to eMAG. Enter your user name and password and save (save) the settings.

General

Active

Activate the eMAG account (toggle_on). 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.

Item

Item export

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

Shipping service providers

Map 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

Order import

Activate (toggle_on) 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 (toggle_on) 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 (today).
Only offers starting from this date will be updated on eMAG.

5.3. Activating the order referrer

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

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:

  1. Go to Setup » Orders » Order referrer.

  2. Click Search (search).

  3. In the list, navigate to the option eMAG or one of the sub-referrers.

  4. On the right of the referrer’s line, click Edit (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.

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

  6. Click SAVE (save).
    → The referrer is active.

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

  1. Go to Setup » Item » Sales prices » [Open sales price].
    Tip: No sales prices? Then create a sales price first.

  2. Activate the referrer eMAG.

  3. Save () the settings.

5.5. Frequency of data exchange

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

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

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

6. Preparing variations

Now, prepare your variations for the export.

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

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

  2. In the Availability and visibility section, enable the option Active (toggle_on).

  3. Click the Sales channels tab.

  4. In the Sales channels section, activate the sales channel eMAG in the Status column (toggle_on).
    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 (toggle_on). Click ACTIVATE to confirm the activation.

  5. Save (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:

  1. Go to Item » Items.

  2. Set search filters as needed and start the search.

  3. Select () the variations to be edited.

  4. In the toolbar, click on layers » layers Variation group function.
    → The Variation group function window opens.

  5. Select the action Sales channels from the drop-down list Actions.
    → The action is added to the lower part of the window.

  6. Select (check_box) the option eMAG from the drop-down list Sales channels.
    → The sales channel is added below the drop-down list Sales channels.

  7. Activate (toggle_on) the toggles to the left of the sales channels.

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

  1. Navigate to the area Market availability.

  2. Activate the checkbox to the left of the option eMAG.

  3. Activate the checkbox to the right of the option eMAG.

  4. Navigate to the area Availability.

  5. Activate the checkbox to the left of the option Active.

  6. Activate the checkbox to the right of the option Active.

  7. Click on Apply to apply the settings to the variations.

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

  1. Go to Item » Items » [Open variation].

  2. Click the Pricing tab.

  3. In the Sales prices section, click More (more_vert) and then Add sales prices (add).

  4. Select the sales price for eMAG from the drop-down list on the left.

  5. Click APPLY.
    → The sales price is added and displayed in the list.

  6. Enter the monetary price into the Price field.

  7. Click Save (save).

7. Setting up the item export

Item data is exported to eMAG via catalogues.

7.1. Creating a catalogue

To export your items to eMAG, create catalogues in the Data » Catalogue menu. 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.

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.

  • 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 format for this export type. All offers are therefore exported with only one catalogue.

Creating a catalogue:

  1. Go to Data » Catalogues.

  2. Click Create catalogue (add).

  3. Enter a name for the catalogue.

  4. In the drop-down list Export type, select the option eMAG Offers.

  5. In the drop-down list Format type, select the option Item (new).

  6. From the drop-down list Format, select the option Offers.

  7. Click Save (save).
    → The catalogue is created.
    → The catalogue is opened for editing.

  8. On the left-hand side of the menu, click settings Settings.

  9. In the Basic settings, select the account that you want to use this catalogue for.

  10. Click Save (save).

Products are exported using the export type eMAG Products. As the catgory, 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:

  1. Go to Data » Catalogues.

  2. Click Create catalogue (add).

  3. Enter a name for the catalogue.

  4. In the drop-down list Export type, select the option eMAG Products.

  5. In the drop-down list Format type, select the option Item (new).

  6. In the drop-down list Format, select a category of the marketplace.
    Important: eMAG has to activate you for each category in which you want to sell your items.

  7. Click Save (save).
    → The catalogue is created.
    → The catalogue is opened for editing.

  8. On the left-hand side of the menu, click settings Settings.

  9. In the Basic settings, select the account that you want to use this catalogue for.

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

  1. Go to Data » Catalogues.

  2. Click Create catalogue (add).

  3. Enter a name for the catalogue.

  4. In the drop-down list Export type, select the option eMAG Generic Products.

  5. In the drop-down list Format type, select the option Item (new).

  6. In the drop-down list Format, select the option Generic Product.

  7. Click Save (save).
    → The catalogue is created.
    → The catalogue is opened for editing.

  8. On the left-hand side of the menu, click settings Settings.

  9. In the Basic settings, select the account that you want to use this catalogue for.

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

7.2. Mapping data fields in the catalogue

After you have created a catalogue, map the market’s data fields to item data saved in PlentyONE. Check the documentation of the sales channel to find out what data the market 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
catalogue menu colours
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.

Live preview

You can use the Live preview feature to display which values of a given variation would be exported to the marketplace by each mapping. Simply activate the toggle and enter the ID of the variation you want to use in order to show live previews for that variation.
Important: Live preview is only available for catalogues that also support the Preview (preview) function.

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

PlentyONE data sources

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

Mapping catalogue fields:

  1. Go to Data » Catalogues.

  2. Click on the catalogue.
    → The Mapping tab opens.
    → In the left-hand column, the market’s data fields are listed.
    Tip: Mandatory fields are flagged with an asterisk (*).
    → In the right-hand column, you can map your PlentyONE data sources. Any PlentyONE data sources that you already mapped are also shown in this column.

  3. Map suitable PlentyONE data sources 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 sources

    • 1:n mapping

    • Own value mapping

    • Mapping with mathematical calculations

  4. Save () the catalogue.
    → The mappings are saved.

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

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

As such, simple 1:1 mappings are useful if you want to achieve the following:

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

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. Select a PlentyONE data source in the list.
    → The data source is added to the right, but not yet confirmed or saved.

  3. Click on Confirm.

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

In a simple 1:1 mapping, you map a PlentyONE data source to the marketplace data field. But PlentyONE does not always offer a suitable data source. In such cases you can create the data source in your system yourself by setting up a property. Properties allow you to save any kind of information in your properties.

Creating a simple 1:1 mapping with properties:

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. Expand the group Property.
    → The property groups are shown.

  3. Expand the group you need.

  4. Click on the Plus sign on the right of the property you want. → The property is added as a data source, but not yet confirmed or saved.

  5. From the drop-down list Language, select the language in which you send the data to the market.

  6. Click on Confirm.
    → The property is mapped to the marketplace data field.

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

Complex mappings are necessary whenever a marketplace data field only has a select number of possible values. Like the name implies, they cannot be resolved by simply mapping the whole data field to one of your PlentyONE data sources. Instead, you map the individual values that can be entered in the data field to PlentyONE data sources.
For example, a marketplace may only allow for the color of an item to be described using a limited selection of terms such as "Blue", while the variations saved in your system may use more distinct terms such as "Sky blue" or "Royal blue". In such cases the marketplace data field for item colors will be a complex mapping that allows you to map the colors "Sky blue" and "Royal blue" saved in your variations to the value "Blue" used by the marketplace.

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.

A complex mapping will always export the value selected for the marketplace data field, regardless of what kind of data source you mapped it to. The only exception are own values, which will be exported as-is.

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.

catalogue complex mappings

Examples for complex 1:1 mappings are:

  • Categories

  • Brands

  • Shipping settings

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

Creating a complex 1:1:n mapping:

  1. Click on the field for the marketplace data field.
    → A list of the available values is shown.

  2. Select the value that you want to map a PlentyONE data source to.
    → The value is added as a mappable field.

  3. Next to the added field, click on + Add data source.
    → To the left, the available PlentyONE data sources are listed in groups.

  4. Select the PlentyONE data source you want to map tho the marketplace value.
    Important: Do not map own values or properties of the type None.

  5. Your next steps depend on the PlentyONE data source 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 source 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 source.

      • Click on Confirm.

    • Alternative 3: The PlentyONE data source 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 source.
        Exception: If you map an own value to a marketplace data field, the own value that you enter is exported directly.

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

You can use fallback data sources in a 1:1 mapping to ensure that a value is provided for a marketplace data field even when the preferred data source is missing or empty.

In other words, this mapping specifies:

  • I want to fill the marketplace data field with the data from the selected primary PlentyONE data source.

  • If that data source is missing or empty for a variation, then the first fallback data source for this field is checked. If this fallback data source contains usable data, then that data is used to fill the marketplace data field.

  • If the first fallback data source is also missing or empty and other fallback data sources are mapped to this data field, then this process is repeated for the other fallback data sources in sequence until either usable data is found or all fallback data sources have been checked.

Two separate fallback conditions are available:

Null (default)

The fallback data source 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 sources for the following types of PlentyONE data sources:

  • SKU

  • Barcodes

  • Sales prices

  • Properties

Empty

The fallback data source 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 sources for the following type of PlentyONE data sources:

  • PlentyONE data sources that are available for variations by default

Important: When you add a fallback data source, the fallback condition "Null" is selected automatically. To apply the fallback condition "Empty", you need to change the default setting.

Note: If you assign multiple fallback data sources to a single data field, the value of only one of those fallback data sources is exported, i.e. the first mapped fallback data source that provides a usable value.

Creating a 1:1 mapping with fallback data sources:

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. Click on the plus to the right of the PlentyONE data source you want to use as the primary data source.
    → The PlentyONE data source is added to the right.

  3. Click on + Add fallback data source below the primary data source.
    → The fallback data source is added with the fallback condition Null.

  4. (Optional) If you want to use the fallback condition Empty instead:

    1. Hover over the fallback data source with your cursor and click on the Settings () option that appears to the right.
      → The window Data column settings is shown.

    2. For the setting Fallback condition, select the option Empty.

    3. Click on Save.
      → The fallback data source’s fallback condition is changed to Empty.

  5. Click on Confirm.
    → The fallback data source is exported if the fallback condition is fulfilled.

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

In a 1:n mapping, you map several PlentyONE data sources to the same marketplace data field. Unlike fallback data sources, these data sources are combined using a specified separator and used as a single value.

In other words, this mapping specifies:

  • I want to combine these PlentyONE data sources 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:

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. Click on the plus to the right of the PlentyONE data source you want to select.
    → The PlentyONE data source is added to the right.

  3. Click on Confirm.

  4. To the right of the mapped PlentyONE data source, click on Add data source ().
    → To the left, the list of available PlentyONE data sources again are shown in groups.

  5. Map the desired number of additional PlentyONE data sources to the marketplace data field as described above.

  6. Click on Confirm.

  7. To the very right of the row, click on Settings ().

  8. Select a separator from the drop-down list Separator or add a custom separator.

  9. Click on Save.

  10. Save () the catalogue.
    → The mappings are saved.
    → During the export, the content of the PlentyONE data sources is combined and exported as one field.

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

If you want to export the exact same value for all of your variations to a particular marketplace data field, then you can map this value to the data field using the Own value data source.

This kind of mapping specifies:

  • For this marketplace data field, I want to export the value that I entered in the data source Own value for all variations of this catalogue.

Creating an own value mapping:

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. Select the Own value option at the top of the list.
    → The data source Own value is mapped to the data field.

  3. Enter a value into the input field in the Own value.

  4. Click on Confirm.
    → The entered value is exported for all variations.

Be especially careful when using Own value mappings

The value you enter in an Own value mapping is always exported for every variation tied to the catalogue. The value also overwrites the market value in complex mappings where usually the value of the market would be exported. As such, only use an Own value mapping for a marketplace data field when you are certain that the value you entered will be accepted for that data field by the marketplace for all of your variations in order to ensure that your variations are exported to the marketplace successfully.
Mapping with mathematical formulas: 1 Marketplace data field, the PlentyONE value is recalculated using the formula during export

Mathematical formulas allow you to change numerical values automatically during the export. In other words, this mapping specifies:

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

Recalculating numerical values:

  1. Next to the marketplace data field, click on + Add data source.
    → To the left, the list of available PlentyONE data sources are shown in groups.

  2. At the very top of the list, click on the + icon next to Formula (calculate).
    → The data field Formula is added to the field on the right.

  3. Click into the data field.
    → The window Modify value is shown.

  4. Enter a numerical value or select a PlentyONE data source at the bottom right of the window to add it to the calculation (add).
    Tip: Use the search function. This helps you to find data fields quickly.

  5. Optional: If the symbol more_vert is shown in the data field, select the correct assignment for the data field.
    Tip: A number tells you how many assignments are necessary for the data field.

    1. Click on the icon more_vert.

    2. In the window shown, select the assignments from the drop-down list.

    3. Save the settings.

  6. Enter numbers and mathematical operators with the on-screen calculator or the keyboard.

  7. Save the settings.
    → The entered formula is displayed in the overview.
    → When an export is carried out, the formula is used to calculate the value that is exported for each variation.

Keep in mind that this mapping type only works with PlentyONE data sources that provide numerical values and for marketplace data fields that accept numerical values. Additionally, this mapping type is relatively new and not available for all catalogue formats yet.

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
eMAG offers: list of recommended data field mappings

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

  1. Go to Data » Catalogues.

  2. Click on the catalogue.
    → The catalogue opens.

  3. On the left-hand side of the menu, click filter_alt Filters.
    → The Filters tab opens.

  4. In the Custom filters section, select the option Has tags from the Select filter drop-down list.

  5. Click add ADD FILTER.
    → The filter is added.

  6. For the Has tags filter, select the tag from the drop-down list for which the catalogue should filter.

  7. Click Save (save).

7.5. Activating the catalogue

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:

  1. Go to Data » Catalogues.
    → The catalogues are listed.

  2. Scroll to the eMAG catalogue.

  3. In the Active column, move the toggle button to the right (toggle_on).
    → 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 Setup » Markets » eMAG » Data exchange you can import and export data manually. This menu is mainly meant to test the export. For example, you can only export specific item and offer data or only import individual orders to PlentyONE. This can be helpful if you want to test the export or if you have to import missing orders.

8.1. Manually exporting item data

In the Setup » Markets » eMAG » 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.

8.1.1. Manually exporting items

Manually exporting an item:

  1. Go to Setup » Markets » eMAG » Data exchange » Item export.

  2. In the Item export section, select the Account from the drop-down list.

  3. Select a Catalogue from the drop-down list.

  4. Enter one or more Variation IDs separated by comma. These variations will be exported to eMAG.

  5. Click upload EXPORT.
    Tip: Click Preview to generate a preview of the export.

8.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 Setup » Markets » eMAG » Data exchange » Item export menu, you can export individual items 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:

  1. Go to Setup » Markets » eMAG » Data exchange » Item export.

  2. In the Generic item export section, select the Account from the drop-down list.

  3. Select a Catalogue from the drop-down list.

  4. Enter one or more variation IDs separated by comma. These variations will be exported to eMAG.

  5. Click upload EXPORT.

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

  1. Go to Setup » Markets » eMAG » Data exchange » Item export.

  2. In the section Product documentation check, select the Account from the drop-down list.

  3. Enter a variation ID.

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

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

  1. Go to Setup » Markets » eMAG » Data exchange » Item export.

  2. In the Get variations IDs by eMAG products IDs section, select the Account from the drop-down list.

  3. Enter one or more eMAG product IDs separated by comma.

  4. Click Check.
    → The variation IDs for those eMAG product IDs are displayed.

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

  1. Go to Setup » Markets » eMAG » Data exchange » Item export.

  2. In the Get eMAG products IDs by variations IDs section, select the Account from the drop-down list.

  3. Enter one or more variation IDs separated by comma.

  4. Click Check.
    → The eMAG product IDs for those variation IDs are displayed.

8.2. Manually exporting offers

In the Setup » Markets » eMAG » 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:

  1. Go to Setup » Markets » eMAG » Data exchange » Offer update.

  2. Select the Account from the drop-down list.

  3. Select a Catalogue from the drop-down list.

  4. Enter one or more Variation IDs separated by comma. The offers for these variations will be exported to eMAG.

  5. Click upload EXPORT.
    Tip: Click Preview to generate a preview of the export.

8.3. Manually importing orders

In the Setup » Markets » eMAG » Data exchange » Order import menu, you can manually import individual orders into PlentyONE.

Manually importing orders

  1. Go to Setup » Markets » eMAG » Data exchange » Order import.

  2. Select the Account from the drop-down list.

  3. Enter one or more order IDs into the input field Order IDs. Separate the IDs by comma if you enter more than one ID.

  4. Click download IMPORT.
    → The orders are imported into PlentyONE.

9. Automating order processing

You can automatically inform eMAG about changes to the order status by using one of the following options:

  • Option 1: PlentyONE Flow (recommended)

  • Option 2: Event procedures (old method)

9.1. Option 1: PlentyONE Flow (recommended)

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.

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → A stepper opens and guides you through the following three steps.

    1. General

      1. Enter a unique name and, if necessary, a description for the new flow.

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

      1. If desired, select a UI from the optional drop-down list Flow available in.
        → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
        Note: UIs currently selectable: Order UI.

      2. From the drop-down list Trigger selection, select the event according to Table 4.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

      3. Save () the settings.
        → The flow is created.
        → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
        Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.

  3. Configure the new flow according to Table 4.

  4. Save () the settings.

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

Table 4. Event-based flow for sending shipping confirmations to eMAG
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order status changed

or

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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → A stepper opens and guides you through the following three steps.

    1. General

      1. Enter a unique name and, if necessary, a description for the new flow.

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

      1. If desired, select a UI from the optional drop-down list Flow available in.
        → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
        Note: UIs currently selectable: Order UI.

      2. From the drop-down list Trigger selection, select the event according to Table 5.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

      3. Save () the settings.
        → The flow is created.
        → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
        Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.

  3. Configure the new flow according to Table 5.

  4. Save () the settings.

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

Table 5. 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 (playlist_add). 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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → A stepper opens and guides you through the following three steps.

    1. General

      1. Enter a unique name and, if necessary, a description for the new flow.

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

      1. If desired, select a UI from the optional drop-down list Flow available in.
        → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
        Note: UIs currently selectable: Order UI.

      2. From the drop-down list Trigger selection, select the event according to Table 6.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

      3. Save () the settings.
        → The flow is created.
        → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
        Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.

  3. Configure the new flow according to Table 6.

  4. Save () the settings.

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

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

or

  • [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 (playlist_add). 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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → A stepper opens and guides you through the following three steps.

    1. General

      1. Enter a unique name and, if necessary, a description for the new flow.

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

      1. If desired, select a UI from the optional drop-down list Flow available in.
        → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
        Note: UIs currently selectable: Order UI.

      2. From the drop-down list Trigger selection, select the event according to Table 7.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

      3. Save () the settings.
        → The flow is created.
        → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
        Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.

  3. Configure the new flow according to Table 7.

  4. Save () the settings.

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

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

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

  1. Go to Automation » Flow Studio.

  2. Click Create flow (add).
    → A stepper opens and guides you through the following three steps.

    1. General

      1. Enter a unique name and, if necessary, a description for the new flow.

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

      1. If desired, select a UI from the optional drop-down list Flow available in.
        → The option to manually trigger the flow directly from the selected UI is added to the group functions in that UI.
        Note: UIs currently selectable: Order UI.

      2. From the drop-down list Trigger selection, select the event according to Table 8.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

      3. Save () the settings.
        → The flow is created.
        → The Flow Studio Canvas appears, on which two elements are already displayed: The trigger type and the placeholder for the next step.
        Note: With some event-based flows you cannot save the flow if it consists of only a trigger. In such cases, you need to add at least one further step.

  3. Configure the new flow according to Table 8.

  4. Save () the settings.

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

Table 8. 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 (playlist_add). 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

9.2. Option 2: Event procedures (old method)

Set up event procedures to automatically inform eMAG about changes to the order status. The following event procedures are available for eMAG:

  • 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?)

9.2.1. Sending shipping confirmations to eMAG

Set up an event procedure to automatically send shipping confirmations to eMAG when the outgoing items are booked.

When you start the eMAG integration and want to send the package number to eMAG via our event procedure, you need to request activation of the EXTERNAL AWB service from eMAG beforehand.

Note: Without activating the EXTERNAL AWB service, you will not receive the package number sent by PlentyONE. This will cause an error in the PlentyONE logs.

You can request activation of the EXTERNAL AWB service by eMAG when creating your eMAG account.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure ().
    → The Create new event procedure window opens.

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 9.

  5. Save () the settings.

  6. Carry out the additional settings according to Table 9.

  7. Select the setting Active ().

  8. Save () the settings.

Table 9. Event procedure for sending shipping confirmations to eMAG
Setting Option Selection

Event

Order change: Outgoing items booked

Filter 1

Order > Order type

Order

Filter 2

Order > Referrer

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

Procedure

Plugins

eMAG: Send fulfilment notification to eMAG

9.2.2. Sending invoice notifications to eMAG

Set up an event procedure to notify eMAG that an invoice has been created for an order.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure ().
    → The Create new event procedure window opens.

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 10.

  5. Save () the settings.

  6. Carry out the additional settings according to Table 10.

  7. Select the setting Active ().

  8. Save () the settings.

Table 10. Event procedure to send invoice notifications to eMAG
Setting Option Selection

Event

Select an event, for example:

  • Documents: Invoice generated

Filter 1

Order > Order type

Order

Filter 2

Order > Referrer

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

Procedure

Plugins

eMAG: Send invoice notification to eMAG

9.2.3. Reporting the acceptance of a cancellation request to eMAG

Set up an event procedure to automatically inform eMAG when you have accepted a cancellation request. Note that orders marked as shipped can no longer be cancelled.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure ().
    → The Create new event procedure window opens.

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 11.

  5. Save () the settings.

  6. Carry out the additional settings according to Table 11.

  7. Select the setting Active ().

  8. Save () the settings.

Table 11. Event procedure to report the acceptance of a cancellation request to eMAG
Setting Option Selection

Event

Select an event, for example:

  • Order change: Status change

Select a status, for example:

  • [8] Cancelled

or

  • [8.1] Cancelled by customer

Filter

Order > Referrer

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

Procedure

Plugins

eMAG: Send Cancel request accepted to eMAG

9.2.4. Reporting the acceptance of a return request to eMAG

Set up an event procedure to automatically inform eMAG when you have accepted a return request.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure ().
    → The Create new event procedure window opens.

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 12.

  5. Save () the settings.

  6. Carry out the additional settings according to Table 12.

  7. Select the setting Active ().

  8. Save () the settings.

Table 12. Event procedure to report the acceptance of a return request to eMAG
Setting Option Selection

Event

Select an event, for example:

  • Order change: Status change

Select a status, for example:

  • [9] Return

Filter 1

Order > Order type

Return

Filter 2

Order > Referrer

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

Procedure

Plugins

eMAG: Send Return request accepted to eMAG

9.2.5. Reporting the rejection of a return request to eMAG

Set up an event procedure to automatically inform eMAG when you have rejected a return request.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

  2. Click on Add event procedure ().
    → The Create new event procedure window opens.

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 13.

  5. Save () the settings.

  6. Carry out the additional settings according to Table 13.

  7. Select the setting Active ().

  8. Save () the settings.

Table 13. Event procedure to report the rejection of a return request to eMAG
Setting Option Selection

Event

Select an event, for example:

  • Order change: Status change

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

Filter 1

Order > Order type

Return

Filter 2

Order > Referrer

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

Procedure

Plugins

eMAG: Send Return request rejected to eMAG

10. Troubleshooting

10.1. Check list: Variation export

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

Is the order referrer active?

  1. Go to Setup » Orders » Order referrer.

  2. Is the option eMAG or one of the sub-referrers active?

  3. If necessary, activate this order referrer.

  4. Click Save (save).

Have you enabled the variation for the sales channel?

The variation must be enabled for the sales channel.

  1. Go to Item » Items » [Open variation].

  2. Switch to the Sales channels tab.

  3. In the section Sales channels, select the option eMAG (check_box).

  4. Activate the toggle button Activate sales channel (toggle_on).

  5. Confirm the pop-up by clicking ACTIVATE.

  6. Click Save (save).
    → The variation is available for eMAG.

Have you activated the variation?

  1. Go to Item » Items » [Open variation].

  2. In the Availability and visibility section of the General tab, activate the option Active.

  3. Click Save (save).

Does the variation have positive net stock?

  1. Go to Item » Items » [Open variation].

  2. Switch to the Stock tab.

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

  1. Go to Setup » Item » Sales prices.

  2. For the filter Referrer, select eMAG.

  3. Click Search (search).
    → The sales price that is active for the referrer is shown.

  4. Check the settings of the sales price.

  5. Make any necessary corrections.

Check the price:

  1. Go to Item » Items » [Open variation].
    → The sales prices are listed in the tab Pricing.

  2. Check the following settings:

    • Is the sales price for the referrer linked?

    • Does the price for the referrer have the correct price?

  3. Make any necessary corrections.

Does the variation have at least one image?

  1. Go to Item » Items » [Open variation].

  2. Switch to the Images tab.

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

  1. Go to Data » Catalogues.
    → The catalogues are listed.

  2. Scroll to the eMAG catalogue.

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

  1. Go to Data » Log.

  2. Use the following filters:

    • Integration = eMAG

  3. Click Search (search).

  4. Check all entries for the levels warning and error.

  5. Open the logs containing the message Variation invalid.
    → The the variation ID and the reason for the rejection or the missing characteristic are shown.

  6. Correct the variation data.