Voelkner Core Integration
Voelkner is a market specialised in cosumer electronics, home technology, tools, and work safety.
Switch from Voelkner plugin to Voelkner Core Integration
If you want to switch from the Voelkner plugin to the Voelkner Core Integration, you can transfer your existing settings and SKUs to the new Voelkner Core Integration. You can find instructions on how to do this here. |
1. Becoming a seller at Voelkner
First, become a seller with Voelkner to start selling items on Voelkner.
After registering, you will receive login details from Voelkner. You need these login details to set up Voelkner in PlentyONE.
2. Frequency of data exchange
After you have set up Voelkner in PlentyONE, data is exchanged with the market in the intervals described in Table 1.
Data | Interval |
---|---|
Item export |
once a day |
full item export (creating + and updating offers) |
once a day |
Stock synchronisation |
every 15 minutes |
Price synchronisation |
hourly |
Order import |
every 15 minutes |
Importing refunds |
every 15 minutes |
3. Workflow of an order
-
Your items are listed on Voelkner. The name of your company is shown with your items.
-
Customers place an order on Voelkner.
-
Customers make their payments to Voelkner.
-
The order is imported into PlentyONE.
Tax refunds for solar panels cannot be processed via PlentyONE
Customers who buy solar panels at Voelkner and have them installed by companies with a specific certification can receive a certificate to have the value added tax refunded. |
No cancellations possible
At Voelkner, customers cannot cancel orders. The items need to be returned instead. |
4. Setting up Voelkner in PlentyONE
Now set up the market in PlentyONE.
4.1. Account overview
The Setup » Markets » Voelkner » Settings menu provides an overview of your Voelkner accounts. Table 2 lists the columns and available actions in the account overview.
Configuring columns
Click on Configure columns (settings) to define which settings should be displayed in the account overview. |
Note: The account overview looks different depending on which columns you add or hide via Configure columns (settings). The following table only lists the columns which are displayed in the overview by default.
Column | Explanation | ||
---|---|---|---|
ID |
The ID of your Voelkner account. The ID is assigned automatically when you create a new account. |
||
Name |
The name of your Voelkner account. |
||
Active |
circle = The account is active and data is exchanged with Voelkner. Note: Data is only exchanged with Voelkner if the account is both connected with Voelkner and active. In addition, an API key must be saved for the account. Click on Test connection in the account settings in order to connect to Voelkner. |
||
Client |
The client (shop) that orders of this Voelkner account are assigned to. |
||
Order import |
done = The order import for this account is active. Orders are imported into PlentyONE every 15 minutes. close = Orders are not imported. |
||
Item export |
done = The item export for this account is active. Items are exported to Voelkner once per day. close = Items are not exported. |
||
Offer export |
done = The offer export for this account is active. A full offer export is carried out once per day. This means that new offers are created and existing offers are updated. close = Offers are not exported. |
||
more_vert More |
Click here to display more actions.
|
4.2. Carrying out the basic settings
Carry out the basic settings for the market in the Setup » Markets » Voelkner » Settings menu.
First, add a new account for Voelkner.
Adding a new account:
-
Go to Setup » Markets » Voelkner » Settings.
-
Click on Add account (add).
→ The Add account window opens. -
Enter an account name.
-
Save () the settings.
→ A view with account settings opens. -
Carry out the additional settings. Pay attention to the explanations given in Table 3.
-
Save () the settings.
Setting | Explanation | ||
---|---|---|---|
Save |
Save the settings. |
||
more_vert More |
Click here to display more actions.
|
||
Test connection |
Click here to test whether a connection to Voelkner could be established. In this step, the API key is checked. Note: You have to test the connection again if you change the API key. |
||
General |
|||
Account |
The name of your Voelkner account. You entered the name when you created the account. |
||
Active |
Activate the Voelkner account. Data is exchanged with Voelkner. We recommend to only activate the account after you carried out all settings. Note: The account has to be connected to a Voelkner account so that data can be exchanged between PlentyONE and Voelkner. The Voelkner API key must be saved in PlentyONE. |
||
Voelkner API key |
Enter the API key. You have received the API key from Voelkner. |
||
Client |
Select a client (shop). The orders of this Voelkner account will be assigned to this client. |
||
Item |
|||
Item export |
Activate to export items to Voelkner once per day. |
||
Map shipping profiles |
Map your PlentyONE shipping profiles with shipping profiles from Voelkner. Mapping shipping profiles:
|
||
Orders |
|||
Order import |
Activate to import Voelkner orders into PlentyONE every 15 minutes. |
||
Order import start date |
Enter a date in the format D.M.YYYY or select a date via the calendar (today). |
||
Allow cancellations for orders with invoice |
Should customers be able to cancel an order if an invoice was already created? |
||
Automatically cancel refunded orders until order status |
Select an order status until which orders that were fully refunded should be automatically cancelled. Orders will automatically be cancelled if they have this status or a lower status. If the order has a higher status, then it will be refunded. Tip: Select a status in which you can make sure that the item will not be shipped. Orders which have already been shipped cannot be cancelled. |
||
Status for shipped orders |
Select the order status for orders that were shipped. |
||
Status for credit notes |
Select the order status for orders that were refunded by Voelkner. |
||
Status for cancelled orders |
Select the order status for orders that were cancelled. Tip: Select a status higher than status 8. |
||
Offers |
|||
Offer export |
Activate to export items to Voelkner once per day. Note: Offers can only be exported if an item has already been activated. If an item has not been activated by Voelkner, then the offer cannot be exported. |
4.3. Activating the order referrer
Go to Setup » Orders » Order referrer to activate the order referrer. This ensures that orders are assigned to the correct sales channel.
An order referrer tags an order with the sales channel on which the order was generated. Sales channels can be e.g. your online shop or markets on which you sell your items. Each sales channel has an individual order referrer. Some order referrers are available by default in your PlentyONE system. Further order referrers are added e.g. if you install a new plugin. For further information about the order referrer, see the page Order referrer of the PlentyONE manual.
Activating the order referrer for voelkner:
-
Go to Setup » Orders » Order referrer.
-
Click Search (search).
-
In the list, navigate to the option Voelkner with the ID 175.
-
On the right of the referrer’s line, click on Edit (edit).
→ The window Edit referrer opens. -
Activate the option Visible in selection (toggle_on).
-
Click on Save (save).
→ The referrer is active.
5. Preparing variations
Now, prepare your variations.
5.1. Setting the variation availability
You need to activate the variations that you want to sell on Voelkner. This is done in the Availability and visibility section of a variation within the Item » Items » [Open item] » [Open variation] menu.
Making a variation available for Voelkner:
-
Go to Item » Items » [Open item] » [Open variation].
Tip: To sell all variations of an item on Voelkner, carry out the settings for the item’s main variation. If the inheritance function is active for the variations, then this activates the availability of all variations of the item. -
In the Availability and visibility section, activate the option Active.
-
In the Sales channels section, click Add sales channels (add).
→ The window Add sales channels opens. -
In the drop-down list Sales channels, select the option Voelkner.
-
Click Apply.
→ The sales channel is added. -
Save () the settings.
→ The variation is available for Voelkner.
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 Voelkner using the variation group function:
-
Go to Item » Items.
-
Select () the variations to be edited.
-
In the toolbar, click on layers » layers Variation group function.
→ The Variation group function window opens. -
Select the action Sales channels from the drop-down list Actions.
→ The action is added to the lower part of the window. -
In the drop-down list Sales channels, select the option Voelkner.
-
Select the action Active from the drop-down list Actions.
→ The action is added to the lower part of the window. -
Activate the option Active.
-
Navigate to the area Availability.
-
Click Execute to apply the settings.
Batch processing allows you to edit several variations at once. You use filters to limit which variations are edited.
Making several variations available for Voelkner using batch processing:
-
Go to Item » Batch processing.
-
Click on the tab Variations in the upper left corner.
-
Use the filters on the left to specify which variations should be processed.
-
Navigate to the area Market availability.
-
Activate the checkbox to the left of the option Voelkner.
-
Activate the checkbox to the right of the option Voelkner.
-
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.
6. Exporting item data
Item data is exported to Voelkner using catalogues. Go to Data » Catalogues to create catalogues for Voelkner.
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.
6.1. Adding product categories
Before you can create catalogues for Voelkner, you have to add the product categories in which you want to offer your items on Voelkner. This is done in the Setup » Markets » Voelkner » Add catalogue templates menu.
After you added a product category in the Add catalogue templates menu, you can create a catalogue for this product category in the Data » Catalogues menu.
Adding product categories:
-
Go to Setup » Markets » Voelkner » Add catalogue templates.
-
Click on Add categories (add).
-
Select a category for offering your items.
Tip: You can either search the category by entering the name in the input field or you can expand the category tree to browse the available categories. -
Save () the settings.
→ The category was added. You can now create a catalogue for this category in the Data » Catalogues menu.
6.2. Linking variations to a Voelkner product category
Which variations are exported to Voelkner?
You can use catalogue filters in the menu Data » Catalogues » [Open catalogue] » Filters to define which variations should be exported to Voelkner. The filters Voelkner and Active are already set by default. This means that all variations which are active and which have the market availability for Voelkner in the Availability tab will be exported to Voelkner. |
You can use properties to define in which product category on Voelkner a variation should be listed. For example, you can create the property Voelkner product categories of the type selection and use the Voelkner product categories as selection values. You can then use the filters in the catalogue and filter for the property to define into which product category on Voelkner the variations should be exported.
Creating a property of the type selection:
-
Go to Setup » Settings » Properties » Configuration.
-
Click on add Create property.
→ The settings for the new property are displayed. -
In the area Details, select the type selection.
-
In the area Details, select the section Items.
-
Carry out the additional settings.
→ Tip: For example, you can use Voelkner product category as name for the property. -
Save (save) the settings.
→ The property is created. -
In the area Selection values, click on Create selection value.
-
Enter a name for the selection value.
→ Tip: You can enter the different Voelkner product categories as names for the selection values. -
Save (save) the settings.
→ The selection value is created and displayed in the overview. The value automatically receives a consecutive and unique ID that cannot be changed. You need this ID to only export specific variations in a catalogue.
Next, link the desired variations with the selection property that you created.
Link variation with property:
-
Go to Item » Edit item » [Open item].
-
Click on the Variations tab.
-
Open the variation that should be linked.
-
Open the Properties tab.
-
In the Variation properties area, select the property you created from the Properties drop-down list and click on Add ().
→ The property is added. -
Select the desired product category from the drop-down list Value.
-
Save () the settings.
Afterwards, add the ID of the selection value as filter in the desired Voelkner catalogue.
Tip: Open the property in the menu Setup » Settings » Properties » Configuration to see the IDs of the selection values.
Apply filters in the catalogue:
-
Go to Data » Catalogues.
-
Open the Voelkner catalogue.
-
On the left-hand side, open the tab Filters.
-
In the area Custom filters, select the filter Linked to at least one property selection value.
-
Enter the ID of the selection value of the property.
Tip: Open the property in the menu Setup » Settings » Properties » Configuration to see the IDs of the selection values. -
Save (save) the settings.
6.3. Creating a catalogue
Item data is exported to Voelkner using catalogues. To export your items to Voelkner, create a catalogue in the Data » Catalogues menu. Afterwards, link the Voelkner data fields with item data saved in PlentyONE in the catalogue.
After you activate the catalogue, the catalogue data is automatically exported to Voelkner in regular intervals.
Note: There is a separate catalogue format for each Voelkner product category. Different item data is exported in the different catalogue formats, depending on which information Voelkner requires for each product category.
This means that you have to create a separate catalogue for each Voelkner product category that you want to sell your items in. Go to Setup » Markets » Voelkner » Add catalogue templates to add product categories.
Create a catalogue for offers
For Voelkner, you always have to create a catalogue for offers. To do so, select the format Offer when you create a catalogue in the Data » Catalogues menu. |
Creating a catalogue:
-
Go to Data » Catalogues.
-
Click on Create catalogue (add).
-
Enter a name for the catalogue.
-
In the drop-down list Marketplace, select the option Voelkner.
-
In the drop-down list Export type, select the option Item (new).
-
In the drop-down list Category, select a category of the sales channel.
-
Save () the settings.
→ The catalogue is created.
→ The catalogue is opened for editing.
Other catalogue settings
Other catalogue settings are optional. Once you carried out the settings described on this page, your catalogue is automatically exported to Voelkner. 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 Voelkner was successful.
You should not change the format in the catalogue’s Format settings. To ensure that the export to the sales channel works, all required settings are already configured when you create a catalogue. If you change the settings, errors might occur during the export. |
6.3.1. Mapping data fields in the catalogue
After you have created a catalogue, map the market’s data fields to item data saved in PlentyONE. This chapter describes how you map data fields and what particularities apply for item exports to Voelkner.
-
The market expects product data that cannot be saved in the PlentyONE item menu? Then create a property for this data. Link this property with your variations. The actual values are saved as property values for this property. Is this your first time working with properties? Then read up on the principles of properties first.

