bol.com (Setup via Channel Control Centre)

The Dutch market bol.com is the leading online market in Benelux and offers many different products, including multimedia, electronics, toys, etc. On bol.com, you can sell your items in the Netherlands and Belgium.

Channel Control Centre

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

1. Frequency of data exchange

After you have set up the interface to bol.com, the automatic processes described in [data-exchange] are available.

Table 1. Frequency of data exchange
Data Interval

Item export

once a day

Stock synchronisation

Every 15 minutes

Price synchronisation

hourly

Synchronisation of delivery times, visibility of offers etc.

hourly

Deletion of offers for deleted or deactivated variations

daily

Order import

Every 15 minutes

Import of returns registered on bol.com

hourly
Note: Returns are imported with the status [9.00] by default.

2. Registering with bol.com

Before setting up bol.com in PlentyONE, you have to register with bol.com.

3. Setting up bol.com in PlentyONE

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

3.1. Sales channel overview

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

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

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

Name

The name of the sales channel.

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

3.2. Adding the sales channel

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

  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 bol.com.
    → The sales channel for bol.com is added.

3.3. Carrying out the basic settings

The basic settings for bol.com are carried out in the menu Sales Channels » Channel Control Center » [Open sales channel for bol.com] within an assistant.

Carrying out the basic settings for bol.com:

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the tile for bol.com.
    → The tab General settings opens.

  3. Switch to the Settings tab.
    → The assistant for the bol.com basic settings opens.

  4. Follow the instructions on the screen. If you need more information about the options, see [einstellungen-bol-com] below.

  5. In the Summary step, check your settings to make sure they are correct.
    Tip: In the Summary step, click the arrow (chevron_forward) to show the settings.

  6. If everything is correct, click FINALISE.

Setting Explanation

Step Settings

Select the client that should be used to sell your items.

From the drop-down list Client, select a client. This client is used to generate the item URL in the catalogue and bol.com orders are assigned to this client.

Would you like to activate your bol.com user account?

check_box_outline_blank = The settings are saved but the data exchange with bol.com is not started.
check_box = Data exchange with bol.com is started once the assistant is completed.
Recommendation: Check all settings before activating the user account.

Step Access data

Enter the API access data.

The API access data can be generated in the seller section at bol.com.

  • Client ID (mandatory) = Enter the user ID for the API interface you received from bol.com.

  • Client Secret (mandatory) = Enter the password for the API interface that you received from bol.com.

Step Validating access data

Is the access data correct?

It is checked whether your API access data for bol.com is correct. The field Status of validation shows whether the access data is correct. If the access data is invalid, then enter it once again in the step Access data.

Step Event procedure status changes

Select an order status after an event procedure was executed

Select an order status that orders should move to after an event procedure was executed. Select two order statuses for each event procedure: one status that orders should move to after a successful event procedure and one status that orders should move to after an event procedure has failed. If orders should not change their statuses after an event procedure, then select No status change.

Select statuses for the following event procedures:

  • Send order cancellation to bol.com

  • Send order shipping confirmation to bol.com

  • Send return status to bol.com

  • Create a return at bol.com

  • Upload invoice to bol.com

Step Warehouse

Select how stock for bol.com should be calculated.

Select the stock quantity for the offer export. Select one of the following options:

  • Use stock quantity sum of all sales warehouses

  • Use main warehouse of item

  • Select warehouses = Select one or more warehouses.
    → The warehouses listed under Warehouses can be selected. Place a check mark to select a warehouse.

Important: The option Warehouse selection affects the item export. If an item is not linked to the warehouses selected here, then this item will not be exported.

Step Delivery times

Link bol.com delivery times

Link one or more bol.com delivery times with delivery times saved in PlentyONE. The linked delivery times will be shown with your items on bol.com.

3.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 bol.com.
    → 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.

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

  1. Go to Setup » Orders » Order referrer.

  2. Click Search (search).

  3. In the list, navigate to the option bol.com with ID 152.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.

3.6. Setting the variation availability

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

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

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 bol.com 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 bol.com 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 bol.com using batch processing:

  1. Navigate to the area Market availability.

  2. Activate the checkbox to the left of the option bol.com.

  3. Activate the checkbox to the right of the option bol.com.

  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.

3.7. Selecting the sales price

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

