Skip to main content

Bol.com synchronisation

Learn how Optiply synchronises data with Bol.com. This guide covers its role as a secondary integration, the required product mapping keys (EAN/SKU), and the logic for syncing both FBR and FBB orders.

Ricardo Guerreiro avatar
Written by Ricardo Guerreiro
Updated over 2 weeks ago

πŸ”— Bol.com: Data Mapping & Synchronisation

This guide details the data flow between Bol.com and Optiply.

Important: Bol.com functions as a Secondary Integration in Optiply. This means we only sync Sell Orders and Sell Order Lines from Bol.com. Your Products must be imported from a different primary source (such as WooCommerce, Shopify, or an ERP).

⏱️ Synchronisation General Board

The following table outlines the data entities and their update frequency.

Entity

Direction

Frequency

Sell Orders

Bol.com β†’ Optiply

Every 60 minutes

Sell Order Lines

Bol.com β†’ Optiply

Every 60 minutes


βš™οΈ Configuration: Mapping Keys

Since products originate from another system, Optiply needs to know how to link the items sold on Bol.com to your existing product database.

  • The Challenge: Bol.com uses EAN as its main key. However, many sellers mistakenly or intentionally enter their internal SKU Code into the EAN field on Bol.com.

  • The Solution: During the integration setup, you will see an option to select the Mapping Key. You must choose which field Optiply should use to match the products:

    • SKU Code

    • EAN Code


πŸ—ΊοΈ Data Mapping Details

1. Sell Orders

Data is retrieved from the /retailer/orders? and /retailer/shipments? endpoints.

Fulfilment Scope:

Unlike some integrations, we pull BOTH:

  • FBR: Fulfilled by Retailer (orders you ship yourself).

  • FBB: Fulfilled by Bol.com (Logistiek via Bol).

Optiply

Bol.com

Total Value

Sum of SellOrderLine.subtotalValue.

Placed Date

orderPlacedDateTime

Remote ID

orderId

⚠️ Important Limitation: We do not sync order changes. Once an order is imported, any subsequent line changes, deletions, or new lines added to that existing order in Bol.com will not be updated in Optiply.

2. Sell Order Lines

Data is retrieved from /retailer/orders/{order-id} and /retailer/shipments/{shipment-id}.

Optiply Field

Bol.com Field

Notes

Product ID

optiplyWebshopProductId

Mapped via EAN or SKU (see Configuration above).

Quantity

quantity

-

Subtotal Value

Calculated

unitPrice * quantity


❓ Frequently Asked Questions (FAQs)

Why don't I see my products in Optiply yet?

Because Bol.com is a Secondary integration, it does not import products. You must first connect a Primary source (like Shopify or Magento) to populate your product list. Bol.com only adds sales history to those existing items.

I ship my own orders (FBR). Will they sync?

Yes. This integration pulls both FBB (Fulfilled by Bol) and FBR (Fulfilled by Retailer) orders.

Why is the Total Value calculated differently?

We calculate the order total by summing the subtotal of the lines (unitPrice * quantity). This ensures the value in Optiply reflects the actual product revenue relevant for purchasing forecasts, excluding unrelated platform fees or taxes where possible.

Can I map using the internal Bol.com ID?

No. You must map using EAN or SKU. Please ensure the identifier you select in the settings matches the data you have in your primary webshop.
​

Did this answer your question?