XXXLutz Core Integration (Setup via Channel Control Centre)

XXXLutz offers customers a wide range of furniture, home textiles, flooring, lighting, household items and decorative articles.

Sales Channels » Channel Control Centre

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

1. Becoming a seller at XXXLutz

First, register as a seller with XXXLutz to start selling items on XXXLutz.

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

2. Frequency of data exchange

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

Table 1. Frequency of data exchange
Data Interval

Item export

once a day

Full item export (creating + and updating offers)

once a day

Stock synchronisation

every 15 minutes

Price synchronisation

hourly

Order import

every 15 minutes

Importing refunds

every 15 minutes

3. Setting up the data exchange

In order for the interface to successfully carry out the item export, the offer export, the stock and price synchronisation, the order import and the import of refunds, certain settings are mandatory. Pay attention to the following list.

Table 2. Mandatory settings for XXXLutz
Settings section Settings

Item export

Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:

  • XXXLutz is added as a sales channel to your system.

  • The following basic settings for XXXLutz are carried out:

    • An account for XXXLutz is created.

    • The XXXLutz API key is entered.

    • The Shop ID is entered.

    • The Item export is activated.

    • The account for XXXLutz is activated.

Variation settings

Catalogue settings

Listing settings

Offer export

Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:

  • XXXLutz is added as a sales channel to your system.

  • The following basic settings for XXXLutz are carried out:

    • An account for XXXLutz is created.

    • The XXXLutz API key is entered.

    • The Shop ID is entered.

    • The Offer export is activated.

    • The account for XXXLutz is activated.

Variation settings

Catalogue settings

Listing settings

Stock synchronisation / Price synchronisation

Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:

  • XXXLutz is added as a sales channel to your system.

  • The following basic settings for XXXLutz are carried out:

    • An account for XXXLutz is created.

    • The XXXLutz API key is entered.

    • The Shop ID is entered.

    • The Offer export is activated.

    • The account for XXXLutz is activated.

Variation settings

Catalogue settings

Listing settings

Order import

Basic settings for the sales channel in the menu Sales Channels » Channel Control Centre:

  • XXXLutz is added as a sales channel to your system.

  • The following basic settings for XXXLutz are carried out:

    • An account for XXXLutz is created.

    • The XXXLutz API key is entered.

    • The Shop ID is entered.

    • The Client is selected.

    • The Order import is activated.

    • The shipping profiles are mapped.

    • The account for XXXLutz is activated.

4. Workflow of the product data and offer export to XXXLutz

Workflow of the product data export

  • If you want to offer a product that is not yet listed on XXXLutz, create a product catalogue with the following mandatory information:

    • Shop sku

    • Name [de]

    • Description [de]

    • GTIN

    • Main picture

    • Width

    • Length/Depth

    • Main Material

    • Color
      Depending on the product category, further mandatory information may be required.
      Note: Pay attention to the information on recommended data field mappings.

  • Create a product listing.

  • The product listing is exported to XXXLutz.
    Important: If the product catalogue contains a product that does not yet exist on XXXLutz, XXXLutz must first approve this product. The report for the product catalogue remains in PENDING status until the product is approved.

Workflow of the offer export to XXXLutz

Do I always have to create a product catalogue and an offer catalogue?

If you only want to offer products that already exist on XXXLutz, you do not need to create a product catalogue beforehand. You can directly create an offer catalogue.

  • Create an offer catalogue with the following mandatory information:

    • Offer Price

    • Product ID Type
      Tip: Use the EAN as primary identifier.
      Alternatively, you can enter the SHOP-SKU. Make sure to select the same source for the SHOP_SKU that you used for the Shop sku field in the product catalogue.

    • Offer State

  • Create an offer listing.

  • The offer listing is exported to XXXLutz.

5. Workflow of an order

There are two different order workflows at XXXLutz, which differ depending on the payment method:

  • Pay on Acceptance: The order must be accepted or rejected via an event procedure. Customers pay directly after the order has been accepted.

  • Pay on Shipment: Customers pay by invoice via Klarna after the order has been shipped.

Pay on Acceptance

  • Your items are listed on XXXLutz.

  • Customers place an order on XXXLutz.

  • The incomplete order is imported into PlentyONE with the payment method XXXLutz - Pay on Acceptance.
    → At this point, the invoice and delivery address for the order are still missing and the order has not yet been paid for.

  • The order must:

    • be accepted via flow
      or

    • be rejected via flow

  • If the order is accepted, customers make their payments to XXXLutz.

  • With the payment confirmation, the invoice and delivery address on the order are updated in PlentyONE.
    → The order is complete.

  • The order is shipped.

  • The shipping confirmation must be sent to XXXLutz by flow.

  • The invoice must be uploaded to XXXLutz via flow.
    → The invoice is sent to the customer via flow.

No cancellations possible

With Pay on Acceptance, customers cannot cancel orders. The items need to be returned instead.

Pay on Shipment

  • Your items are listed on XXXLutz.

  • Customers place an order on XXXLutz.

  • The incomplete order is imported into PlentyONE with the payment method XXXLutz - Pay on Shipment.
    → At this point, the invoice and delivery address for the order are still missing and the order has not yet been paid for.

  • The order must:

    • be accepted via flow
      or

    • be rejected via flow

  • With the payment confirmation, the invoice and delivery address on the order are updated in PlentyONE.
    → The order is complete.

  • The order is shipped.

  • The shipping confirmation must be sent to XXXLutz by flow.

  • The invoice must be uploaded to XXXLutz via flow.
    → The invoice is sent to the customer via flow.

  • Customers send their payment to XXXLutz within 30 days (via Klarna).

Cancellations possible

If Pay on Shipment is used, customers can cancel their orders as long as they have not been shipped. The order will not be refunded as it has not been paid yet.

6. Setting up XXXLutz in PlentyONE

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