What is a sales price?

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

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

Defining a sales price for bol.com:

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

  2. Activate the referrer bol.com.

  3. Save () the settings.

3.8. Permitting the payment method in a customer class

The payment method bol.com is automatically available in your PlentyONE system as soon as an active bol.com account exists. No separate configurations are needed for this. You just need to permit the payment method in one or more customer classes.

What are customer classes?

Customer classes allow you to divide your customer base according to specific criteria. Examples of use for customer classes are:

  • Create two separate customer classes for end customers (B2C) and business customers (B2B) respectively. Depending on the customer class, customers either see net prices or gross prices in your plentyShop.

  • Give discounts to specific customer classes.

For more information about customer classes, head over to the to the Managing contacts page.

Permitting the payment method in a customer class:

  1. Go to Setup » CRM » Customer classes.

  2. Open the customer class for which you want to permit the payment method.

  3. For the setting Allowed payment methods, activate the option bol.com.

  4. Save () the settings.

3.9. Preparing shipping settings

Next, carry out settings for shipping. For bol.com, you have to save the shipping provider names in Dutch and activate the order referrer bol.com in the shipping profiles that you want to use for bol.com.

3.9.1. Saving names for shipping service providers in Dutch

For bol.com, you have to enter an API transporter code as name for the shipping service provider. In addition, the name of the shipping service provider has to be saved in Dutch. These settings are carried out in the Setup » Orders » Shipping » Settings menu.

Saving names for shipping service providers:

  1. Go to Setup » Orders » Shipping » Settings.

  2. Click on the Shipping service provider tab.

  3. In the Filters section, select the language nl from the Language drop-down list.

  4. Click Search (search).
    → The shipping service providers are displayed.

  5. In the input field Name (nl), enter the API transporter code for every shipping service provider that you want to use for bol.com.
    Tip: The API transporter codes for the shipping service providers can be found in the developer documentation for bol.com.

  6. Save () the settings.
    → The Dutch names for bol.com shipping service providers were saved.

3.9.2. Activating the referrer in shipping profiles

Now activate bol.com in the shipping profiles that you want to offer for this market.

Activating referrer bol.com in the shipping profile:

  1. Go to Setup » Orders » Shipping » Settings.

  2. Click on the Shipping profiles tab.

  3. Click on the shipping profile.
    Tip: No shipping profiles? Learn how to create shipping profiles here.

  4. For the setting Order referrer, activate the option bol.com.

  5. Save () the settings.
    → The shipping profile is available for orders with the referrer bol.com.

  6. If desired, activate the referrer in additional shipping profiles.

Saving shipping service provider names in Dutch

Make sure that the names for the shipping service providers in the shipping profiles for bol.com are saved in Dutch with the API transporter codes required by bol.com.

4. Preparing variations

Continue with preparing your variations.

4.1. Saving mandatory item information

In order to list a variation as an offer on bol.com, you need to save at least the settings described in Table 3 for this variation.

Table 3. Mandatory fields for the variation
Mandatory data Explanation

EAN or ISBN

An EAN or an ISBN must be saved for the variation.

  • In the Setup » Item » Barcode menu, an EAN or ISBN must be created and linked to the referrer bol.com.

  • The EAN/ISBN must be added to the Barcodes section in the variation’s Product details tab and a barcode code must be entered.

Price

A price must be saved for the variation.

  • The sales price must be activated for the referrer bol.com in the Setup » Item » Sales prices.

  • The sales price must be added in the Sales prices section of the variation.

  • A price must be saved for the sales price in the Sales prices section in the variation’s Pricing tab.

Name

A name in the language of the target country must be saved for the variation.
Example: If you want to sell your items in the Netherlands, a name in the language Dutch must be saved for the variation.

  • In the catalogue, a name must be saved in the PlentyONE data field that you mapped to the marketplace data field for the name.

Item description

A description in the language of the target country must be saved for the variation.
Example: If you want to sell your items in the Netherlands, a description in the language Dutch must be saved for the variation.

  • In the catalogue, a description must be saved in the PlentyONE data field that you mapped to the marketplace data field for the description.

Manufacturer

A manufacturer must be saved for the variation.

  • In the catalogue, a manufacturer must be saved in the PlentyONE data field that you mapped to the marketplace data field for the manufacturer.