Availability | Explanation |
---|---|
Navigation |
When you open a catalogue, the view Mapping is shown. On the very left is the navigation.
|
Toolbar |
The toolbar provides actions for the catalogue. For example, save your mappings, restore an older version of the catalogue or hide or show optional marketplace data fields. |
Marketplace data field |
To the right of the navigation, all data fields available for the market are listed. Mandatory fields are marked with an asterisk (✱). |
PlentyONE data fields |
On the right side of the catalogue, you map the marketplace data fields to appropriate PlentyONE data fields. In the screenshot above, a few of the fields are already mapped. |
Mapping catalogue fields:
-
Go to Data » Catalogues.
-
Click on the catalogue.
→ The Mapping tab opens.
→ In the left-hand column, the market’s data fields are listed.
Tip: Mandatory fields are flagged with an asterisk (*).
→ In the right column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column. -
Map suitable PlentyONE data fields to the market data fields.
For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.-
Simple 1:1 mapping
-
Simple 1:1 mapping with properties
-
Complex 1:1 mapping
-
1:1 mapping with fallback data fields
-
1:n mapping
-
Own value mapping
-
Mapping with mathematical calculations
-
-
Save () the catalogue.
→ The mappings are saved.
In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. If no suitable setting exists in PlentyONE. you can map a property instead.
As such, simple 1:1 mappings allow you to:
-
I want to fill this marketplace data field with the data from this PlentyONE setting.
-
If the data field is empty for a variation, no value is exported for this variation.
Creating a simple 1:1 mapping:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Click on the group you need.
→ The PlentyONE data fields of the group are shown. -
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right. -
Click on Confirm.
Example: Sales price and RRP for Otto Market
This gif shows you how to map the marketplace data fields Sales price and RRP for Otto Market to PlentyONE data fields:

