INTEGRATIONSBOLbol.com integration
Selling on bol, the Dutch and Belgian marketplace, means working to strict rules. Your delivery promise counts, shipments must be reported on time and your stock has to be right, or you get cancellations and a lower performance score. An integration pulls in orders automatically, reports shipments with tracking and keeps your offers in line with your stock.
ISO 9001 & 27001
- Offers, price and stock goes back and forth with Your other systems
- Orders and cancellation requests goes back and forth with Your other systems
- Shipping and tracking goes back and forth with Your other systems
- Returns goes back and forth with Your other systems
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
This is the data organisations most often let flow between systems. Which of it matters to you depends on where work is getting stuck today.
Offers, price and stock
Your offers on bol revolve around the EAN. For each EAN you pass on price, stock and delivery promise. When your stock changes in your online store or ERP, bol needs to know quickly, or you sell what you no longer have.
Orders and cancellation requests
New bol orders arrive in your online store, ERP or warehouse system, with order lines and delivery address. If a customer asks to cancel, that shows on the order line. Your system has to pick it up before the parcel leaves the building.
Shipping and tracking
As soon as the parcel has gone, you report the shipment with carrier and tracking, or with a bol shipping label. That lets the customer see where their parcel is, and lets bol measure whether you deliver on time.
Returns
Returns come in per return line. Once received, you indicate what you'll do with it, such as refund, exchange or reject. If the product can be sold again, your stock goes up.
Fulfilment by bol (LVB)
With Fulfilment by bol (LVB, Logistiek via bol), your stock sits in bol's warehouse and bol ships it. Your integration then fetches the LVB stock, announces new shipments to the warehouse and only processes LVB orders in your administration.
Invoices and commission
bol sends invoices with a breakdown of items such as commission and LVB costs. If you fetch them automatically, your accounts reconcile with your bol sales.
For each combination: which data moves back and forth, what the standard integration does and what to watch out for.
- Connect Exact Online to bolConnect Exact Online to bol.com: post orders, process bol's invoice with commission and fees, upload business invoices and track Fulfilment by bol stock.
- Connect SnelStart to bolConnect SnelStart to bol: how to post bol orders, process the bol invoice with its commission, and upload invoices for business buyers per shipment.
- Connect Shopify to bolConnect Shopify to bol: stock to bol, orders back into Shopify, shipping yourself or with Fulfilment by bol. Which system leads and how to avoid selling twice.
- Connect WooCommerce to bolConnect WooCommerce to bol: offers and stock to bol, orders back into your WordPress store, with your own shipping or Fulfilment by bol, without double sales.
Not always. If an existing integration for bol does exactly what you need, we'll tell you.
bol names two routes for integrating: through apps and service providers already connected to bol, or yourself through the Retailer API. On the bol Partner Platform you'll find apps for things like stock and order management, pricing and product content. According to bol, your own route gives the most flexibility and control, but it takes technical knowledge and development capacity.
For Shopify and WooCommerce there are ready-made integrations from other parties. They cover the basic process: listing offers, updating stock, pulling in orders and reporting tracking back. If your process fits that, it's a sensible choice.
A standard integration gets tight when bol orders need to go into an ERP or WMS the integration doesn't know, when you mix LVB with your own shipping, or when you want to split stock across channels. We can integrate bol with any system, even when there is no standard integration for it.
- bol orders need to go straight into your ERP or WMS, without a detour through your online store.
- You combine your own shipping with LVB and want both stock levels in one overview.
- You want to reserve part of your stock for your own online store or other channels.
- You have a large range and only want to send changed prices and stock, within bol's limits.
- bol invoices and commission need to go into your accounts automatically.
Retailer API
bol has one API for sellers: the Retailer API. Version 10 is the current stable version; for offers, among other things, version 11 is already available. Through the API you manage offers, product content, orders, shipments, returns, LVB, invoices and commission.
Signing in with client credentials
You create API credentials in your seller account, in the API settings under Services. With the client ID and secret you request a token from login.bol.com through OAuth2 (client credentials). A token is valid for a few minutes. Don't request a new token for every call: bol may block your IP address.
Asynchronous processing
bol doesn't process many changes, such as reporting a shipment, straight away. You get back a process status that goes from PENDING to SUCCESS or FAILURE. bol keeps that status for at most a day, so your integration needs to check it in time.
Push notifications and polling
Push notifications send you a message for events such as a new order, a cancellation request, a process status or a change to a shipment. They arrive through a webhook, Google Cloud Pub/Sub or Amazon SQS, with a digital signature you verify. If you fetch orders yourself, set the change-interval-minute parameter wider than the time between two polling rounds.
Limits and demo environment
Every response contains headers with your remaining budget. Go over it and you get a 429. So only send what has actually changed. The demo environment returns fixed sample responses with the same validation as production, but doesn't actually process anything: you can't test a complete process there.
An integration moves data. In between, AI can read, sort and prepare a suggestion. Where it matters, a person decides.
Product content per EAN
If a product isn't on bol yet, you supply the content yourself. AI turns your existing product data into titles and descriptions in Dutch, and for Belgium in French as well. A team member checks them before the integration submits them.
Preparing returns
AI reads the return reason and the order details and suggests how to handle it: refund, exchange or get in touch first. The decision stays with a person.
Checking invoices
AI compares bol's breakdown with your orders and returns and reports what doesn't match, such as a shipped order that isn't on the breakdown. Your finance team decides what happens.
Stock that updates too late
If your online store and bol share the same stock and the integration only syncs now and then, you sell the same product twice. Then you have to cancel, and cancellations that don't come from the customer count against your performance.
Missing cancellation requests
If your warehouse doesn't pick up a cancellation request, the parcel goes out anyway. A cancellation at the customer's request doesn't count against you at bol, so confirm it quickly with the right reason.
Reporting shipments too late
bol bases the delivery promise on the moment of ordering. If your integration only reports shipments in one go in the evening, the customer gets their tracking late. Order lines you don't handle expire a few days after the expected delivery date and are then cancelled by bol.
EANs that are wrong
Offers on bol are tied to the EAN. A wrong or missing EAN means your offer doesn't go live or ends up on the wrong product. You may not offer identical items under different EANs.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Offers, price and stock, Orders and cancellation requests, Shipping and tracking, Returns, Fulfilment by bol (LVB), Invoices and commission.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: Retailer API, Signing in with client credentials, Asynchronous processing, Push notifications and polling, Limits and demo environment.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Does bol have an API for sellers?
Yes, the Retailer API. With it you manage offers, stock, orders, shipments, returns, LVB and invoices from your own systems. You create the API credentials in your seller account, in the API settings.
Can I connect bol to my own online store?
Yes. For Shopify and WooCommerce there are ready-made apps and plugins from other parties, and through the Retailer API an integration with any other system is possible. Decide up front which system leads for stock and price.
Does an integration also work with Fulfilment by bol?
Yes. For LVB products bol ships them itself, and your integration only processes those orders in your administration. Through the API you fetch the LVB stock and announce new shipments to bol's warehouse. You do need to sign up for LVB separately with bol.
How often should an integration fetch bol orders?
That depends on your delivery promise. If you promise 'order before 4 pm, delivered tomorrow', you want to see new orders within minutes. With push notifications for new orders, you don't need to keep asking. If you do poll, set change-interval-minute wider than the time between two rounds, so you don't miss anything.
Can I test a bol integration without real orders?
Partly. bol has a demo environment with fixed sample responses and the same validation as production. That lets you test whether your requests are correct, but a complete process from order to return isn't possible there. So start live with a few products and expand from there.
What happens if I send too many requests?
You get a 429 response and wait until your budget has been topped up. Every response shows how much budget you have left. Only send changed prices and stock, and don't request a new token for every call.
- Mollie integrationPayment provider for online and in-person payments, with iDEAL, cards and other European payment methods.
- Shopify integrationHosted ecommerce platform for brands and retailers, from a first store to Shopify Plus.
- WooCommerce integrationOpen-source ecommerce plugin for WordPress that you host yourself and extend with plugins.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.
- bol Retailer API: overview
- bol Retailer API: authentication
- bol Retailer API: rate limits
- bol Retailer API: process status
- bol Retailer API: push notifications (event types)
- bol Retailer API: orders and shipments
- bol Retailer API: offers (v11)
- bol Retailer API: returns
- bol Retailer API: Fulfilment by bol (LVB)
- bol Retailer API: LVB stock and replenishment
- bol Retailer API: product content
- bol Retailer API: demo environment
- bol Partner Platform: EAN or ISBN (Dutch)
- bol Partner Platform: items on time (Dutch)
- bol Partner Platform: apps and service providers (Dutch)
- bol Partner Platform: automating through the Retailer API