Image

The variation must have at least one image.

  • At least one image must be linked in the Image tab of the variation.

  • In the Details section within the Images tab of the item, the option bol.com must be selected from the drop-down list Availability.

Property value for bol.com category

The variation must be linked to the property value for the bol.com category. The property bol.com category is created automatically when you complete the assistant.

  • In the Properties tab of the variation, the property for the bol.com category must be linked. The property value has the same name as the bol.com category and the catalogue.

Availability

The variation must be available for the market.

  • In the Sales channels tab of the variation, the sales channels bol.com or bol.com FBB have to be added.

    • Referrer bol.com = You ship orders yourself.

    • Referrer bol.com FBB = bol.com ships the order.

Condition

  • In the section Settings within the tab General of the item, a Condition for API must be saved. This condition for API is automatically exported during the offer export.

The PlentyONE conditions are mapped to the bol.com API conditions like this:

  • 0 New = NEW

  • 1 Used but as new = AS_NEW

  • 2 Used but very good = GOOD

  • 3 Used but good = MODERATE

  • 4 Used but acceptable = REASONABLE

After you created the first marketplace format for bol.com with the assistant, the property bol.com category is created in your PlentyONE system. For each bol.com category that you create a catalogue for, a new selection value is added to this property bol.com category. This property value has the same name as the bol.com category and the catalogue.

In order for your variations to be exported in the appropriate catalogue, they have to be linked to the bol.com category property in the Properties tab of a variation.

Linking variation to bol.com category:

  1. Go to Item » Items.

  2. Open the variation that you want to link.

  3. Switch to the Properties tab.

  4. In the Properties section, click add Add properties (add).

  5. Select the bol.com category property and click APPLY.
    → The property is added.

  6. Select a category from the drop-down list Value for the property bol.com category.
    → The variation will be exported in this catalogue.

  7. Click Save (save).

4.3. Optional: Activating variations for Fulfillment by bol.com (FBB/LVB)

bol.com orders can be fulfilled in two different ways:

  • Fulfilment by Retailer (FBR) = You ship the order yourself.

  • Fullfilment by bol.com (FBB/LVB) = bol.com ships your products.

Note that PlentyONE does not fully support Fulfilment by bol.com. You can flag your item data for Fulfilment by bol.com when you export item data to the market. However, FBB orders and returns are not imported into PlentyONE. In addition, stock information cannot be retrieved from the bol.com fulfilment warehouse.

To sell a variation with Fulfilment by bol.com (FBB or LVB), you need to activate the market availability bol.com FBB.

Activate the market availability bol.com FBB for the variation

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

  2. Switch to the Sales channels tab.

  3. In the section Sales channels, select the option bol.com FBB (check_box).

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

  5. Confirm the pop-up by clicking ACTIVATE.

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

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

To comply with the requirements of the GPSR regulation, bol.com requires that each offer is linked to an Economic Operator within the EU. This Economic Operator contains the information on the manufacturer and EU-responsible person required by the GPSR regulation.

In PlentyONE, the Economic Operator is assigned via a property. The information on the responsible person within the EU are taken from the manufacturer data.

Setup is carried out in two steps:

  1. Enter the required manufacturer data in the menu Setup » Item » Manufacturers.

  2. Create the property Economic Operator Name and link it to the variations.

Proceed as follows to enter the required information and transfer it to bol.com:

5.1. Step 1: Entering manufacturer data

Entering manufacturer data:

  1. Go to Setup » Item » Manufacturers.

  2. You have filled in the required fields for the EU-responsible person for each of your manufacturers.

  3. Click Save (save).

  4. Select the manufacturer at item level to transfer the manufacturer data to bol.com.

  5. Click Save (save).

Note:

  • If the fields for the EU-responsible person are filled in, these data are used for the Economic Operator.

  • If the fields for the EU-responsible person are not filled in, the information on the manufacturer is used instead.

  • Changes to the manufacturer data for the Economic Operator are exported hourly.

Table 4. Required fields for information on the EU responsible person
Field name Beschreibung

EU Responsible Name

Enter the name of the EU-responsible person.

EU Responsible Street

Enter the street of the EU-responsible person.

EU Responsible House No Enter the house number of the EU-responsible person.

EU Responsible Post Code

