Integrations
Integrate bol.com with Odoo
bol.com is the marketplace that matters in the Netherlands and Belgium, and it’s one we know unusually well: we maintain an open-source Python client for the bol.com Retailer API and have run a commercial bol connector for years. One of our longest-standing testimonials comes from a client whose bol.com operation grew to the point that manual order handling broke, and our connector fixed it.
If you’re a UK or NL brand selling on bol.com, this integration puts bol orders, stock and fulfilment in the same Odoo backend as everything else.
What we connect
- Retailer API order flow. New bol orders import with buyer details and delivery promises, and shipment confirmations with track-and-trace flow back to bol within the response windows bol enforces.
- FBR and FBB support. Fulfilled-by-Retailer orders drive your own warehouse in Odoo; Fulfilled-by-Bol (LVB) stock is tracked as a bol location so total inventory stays truthful.
- Offer and stock management. Prices and stock push from Odoo to your bol offers, keeping the buy block position aligned with your actual availability.
- Returns and cancellations. bol’s return notifications create the right reverse-logistics documents in Odoo, so refunds and restocks don’t rely on someone checking the seller portal.
- Performance-score awareness. bol punishes late confirmations. The integration is built around bol’s timing rules, protecting your seller performance score during volume spikes.
How a marketplace connection is built
- Seller account and API access sorted first. Credentials, permission scopes and sandbox access where the operator offers one. This step is routinely the slowest, so we start it on day one.
- Listing and offer mapping to their standard. Marketplace operators reject data that doesn’t meet their taxonomy and attribute rules, so your Odoo product data is shaped to pass their validation rather than ours.
- Order lifecycle and despatch rules encoded. Marketplaces measure late despatch and cancellation rates, and they penalise both. The sync is built around their clocks, not just their endpoints.
- Settlement reconciliation into the ledger. Commissions, fulfilment fees, returns and payouts reconciled against the marketplace’s own statements, so your margin per channel is a fact rather than a guess.
- Go-live watching seller metrics. Production launch with monitoring on both the sync and your seller performance dashboard for the first trading cycle.
Common questions
Why does your bol.com experience matter?
Because bol's API has quirks (strict confirmation windows, offer-based rather than product-based listings) that generic connectors handle badly. We've maintained a bol client library for years and run this in production.
Do you support the newer Retailer API versions?
Yes, we track bol's API deprecation schedule and version migrations as part of connector maintenance, which is the sort of thing that silently breaks unmaintained connectors.
Can we run bol.com plus Shopify plus Amazon in one Odoo?
That's precisely the architecture we recommend: one stock pool, one order pipeline, channels as plugins.
Do you maintain the bol.com client, or is it a one-off build?
We maintain it as open source, which means API version changes get handled upstream rather than becoming your emergency. bol.com deprecates API versions on a published schedule and we track it.
How are bol.com commissions and fees reconciled?
Fees post against the order so per-channel margin is visible in Odoo rather than discovered at month-end, and payouts reconcile against bol.com's settlement statements.
Not sure where to start? Book a free discovery call and we’ll map your current setup, or request a free Odoo health check if you’re already running Odoo.