This Bol.com scraping tutorial shows how to scrape Bol.com product details from known product-page URLs into CSV with the Bol.com Product Details Scraper for UScraper. You will import the workflow, replace the sample URL list, confirm the export path, validate the output, and understand when the official Bol.com APIs are a better fit.
Before you start
Prerequisites for a Bol.com scraping tutorial
You need UScraper installed as a local desktop app, a controlled list of Bol.com product-page URLs, and a folder where CSV exports can be saved. Start with three to five URLs: a normal product, a specification-heavy product, a multi-image product, and one page that might be unavailable. That small set exposes selector, access, and data-quality problems before you process a larger catalog.
Use the Bol.com Product Details Scraper as the download path for this post. The template page carries the current JSON workflow, hosted import file, export column names, and CTA; this article is the runbook that explains why each step exists.
This guide covers visible product detail pages only, not account pages, checkout flows, partner dashboards, login-only data, CAPTCHA bypassing, or resale of marketplace data. Review Bol.com source rules, robots directives, database rights, privacy obligations, and your own commercial permissions before automating collection.
Treat browser access and data permission as separate checks. If the page shows a block, challenge, login wall, or consent state you are not allowed to automate through, stop and choose an approved route.
Workflow shape
What the Bol.com product details scraper exports
The workflow is built for known product URLs, not keyword discovery. Add product pages to the Navigate block, run the multi-URL loop, and UScraper appends one row per page. The bundled JSON sets a large viewport, waits for load, checks for an IP-block message, handles common consent buttons, and then runs Structured Export.
| CSV column | What it captures | Validation check |
|---|---|---|
title | Product name from JSON-LD or the visible page heading | Compare against the H1 on the product page. |
brand | Brand from structured data or brand-like page elements | Expect blanks on listings that do not expose a brand. |
price | Offer price or visible price text cleaned for spreadsheet use | Confirm currency context before downstream analysis. |
image_urls | Product images from JSON-LD, metadata, or visible images | Check that URLs point to product media, not page chrome. |
delivery | Delivery, stock, or availability wording when visible | Treat delivery text as time-sensitive. |
description | Product description or a diagnostic block message | Review long cells for truncation after export. |
specifications | EAN, productinformatie, kenmerken, or table pairs | Keep line breaks if your BI tool supports multiline cells. |
page_url | The current Bol.com URL used for audit and deduplication | Use it as the primary traceability field. |
Runbook
How to scrape Bol.com product data to CSV
Import the template
Open Bol.com Product Details Scraper, download the hosted JSON, and import it into UScraper.
Replace the sample product URL
Edit the Navigate block and paste the Bol.com product-page URLs your team is allowed to process. Keep one URL per target product and remove unnecessary tracking parameters.
Keep the load and consent checks
Leave the Wait, Sleep, Text Contains, Element Exists, and Click blocks in place during the first run. They protect the export from incomplete loads and common consent overlays.
Confirm the export path
In Structured Export, check the save folder, file name, headers, and append mode. The stock file name is bol-scraper-product-details.csv.
Run a small validation batch
Run three to five URLs, open the CSV, and compare title, brand, price, delivery, specifications, and page URL against the browser before widening the list.
Open the exported CSV beside the browser and inspect the first rows manually. Make sure each input URL produced at most one row, blocked rows are obvious, and product fields line up with the visible page. Before reruns, clear the old file or save a timestamped copy so append mode cannot create duplicate rows.
Validate common Bol.com scraper issues
| Symptom | Likely cause | Fix |
|---|---|---|
BLOCKED_BY_BOL_IP in the title column | Bol.com returned an IP protection page before product data was available | Pause, review access, use a trusted residential or approved proxy route, then rerun a tiny test. |
| Blank price | Price module was hidden, delayed, unavailable, or rendered differently | Check the browser view and keep price optional for unavailable products. |
| Missing specifications | The page did not expose the expected productinformatie or table structure | Inspect that product type and update selectors only after testing several pages. |
| Repeated rows | Append mode wrote multiple runs into the same CSV | Clear the export file before reruns or dedupe by page_url. |
| Image URLs look unrelated | The fallback captured page-level images after product images were absent | Prefer JSON-LD and metadata values, then spot-check media hostnames. |
API choice
Bol.com API vs scraper: choose the right path
Bol provides official developer options for approved use cases. The Marketing Catalog API describes catalog retrieval for affiliates, including names, descriptions, specifications, images, prices, and delivery information. The Retailer API is aimed at sellers and store integrations such as orders, offers, and product content. Start with the Bol developer portal, Marketing Catalog API, and Retailer API when your use case fits those programs.
| Approach | Use when | Watch out for |
|---|---|---|
| UScraper local template | You need a supervised CSV from known product URLs and want to inspect the browser during QA. | You maintain waits, selectors, pacing, and access hygiene. |
| Official Bol.com APIs | You have approved affiliate, retailer, or partner access and need documented responses. | You need credentials, scopes, terms, and engineering integration work. |
| Hosted scraper tools | You need cloud scheduling, managed infrastructure, or larger recurring jobs. | Vendor pricing, data custody, retry behavior, and policy fit matter. |
For a small product audit, the best Bol.com scraper is usually the one your team can validate quickly and explain later. For production catalog synchronization or redistribution, choose the route that gives you the permissions and support your risk profile requires.
FAQ
Bol.com scraper FAQ
Bol.com product pages may be publicly accessible, but automated collection can still be limited by Bol.com terms, robots rules, database rights, copyright, privacy law, or local regulations. Use modest volumes, avoid bypassing access controls, and get legal review before commercial use.
Next step
Download the Bol.com product details scraper template
Download the current JSON from Bol.com Product Details Scraper, import it into UScraper, and keep this tutorial open during the first validation pass. For adjacent ecommerce workflows, browse the UScraper template library or continue through the UScraper blog for more marketplace scraping tutorials.