Enter the postcode of the EU-responsible person.

EU Responsible Town

Enter the town of the EU-responsible person.

EU Responsible Country

Enter the country of the EU-responsible person.

EU Responsible Email

Enter the email address of the EU-responsible person.

EU Responsible Phone number

5.2. Step 2: Creating and linking the property for the Economic Operator

Prerequisites

Creating and linking the property in PlentyONE:

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

  2. Create a new property with the name Economic Operator Name.
    Important: The name of the property must not be changed, otherwise it will not be assigned to an Economic Operator in bol.com.

  3. Carry out the following settings:

    • In the drop-down list Section, select the option Items.

    • In the drop-down list Type, select the option Text.

    • In the section Groups, select the appropriate group for bol.com from the drop-down list.

  4. Link the property with the variations for which you need an Economic Operator.

  5. In the Text for Economic Operator Name field, enter exactly the name you specified as the Economic Operator Name in the partner portal.
    Important: The name must match the Economic Operator Name in bol.com and the manufacturer name in the menu Setup » Item » Manufacturers exactly. Only then the variation is assigned to the corresponding Economic Operator on bol.com.
    Example: If you have entered the manufacturer name Exclusive Leather under Economic Operator Name in bol.com, you must also enter the manufacturer name Exclusive Leather under Text for Economic Operator Name when linking the property to the variation in PlentyONE.

Do not link the Economic Operator directly in bol.com

After you have created the Economic Operator in bol.com, you must not link it directly to your items in bol.com. Otherwise, the data entered for the Economic Operator in bol.com will be overwritten with the information stored in PlentyONE during the daily export.

6. Exporting product data

Product data is exported to bol.com using catalogues. Catalogues for bol.com are created with the assistant bol.com - Creating catalogues. To do so, go to Sales Channels » Channel Control Centre » [Open sales channel for bol.com] » Mapping » Product mapping and click Create catalogue (add). You are then forwarded to the assistant bol.com - Creating catalogues in the Setup » Assistants menu.

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.

6.1. Creating a catalogue in the assistant

You need to create a separate catalogue for each combination of a bol.com category and a language.
Tip: In the catalogue, the language is shown in brackets behind the category name.

Creating a catalogue:

  1. Go to Sales Channels » Channel Control Centre » [Open sales channel for bol.com] » Mapping » Product mapping.

  2. Click Create catalogue (add).
    → You are then forwarded to the assistant bol.com - Creating catalogues in the Setup » Assistants menu.

  3. In the step Category and platform, select a category for your catalogue.

  4. Click on NEXT.

  5. In the step Summary, check your settings to make sure they are correct.
    Tip: In the step Summary, click the arrow (chevron_right) to show the settings.

  6. If everything is correct, click FINALISE.
    → The catalogue is created.

  7. Open the catalogue in the Data » Catalogues menu to assign PlentyONE data fields to the corresponding sales channel data fields.
    Note: You need to create a separate catalogue for each combination of a bol.com category and a language.

6.2. Mapping data fields in the catalogue

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

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

Getting to know the catalogue menu for marketplace formats
catalogue menu colours
Availability Explanation

Navigation

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

  • Switch to other views of the catalogue.

  • Open the catalogue settings.

  • Use filters that limit the data that is exported.

  • Go back to the list of catalogues.

  • Create a new catalogue.

Toolbar

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

Live preview

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

Marketplace data field

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

PlentyONE data sources

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

Mapping catalogue fields:

  1. Go to Data » Catalogues.

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

  3. Map suitable PlentyONE data sources to the market data fields.
    For each marketplace data field, you have a number of mapping options. Expand the info boxes below to get more information about each of these mapping options.

    • Simple 1:1 mapping

    • Simple 1:1 mapping with properties

    • Complex 1:1 mapping

    • 1:1 mapping with fallback data sources

    • 1:n mapping

    • Own value mapping

    • Mapping with mathematical calculations

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

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

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

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

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

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

Creating a simple 1:1 mapping:

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

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

  3. Click on Confirm.

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

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

Creating a simple 1:1 mapping with properties:

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

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

  3. Expand the group you need.

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

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

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

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

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

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

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

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

catalogue complex mappings

Examples for complex 1:1 mappings are:

  • Categories

  • Brands

  • Shipping settings

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