6.1. Sales channel overview

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

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

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

Name

The name of the sales channel.

more_vert More

Click here to display more actions for a sales channel.

list Listings

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

settings Settings

Opens the respective Settings menu of the sales channel.

delete Delete sales channel

Deletes the sales channel from the overview.

6.2. Adding the sales channel

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

Adding a sales channel:

  1. Open the Sales Channels » Channel Control Centre menu.

  2. Click Add sales channel (add).
    → The menu Add sales channel opens.

  3. Click Continue in the tile of XXXLutz.

  4. Enter a name for the sales channel.

  5. If asked to, select the Client (Shop) from the drop-down list.

  6. Click add Add XXXLutz.
    → The sales channel for XXXLutz is added.

6.3. Carrying out the basic settings for XXXLutz

Next, carry out the basic settings for XXXLutz.

First, add a new account for XXXLutz.

Adding an account for XXXLutz:

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the XXXLutz tile.
    → The tab Settings opens.

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

  4. Enter an account name.

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

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

  7. Click Save (save).
    → The settings are saved.

Table 4. Settings for the sales channel XXXLutz
Setting Explanation

save Save

Save the settings.

more_vert More

Click here to display more actions.

delete Delete account

Delete the account.

TEST CONNECTION

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

Active

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

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

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

XXXLutz API key

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

Shop ID

Enter the Shop ID. You have received the Shop ID from XXXLutz.

Client

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

Item

Item export

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

Map shipping profiles

Shipping zone

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

Mapping shipping profiles:

  1. Select the shipping zone from the drop-down list.
    Note: You need to have a default mapping to prevent errors during the order import. Define a fallback for unassigned shipping zones.

  2. Click Show mappings for the selected zone.
    → A new view for mapping shipping profiles opens.
    Note: Your changes will not be saved. In order to save your changes first, click Save (save) in the top left corner before mapping the shipping profiles.

  3. Click Add mapping.
    → The window Add new shipping profile mapping opens.

  4. Select the XXXLutz shipping method.

  5. Select the PlentyONE shipping profile.

  6. Select the XXXLutz shipping service provider.

  7. Click save Save.
    → The new mapping is shown in the menu.
    Tip: You can edit the shipping profile mappings later on. To do so, click More (more_vert) and then on Edit mapping (edit).

Orders

Order import

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

Order import start date

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

Allow cancellations for orders with invoice

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

Note: At XXXLutz, customers cannot cancel orders with Pay on Acceptance.

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

Status for cancelled orders

Select the order status for orders that were cancelled.

Note: At XXXLutz, customers cannot cancel orders with Pay on Acceptance.

Offers

Offer export

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

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

6.4. Adjusting the general settings

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

Renaming a sales channel:

  1. Go to Sales Channels » Channel Control Centre.

  2. Open the sales channel for XXXLutz.
    → The Settings menu opens.

  3. Switch to the menu General settings.

  4. Enter a new Channel name.

  5. Click Save (save).
    → The new channel name is saved.

6.5. Activating the order referrer

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

What is an order referrer?

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

Activating the order referrer for XXXLutz:

  1. Go to Setup » Orders » Order referrer.

  2. Click Search (search).

  3. In the list, navigate to the option XXXLutz with the ID 179.00.

  4. On the right of the referrer’s line, click Edit (edit).
    → The window Edit referrer opens.

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

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

Note: If you want to sell your items on XXXLutz, then the parent referrer for XXXLutz must also be activated (179.00 XXXLutz). In addition, you have to activate the referrer for the XXXLutz country platform on which you want to sell your items. The following order referrers are available for XXXLutz:

  • 179.00 XXXLutz = Parent referrer for XXXLutz

  • 179.01 XXXLutz Germany = XXXLutz Germany

Example: If you want to sell your items on XXXLutz Germany, you have to activate the parent referrer for XXXLutz (179.00 XXXLutz) and the referrer for XXXLutz Germany (179.01 XXXLutz Germany).

7. Preparing variations

Now, prepare your variations.

7.1. Setting the variation availability

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

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

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

  1. Navigate to the area Market availability.

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

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

  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.

8. Exporting product data

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

What is a catalogue?

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

  • Marketplace formats are used to export item data to markets.

  • Standard formats are used to export data from your PlentyONE system into a file.

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

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

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

8.1. Adding product categories

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

Adding product categories:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Category whitelist.

  2. Click Add categories (add).

  3. Select a category for offering your items (check_box).
    Tip: You can either search the category by entering the name in the input field or you can expand the category tree to browse the available categories. Click Show categories (chevron_right) in the category tree to expand the available subcategories.

  4. Click SAVE (save).
    → The category was added. You can now create a product catalogue for this category in the Data » Catalogues menu.
    Tip: Once you have added at least two product categories, you can create a Channel map for these categories in the addSales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Mapping » Product mappingadd menu.

Which variations are exported to XXXLutz?

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

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

Creating a property of the type selection:

  1. Go to Setup » Settings » Properties » Configuration.

  2. Click add Create property.
    → The settings for the new property are displayed.

  3. In the Details section, select the section Items.

  4. In the Details section, select the type selection.

  5. Carry out the additional settings.
    → Tip: For example, you can use XXXLutz product category as name for the property.

  6. Click Save (save).
    → The property is created.

  7. In the section Selection values, click Create selection value.

  8. Enter a name for the selection value.
    → Tip: You can enter the different XXXLutz product categories as names for the selection values.

  9. Click Save (save).
    → The selection value is created and displayed in the overview. The value automatically receives a consecutive and unique ID that cannot be changed. You need this ID to only export specific variations in a catalogue.

Next, link the desired variations with the selection property that you created.