Reminder: In a simple 1:1 mapping, you map a PlentyONE data field to the marketplace data field. However, what can you do if PlentyONE does not offer a suitable data field? Then it’s the properties' moment to shine. Properties allow you to save any kind of information in your properties.
-
Is this your first time working with properties? Then read up on the principles of properties first.
Creating a property:
-
Create a property with the necessary values.
Tip: Find out how to do that here.
Creating a simple 1:1 mapping with properties:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Expand the group Property.
→ The property groups are shown. -
Expand the group you need.
-
Click on the Plus sign on the right of the property you want.
-
From the drop-down list Language, select the language in which you send the data to the market.
-
Click on Confirm.
→ The property is mapped to the marketplace data field.
Like with the simple 1:1 mappings, you map a PlentyONE setting or property to a marketplace data field. Complex mappings are necessary whenever a marketplace data field has more than one possible value. Instead of mapping data fields, for complex mappings you map individual values of these data fields. For example, you cannot simply map the PlentyONE data field Shipping profile to the marketplace data field Shipping method. Why? The market cannot know which of your shipping profiles in PlentyONE corresponds to which of their shipping methods.
Do not enter own values for complex mappings. All values that you enter must be saved for the variations, either in a setting or as a property value. This also applies if the value Comparative value is shown. You still need to enter exactly the value of the setting or property that you mapped. |
In complex mappings, the value of the market is always exported. Only when you map an own value, the own value that you enter is exported.
You can recognise complex mappings from the field that is shown below the name of the marketplace data field. Click on the field to show the values available for the marketplace data field.

Examples for complex 1:1 mappings are:
-
Categories
-
Brands
-
Shipping setting
Important: For complex mappings, do not map own values or properties of the type None.
Creating a complex 1:1:n mapping:
-
Click on the field for the marketplace data field.
→ A list of the available values is shown. -
Select the value that you want to map a PlentyONE data field to.
→ The value is mapped. -
Next to the marketplace data field, click on + Add data field.
→ To the left, the available PlentyONE data fields are listed in groups. -
Click on a group.
→ The PlentyONE data fields of the group are shown. -
Click on the PlentyONE data field for which you want to map values.
Important: Do not map own values or properties of the type None. -
Your next steps depend on the PlentyONE data field you selected:
-
Alternative 1: The available values for the PlentyONE data value are shown on the left.
-
Next to the value you want to select, click on the plus.
→ The value is added to the field on the right. -
Click on Confirm.
-
-
Alternative 2: The PlentyONE data field is inserted and the field Comparative value is shown.
-
In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data field.
-
Click on Confirm.
-
-
Alternative 3: The PlentyONE data field is inserted and a drop-down list is shown.
-
Select a value from the drop-down list.
-
Click on Confirm.
→ The value of the marketplace data field is exported, not the value of the PlentyONE data field.
Exception: Only when you map an own value, the own value that you enter is exported.
-
-
Example: Delivery time in days for Otto Market
This gif shows you how to map suitable PlentyONE values to the values of the marketplace data fields Delivery time in days for Otto Market:

In a 1:1 mapping with one or more fallback data fields, you map a PlentyONE data field to the marketplace data field. In addition, you specify one or more fallback data fields. This ensures that the system keeps looking if the first PlentyONE data field is missing or empty.
So this mapping specifies:
-
I want to fill the marketplace data field with the data from the selected PlentyONE setting.
-
If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.
-
If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.
Two separate fallback conditions are available:
Null (default) |
The fallback data field is used if the data field above is mapped in the catalogue but not linked to the variation. The condition "Null" is useful when you want to map fallback data fields for the following types of PlentyONE data fields:
Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting. |
Empty |
The fallback data field is used if the data field above is mapped in the catalogue and linked to the variation, but is empty. The condition "Empty" is useful when you want to map fallback data fields for the following type of PlentyONE data fields:
Important: When you add a fallback data field, the fallback condition "null" is selected automatically. To apply the fallback condition "leer", you need to change the default setting. |
Note: Even if you assign one or more fallback data fields, the value of only one of those fields is exported. For each variation, the mapped PlentyONE data fields are checked in the order in which you mapped them. This means that if the first data field does not provide a value for a variation, the first fallback data field is exported etc.
Creating a 1:1 mapping with fallback data fields:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Click on the group you need.
→ The PlentyONE data fields of the group are shown. -
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right. -
In the list of PlentyONE data fields, click on the plus icon next to the PlentyONE data field that you want to map.
→ The fallback data field is added with the fallback condition "null". -
Alternative 1: To add the fallback data field with the fallback condition "null":
-
Click on Confirm.
→ The fallback data field is exported if the data field above is not linked to the variation.
-
-
Alternative 2: To add the fallback data field with the fallback condition "empty":
-
To the left of the fallback data field, click on the cog ().
→ The window Data column settings is shown. -
For the setting Fallback condition, select the option Empty.
-
Click on Save.
→ The fallback data field is added with the fallback condition "empty". -
Click on Confirm.
→ The fallback data field is exported if the data field above is empty for the variation.
-
Example: Fallback data field for SKU for Otto Market
This GIF shows you the mapping for the OTTO Market marketplace data field SKU. The PlentyONE data field SKU is mapped to this marketplace data field. The PlentyONE data field Variation ID is mapped as the fallback data field. The fallback condition "null" is applied automatically.
Result: The fallback data field Variation ID is exported if the data field SKU is not linked to the variation.

In a 1:n mapping, you map several PlentyONE data fields to the marketplace data field. You can link these data fields with a separator.
So this mapping specifies:
-
I want to combine these PlentyONE data fields during export so that the marketplace data field is filled with the data of these two or more PlentyONE settings.
Creating a 1:n mapping:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Click on the group you need.
→ The PlentyONE data fields of the group are shown. -
Click on the plus to the right of the PlentyONE data field you want to select.
→ The PlentyONE data field is added to the right. -
Click on Confirm.
-
To the right of the mapped PlentyONE data field, click on Add data field ().
→ To the left, the list of available PlentyONE data fields again are shown in groups. -
Map one or several additional PlentyONE data fields to the marketplace data field as described above.
-
Click on Confirm.
-
To the very right of the row, click on Settings ().
-
Select a separator from the drop-down list Separator or add a custom separator.
-
Click on Save.
-
Save () the catalogue.
→ The mappings are saved.
→ During the export, the content of the PlentyONE data fields is combined and exported as one field.
You are sure that you want to export the same value for all variations of a catalogue for a marketplace data field? Then specify an own value. This own value is then exported for all variations.
So this mapping specifies:
-
For this marketplace data field, I want to export the value that I entered in the field Own value for all variations of this catalogue. The value you enter is always exported. The value overwrites the market value also in complex mappings where usually the value of the market is exported. As such, make sure you enter an own value that the market accepts for this marketplace data field.
Creating an own value mapping:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view. -
Enter a value into the input field.
→ This value is exported for all variations.
Example: Diameter information
You want to export diameter information for some of your variations. The diameter is saved in centimetres for all your variations. Instead of creating a property for the unit and linking this property to the variations, you can enter the own value cm
.
This is an example of how you can map an own value for the diameter unit:

Mathematical calculations allow you to change numerical values automatically during the export.
-
This function only works for data fields that contain numerical values.
-
This functionality is new and not available for all catalogue formats.
So this mapping specifies:
-
I want the numerical value of a PlentyONE data field to be recalculated during the export. Basic arithmetic operations are available for the formulas.
Recalculating numerical values:
-
Next to the marketplace data field, click on + Add data field.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
At the very top of the list, click on the plus icon next to Formula (calculate).
→ The data field Formula is added to the field on the right. -
Click into the data field.
→ The window Modify value is shown. -
Enter a numerical value or select a PlentyONE data field at the bottom right of the window to add it to the calculation (add).
Tip: Use the search function. This helps you to find data fields quickly. -
Optional: If the symbol more_vert is shown in the data field, select the correct assignment for the data field.
Tip: A number tells you how many assignments are necessary for the data field.-
Click on the icon more_vert.
-
In the window shown, select the assignments from the drop-down list.
-
Save the settings.
-
-
Enter numbers and mathematical operators with the on-screen calculator or the keyboard.
-
Save the settings.
→ The entered formula is displayed in the overview.
→ The calculation will be carried out in the next export.
6.3.2. Recommendations for data field mappings
To help you with mapping your data fields for the catalogue, we have created a list of recommended data field mappings. Note that these mappings are recommendations only. Depending on how you manage your item data, other mappings may be more appropriate than the recommendation given here.
-
Need more information about the PlentyONE data fields? All data fields are described on the manual page for the standard format Item (new).
Note: You have to create a separate catalogue for each Voelkner product category that you want to offer your items in.
Catalogues for different product categories contain different data fields. This is because different item data has to be specified in each Voelkner product category.
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
General |
||
Product.SellerProductID |
yes |
|
SHOP.PRODUCT.TITLE |
yes |
|
ATT.GLOBAL.ManufacturerAID |
yes |
|
ATT.GLOBAL.NoCUperOU |
yes |
Here you provide information about the content of the item, for example
|
Product.DocumentSecurityAdvisory01URL_MP |
no |
Enter the URL to a pictogram that indicates whether a charger is included in the scope of delivery (charger plug is not crossed out) or not (charger plug is crossed out).
|
ATT.Text.ProductTextLong |
yes |
|
Product.PrimaryImageURL_MP |
yes |
|
ATT.NUM.CHARGING_CAPACITY_MAX |
no |
The required power for maximum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed.
Example: 27 |
ATT.NUM.CHARGING_CAPACITY_MIN |
no |
The required power for minimum charging capacity must be specified as a whole number in watts. Decimal numbers are not allowed.
Example: 20 |
ATT.GLOBAL.Brandname |
||
ATT.GLOBAL.Brandname |
yes |
Here you map manufacturers. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your manufacturers. The values are then assigned to a PlentyONE data field. Example:
|
Product.BaseUnit |
||
Product.BaseUnit |
yes |
Here you map the sales quantity unit. Enter the smallest amount of the item that can be sold individually. This unit is independent of the unit that you want to use to price or store the item. Example:
|
ATT.GLOBAL.NoCUperOU__UNIT |
||
ATT.GLOBAL.NoCUperOU__UNIT |
yes |
Here you map the content unit. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are content units. The values are then assigned to a PlentyONE data field. Example:
|
Product.TaxIndicator |
||
Product.TaxIndicator |
yes |
Here you map the VAT class. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your VAT classes. The values are then assigned to a PlentyONE data field. Example:
|
ATT.LOV.LOADING_TECHNOLOGY_PD |
||
ATT.LOV.LOADING_TECHNOLOGY_PD |
no |
Is the USB Power Delivery (PD) charging protocol supported?
Allowed values: |
ATT.NUM.CHARGING_CAPACITY_MAX__UNIT |
||
ATT.NUM.CHARGING_CAPACITY_MAX__UNIT |
no |
The required power for maximum charging capacity must be specified in watts.
Allowed values: |
Product.PowerSupplyIncluded |
||
Product.PowerSupplyIncluded |
no |
Is a charger included in the scope of delivery?
Allowed values: |
ATT.NUM.CHARGING_CAPACITY_MIN__UNIT |
||
ATT.NUM.CHARGING_CAPACITY_MIN__UNIT |
no |
The required minimum charging capacity must be specified in watts.
Allowed values: |
-
You need more information on how to map items? Here is an example of item mappings for different product categories. Only the mandatory fields are mapped in the examples. Note that these examples are recommendations only. Depending on how you manage your item data, other mappings may be more appropriate than the recommendation given here.
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
General |
||
Product.SellerProductID |
yes |
|
SHOP.PRODUCT.TITLE |
yes |
|
ATT.GLOBAL.ManufacturerAID |
yes |
|
ATT.GLOBAL.NoCUperOU |
yes |
Here you provide information about the content of the item, for example
|
ATT.Text.ProductTextLong |
yes |
|
Product image 1 URL |
yes |
|
ATT.GLOBAL.Brandname |
||
ATT.GLOBAL.Brandname |
yes |
Here you map manufacturers. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your manufacturers. The values are then assigned to a PlentyONE data field. Example:
|
Product.BaseUnit |
||
Product.BaseUnit |
yes |
Here you map the sales quantity unit. Enter the smallest amount of the item that can be sold individually. This unit is independent of the unit that you want to use to price or store the item. Example:
|
ATT.GLOBAL.NoCUperOU__UNIT |
||
ATT.GLOBAL.NoCUperOU__UNIT |
yes |
Here you map the content unit. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are content units. The values are then assigned to a PlentyONE data field. Example:
|
Product.TaxIndicator |
||
Product.TaxIndicator |
yes |
Here you map the VAT class. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values are your VAT classes. The values are then assigned to a PlentyONE data field. Example:
|
ATT.LOV.WIRELESS_CHARGING |
||
ATT.LOV.WIRELESS_CHARGING |
yes |
Here you indicate whether wireless charging is possible. This data field contains a complex mapping. This means that you can select from different values of the marketplace data field. In this case, the values provide information on wireless charging. The values are then assigned to a PlentyONE data field. Example:
|
Marketplace field | Mandatory? | Recommended PlentyONE mapping |
---|---|---|
Offer SKU |
yes |
This data field is assigned automatically. |
Offer SKU status |
yes |
This data field is assigned automatically. |
Offer SKU base |
no |
|
ItemID |
no |
This data field is assigned automatically. |
VariationID |
no |
This data field is assigned automatically. |
Offer Description |
no |
|
Offer Internal Description |
no |
The internal offer description. This description will not be shown on Voelkner.
|
Offer Price |
yes |
The sales price of the item.
|
Offer Price Additional Info |
no |
Additional information about the sales price. |
Offer Quantity |
no |
The stock of the variation.
Tip: Use the data fields in the group Virtual warehouse to export the stock quantity sum of all sales warehouses. |
Minimum Quantity Alert |
no |
You will be informed via email when the stock reaches the defined minimum quantity. If you do not enter a quantity here, then you will not receive an email. |
Availability Start Date |
no |
When will the item be available?
|
Availability End Date |
no |
Until when will the item be available?
|
Discount Price |
no |
The offer price. |
Discount Start Date |
no |
When will the discount start? |
Discount End Date |
no |
When will the discount end? |
Lead Time to Ship (in days) |
no |
The processing time in days until the item can be shipped.
|
Update/Delete |
no |
This data field is automatically mapped with UPDATE so that items can be updated on Voelkner. |
Active channels |
yes |
This data field is assigned automatically. |
Voelkner EPR producer ID |
yes |
EPR is short for Extended Producer Responsibility. You receive the EPR producer ID when you register your products under the extended product responsibility laws.
|
Voelkner EPR category |
no |
Use this property to specify the EPR category of each of your variations.
|
Voelkner EPR amount |
no |
|
Warehouse address |
no |
or
|
Warehouse name |
no |
or
|
Warehouse street |
no |
or
|
Warehouse house number |
no |
or
|
Warehouse postal code |
no |
or
|
Warehouse city |
no |
or
|
Product safety responsible name |
no |
|
Product safety registered trademark |
no |
|
Product safety responsible electronic address |
no |
or
For example, the value of the property can be the URL to the manufacturer’s homepage. |
Product safety responsible street |
no |
|
Product safety responsible house number |
no |
|
Product safety responsible zip code |
no |
|
Product safety responsible city |
no |
|
Product ID Type |
||
Product ID Type |
yes |
If you want to add items to existing offers with content provided by Voelkner:
If you want to create offers with your own content, such as product title and description:
|
Offer State |
||
Offer State |
yes |
The item’s condition, for example new or used.
|
Product safety responsible country |
||
Product safety responsible country |
no |
The country ID of the manufacturer’s EU-responsible person according to ISO-3166, for example DE or GB. recommended mapping:
Enter the name of the country in the Comparative value field. |
Logistic Class |
||
Logistic Class |
no |
Voelkner calculates the shipping costs of an item with the item’s logistic class. |
Free return |
||
Free return |
no |
Can the item be returned free of charge?
Allowed values: |
Reverse charge |
||
Reverse charge |
yes |
Does the reverse charge procedure apply to the item?
Allowed values: |
Warehouse country |
||
Warehouse country |
no |
For simple mapping:
or for complex mapping:
|
Warehouse type |
||
Warehouse type |
no |
For simple mapping:
or for complex mapping:
|
Customer group availability |
||
Customer group availability |
no |
For simple mapping:
or for complex mapping:
|
6.3.3. Notes on mapping data fields
In the catalogues, you will find data fields that allow both simple and complex 1:1 mapping. This selection gives you the flexibility to adapt the mapping to the nature of your data.
Example: The data field Offer state in the offer catalogue
For the data field Offer state, both the simple and the complex mapping are marked as mandatory. You only have to configure one of these two options.
-
Simple 1:1 mapping: Select this option if the value for the data field should be the same for all your offers in the catalogue. For example, if you only offer new products and the status New (value 11) applies to all items.
-
Complex 1:1 mapping: This option is useful if you want to transmit different values for the data field. For example, if you offer new and used products at the same time and therefore need to transmit the status New (value 11) as well as the status Very good (value 2). The complex mapping allows you to react flexibly to different values for item settings or properties.
If you want to transmit the status New for all items:
-
Next to the marketplace data field, click on + Add data source.
→ To the left, the list of available PlentyONE data fields are shown in groups. -
Click on the plus next to Own value at the top of the list.
→ The field for the own value is added to the view. -
Enter the value 11 into the input field.
→ This value is exported for all variations.
Note: Make sure that the value corresponds to the marketplace standard. In this case, 11 corresponds to the status New at Voelkner. You can find the list of valid values in the Mirakl backend.

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