Creating a complex 1:1:n mapping:

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

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

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

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

  5. Your next steps depend on the PlentyONE data source you selected:

    • Alternative 1: The available values for the PlentyONE data value are shown on the left.

      • Next to the value you want to select, click on the plus.
        → The value is added to the field on the right.

      • Click on Confirm.

    • Alternative 2: The PlentyONE data source is inserted and the field Comparative value is shown.

      • In the field Comparative value, enter a value that is saved in the setting or the property of the mapped PlentyONE data source.

      • Click on Confirm.

    • Alternative 3: The PlentyONE data source is inserted and a drop-down list is shown.

      • Select a value from the drop-down list.

      • Click on Confirm.
        → The value of the marketplace data field is exported, not the value of the PlentyONE data source.
        Exception: If you map an own value to a marketplace data field, the own value that you enter is exported directly.

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

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

In other words, this mapping specifies:

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

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

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

Two separate fallback conditions are available:

Null (default)

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

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

  • SKU

  • Barcodes

  • Sales prices

  • Properties

Empty

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

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

  • PlentyONE data sources that are available for variations by default

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

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

Creating a 1:1 mapping with fallback data sources:

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

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

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

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

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

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

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

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

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

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

In other words, this mapping specifies:

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

Creating a 1:n mapping:

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

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

  3. Click on Confirm.

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

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

  6. Click on Confirm.

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

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

  9. Click on Save.

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

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

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

This kind of mapping specifies:

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

Creating an own value mapping:

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

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

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

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

Be especially careful when using Own value mappings

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

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

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

Recalculating numerical values:

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

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

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

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

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

    1. Click on the icon more_vert.

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

    3. Save the settings.

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

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

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

6.3. Activating the catalogue export

Creating a catalogue:

  1. Go to Sales Channels » Channel Control Centre.

  2. Click on the bol.com tile.

  3. Click Create catalogue (add).

  4. Enter a name for the catalogue.

  5. In the drop-down list Marketplace, select the option {marketplace}.

  6. In the drop-down list Export type, select the option {export-type}.

  7. In the drop-down list Category, select a category of the sales channel for which you want to create a catalogue.

  8. 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 bol.com. 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 bol.com was successful.

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

7. Managing listings

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

Right now, only product listings can be created for bol.com.

7.1. 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.
!====
|===

7.2. Creating listings

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

Right now, only product listings can be created for bol.com.
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.

7.2.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 bol.com.
    → 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 BOL.

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

7.2.2. Activating product listings

After you have created the product listings, you have to activate the listings so that they can be transferred to bol.com.
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 bol.com].
    → 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 bol.com].
    → 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.