Link variation with property:

  1. Go to Item » Items.

  2. Open the variation that you want to link.

  3. Click the Properties tab.

  4. In the Properties section, click add Add properties.
    → The window Add properties opens.

  5. Select the newly created property (check_box).
    Tip: Use the search (search) or the filters (tune) to search for the new property.

  6. Click APPLY.
    → The property is added.

  7. Select the desired product category from the drop-down list Value.

  8. Click Save (save).

Afterwards, add the ID of the selection value as filter in the desired XXXLutz 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:

  1. Go to Data » Catalogues.

  2. Open the XXXLutz catalogue.

  3. On the left-hand side, open the tab Filters.

  4. In the Custom filters section, select the filter Linked to at least one property selection value.

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

  6. Click Save (save).

8.3. Creating a product catalogue

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

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

Create a catalogue for offers

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

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

Creating a product channel map:

  1. Open the menu Sales Channels » Channel Control Centre » [Name of your XXXLutz Sales Channel] » Mapping » Product mapping.

  2. Click on Create Channel map (add).

  3. Enter a name for the channel map.

  4. In the drop-down list Marketplace, select the option XXXLutz.

  5. In the drop-down list Catalogue type, select the option Product.

  6. In the drop-down list Categories, select the product categories you want to sell on XXXLutz.

  7. Click on CREATE CHANNEL MAP.
    → The channel map is created.

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

Linking a product catalogue to the channel map:

  1. Go to Sales Channels » Channel Control Centre » [Name of your XXXLutz sales channel] » Mapping » Product mapping.

  2. In the row of the channel map you want to edit, click on more_vert More and select Connect catalogues.

  3. In the drop-down list Select catalogues, click Create catalogue.

  4. Enter a name for the catalogue.

  5. In the drop-down list Marketplace, select the option XXXLutz.

  6. In the drop-down list Export type, select the option Item (New).

  7. In the drop-down list Categories, select the product categories in which you want to sell on XXXLutz.

  8. Click CREATE AND CONNECT TO CHANNEL MAP.
    → The catalogue is created and connected to the channel map.

8.3.1. Mapping data fields in the product catalogue

After you have created a catalogue, map the market’s data fields to item data saved in PlentyONE. This chapter describes how you map data fields and what particularities apply for product exports to XXXLutz.

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

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

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the tile of your XXXLutz Sales Channel.

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

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

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

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

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

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

  • I want to fill this marketplace data field with the data from this PlentyONE setting.

  • If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

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

gif catalogue mapping simple en
Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

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

Creating a property:

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

Creating a simple 1:1 mapping with properties:

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

  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.

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

catalogue complex mappings

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:

  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 field to.
    → The value is mapped.

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

  4. Click on a group.
    → The PlentyONE data fields of the group are shown.

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

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

gif catalogue mapping complex en
1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

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

So this mapping specifies:

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

  • If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.

  • If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

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

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

  • SKU

  • Barcodes

  • Sales prices

  • Properties

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

Empty

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

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

  • PlentyONE data fields that are available for variations by default

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

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

Creating a 1:1 mapping with fallback data fields:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

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

  5. Alternative 1: To add the fallback data field with the fallback condition "null":

    1. Click on Confirm.
      → The fallback data field is exported if the data field above is not linked to the variation.

  6. Alternative 2: To add the fallback data field with the fallback condition "empty":

    1. To the left of the fallback data field, click on the cog ().
      → The window Data column settings is shown.

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

    3. Click on Save.
      → The fallback data field is added with the fallback condition "empty".

    4. Click on Confirm.
      → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

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

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

gif catalogue mapping fallback en
1:n mapping: 1 marketplace data field, several PlentyONE data fields

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

So this mapping specifies:

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

Creating a 1:n mapping:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

  4. Click on Confirm.

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

  6. Map one or several additional PlentyONE data fields to the marketplace data field as described above.

  7. Click on Confirm.

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

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

  10. Click on Save.

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

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

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

So this mapping specifies:

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

Creating an own value mapping:

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

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

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

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

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

  • This function only works for data fields that contain numerical values.

  • This functionality is new and not available for all catalogue formats.

So this mapping specifies:

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

Recalculating numerical values:

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

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

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

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

  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.
    → The calculation will be carried out in the next export.

To help you with mapping your data fields for the catalogue, we have created a list of recommended data field mappings. Note that these mappings are recommendations only. Depending on how you manage your item data, other mappings may be more appropriate than the recommendations given here.

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

Note: You have to create a separate catalogue for each XXXLutz product category that you want to offer your items in.
Catalogues for different product categories contain different data fields. This is because different product data has to be specified in each XXXLutz product category.
However, some data fields are the same in each category. Only the recommended mappings for those data fields are described here.

List of recommended item mappings

  • You need more information on how to map items? Here are two examples of item mappings for different product categories. Only the mandatory fields are mapped in the examples. Note that these examples are recommendations only. Depending on how you manage your product data, other mappings may be more appropriate than the recommendations given here.

Example 1: Recommended mappings of mandatory fields for the category Sinks
Example 2: Recommended mappings of mandatory fields for the category Toys

8.3.3. Notes on mapping data fields

Requirements for texts, images, dimensions and weight

For XXXLutz there are requirements for text length, image size and how dimensions and weights have to be specified in the catalogues.

  • Dimensions, such as the Width, must be specified in the size unit Centimetres. A maximum of two decimal places are allowed.

  • The Weight must be given in the weight unit Kilogram. A maximum of three decimal places is allowed.

  • For images and texts, such as Name or Description, you can find detailed specifications in the Mirakl backend. Under Templates and documents, the following documents are available:

    • Style Guide XXXLutz Marketplace DE

    • Produktanlage XXXLutz Marketplace DE (product creation)

    • Angebotsanlage XXXLutz Marketplace DE (offer creation)

    • Taxonomie & Attribute XXXLutz Marketplace DE (taxonomy & attributes)

Exporting an image list

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

