↑↓ selectEnter openEsc close

    1. Elbuz
    2. European marketplaces

    How to connect Bol.com to Elbuz: offers, orders, prices in euros

    7 min readUpdated

    Elbuz connects to your Bol.com seller account (Dutch and Belgian marketplace) with two Retailer API keys: it imports your offers, receives orders and sends prices and stock back.

    When you need this:

    • You sell on Bol.com and elsewhere — all channels' stock and orders live in one catalog.
    • Many orders — new and changed orders arrive every 5 minutes.
    • You price in Elbuz — the export updates each offer's price and stock on Bol.com.
    • New products — Elbuz lists an offer by EAN and, if there's no card yet, submits one to the Bol.com catalog.

    Where to start: create keys in Seller Dashboard and paste them into a “Bol.com” template.

    What the Bol.com connection can do

    • Connection with two keys — no app to link and no signing in to the seller account from Elbuz.
    • Offer import — the title, description and brand of the Bol.com product card, your SKU, , price and stock.
    • Orders — open ones on the first run, then everything changed over the last few days.
    • Prices and stock back to Bol.com — offer by offer, with a separate log line for every rejection.
    • Publishing new products — an offer by EAN on an existing card, or a new card based on the mapped category.

    Where to get Bol.com keys

    You create the keys yourself; there's no app to register. The Bol.com dashboard is in Dutch, so menu items are given as they appear there:

    1. Sign in to Seller Dashboard (partner.bol.com) and open Instellingen → API-instellingen.
    2. Create keys for the Retailer API, not the Advertising API.
    3. Copy the Client ID and Client secret. The secret is shown only once: if you close the window without copying it, create a new pair.

    In an import template of type “Bol.com”, the “Connection” card has four fields; the first two are required:

    Template fieldWhat to enter
    Client IDThe Client ID from API-instellingen. Required
    Client secretThe Client secret from the same place. After saving, the field shows dots and the key itself isn't visible. Required
    Content languagenl, nl-BE, fr or fr-BE. Empty or any other value means nl. Needed only for new cards
    Delivery time to customerDays in min-max format, for example 1-2 (the value used if left empty). Needed only for new offers

    After pasting the keys, click “Test connection”. Elbuz gets an access token and reads one of your offers. The reply “Connection works. Bol.com” means the keys were copied in full and belong to the Retailer API.

    “Active” and “Orders” are already on in a new template: within 5 minutes of saving the keys, Elbuz starts pulling open orders. Elbuz maps marketplace statuses to yours by name; what arrived and how it was mapped is shown in the template's “Order statuses” window. Want to check first? Clear “Orders”.

    Bol.com import template: Connection card with credentials, content language and delivery time
    1Client ID
    2Client secret
    3Content language
    4Delivery time
    1. Client ID — the first half of the key pair from the Seller Dashboard.
    2. Client secret — the secret half; it is hidden after saving.
    3. Content language — language for new listings (nl, nl-BE, fr, fr-BE).
    4. Delivery time — the promise to the buyer for new offers.

    Bol.com documentation for sellers: Retailer API (in English).

    What goes into the product card

    The Bol.com catalog is shared: the marketplace maintains the product card (title, description, photos) and finds it by EAN, while your offer is the price, stock and delivery time. Elbuz fetches the list of your offers and reads the card for each one separately by EAN.

    Bol.com dataProduct field in Elbuz
    card title (if there's no card, the title you listed the offer with)Name
    card descriptionDescription
    card brandManufacturer
    reference — your offer codeSKU
    offer EANBarcode
    offer pricePrice — the number as is
    offer stockQuantity
    the offer isn't on hold and stock is above zeroproduct enabled; otherwise disabled

    What does not come from Bol.com: photos (the Retailer API has no image links), specifications, category. The “Photo” checkbox in the template form does nothing for Bol.com.

    Bol.com works only in euros, and Elbuz writes the offer price into the “Price” field as the same number. If your catalog is in another currency, 19.99 from Bol.com becomes 19.99 in your currency. In that case, don't import prices from Bol.com; manage them in Elbuz (Bol.com as a channel).

    All new products go into the service category “Products - bol”. It's created disabled and excluded from exports: these products go nowhere until you sort them into your own categories. How to get rid of the service category: service categories and brands.

    What a repeat run overwrites

    A repeat import finds your product first by the offer link Elbuz saved last time, then by name. Existing catalog products aren't matched by EAN: the first run links an offer to your card only if the name matches and the card has no manufacturer part number or product URL. Otherwise it creates a new card.

    What the run doesFields
    Overwrites with Bol.com dataname, description, manufacturer, SKU, barcode, price, quantity, the “enabled” flag
    Doesn't clear, because Bol.com doesn't send themshort description, old price, tags
    Doesn't touchposition in the category tree, photos, specifications

    An empty value from Bol.com doesn't erase a filled field. If the card couldn't be read by EAN, the name and description of an existing product stay as they were instead of being replaced with a placeholder.

    The Bol.com template has no “don't update name” checkbox. To keep your names and descriptions, turn on “Do not update” in the product card (“Import protection” section): the run won't change anything there. “Fixed Price” protects only the price. For the whole catalog, simply clear the “Products” checkbox after the first run (scenario).

    An offer missing from the run is left alone: the product keeps its last price and stock and isn't disabled or deleted.

    How orders arrive

    Elbuz takes the orders that you ship yourself. Orders that Bol.com ships from its own warehouse don't come through this connection.

    • The first run takes only open orders — Elbuz doesn't bring over the history of shipped ones.
    • Later runs take all orders changed since the previous run's date, with a twelve-hour margin. This way shipments and cancellations reach orders already imported.
    • Elbuz doesn't look back further than 90 days: that's how much history Bol.com keeps.

    The “Customer order” document gets the order number and date, recipient's full name, phone, email, delivery address (street, house number, city, postcode, country; or the pickup point name), items with prices and the total in euros. Bol.com's email is anonymized but constant per buyer, so repeat orders from one person go to one contact.

    Bol.com has no single order status; Elbuz derives it from the order lines:

    CodeWhen
    OPENthere are items not yet shipped and not cancelled
    SHIPPEDeverything is shipped, or some items are cancelled and the rest shipped
    CANCELLEDeverything is cancelled

    Elbuz maps SHIPPED and CANCELLED to “Shipped” and “Canceled” by itself, and OPEN comes in as “New”. To set it up differently, use the “Order statuses” button in the “Related settings” card of the template form. What a repeat run changes in an order already imported: who overwrites whom — your status or the marketplace's.

    Related settings card with Order statuses and Schedule setup buttons
    1Order statuses
    2Schedule setup
    1. Order statuses — map OPEN, SHIPPED, CANCELLED to your own statuses.
    2. Schedule setup — how often to fetch orders and the catalog.

    Elbuz doesn't confirm or send anything to Bol.com: you register the shipment and tracking number in the Bol.com dashboard, and the next run moves the order to SHIPPED.

    If the details of a particular order couldn't be retrieved, the log gets a line with its number, and the date from which the next batch starts moves back. The next run picks up that order again.

    How prices and stock go back to Bol.com

    The reverse direction is a separate export template of type “Bol.com”. The “Connection” card holds the same Client ID and Client secret, and the “API version (marketplace parameters)” field sets the content language and delivery time separated by a pipe: nl|1-2.

    The Connection card of the Bol.com export template
    1Client ID
    2Client secret
    3API version (marketplace parameters)
    1. Client ID — the same key as in the import template.
    2. Client secret — the secret half of the key pair.
    3. API version (marketplace parameters) — card language and delivery time, joined with a vertical bar.

    With “Products” checked in the “What to export” card, Elbuz sends each offer's price and stock in a separate request. The offer key comes from the link made by the catalog import or a past publication, so import the Bol.com catalog once first. Unlinked products in the filtered set are skipped silently unless “Publish new products” is on.

    • Currency. Bol.com accepts only euros, and Elbuz sends the price as the number in the product, unconverted. If your catalog is in hryvnias or zlotys, convert the price with a formula in the template's “Export fields”, otherwise UAH 1,500 goes out as EUR 1,500.
    • Markup for Bol.com is set with the same price formula in the export template; catalog prices stay as they are.
    • Price limits are 1 to 9999 euros. An offer priced outside them isn't sent, and the log gets the line “Bol.com: “…” — price … is outside the allowed range 1–9999 EUR, offer not updated”.
    • Negative stock is sent as zero.

    Elbuz can't take offers offline or delete them: a product dropped from the filtered set just stops getting updates. To stop selling, set stock to zero and wait for the export, or remove the offer in the Bol.com dashboard.

    Publishing new products

    With the “Publish new products” checkbox in the “What to export” card, Elbuz lists an offer for a product that isn't linked to Bol.com yet. You need a barcode of at least 8 digits and a price from 1 to 9999 euros.

    The What to export card with Products and Publish new products checked
    1Products
    2Publish new products
    1. Products — updates prices and stock of linked offers.
    2. Publish new products — lists products without an EAN link on Bol.com.

    The offer goes out with your price, stock, SKU (or the Elbuz product number if there's no SKU), the delivery time from the “API version” field and the condition from the “Product condition” field:

    Product condition in ElbuzOffer condition on Bol.com
    New or not filled innew
    Discountedused, as new
    Usedused, good condition
    Refurbishedrefurbished

    If you already have an offer for this EAN on Bol.com (listed in the dashboard or by a previous run), Elbuz links that one to the product instead of creating a second. Each publication adds the log line “Bol.com: product “…” published (offer …)”.

    If Bol.com has no product card yet

    Before publishing, Elbuz checks the EAN in the Bol.com catalog. If there's no card, it submits one for the marketplace's review: EAN, name, description, manufacturer, main photo and Bol.com category. The category comes from the mapping of the product's category.

    Where: Directories → Categories → the “Marketplace mapping” tile → the “Bol.com” toggle.

    On first opening, click “Load marketplace dictionary” — the Bol.com category tree loads with the import template's keys. Then map your categories in the “Bol.com category” column. How the window works: mapping categories to marketplaces.

    Category–marketplace mapping window with the Bol.com chip active and the Bol.com category and Bol.com ID columns
    1Bol.com chip
    2Bol.com category column
    3Load marketplace dictionary
    1. The Bol.com chip shows the columns for this marketplace only.
    2. The Bol.com category column holds the Bol.com category where a new product card will land.
    3. The Load marketplace dictionary button fetches the Bol.com category tree.

    Limits of a new card:

    • one card, one product: Elbuz doesn't group variants (size, color);
    • one photo — the product's first link, marked as main;
    • only name, description and brand are sent — the marketplace may ask you to fill in the rest in the dashboard;
    • the card language comes from the “API version” field (nl, nl-BE, fr, fr-BE).

    Elbuz waits a few seconds for Bol.com's response. In time — the log shows “product content sent to the Bol.com catalog (status: SUCCESS)” or “product content rejected: …” with the reason. Too late — status PENDING: the offer is still created and appears on Bol.com once the card is approved.

    Scheduled updates

    Bol.com doesn't send instant notifications, so Elbuz pulls orders by itself every 5 minutes if “Orders” is selected in the template and the keys are filled in. This is done by the shared “Marketplace orders” task in the “Job schedule” window, where you can also change the interval. This pass doesn't load the catalog, and orders also picked up by the template's schedule aren't duplicated.

    The catalog is updated by the template's own schedule: the “Schedule setup” button. Run it rarely, at night for example: while the catalog is loading, the orders pass is skipped until the next one. The export is a separate template with its own schedule and its own “Active” toggle.

    Bol.com's request limit is strict: about 25 requests per minute for orders. When rejected over the limit, Elbuz waits as long as the marketplace says (up to a minute) and retries up to three times. The slowest are the catalog import, since Elbuz requests each offer's card separately, and the export, since each offer is updated by its own request.

    A broken-off run is safe: the catalog is written in batches of 500 offers, orders are looked up by number, and a linked offer is updated by the same key. General rules: if a run breaks off.

    Scenarios

    Select data to import card with Products and Orders checkboxes
    1Products
    2Orders
    1. Products — bring your Bol.com offers into the catalog.
    2. Orders — receive Bol.com orders.

    Bring your Bol.com catalog into Elbuz

    What to turn on. Fill in “Client ID” and “Client secret”, and in the “Select data to import” card, check “Products”.

    What you get. Each offer lands in the “Products - bol” category with the card's name, description and brand, your SKU, barcode, price in euros and stock. Add photos, specifications and categories yourself or from a supplier price list.

    Receive Bol.com orders

    What to turn on. The “Orders” checkbox; Elbuz maps the statuses itself, and the “Order statuses” button is there if you want it differently. No template schedule is needed: orders arrive by themselves every 5 minutes.

    What you get. The first run takes open orders; later runs take everything changed since the date in the “Import orders from date (YYYY-MM-DD)” field in the “Advanced” block. A shipment registered in the Bol.com dashboard changes the document status on the next run.

    Bol.com as a channel for a catalog you manage in Elbuz

    What to turn on. Run the import once with the “Products” checkbox — it links products to offers. After that, keep only “Orders”, otherwise the catalog run will overwrite price and stock with Bol.com figures. Prices are sent by an export template of type “Bol.com”, with a euro conversion formula if needed.

    What you get. Linked products get the new price and stock on every export, and with the “Publish new products” checkbox Elbuz also lists new items by EAN.

    What to do when Bol.com won't send or accept data

    Troubleshooting common problems
    What you seeWhyWhat to do
    “Bol.com: enter Client ID and Client secret from Seller Dashboard” One of the key fields is empty Paste both keys and save the template (where to get the keys)
    “Connection failed: HTTP 401 (token): …” or “Bol.com: API error — HTTP 401 (token): …” The key was copied incompletely, deleted in the dashboard, or it's an Advertising API key Create a new pair for the Retailer API in API-instellingen and paste both keys again
    “Bol.com: API error — HTTP 429: rate limit” The request limit didn't reset even after three retries In the orders pass, increase the interval of the “Marketplace orders” task: each pass re-requests the details of all orders changed today (in the morning, yesterday's too); for the catalog, run it less often. A retry is safe (schedule)
    “Bol.com: prices and stock updated, offers: N (errors: M)” with a non-zero M Bol.com rejected some offers; the reason is in the “Bol.com: export error [name] …” line above Fix what's indicated in the products and run the export again — the other offers are already updated
    “Bol.com: “…” — price … is outside the allowed range 1–9999 EUR, offer not updated” The price is empty, zero or not converted to euros Set a price or a conversion formula in the export template (currency)
    “Bol.com: “…” — no EAN barcode, cannot publish on Bol.com” An offer on Bol.com can exist only with an EAN Fill in a barcode of 8 digits or more in the product (publishing)
    “Bol.com: “…” — the product is not in the Bol.com catalog and no Bol.com category is mapped…” A new card needs a Bol.com category Map the product's category to a Bol.com category (new cards)
    “Bol.com: “…” — product content rejected: …” Bol.com didn't accept the card data; the reason follows the colon Fix the product's name, description or photo, or create the card in the Bol.com dashboard
    A product got duplicated after the first import The name differs in Elbuz and on Bol.com, and the import doesn't match by EAN Keep working with the new card — the offer is linked to it; move what you need from the old one and delete it (repeat run)

    FAQ

    I'm not from the Netherlands or Belgium — can I connect?

    Only if Bol.com has invited you to sell and the connection goes through a certified partner. Sort this out with Bol.com; with a working account, the keys are created the same way (who can sell).

    Why did products from Bol.com arrive without photos?

    The Retailer API doesn't provide links to card images. Add photos in Elbuz yourself or from a supplier price list (what gets imported).

    Why are there no old orders after the first run?

    The first run takes only open orders. Orders shipped earlier aren't brought into Elbuz (orders).

    Does Elbuz send the tracking number to Bol.com?

    No. Register shipments in the Bol.com dashboard — the next run moves the order to SHIPPED (orders).

    How do I sell in Belgium in French?

    It's one marketplace for both countries, so you don't need a separate template. For new cards, enter fr-BE in the “Content language” field and in the export template's “API version” field: fr-BE|1-2.

    A product disappeared from Bol.com — will Elbuz delete it?

    No. The item stays with its last price and stock; remove it manually (repeat run).

    Where it is and who has access

    Menu
    Directories → Operations → Data import → new template of type “Bol.com”
    Other entry points
    Directories → Operations → Data export — a template for prices and stock
    Access right
    the “Import” window in “Group permissions”
    Have ready
    the Client ID and Client secret from Bol.com Seller Dashboard

    Bol.com sells only to buyers in the Netherlands and Belgium. A seller registered in another country can join only by invitation from Bol.com and through a certified connection partner. Sort this out with Bol.com before connecting to Elbuz: without an active seller account, there are no keys in the dashboard.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free