8. Automating order processing

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

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

  • Automatically upload invoices to bol.com. (How?)

  • Automatically inform bol.com about cancellations. (How?)

  • Automatically send the return status to bol.com. (How?)

  • Automatically create a return at bol.com. (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.

8.1. Sending shipping confirmation to bol.com

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

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

  3. Configure the new flow according to Table 5.

  4. Save () the settings.

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

Tip: If you set statuses for successful and failed shipping confirmations in the Send shipping confirmation to bol.com section of the Flow or event procedure status changes step of the bol.com - Base settings assistant, then orders will automatically be moved to the selected status if a shipping confirmation was successful or if it failed.

Table 5. Event-based flow for uploading shipping confirmations to bol.com
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order status changed

or

  • Order > Book outgoing items

Select an order status, for example:

  • [7] Outgoing items booked

Controls

Branch

  • Object type: Order

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

Filter Operator Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

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

Actions

Multichannel > bol.com

Send fulfillment to bol.com

8.2. Uploading invoice to bol.com

Create an event-based Flow to automatically upload invoices to bol.com.

Creating an event-based flow

  1. Go to Automation » Flow Studio.

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

    1. General

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

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

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

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

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

  3. Configure the new flow according to Table 6.

  4. Save () the settings.

The data is not transferred in real time when this flow is triggered. Instead, the data is registered in a queue. If there are several jobs in the queue, it can take several minutes for the data to be transferred. The advantage? If the target server is unavailable or throttled, several attempts are made to transfer the data.

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

Tip: If you set statuses for successful and failed invoice uploads in the section Upload invoice to bol.com of the Flow or event procedure status changes step of the bol.com - Base settings assistant, then orders will automatically be moved to the selected status if an invoice upload was successful or if it failed.

Table 6. Event-based Flow for uploading invoices to bol.com
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Document > Document created

Select a document type, for example:

  • Invoice

Controls

Branch

  • Object type: Order

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

Filter Operator Input field

Order > Order type

Is in (IN)

Select an order type, for example:

  • Sales order

or

  • Delivery order

Note: For delivery orders, the invoice must be generated in the main order.

Order > Order referrer

Is in (IN)

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

Actions

Multichannel > bol.com

Upload invoices

8.3. Automatically sending cancellations to bol.com

Create an event-based flow to automatically inform bol.com about cancellations. Whenever you are dealing with cancellations, you need to send bol.com a reason for the cancellation. Open the Setup » Orders » Status menu and create additional order statuses as needed. The following cancellation reasons can be transferred to bol.com:

  • Item ordered twice

  • Item is in a bad condition

  • Item untraceable

  • Item retained

  • Incorrect price

  • Higher shipping costs

  • No bol.com warranty

  • Item not available in time

  • Out of stock

  • Other

  • Cancellation requested by customer

  • Technical issue

Creating an event-based flow

  1. Go to Automation » Flow Studio.

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

    1. General

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

      2. Click Next.

    2. Trigger

      1. Select Event-based as the trigger.

      2. Click Next.

    3. Settings

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

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

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

  3. Configure the new flow according to Table 7.

  4. Save () the settings.

The data is not transferred in real time when this flow is triggered. Instead, the data is registered in a queue. If there are several jobs in the queue, it can take several minutes for the data to be transferred. The advantage? If the target server is unavailable or throttled, several attempts are made to transfer the data.

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

Table 7. Event-based flow to send a cancellation to bol.com
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order status changed

Select an order status, for example:

  • [8] Cancelled

or

  • [8.1] Cancelled by customer

Controls

Branch

  • Object type: Order

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

Filter Operator Input field

Order > Order type

Is in (IN)

Sales order

Order > Order referrer

Is in (IN)

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

Actions

Multichannel > bol.com

Select the action Send order cancellation to bol.com and an appropriate reason.

8.4. Automatically sending the return status to bol.com

Create an event-based Flow to automatically inform bol.com about the status of a return. bol.com requests the status of returns. The following return statuses can be sent to bol.com:

  • Item must be repaired

  • Item will be exchanged

  • Customer keeps item

  • Return does not meet conditions

  • Return received

  • Return accepted after consultation with customer

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.

The data is not transferred in real time when this flow is triggered. Instead, the data is registered in a queue. If there are several jobs in the queue, it can take several minutes for the data to be transferred. The advantage? If the target server is unavailable or throttled, several attempts are made to transfer the data.

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

Table 8. Event-based flow to send a return status to bol.com
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order created

Select an order type, for example:

  • Return

Controls

Branch

  • Object type: Order

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

Filter Operator Input field

Order > Order type

Is in (IN)

Return

Order > Order referrer

Is in (IN)

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

Actions

Multichannel > bol.com

Select the action Send return status to bol.com and an appropriate return reason.

8.5. Sending information on direct returns to bol.com

Create an event-based Flow to automatically inform bol.com about returns that customers sent back to you directly without registering the return with bol.com first. bol.com requests the status of returns. The following return statuses can be sent to bol.com:

  • Item must be repaired

  • Item will be exchanged

  • Customer keeps item

  • Return does not meet conditions

  • Return received

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.

The data is not transferred in real time when this flow is triggered. Instead, the data is registered in a queue. If there are several jobs in the queue, it can take several minutes for the data to be transferred. The advantage? If the target server is unavailable or throttled, several attempts are made to transfer the data.

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 inform bol.com about returns
Setting Option Selection

Trigger selection

Select a trigger, for example:

  • Order > Order status changed

Select an order status, for example:

  • [9.5] Credit note created

Controls

Branch

  • Object type: Order

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

Filter Operator Input field

Order > Order type

Is in (IN)

Return

Order > Order referrer

Is in (IN)

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

Actions

Multichannel > bol.com

Select the action Create a return at bol.com and an appropriate return reason.

9. Deleting the sales channel

In the overview of the Channel Control Centre, you can delete the bol.com sales channel and the account associated with it. Before deleting the sales channel, make sure that no orders exist anymore and that the data exchange is deactivated.

Deleting the sales channel:

  1. Go to Sales Channels » Channel Control Centre.

  2. Click More (more_vert) in the tile for bol.com.
    → A drop-down list with further options appears.

  3. Click Delete sales channel (delete).
    → A pop-up for deleting the sales channel opens. If you want to delete the sales channel, confirm the pop-up by clicking delete Delete sales channel.
    → The sales channel is deleted.

10. Troubleshooting

10.1. Check list: Why is my variation not exported?

To export a variation to bol.com, this variation has to meet the following requirements:

Is the order referrer active?

  1. Go to Setup » Orders » Order referrer.

  2. Is the option bol.com with ID 152.00 active?

  3. If necessary, activate this order referrer.

  4. Click Save (save).

Have you activated the variation?

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

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

  3. Click Save (save).

Have you enabled the variation for the sales channel?

The variation must be enabled for the sales channel.

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

  2. Switch to the Sales channels tab.

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

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

  5. Confirm the pop-up by clicking ACTIVATE.

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

Does the variation have positive net stock?

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

  2. Switch to the Stock tab.

  3. Expand the Stock (arrow_forward_ios) section.
    → The net stock per warehouse is shown in the Net stock column.

Are the sales price and price settings correct?

Check the sales price:

  1. Go to Setup » Item » Sales prices.

  2. For the filter Referrer, select bol.com.

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

  4. Check the settings of the sales price.

  5. Make any necessary corrections.

Check the price:

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

  2. Check the following settings:

    • Is the sales price for the referrer linked?

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

  3. Make any necessary corrections.

Is each mandatory field for bol.com mapped to a PlentyONE data field?

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

Is the variation linked to the property of the bol.com category?

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

  2. Open the Properties tab.

  3. Click Add properties (add).
    → The window Add properties opens.
    Tip: Use the filters to search for the property bol.com category.

  4. Place a check mark next to the property bol.com category (check_box).

  5. Click APPLY.
    → The property is added.

  6. For the property bol.com category, select the desired category group from the drop-down list Value.
    → The variation will be exported in this catalogue.

  7. Click Save (save).

Is the catalogue active?

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

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

  2. Scroll to the bol.com catalogue.

  3. In the column Active, activate the toggle (toggle_on).

Couldn’t find any errors?

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

  1. Go to Data » Log.

  2. Use the following filters:

    • bol.com

  3. Click Search (search).

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

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

  6. Correct the variation data.

10.2. Viewing log entries

The Data » Log menu contains a history of processes that run via the bol.com interface.
Note that integrations and identifiers are only shown in the drop-down lists as filters after the process has run at least once.

For bol.com, the following filters are recommended:

  • Identifier » bol.com

Filtering and checking log entries

  1. Go to Data » Log.

  2. In the toolbar, click on tune.

  3. Select appropriate filters from the drop-down lists.

  4. Optional: Select filters for dates and/or times to only show entries from a specific period.
    Tip: For information about the filters, refer to the Data log page of the manual.

  5. Click on Search ().
    → The results are shown.

  6. Check all entries for the levels warning and error.
    Tip: Click on the entry to see details.

Use the reference types and reference values listed in Table 10 to limit the search results:

Table 10. Reference types and reference values for bol.com
Reference type Explanation Reference value

action

Filters by events.

Select a reference type to filter for specific events.

  • orderImport = Order import

  • CreateOffer = Creation of offers

  • CheckOfferStatus = Checking the successful creation of offers

  • DeleteOffer = Deletion of offers

  • UpdateOffer = Updating delivery time, delivery type (FBB, FBR), SKU and activity state of offers

  • UpdateOfferPrices = Updating prices of offers

  • UpdateOfferStock = Updating stock of offers

  • CancelOrder = Cancellation of the order

  • ShipOrder = Shipping of the order

  • HandleReturn = Confirmation of receipt of a return announced on bol.com

  • CreateReturn = Report receipt of a return not announced on bol.com

orderId

Filters by the order ID of the order in PlentyONE.

externalOrderId

Filters by the bol.com order number of the order.

externalOrderItemId

Filters by the ID of the bol.com order item.