Data fields for image export to XXXLutz

  • Main picture

  • Secondary picture

  • Mood picture 1

  • Mood picture 2

  • Dimension image 1

  • Dimension image 2

  • Miscellaneous image 1

  • Miscellaneous image 2

  • Miscellaneous image 3

  • Miscellaneous image 4

  • Miscellaneous image 5

To export an image list, select one of the above data fields and map the image list as follows:

  • Image » Variation images » Image list, image information Full image URL
    or
    Image » Item images » Image list, image information Full image URL

  • Under Maximum number of images, enter the number of images you want to export from the image list.

The URLs of the images from the image list are automatically mapped to the next available image data fields in order.
Example: If the image list is mapped to the data field Mood picture 1 and contains three images:

  • The URL of the first image is mapped to the data field Mood picture 1,

  • the URL of the second image to Mood picture 2,

  • the URL of the third image to Dimension image 1.

Note: If a subsequent data field is already mapped, this data field is skipped. The image URL is then mapped to the next available empty image data field instead.
Important: Only as many images are mapped as the number of available following data fields for images. Excess images from the image list are not added.

Exporting item groups

You can use the Variant Group Code data field in the product catalogue to export different variations of a product as an item group to XXXLutz.

There are two options for the mapping:

  • Option 1: Map the Variant Group Code to the Item ID in PlentyONE

    • Select this option if the variations you want to export as an item group are located within one item in your PlentyONE system.

    • Map the Variant Group Code data field to the Item ID of the item in which the variations are located.

  • Option 2: Map the Variant Group Code to a property of the type Text

    • Select this option if the variations are located in different items and do not have a common item ID.

    • Create a property of the type Text, for example with the name Item_group.

    • Link the newly created property with the variations that you want to export as an item group.

    • For each item group, enter a unique property value in the text field on the variations, for example Item_group_1. This way you prevent that already exported variations are transferred again.

    • Map the Variant Group Code data field to the Item_group property.

Data fields with different mapping options

In the catalogues, you will find data fields that allow both simple and complex 1:1 mapping. This selection gives you the flexibility to adapt the mapping to the nature of your data.

Example: The data field Season type in the product catalogue

For the data field Season type, both a simple and a complex mapping are possible. If both options are marked as mandatory, you only need to configure one of them.

  • 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 products for the summer season and the season type Summer (value season_summer) 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 products for the spring and summer seasons at the same time and therefore need to transmit the season type Summer (value season_summer) as well as the season type Spring (value season_spring). The complex mapping allows you to react flexibly to different values for item settings or properties.

How does the simple mapping look like in this example?

If you want to transmit the season type Summer for all items:

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

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

  3. Enter the value season_summer 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, season_summer corresponds to the season type Summer at XXXLutz. You can find the list of valid values in the Mirakl backend.

xxxlutz simple mapping
How does the complex mapping look like in this example?

If you want to transmit the season type Summer for some items and the season type Spring for other items:

Create mapping for season type Summer:

  1. Click on the field for Season type.
    → A list of the available values is shown.

  2. Select the value Summer.
    → The value season_summer is mapped.

  3. Next to the marketplace data field, click add Add data source.
    → To the left, the available PlentyONE data fields are listed in groups.

  4. Under Property, click on the plus next to the property value you have created for the season.
    → The value is added to the field on the right.

  5. Click Confirm.

Create mapping for season type Spring:

  1. Click add Add Season type.

  2. Click on the field for Season type.
    → A list of the available values is shown.

  3. Select the value Spring.
    → The value season_spring is mapped.

  4. Next to the marketplace data field, click add Add data source.
    → To the left, the available PlentyONE data fields are listed in groups.

  5. Under Property, click on the plus next to the property value you have created for the season.
    → The value is added to the field on the right.

  6. Click Confirm.

xxxlutz complex mapping

You can find further details on the configuration of simple and complex mapping in the chapter Mapping data fields in the product catalogue.

8.3.4. Providing information on manufacturer and EU-responsible person (GPSR)

The General Product Safety Regulation of the EU (GPSR) requires manufacturers and sellers to ensure the product safety of certain goods and to provide certain information for this purpose. This information includes details about the manufacturer and, in the case of manufacturers without an establishment in the EU, details about the responsible person within the EU. The GPSR regulation ensures that products are safe and comply with consumer protection requirements before being placed on the market.

In this chapter, you will learn how to add information on the manufacturer and the responsible person within the EU in PlentyONE to comply with the GPSR regulation.

If you export your items to XXXLutz via catalogues, you can add the information on the manufacturer and the EU-responsible person directly via the data field mappings for items.

8.3.5. Activating the catalogue export

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

Activating the catalogue export to XXXLutz:

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

  2. Scroll to the XXXLutz 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 XXXLutz once a day.
    Tip: Go to Data » Catalogue export status for information about the status of the export.

9. Exporting offer data

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

What is a catalogue?

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

  • Marketplace formats are used to export item data to markets.

  • Standard formats are used to export data from your PlentyONE system into a file.

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

9.1. Creating an offer catalogue

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

Creating a catalogue:

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the XXXLutz tile.

  3. Go to Mapping » Offer mapping.

  4. Click Create catalogue (add).

  5. Enter a name for the catalogue.

  6. In the drop-down list Marketplace, select the option XXXLutz.

  7. In the drop-down list Export type, select the option Item (New).

  8. In the drop-down list Category, select Offer.

  9. 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 XXXLutz. 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 XXXLutz 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.

9.1.1. Mapping data fields in the offer catalogue

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

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

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

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the tile of your XXXLutz Sales Channel.

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

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

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

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

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

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

  • I want to fill this marketplace data field with the data from this PlentyONE setting.

  • If the data field is empty for a variation, no value is exported for this variation.

Creating a simple 1:1 mapping:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

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

gif catalogue mapping simple en
Simple 1:1 mapping: with properties: 1 marketplace data field, no PlentyONE data field

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

