Integration
bol and Zuduno
The largest marketplace in the Netherlands and Flemish Belgium.
What syncs
Four things move, and the arrow says which way.
Nothing here is maintained separately. What Zuduno sends is derived from the one product record; what it receives lands on the same records as every other channel.
- Products
- Zuduno sends.This channel's version of the record, generated from the master and kept in step with it.
- Inventory
- Zuduno sends.Availability by location, with reservations held back so a promised unit is not sold twice.
- Orders
- Zuduno receives.Orders and their exceptions land in the same worklist as every other source.
- Prices
- Zuduno sends.Channel prices derived from the record, resolved per market.
Markets
Where this one applies.
Belgium · the Netherlands
Markets, not marketplaces. The same channel can serve two countries whose rules differ, and readiness resolves against the country.
Readiness
What is checked before anything is submitted.
- Required attributes for each product type
- Identifiers — GTIN, EAN, SKU, MPN — present and valid
- Compliance fields the market requires, resolved per market rather than per channel
- Category and taxonomy mapping
What it needs from you
Credentials, and nothing else.
API credentials for your own account, scoped to the operations above. Zuduno connects as you; it does not resell access and there is no partnership behind this page.
Known limitations
What this one does not do.
- It does not manage advertising, campaigns or bidding.
- It does not create the channel account or negotiate the terms.
- It submits only what readiness has passed — a product with a blocking issue is held back rather than submitted and corrected.
bol is a third-party product. The name and mark identify it and imply no partnership or endorsement.
Evaluate bol in your operating scope.
Confirm the data flows, markets, account permissions and readiness rules your implementation requires.