bol.com

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.

1. Frequency of data exchange

After you have set up the interface to bol.com, the automatic processes described in Table 1 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 the market in PlentyONE

The basic settings for bol.com are carried out in the Setup » Assistants » Omni-Channel menu with the Basic settings - bol.com assistant. With this assistant, you set up your bol.com account in PlentyONE. You also carry out settings for warehouses and map PlentyONE delivery times with bol.com delivery times.

Carrying out settings in the assistant:

  1. Go to Setup » Assistants » Omni-Channel.

  2. Click on the assistant Base settings - bol.com.

  3. Follow the instructions on the screen. If you need additional information about one of the options, expand the info box below this description ().

  4. In the Summary step, check your settings to make sure they are correct.
    Tip: In the Summary step, click on the arrow () to show the settings.
    Tip: You can run through the assistant again at any time to update settings.

Options in the assistant
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

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

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

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

  6. Click on Save (save).
    → The referrer is active.

3.2. 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. Open the Settings tab.

  3. Activate the referrer bol.com.

  4. Save () the settings.

3.3. 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.4. 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.4.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 on 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.4.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. Setting up the item export

Item data is exported to bol.com using catalogues. Use the assistant Create catalogues - bol.com to create a marketplace format for every bol.com category.

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.

4.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 in the assistant:

  1. Open the menu Setup » Assistants » Omni-Channel.

  2. Click on the assistant Create catalogues - bol.com.

  3. Follow the instructions on the screen. If you need additional information about one of the options, expand the info box below this description ().

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

  5. If everything is as it should be, click on Finalise.
    → The catalogue is created.

  6. Open the catalogue in the Data » Catalogues menu to map the marketplace data fields with PlentyONE data fields fields.
    Note: You need a separate catalogue for each combination of bol.com category and language.

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

Settings in the assistant
Setting Explanation

Select a category for your catalogue.

Select a product category from the drop-down list.
Tip: Enter a few names of the category name to get suggestions.
→ The catalogue is created with the name of the category and shown in the Data » Catalogues menu.
Note: You need to create a separate catalogue for each combination of a bol.com category and a language.

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

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 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 column, you map the PlentyONE data fields. Any PlentyONE data fields that you already mapped are also shown in this column.

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

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

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 this chapter, you will learn how to add information on the manufacturer and the responsible person within the EU in PlentyONE and export it to bol.com.

5.1. Option 1: Exporting information on the manufacturer and EU-responsible person via manufacturer data

In PlentyONE, you can export the information on the manufacturer and EU-responsible person that is required for the Economic Operator directly to bol.com via the manufacturer:in data.

5.1.1. Prerequisites

  • In the Setup » Item » Manufacturers menu, fill in the required fields for the EU-responsible person for each of your manufacturers.

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

Note: The manufacturer data is exported to bol.com once a day. When exporting the manufacturer data, the system first checks whether the fields for the EU-responsible person have been filled in.

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

5.1.2. bol.com fields for EU-responsible person

The following table lists the required fields for information on the EU-responsible person. These fields are mapped as data fields by default in the Product Safety section of the OTTO Market catalogue.

Table 2. Required fields for information on the EU-responsible person
Field name Description

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. Option 2: Exporting information on the manufacturer and EU-responsible person via properties

As an alternative to option 1, you can export the information on the manufacturer and EU-responsible person that is required for the Economic Operator via properties to bol.com.

Prerequisites

  • Create an Economic Operator for each of your manufacturers in the bol.com partner portal.

  • Fill in the required fields for each Economic Operator in the bol.com partner portal.

  • Next, create a new property in PlentyONE under Setup » Settings » Properties » Configuration 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.

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

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

    • Enter the name of the manufacturer or the manufacturer’s EU-responsible person in the Text for Economic Operator Name field.
      Important: The name entered under Text for Economic Operator Name must be identical to your entry of the Economic Operator Name at bol.com. 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. Preparing variations

Continue with preparing your variations.

6.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 of the variation 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 of the variation.

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.

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

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

  • 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 Images section of the variation.

  • in 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 section 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 tab Global 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 should be linked.

  3. Open the Properties tab.

  4. Click Add properties in the Selection and multi selection section.

  5. Click Search to see a list of all properties of the type Selection, Multi selection.

  6. Select the bol.com category property and click Apply.
    → The property is added.

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

  8. Save () the settings.