Creating a property:

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

Creating a simple 1:1 mapping with properties:

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

  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.

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

catalogue complex mappings

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:

  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 field to.
    → The value is mapped.

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

  4. Click on a group.
    → The PlentyONE data fields of the group are shown.

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

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

gif catalogue mapping complex en
1:1 mapping with fallback data fields: 1 marketplace data field, 1 PlentyONE data field with alternative(s)

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

So this mapping specifies:

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

  • If that data field is missing or empty for a variation, the first fallback data field is checked. The value of that fallback data field is exported instead.

  • If the first fallback data field is also missing or empty for the variation, the second fallback data field is checked. If a value is found, the value of the second fallback data field is exported for the variation etc.

Two separate fallback conditions are available:

Null (default)

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

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

  • SKU

  • Barcodes

  • Sales prices

  • Properties

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

Empty

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

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

  • PlentyONE data fields that are available for variations by default

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

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

Creating a 1:1 mapping with fallback data fields:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

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

  5. Alternative 1: To add the fallback data field with the fallback condition "null":

    1. Click on Confirm.
      → The fallback data field is exported if the data field above is not linked to the variation.

  6. Alternative 2: To add the fallback data field with the fallback condition "empty":

    1. To the left of the fallback data field, click on the cog ().
      → The window Data column settings is shown.

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

    3. Click on Save.
      → The fallback data field is added with the fallback condition "empty".

    4. Click on Confirm.
      → The fallback data field is exported if the data field above is empty for the variation.

Example: Fallback data field for SKU for Otto Market

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

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

gif catalogue mapping fallback en
1:n mapping: 1 marketplace data field, several PlentyONE data fields

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

So this mapping specifies:

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

Creating a 1:n mapping:

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

  2. Click on the group you need.
    → The PlentyONE data fields of the group are shown.

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

  4. Click on Confirm.

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

  6. Map one or several additional PlentyONE data fields to the marketplace data field as described above.

  7. Click on Confirm.

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

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

  10. Click on Save.

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

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

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

So this mapping specifies:

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

Creating an own value mapping:

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

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

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

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

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

  • This function only works for data fields that contain numerical values.

  • This functionality is new and not available for all catalogue formats.

So this mapping specifies:

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

Recalculating numerical values:

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

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

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

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

  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.
    → The calculation will be carried out in the next export.

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

List of recommended data field mappings for the format Offer

9.1.3. Notes on mapping data fields

Data fields with different mapping options

In the catalogues, you will find data fields that allow both simple and complex 1:1 mapping. This selection gives you the flexibility to adapt the mapping to the nature of your data.

Example: The data field Season type in the product catalogue

For the data field Season type, both a simple and a complex mapping are possible. If both options are marked as mandatory, you only need to configure one of them.

  • 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 products for the summer season and the season type Summer (value season_summer) 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 products for the spring and summer seasons at the same time and therefore need to transmit the season type Summer (value season_summer) as well as the season type Spring (value season_spring). The complex mapping allows you to react flexibly to different values for item settings or properties.

How does the simple mapping look like in this example?

If you want to transmit the season type Summer for all items:

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

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

  3. Enter the value season_summer 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, season_summer corresponds to the season type Summer at XXXLutz. You can find the list of valid values in the Mirakl backend.

xxxlutz simple mapping
How does the complex mapping look like in this example?

If you want to transmit the season type Summer for some items and the season type Spring for other items:

Create mapping for season type Summer:

  1. Click on the field for Season type.
    → A list of the available values is shown.

  2. Select the value Summer.
    → The value season_summer is mapped.

  3. Next to the marketplace data field, click add Add data source.
    → To the left, the available PlentyONE data fields are listed in groups.

  4. Under Property, click on the plus next to the property value you have created for the season.
    → The value is added to the field on the right.

  5. Click Confirm.

Create mapping for season type Spring:

  1. Click add Add Season type.

  2. Click on the field for Season type.
    → A list of the available values is shown.

  3. Select the value Spring.
    → The value season_spring is mapped.

  4. Next to the marketplace data field, click add Add data source.
    → To the left, the available PlentyONE data fields are listed in groups.

  5. Under Property, click on the plus next to the property value you have created for the season.
    → The value is added to the field on the right.

  6. Click Confirm.

xxxlutz complex mapping

You can find further details on the configuration of simple and complex mapping in the chapter Mapping data fields in the offer catalogue.

9.1.4. Activating the catalogue export

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

Activating the catalogue export to XXXLutz:

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

  2. Scroll to the XXXLutz catalogue.

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

10. Manually exporting product and offer data

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

Note: To appear in the drop-down list for manual export, the catalogue must be linked to an account under Data » Catalogues » [Open catalogue] » Tab: Basic settings » Section: Basic settings.
In the Data export menu, you can already export data even if the account has not been activated yet. This way, you can test the export with individual items and offers before you activate the account and exchange data with XXXLutz.

Manually exporting an item:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Settings » Data exchange » Data export.

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

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

  4. Enter one or more Item IDs separated by comma. Those items will then be exported to XXXLutz.

  5. Click 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 Preview to generate e preview of the export.

Manually exporting offers:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Settings » Data exchange » Data export.

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

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

  4. Enter one or more Item IDs separated by comma. The offers for those items will then be exported to XXXLutz.

  5. Click file_upload Export.
    Note: You can run this process every 15 minutes.
    Tip: Click Preview to generate e preview of the export.

11. Managing listings

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

11.1. Offer listings

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

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

  • menu gives you an overview of all the offer listings.

  • folder shows you the listing groups of the offer listings. Extend a listing group by clicking chevron_right, to see all listings within the group.

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

Applying filters:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel] » Offer listings.

  2. Click Filters (tune) at the top of the menu.

  3. Select one or multiple filters.

  4. Click Search (search).
    → The selected filters are applied and the appropriate offer listings are displayed.
    → The filters that were applied are displayed at the top of the menu.

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

  • Single listing view

  • Group view

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

