Appearance
Bol.com integration
The Bol.com integration reads the Retailer API and the Advertiser API and lands the result in your own data warehouse. The two use separate credential pairs on purpose: either can be revoked without touching the other.
What the Bol.com integration pulls
| Object | What lands | Refresh |
|---|---|---|
| Orders | Order id, order date, pickup-point flag, derived order total and currency, anonymised flag | Incremental, every few hours |
| Order items | Order item id, EAN, offer reference, quantity, unit and total price | With the order |
| Commission | Commission per order item, reconciled against the invoice | Daily |
| Returns | Return registrations and their handling result | Daily |
| Sponsored products performance | Impressions, clicks, spend and conversions, one row per campaign per day | Daily, rolling 30 days |
| Campaigns | Campaign list, state and budget | Daily full refresh |
Marketplace orders carry no usable customer identity. Bol.com issues a per-order alias address rather than a real email, so the connector performs no identity hashing at all. That is deliberate: running an alias through the shared hash would manufacture people who do not exist and pollute the identity graph.
The connector also lands an anonymised flag, which quantifies something worth knowing on its own: how much of your marketplace channel is opaque by the customer's own choice.
What the Bol.com integration can be used for
Bol.com can be used for true marketplace margin. Revenue, commission and returns land together, so margin is computed per order item rather than inferred from a monthly statement.
Bol.com can be used for channel comparison against your own shop. Marketplace orders that have a twin in your own shop are matched on the order id that both sides carry, so the same product can be compared like for like across channels.
Bol.com can be used for sponsored product return on ad spend. Advertising performance lands at daily grain, which is the only grain that can be summed safely.
Bol.com can be used for restatement-aware reporting. The last thirty days are re-pulled on every run, so a commission correction or a late return updates the history rather than sitting as a discrepancy.
Bol.com can be used for assortment decisions, because EAN-level performance sits next to your own catalogue.
Bol.com can be used as a demand signal for content, so the marketplace bestsellers inform which topics the pipeline writes about on your own site.
Bol.com combined with other integrations
| Combination | What it gives you |
|---|---|
| Bol.com + Shopify | Own-shop versus marketplace margin per product, with the twin order matched |
| Bol.com + Google Ads | Total paid acquisition across both channels rather than two disconnected dashboards |
| Bol.com + Search Console | Whether the products people search for on your site are the products that sell on the marketplace |
| Bol.com + content pipeline | Product content written for the items with proven marketplace demand |
| Bol.com + Slack | A morning digest of marketplace orders, returns and commission |
What you need to connect Bol.com
- A retailer API client id and secret, with the retailer scope
- Optionally an advertiser API client id and secret, if you run sponsored products
- Nothing else
Two things are worth knowing before you compare the numbers to your Bol.com dashboard. The orders endpoint defaults to open, fulfilled-by-retailer orders only, so a naive integration under-reports. This connector asks for all fulfilment methods and all statuses on every call. And advertising performance is fetched one day at a time rather than as a range, because a range call returns a rolling total that inflates a month if you sum it.
Frequently asked
Does the Bol.com integration store customer data? No. Bol.com does not expose a real customer identity and the connector deliberately keeps it that way. Names, addresses and alias emails are not landed.
Does it cover both the Retailer API and the Advertising API? Yes, with separate credentials for each.
How far back can advertising data go? Thirty days. That is a hard limit of the advertising API, which is why the schedule matters: a day not ingested inside the window is lost.
Can commission be reconciled? Yes. Commission is checked against the invoice totals and a mismatch surfaces as a failing data test rather than as a silently wrong report.