6.3. Activating variations for the market

You need to activate the variations that you want to sell on bol.com. This is done in the Availability and visibility section of a variation within the Item » Items » [Open item] » [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 item] » [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, activate the option Active.

  3. In the Sales channels section, click Add sales channels (add).
    → The window Add sales channels opens.

  4. In the drop-down list Sales channels, select the option bol.com.

  5. Click Apply.
    → The sales channel is added.

  6. 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. In the drop-down list Sales channels, select the option bol.com.

  7. Select the action Active from the drop-down list Actions.
    → The action is added to the lower part of the window.

  8. Activate the option Active.

  9. Navigate to the area Availability.

  10. Click Execute to apply the settings.

Batch processing allows you to edit several variations at once. You use filters to limit which variations are edited.

Making several variations available for bol.com using batch processing:

  1. Go to Item » Batch processing.

  2. Click on the tab Variations in the upper left corner.

  3. Use the filters on the left to specify which variations should be processed.

  4. Navigate to the area Market availability.

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

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

  7. Navigate to the area Availability.

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

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

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

6.4. 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. Click Add sales channels () in the Sales channels section.

  3. Select the option bol.com FBB from the Sales channels drop-down list.

  4. Click Apply.

  5. Save () the settings.
    → The variation is available for bol.com.

7. Automating order processing

You can automatically notify bol.com about changes to the order status. There are two ways to do this:

  • Option 1: PlentyONE Flow (recommended)

  • Option 2: Event procedures (old method)

7.1. Option 1: PlentyONE Flow (recommended)

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 ongoing or finished 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.

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

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

  3. Configure the new flow according to Table 4.

  4. Save ​​() the settings.

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

Tip: If you set statuses for successful and failed shipping confirmations in 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 4. Event-based flow for uploading shipping confirmations to bol.com
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order > Order status changed

or

  • Order > Book outgoing items

Select an order status, for example:

  • [7] Outgoing items booked

Control element

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 > 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 order shipping confirmation to bol.com

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

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 5 only serve as an example. Select the status, controls and filters for the flow which best suit your workflow.

Tip: If you set statuses for successful and failed invoice uploads in 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 5. Event-based flow for uploading invoices to bol.com
Setting Option Selection

Trigger selection

Select an event, for example:

  • Document > Document created

Select a document type, for example:

  • Invoice

Control element

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

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

  • Cancellation requested by customer

  • Higher shipping costs

  • Incorrect price

  • Item is in a bad condition

  • Item not available in time

  • Item ordered twice

  • Item retained

  • Item untraceable

  • No bol.com warranty

  • Other

  • Out of stock

  • 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 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 status, controls and filters for the flow which best suit your workflow.

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

Trigger selection

Select an event, for example:

  • Order > Order status changed

Select an order status, for example:

  • [8] Cancelled

or

  • [8.1] Cancelled by customer

Control element

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

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

  • Customer keeps item

  • Item must be repaired

  • Item will be exchanged

  • Return accepted after consultation with customer

  • 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 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 status, controls and filters for the flow which best suit your workflow.

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

Trigger selection

Select an event, for example:

  • Order > Order created

Select an order type, for example:

  • Return

Control element

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

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

  • Customer keeps item

  • Item must be repaired

  • Item will be exchanged

  • 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 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 status, controls and filters for the flow which best suit your workflow.

Table 8. Event-based flow to inform bol.com about returns
Setting Option Selection

Trigger selection

Select an event, for example:

  • Order status changed

Select an order status, for example:

  • [9.5] Credit note created

Control element

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

7.2. Option 2: Event procedures (old method)

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

  • Send shipping confirmation to bol.com (How?)

  • Send order cancellation to bol.com (How?)

  • Send return status to bol.com (How?)

  • Create a return at bol.com (How?)

7.2.1. Automatically sending shipping confirmations

Set up an event procedure to automatically send shipping confirmations to bol.com when the outgoing items have been booked.

Setting up an event procedure

  1. Go to Setup » Orders » Events.

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

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 9.

  5. Save () the settings.

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

  7. Select the setting Active ().

  8. Save () the settings.

Tip: If you set statuses for successful and failed shipping confirmations in the 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 9. Event procedure for automatically sending shipping confirmations to bol.com
Setting Option Selection

Event

Order change: Outgoing items booked

Filter 1

Order > Order type

Order

Filter 2

Order > Referrer

bol.com

Procedure

Shipping > Send shipping confirmation to bol.com

7.2.2. Automatically sending cancellations

Set up an event procedure to automatically inform bol.com of cancellations. Whenever you are dealing with cancellations, you need to send bol.com a reason for the cancellation. Open the Setup » Orders » Order status menu and create additional order statuses as needed. The following cancellation reasons can be transferred to bol.com:

  • Out of stock

  • Cancellation requested by customer

  • Item is in a bad condition

  • Higher shipping costs

  • Incorrect price

  • Item not available in time

  • No bol.com warranty

  • Item ordered twice

  • Item retained

  • Technical issue

  • Item untraceable

  • Other

Setting up an event procedure

  1. Go to Setup » Orders » Events.

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

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 10.

  5. Save () the settings.

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

  7. Select the setting Active ().

  8. Save () the settings.

Table 10. Event procedure for automatically sending cancellations to bol.com
Setting Option Selection

Event

Order change: Status change

[8.1] Cancelled by customer

Filter 1

Order > Order type

Order

Filter 2

Order > Referrer

bol.com

Procedure

Order > Send cancellation to bol.com

Customer cancellation

7.2.3. Automatically sending the return status

Set up an event procedure to automatically inform bol.com of the status of a return. bol.com requests the status of returns. The following return statuses can be sent to bol.com:

  • Return received

  • Item will be exchanged

  • Return does not meet conditions

  • Item must be repaired

  • Customer keeps item

  • Return accepted after consultation with customer

Setting up an event procedure

  1. Go to Setup » Orders » Events.

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

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 11.

  5. Save () the settings.

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

  7. Select the setting Active ().

  8. Save () the settings.

The data is not transferred in real time when this event procedure 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.

Table 11. Event procedure for automatically sending return statuses to bol.com
Setting Option Selection

Event

New return

Filter 1

Order > Order type

Return

Filter 2

Order > Referrer

bol.com

Procedure

Order > Send return status to bol.com

Select a status.

7.2.4. Sending information on direct returns to bol.com

In addition, set up an event procedure 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:

  • Return received

  • Item will be exchanged

  • Return does not meet conditions

  • Item must be repaired

  • Customer keeps item

  • Return accepted after consultation with customer

Setting up an event procedure

  1. Go to Setup » Orders » Events.

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

  3. Enter a distinct name for the event procedure.

  4. Select the event according to Table 12.

  5. Save () the settings.

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

  7. Select the setting Active ().

  8. Save () the settings.

The data is not transferred in real time when this event procedure 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.

Table 12. Event procedure to inform bol.com about returns
Setting Option Selection

Event

Order change: Status change

[9.5] Credit note created

Filter 1

Order > Order type

Return

Filter 2

Order > Referrer

bol.com

Procedure

Order > Create a return at bol.com

Select a status.

8. Starting the item export: Activating catalogue export

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

Activating the catalogue export to bol.com:

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

  2. Scroll to the bol.com catalogue.

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

9. Troubleshooting

9.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 active?

  3. If necessary, activate this order referrer.

  4. Save () the settings.

Have you activated the variation?

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

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

  3. Save () the settings.

Is the market availability active?

The variation must be available for the market.

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

  2. In the Sales channels section, click Add sales channels.
    → The window Add sales channels opens.

  3. In the drop-down list Sales channels, select the option bol.com.

  4. Click Apply.
    → The sales channel is added.

  5. Save () the settings.
    → The variation is available for bol.com.

Does the variation have positive net stock?

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

  2. Expand the section Stock ().
    → 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 on 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 item] » [Open variation].
    → The sales prices are shown in the Sales prices section.

  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 market have to be mapped to PlentyONE data fields. These mandatory fields are different for different market 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 item] » [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.

  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. Save () the settings.

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

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

9.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 13 to limit the search results:

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