Table 5. Offer listings overview
Column Explanation

Data sync

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

Group ID

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

Listing Name

Name of the offer listing.

SKU

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

Variation ID

ID of the variation.

Channel

The sales channel to which the listing is exported.

Status on Channel

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

  • help = Unknown

  • progress_activity = Outstanding

  • progress_activity = Creation pending

  • cancel = Failed (before creation)

  • check_circle = Online

  • cancel = Failed (on update)

  • pause_circle = Paused

  • unpublished = Offline

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

List on

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

Errors

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

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

Creation date

The date and time on which the listing was created.

more_vert

Click here to display more actions.

toggle_on Activate data sync

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

delete Delete listing

delete Delete listing

preview Preview export results

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

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

Table 6. Group view of the offer listings
Column Explanation

Data sync

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

Group name

Name of the listing group

SKU

SKU of the listing group.

Channel

The sales channel to which the listing group is exported.

Errors

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

Template

The template selected for the listing group.

Catalogue

The catalogue selected for the listing group.

Creation date

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

more_vert

Click here to display more actions.

toggle_on Activate data sync

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

delete Delete listing group

Delete listing group.

preview Preview export results

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

11.2. Product listings

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

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

  • menu gives you an overview of all the product listings.

  • folder shows you the listing groups of the product listings. Extend a listing group by clicking chevron_right, to see all listings within the group.

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

Applying filters:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel] »Product listings.

  2. Click Filters (tune) at the top of the menu.

  3. Select one or multiple filters.

  4. Click Search (search).
    → The selected filters are applied and the appropriate product listings are displayed.
    → The filters that were applied are displayed at the top of the menu.

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

  • Single listing view

  • Group view

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

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

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

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

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

| *Listing Name*
| Name of the listing.

| *Variation ID*
| ID of the variation.

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

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

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

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

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

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

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

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

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

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

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

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

! material:preview[] *Preview export results*
! Generates the preview of the export results. The preview opens in a separate window.
!====
|===
<<#table-product-listings-group-view>> offers an overview of the group view of product listings.

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

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

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

| *Group name*
| Name of the listing group

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

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

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

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

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

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

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

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

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

11.3. Creating listings

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

What are product listings and offer listings used for?

  • If the item you want to sell is not listed on the sales channel yet you will need to create a product listing for it first. Creating a product listing sends the product data to the sales channel and allows for the item to be listed.
    In order to actually be able to sell the item on the sales channel you will need to additionally create an offer listing. The offer listing contains data related to the sale of the item, such as its price and stock. In other words, a product listing allows you to list an item on a sales channel that did not previously exist on that sales channel, but in order to sell that item on that sales channel you also need an offer listing for that item.

  • If the item you want to sell is already listed on the sales channel you only need to create an offer listing. Offer listings send the data related to your offer, such as the price, stock, shipping costs etc., to the sales channel.
    In most cases you will only need an offer listing in order to offer a product on a sales channel. Many sales channels do not differentiate between product and offer listings. You only need to send offer listings to these kinds of sales channels.

11.3.1. Create product listings

Product listings are created in three steps:

  • First, you enter listing details, meaning you select the platform, template, and catalogue for the listing.

  • Next, you select the variations from which the product listings are created.

  • Lastly, check and confirm your selection and create the listings.

Create product listings using the group function

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

Step 1: Specify listing details:

  1. Go to Sales Channels » Channel Control Center.

  2. Open the account for XXXLutz.
    → The Settings menu opens.

  3. Open the menu format_list_bulleted Product listings.

  4. Click on add Create products.
    → The view Create products opens.

  5. Select the platform XXXLutz.

  6. Select the template for the catalogue.

  7. Select a catalogue with your mapping for item data.
    Tip: If you have no fitting catalogue yet, click on add Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.

  8. Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to XXXLutz after the listing is created.

  9. Click arrow_forward NEXT.
    → The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

  1. Select the variations you want to create the product listing for.
    Tip: Use the search to filter for variations.
    Note: Only variations that are linked to XXXLutz in the Item » Items » [Open item] » [Open variation] menu are displayed.
    Tip: If you want to create a product listing for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Product listings can be created for a maximum of 50,000 variations at a time.

  2. Click add ADD TO SELECTED VARIATIONS.
    → The selected variations are displayed in the Selected variations section.
    Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.

  3. Click arrow_forward NEXT.
    → The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

  1. Preview your settings in the Listing details section.

  2. Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group (chevron_right) to see which variations are contained in the respective listing group.

  3. If everything is set and done, click save CREATE PRODUCT LISTINGS.
    Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click check CONFIRM to create the product listings.

11.3.2. Activating product listings

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

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

Activating product listings:

  1. Go to Sales Channels » Channel Control Center » [Open XXXLutz].
    → The Settings menu opens.

  2. Open the Product listings menu.

  3. In the line of the product listing you want to activate, click more_vert.

  4. Click toggle_on Activate data sync.
    Tip: If you want to activate multiple product listings at once, place a check mark next to the desired product listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
    → The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

  1. Go to Sales Channels » Channel Control Center » [Open XXXLutz].
    → The Settings menu opens.

  2. Open the Product listings menu.

  3. Open the listing group view (folder).

  4. In the line of the listing group you want to activate, click more_vert.

  5. Click toggle_on Activate data sync.
    Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
    → The data exchange for the listing group is activated.

11.3.3. Creating offer listings

Offer listings are created in three steps:

  • First, you enter listing details, meaning you select the platform, template, and catalogue for the listing.

  • Next, you select the variations from which the offer listings are created.

  • Lastly, check and confirm your selection and create the listings.

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