You can find further details on the configuration of simple and complex mapping in the chapter Mapping data fields in the catalogue.
6.3.4. Providing information on manufacturer and EU-responsible person (GPSR)
The General Product Safety Regulation of the EU (GPSR) requires manufacturers and sellers to ensure the product safety of certain goods and to provide certain information for this purpose. This information includes details about the manufacturer and, in the case of manufacturers without an establishment in the EU, details about the responsible person within the EU. The GPSR regulation ensures that products are safe and comply with consumer protection requirements before being placed on the market.
In this chapter, you will learn how to add information on the manufacturer and the responsible person within the EU in PlentyONE to comply with the GPSR regulation.
If you export your items to Voelkner via catalogues, you can add the information on the manufacturer and the EU-responsible person directly via the data field mappings.
6.3.5. Providing information and images for chargers for electrical appliances with radio frequency (FuAG)
On 23rd November2022 the EU directive 2022/2380 on the harmonisation of charger interfaces of radio equipment was passed.
This directive was realized in German law on the 6th May 2024 by changing the Funkanlagengesetz (FuAG). The new FuAG is in effect since the 28th December 2024 and contains new labeling requirements for electrical appliances with radio frequency and chargers, such as:
-
Mobile phones
-
Tablets
-
Digital cameras (all digital cameras except: security cameras and digital cameras that are exclusively used in the audiovisual sector)
-
Headphones
-
Headsets
-
Handheld gaming consoles
-
Portable speakers
-
E-readers
-
Keyboards
-
Mice
-
Portable navigation systems
-
Earbuds
-
Laptops
The following information has to be indicated in the product details for the mentioned electrical appliances that are put into circulation from 28th December 2024 (for laptops starting 28th April 2026) on:
-
Pictogram for charger included in the scope delivery:
-
The pictogram indicates if a charger is included (charger plug is not crossed out) or not (charger plug is crossed out).
-
The mandatory pictogram is described and displayed in Appendix I Part 3 of the directive 2022/2380.
-
-
Label about charging properties of compatible chargers:
-
The label offers all necessary charging properties of the charger that are compatible with the electrical appliance.
-
The mandatory label is described and displayed in Appendix I Part 4 of the directive 2022/2380.
-
Note: The labelling requirement applies to the B2B and B2C section.
Providing information and images for chargers via the product catalogue
If you export your items to Voelkner via catalogues, you can add the information on chargers directly via the data field mappings. The following data fields are available for this purpose:
-
Product.DocumentSecurityAdvisory01URL_MP
-
ATT.NUM.CHARGING_CAPACITY_MAX
-
ATT.NUM.CHARGING_CAPACITY_MIN
-
ATT.LOV.LOADING_TECHNOLOGY_PD
-
Product.PowerSupplyIncluded
-
ATT.NUM.CHARGING_CAPACITY_MAX__UNIT
-
ATT.NUM.CHARGING_CAPACITY_MIN__UNIT
For further information on these data fields, see the recommendations for data field mappings.
-
0611041 Action Cams
-
1805010 Bluetooth® hands-free sets
-
1310040 Bluetooth® speakers
-
0417038 Camcorder
-
3620048 Digital cameras
-
0417009 Visualisers
-
0415035 eBook readers
-
0413098 eBook reader accessories
-
3620049 Disposable cameras, non-digital photography
-
1801021 EX-proof mobile phones
-
1801040 Mobile phones
-
1312021 Headphones
-
0415223 Laptop keyboards
-
0413102 Beginner’s PC
-
0411022 PC mice
-
1310038 Mini speakers
-
1407014 Portable PA speakers
-
0715024 Motorbike headsets
-
0319011 Satnavs
-
3600038 Nintendo consoles
-
0609050 Outdoor satnavs
-
0403047 Outdoor and industry-grade tablets
-
1407020 Party speakers
-
1413185 PC complete sets
-
0416010 PC speakers
-
0413178 PC systems
-
0411033 Pen displays
-
1801022 Satellite phones
-
3600016 Chess computers
-
1801050 Big button mobile phones
-
1801015 Smartphones
-
1801014 Smartphones (contract)
-
3620047 Instant cameras
-
3620020 DSLR cameras
-
3620050 System cameras
-
0403040 Tablets
-
0413122 Tablet keyboards
-
0420013 Keyboard-mouse combos (desktops)
-
0420012 Keyboards
-
1009014 Phone headset cables
-
0413047 USB-keypads, keypads
-
0601013 Wearables
-
0611046 Wildlife cameras
6.3.6. Activating the catalogue export
You have set up Voelkner 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 Voelkner in the Data » Catalogues menu.
Activating the catalogue export to Voelkner:
-
Go to Data » Catalogues.
→ The catalogues are listed. -
Scroll to the Voelkner catalogue.
-
In the Active column, move the toggle button to the right ().
→ The catalogue is active.
→ The catalogue data is exported to Voelkner once a day.
Tip: Go to Data » Catalogue export status for information about the status of the export.
7. Manually managing the data exchange
In the menu Setup » Markets » Voelkner » 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.
7.1. Manually exporting item data
In the Setup » Markets » Voelkner » Data exchange » Data export menu, you can export individual items and offers to Voelkner. For example, this can be helpful if you want to test the export to Voelkner or if you only want to export individual items.
Note: In the Data export menu, you can already export data even if the account has not been activated yet. This way, you can test the export with individual items and offers before you activate the account and exchange data with Voelkner.
Manually exporting an item:
-
Go to Setup » Markets » Voelkner » Data exchange » Data export.
-
Select the Account from the drop-down list.
-
Select a Catalogue from the drop-down list.
-
Enter one or more Item IDs separated by comma. Those items will then be exported to Voelkner.
-
Click on file_upload Export.
Note: You can run this process every 30 minutes. Items cannot be exported manually between 24.00 - 6.00 CET.
Tip: Click on Preview to generate e preview of the export.
Manually exporting offers:
-
Go to Setup » Markets » Voelkner » Data exchange » Data export.
-
Select the Account from the drop-down list.
-
Select a Catalogue from the drop-down list.
-
Enter one or more Item IDs separated by comma. The offers for those items will then be exported to Voelkner.
-
Click on file_upload Export.
Note: You can run this process every 15 minutes.
Tip: Click on Preview to generate e preview of the export.
7.2. Manually importing orders
In the Setup » Markets » Voelkner » Data exchange » Order import menu, you can manually import individual orders into PlentyONE.
You can either enter the order IDs of the orders you want to import, or you can import orders from a specific time frame.
Note: You can run this process every 15 minutes.
Import orders by ID:
-
Go to Setup » Markets » Voelkner » Data exchange » Order import.
-
Open the tab Import orders by order ID.
-
Enter one or more order IDs into the input field Order IDs. Separate the IDs by comma if you enter more than one ID.
-
Click Import.
→ The orders are imported into PlentyONE.
Import orders by date:
-
Go to Setup » Markets » Voelkner » Data exchange » Order import.
-
Open the tab Import orders by date.
-
Enter a start date in the format D.M.YYYY or select a date via the calendar (today).
-
Enter an end date in the format D.M.YYYY or select a date via the calendar (today).
-
Click Import.
→ Orders from the selected time frame are imported into PlentyONE.
8. Automating order processing
Set up event procedures to automatically inform Voelkner about changes to the order status. The following event procedures are available for Voelkner:
Sequence of event procedures
To send a shipping confirmation to Voelkner, two event procedures must be executed in a fixed order. If only one of the procedures is executed or the order is incorrect, the shipping confirmation cannot be transmitted to Voelkner.
|
8.1. Automatically uploading carrier tracking information to Voelkner
Set up an event procedure to automatically upload carrier tracking information to Voelkner.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 4.
-
Save () the settings.
-
Carry out the additional settings according to Table 4.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 4 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
Note: Select an event after which the items have already been shipped. |
|
Filter |
Order > Referrer |
Voelkner |
Procedure |
Plugin |
Upload carrier tracking information to Voelkner |
8.2. Uploading shipping confirmations to Voelkner
Set up an event procedure to automatically inform Voelkner when you have shipped the items of an order.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 5.
-
Save () the settings.
-
Carry out the additional settings according to Table 5.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 5 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
|
Select an event, for example [7] Shipped. Note: Make sure to select different events for the event procedures Upload carrier tracking information to Voelkner and Upload shipping confirmation to Voelkner. The event procedure Upload carrier tracking information to Voelkner must be executed before the event procedure Upload shipping confirmation to Voelkner. |
Filter 1 |
Order > Order type |
Order |
Filter 2 |
Order > Referrer |
Voelkner |
Procedure |
Plugin |
Upload shipping confirmation to Voelkner |
8.3. Automatically uploading invoices to Voelkner
Set up an event procedure to automatically upload invoices to Voelkner.
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 6.
-
Save () the settings.
-
Carry out the additional settings according to Table 6.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 6 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example:
Note: Select an event after which the items have already been shipped. |
|
Filter |
Order > Referrer |
Voelkner |
Procedure |
Plugin |
Upload invoice to Voelkner |
8.4. Reporting refunds to Voelkner
Set up an event procedure to automatically inform Voelkner that an item was refunded.
Different event procedures can be created, depending on the reason for the refund. The following event procedures are available for Voelkner to report a refund:
-
Report refund to Voelkner: Agreement with vendor
-
Report refund to Voelkner: Cancelled before shipping
-
Report refund to Voelkner: Item not received
-
Report refund to Voelkner: Item returned
-
Report refund to Voelkner: Out of stock
-
Go to Setup » Orders » Events.
-
Click on Add event procedure ().
→ The Create new event procedure window opens. -
Enter a distinct name for the event procedure.
-
Select the event according to Table 7.
-
Save () the settings.
-
Carry out the additional settings according to Table 7.
-
Select the setting Active ().
-
Save () the settings.
Note: The selected statuses and filters in Table 7 only serve as an example. Select filters and statuses for the event procedure which best suit your workflow.
Setting | Option | Selection |
---|---|---|
Event |
Select an event, for example: Order generation: New credit note |
|
Filter |
Order > Referrer |
Voelkner |
Procedure |
Plugin |
Select an event procedure for Report refund to Voelkner with the appropriate reason. |
9. Downloading reports
In the Setup » Markets » Voelkner » Reports menu, you can download reports for offer export and product export. These reports are generated after an offer or product export to Voelkner.
Table 8 contains an overview of the reports in the Setup » Markets » Voelkner » Reports menu.
Column | Explanation |
---|---|
Date |
Creation date of the report in the format YYYY.MM.DD hh:mm:ss |
Status |
The processing status of the report.
|
Integration Details |
The number of imported products. |
Transform Lines |
The number of rows in the report in which no errors occurred and the number of rows in which errors occurred. |
Download |
Download report (file_download): The report is downloaded. |
Downloading a report:
-
Go to Setup » Markets » Voelkner » Reports.
-
Click Filters (tune) at the top of the menu.
-
Select a report type. The available report types are listed in Table 9.
-
Click Search (search).
→ The selected filter is applied and the appropriate reports are displayed.
→ The active filter is displayed at the top of the menu.
Tip: If you want to change the filter, you can reset (refresh) it. Then select the desired filter as described above. -
Click Download report (file_download).
→ The report is downloaded.
Report type | Explanation |
---|---|
Offers |
The offer report contains information on the offer export to Voelkner. |
Products |
The product report contains information on the product export to Voelkner. |
10. Switching from the Voelkner plugin to the Voelkner Core Integration
If you are using the Voelkner plugin, you can transfer your settings and SKUs to the new Voelkner Core Integration.
10.1. Transferring settings to the Core Integration
To migrate your settings from the Voelkner plugin, you have to manually configure them in the Voelkner Core Integration. The following table shows which settings from the plugin assistant need to be transferred, along with their corresponding locations in the Core Integration.
Settings in the plugin assistant | Settings section of the Voelkner Core Integration |
---|---|
Authentication |
|
API key |
Setup » Markets » Voelkner » Settings » [Open account]
|
Data exchange |
|
Configuration for automated order import, item and offer export |
Setup » Markets » Voelkner » Settings » [Open account]
|
Options for the offer export |
The setting for the offer export is omitted. |
Refunds |
|
Mapping of refund reasons |
You don’t need to map refund reasons. Instead, event procedures with different refund reasons are used. |
Cancellations |
|
Mapping of cancellation reasons |
At Voelkner, customers cannot cancel orders. The items need to be returned instead. |
Warehouse selection |
|
Warehouse selection |
You directly map your warehouses via the offer quantity data field in the corresponding offer catalogue. Pay attention to the recommendations for data field mappings. |
Shipping profiles |
|
Shipping profile mapping |
Setup » Markets » Voelkner » Settings » [Open account]
|
Offer properties |
|
Offer properties mapping |
You specify which offer data is transferred via the data field mapping in the corresponding offer catalogue. |
10.2. Transferring SKUs
Follow the steps below to transfer the SKUs from your Voelkner plugin account to your Voelkner Core Integration account.
Transferring SKUs for product catalogues:
Important: This process can only be carried out once per account. Therefore, you should only transfer your SKUs when you know that you will no longer be creating new products on Voelkner via the Voelkner plugin.
-
Go to Setup » Markets » Voelkner » Settings » [Open account].
-
Click Migrate plugin SKUs in the Offers section.
→ The plugin SKUs will be transferred to your Voelkner Core Integration account.
→ You can now manage your existing products and offers via the Voelkner Core Integration catalogues.
Note: Your plugin product catalogues cannot be migrated to the Core Integration product catalogues. Instead, create new product catalogues and then map the data fields accordingly.
To manage your offers, no SKU transfer is required. Instead, you manage your offers via offer catalogues. In these catalogues you map the data fields from Voelkner to the corresponding fields in your system. Pay attention to the recommendations for data field mappings.