Step 1: Specify listing details:

  1. Go to Sales Channels » Channel Control Centre.

  2. Open the account for XXXLutz.
    → The Settings menu opens.

  3. Open the menu format_list_bulleted Offer listings.

  4. Click add arrow_drop_down and select Create offers.
    → The Create offers view opens.

  5. Select the platform XXXLutz.

  6. Select the template for the catalogue.
    Tip: Only templates that are available for the platform XXXLutz are displayed.

  7. Select a catalogue with your mappings for offer data.
    Tip: If you have no fitting catalogue yet, click on add Create catalogue. You will be forwarded to the Data » Catalogues menu and can create a catalogue.

  8. Optional: Activate Automatically activate listings after creation, if listing data should be automatically transferred to XXXLutz after the listing is created.

  9. Click arrow_forward NEXT.
    → The Select variations view opens. Next, select the variations you want to add to the listing.

Step 2: Select variations:

  1. Select the variations you want to create the offer listing for.
    Tip: Use the search to filter for variations.
    Note: Only variations that are linked to XXXLutz in the Item » Items » [Open item] » [Open variation] menu are displayed.
    Tip: If you want to create offer listings for all available variations, click on Click here to create listings for all [] variations above. You will be automatically redirected to the Preview and confirmation step. Offer listings can be created for a maximum of 50,000 variations at a time.

  2. Click add ADD TO SELECTED VARIATIONS.
    → The selected variations are displayed in the Selected variations section.
    Note: If you check a variation in the Selected variations section, you can remove the variation from the selection by clicking Remove from list.

  3. Click arrow_forward NEXT.
    → The selected variations will be displayed in a new view. In the last step, you preview and confirm your selection.

Step 3: Preview and confirm selection:

  1. Preview your settings in the Listing details section.

  2. Preview your selected variations in the Listing preview section. The listings are grouped by items. Extend a listing group (chevron_right) to see which variations are contained in the respective listing group.

  3. If everything is set and done, click save CREATE OFFER LISTINGS.
    Note: If you activated Automatically activate listings after creation a window with a summary of your settings opens. Click check CONFIRM to create the offer listings.

11.3.4. Activating offer listings

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

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

Activating offer listings:

  1. Go to Sales Channels » Channel Control Centre » [Open XXXLutz].
    → The Settings menu opens.

  2. Open the Offer listings menu.

  3. In the line of the offer listing you want to activate, click more_vert.

  4. Click toggle_on Activate data sync.
    Tip: If you want to activate multiple offer listings at once, place a check mark next to the desired offer listings and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
    → The data exchange for the listing is activated. The listing can only be transferred to the sales channel if the listing group is also activated.

Activating a listing group:

  1. Go to Sales Channels » Channel Control Centre » [Open XXXLutz].
    → The Settings menu opens.

  2. Open the Offer listings menu.

  3. Open the listing group view (folder).

  4. In the line of the listing group you want to activate, click more_vert.

  5. Click toggle_on Activate data sync.
    Tip: If you want to activate multiple listing groups at once, place a check mark next to the desired listing groups and click toggle_on arrow_drop_down » Activate data sync at the top of the toolbar.
    → The data exchange for the listing group is activated.

11.3.5. Viewing listing errors

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

Here you can see:

  • the affected listings

  • error details

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

Table 7 contains an overview of listing errors.

Table 7. Listing errors of offer listing and product listings
Column Explanation

keyboard_arrow_down [Information about the error]

Information about the error is provided here. It contains the affected field of the data record, a brief description of the error and the number of listings for which this error has occurred.
Example: "Field: gtin Error: Given data is not a string. (1)"
→ The error occurred in the gtin field of the data record.
→ The error occurred because no character string was entered as a value in the gtin field.
→ The error has occurred for one listing.

download Download data as CSV

The CSV file with the data records is downloaded.

Listing name

The name of the listing.

Parent SKU

The parent SKU of the main variation.

SKU

The SKU of the sub-variation.

Variation ID

The ID of the variation.

Channel

The sales channel to which the listing is exported.

Export activity

Shows whether the variation is being exported.

  • Active (circle) = The variation is exported with the listing.

  • Not active (circle) = The variation is not exported with the listing.

Status

The listing’s status on the sales channel.

Possible statuses are:

  • help = Unknown

  • progress_activity = Outstanding

  • progress_activity = Creation pending

  • cancel = Failed (before creation)

  • check_circle = Online

  • cancel = Failed (on update)

  • pause_circle = Paused

  • unpublished = Offline

Errors

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

Template

The template selected for the listing.

Catalogue

The catalogue selected for the listing.

12. Manually importing orders

In the Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Settings » Data exchange » Order import menu, you can manually import individual orders into PlentyONE. This can be helpful if you have to import missing orders.
You can either enter the order IDs of the orders you want to import, or you can import orders from a specific date.

Note: You can run this process every 15 minutes.

  • Entering order IDs

  • Selecting a time frame

Import orders by ID:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Settings » Data exchange » Order import.

  2. Click the tab Import orders by order ID.

  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 Import.
    → The orders are imported into PlentyONE.

Import orders by date:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Settings » Data exchange » Order import.

  2. Click the tab Import orders by date.

  3. Enter a start date in the format D.M.YYYY or select a date via the calendar (today).

  4. Enter an end date in the format D.M.YYYY or select a date via the calendar (today).

  5. Click Import.
    → Orders from the selected time frame are imported into PlentyONE.

13. Automating order processing

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

  • Inform XXXLutz that the order was accepted. (How?)

  • Inform XXXLutz that the order was rejected. (How?)

  • Automatically inform XXXLutz that the items have been shipped. (How?)

  • Automatically upload invoices to XXXLutz. (How?)

  • Automatically inform XXXLutz that an item was refunded. (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.

13.1. Report order confirmation to XXXLutz

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

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 order confirmations to XXXLutz
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order created

For Order types, select the type Incomplete order.

Controls

Branch

  • Object type: Order

  • Filter settings for the branch:

Note: If you want to use multiple filters, add the additional filters as conditions (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 XXXLutz country platforms that you want to use this flow for.

Actions

Plugin (Legacy) > Xxxlutz

Accept incomplete order on XXXLutz

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

13.2. Report order rejection to XXXLutz

Create an event-based flow to automatically inform XXXLutz about the rejection 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 9.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

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

  3. Configure the new flow according to Table 9.

  4. Save () the settings.

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

Table 9. Event-based flow to report order rejections to XXXLutz
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order created

For Order types, select the type Incomplete order.

Controls

Branch

  • Object type: Order

  • Filter settings for the branch:

Note: If you want to use multiple filters, add the additional filters as conditions (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 XXXLutz country platforms that you want to use this flow for.

Actions

Plugin (Legacy) > Xxxlutz

Decline incomplete order on XXXLutz

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

13.3. Uploading shipping confirmations to XXXLutz

Create an event-based flow to automatically inform XXXLutz 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 10.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

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

  3. Configure the new flow according to Table 10.

  4. Save () the settings.

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

Table 10. Event-based flow for uploading shipping confirmations to XXXLutz
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order status changed

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 XXXLutz country platforms that you want to use this flow for.

Actions

Plugin (Legacy) > Xxxlutz

Upload shipping confirmation to XXXLutz

13.4. Automatically uploading invoices to XXXLutz

Create an event-based flow to automatically upload invoices to XXXLutz.

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 11.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

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

  3. Configure the new flow according to Table 11.

  4. Save () the settings.

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

Table 11. Event-based Flow for uploading invoices to XXXLutz
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Document > Document created

Note: Select an event after which the items have already been shipped.

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 referrer

Is in (IN)

Select the order referrers for the XXXLutz country platforms that you want to use this flow for.

Actions

Plugin (Legacy) > Xxxlutz

Upload invoice to XXXLutz

13.5. Reporting refunds to XXXLutz

Create an event-based Flow to automatically inform XXXLutz that an item was refunded.

Different flows can be created, depending on the reason for the refund. The following flows are available for XXXLutz to report a refund:

  • Report refund to XXXLutz: Agreement found between customer and seller

  • Report refund to XXXLutz: Agreement with vendor

  • Report refund to XXXLutz: Cancelled before shipping

  • Report refund to XXXLutz: Chargeback by the customer’s bank

  • Report refund to XXXLutz: Item not received

  • Report refund to XXXLutz: Item returned

  • Report refund to XXXLutz: No response from the shop

  • Report refund to XXXLutz: Out of stock

  • Report refund to XXXLutz: PayPal decision in favor of the customer

To report refunds to XXXLutz, a credit note must be created. If it is a full refund, a credit note for all order items of the parent order must be created. For a partial refund, a partial credit note that only contains the affected order items must be created. In a partial credit note, you can also specify that only a certain amount is refunded.
Carry out the Flows listed in this section for the credit note you have created.

How do I create a credit note for a full refund?

  1. Go to Orders » Orders.

  2. Carry out the search (search) to display orders.

  3. Open the order for which a credit note should be created.

  4. At the top, click Create orders (shopping_cart) > Credit note.

  5. Select the option For all order items.

  6. Click Save (save).
    → The credit note order is created.

  7. Carry out the appropriate flow for this order.

How do I create a credit note for a partial refund?

  1. Go to Orders » Orders.

  2. Carry out the search (search) to display orders.

  3. Open the order for which a credit note should be created.

  4. At the top, click Create orders (shopping_cart) > Credit note.

  5. Select the option For specific order items.

  6. Under Quantity, enter the quantity of order items for which a credit note should be created.

  7. Click Add items to shopping cart (add_shopping_cart) to the right of the relevant item.

  8. Under Price, enter the amount to be refunded for the order item.

  9. Click Save (save).
    → The credit note order is created.

  10. Carry out the appropriate flow for this 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 12.
        Note: If the trigger event has additional settings, then these are invariably mandatory. Without performing these settings, you will not be able to save the flow.

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

  3. Configure the new flow according to Table 12.

  4. Save () the settings.

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

Table 12. Event-based flow to report refunds to XXXLutz
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order created

For Order types, select the type Credit note.

Controls

Branch

  • Object type: Order

  • Filter settings for the branch:

Note: If you want to use multiple filters, add the additional filters as conditions (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 XXXLutz country platforms that you want to use this flow for.

Actions

Plugin (Legacy) > Xxxlutz

Select an action for Report refund to XXXLutz with the appropriate reason.

14. Download reports

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

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

Table 13. Reports for XXXLutz in the Channel Control Centre
Column Explanation

Date

Creation date of the report in the format YYYY.MM.DD hh:mm:ss

Status

The processing status of the report.
Reports can have the following statuses:

  • PENDING = The report has not been processed yet.

  • COMPLETE = The report was processed.

Integration Details

The number of imported products or offers.

Transform Lines

The number of rows in the report in which no errors occurred and the number of rows in which errors occurred.

Download

Download report (file_download): The report is downloaded.

Downloading a report:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for XXXLutz] » Reports.

  2. Click Filters (tune) at the top of the menu.

  3. Select a report type. The available report types are listed in Table 14.

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

  5. Click Download report (file_download).
    → The report is downloaded.

Table 14. Report types
Report type Explanation

Offers

The offer report contains information on the offer export to XXXLutz.

Products

The product report contains information on the item export to XXXLutz.

15. Viewing the data log

Events in your system are logged in the menu Data » Log. This allows you to check the data log for errors without relying on our support.

Viewing the data log:

  1. Go to Data » Log.

  2. Click Filters (tune) at the top of the menu.

  3. In the Identifier field, enter the option XXXLutz.

  4. Optional: Select a date if you only want to see entries for a specific day.

  5. Click SEARCH (*) to display the results.