# Beslist.nl Scraper (`s-r/beslist-scraper`) Actor

- **URL**: https://apify.com/s-r/beslist-scraper.md
- **Developed by:** [SR](https://apify.com/s-r) (community)
- **Categories:** E-commerce, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Beslist.nl Scraper

Point it at a Beslist category or search term and it returns the products with their **barcodes**, the cheapest and dearest price across every shop selling them, and how many shops that is.

No login, no cookie, no API key. It reads the ordinary browse page from an exit inside the Netherlands, so the prices are the ones Dutch shoppers actually see.

### What you get

- **The EAN in the product URL** on catalogue products, so one browse page hands you dozens of barcodes without opening a single product page. That is an exact join key against your own catalogue, against Amazon, against Google Shopping. Coverage depends on the category: electronics runs at or near 100%, apparel at zero, and `product_id` carries Beslist's own identifier either way
- **A real price range, not a single number.** `lowest_offer` and `highest_offer` are the cheapest and dearest of the shops selling that product, and `price_spread` is the difference. On laptops that spread runs to €250 on a single model
- **How many shops sell it**, read from the card's own "Vergelijk 3 prijzen" link. A product sold by one shop and a product sold by eight are completely different competitive situations
- **The range cross-checked against the page's own structured data**, with the number of mismatches reported in the run summary. If the two ever disagree you find out from the summary rather than from a bad decision
- **Selectors built to survive a frontend deploy.** Beslist ships hashed CSS module class names; every selector here matches the stable prefix, never the hash
- **Soft blocks detected rather than parsed.** A 202 carrying a 2 KB shell is retried, not reported as an empty category
- **`ean_only` for catalogue work**, which drops rows that carry no barcode

### Why a comparison site instead of a shop

A shop tells you its own price. A comparison site tells you the market's.

For pricing work that difference is everything. If you sell a product for €629 you cannot tell from your own site whether that is competitive. Beslist lists the same barcode across every merchant carrying it and prints the cheapest and dearest, which is the number you need: not "what does this cost" but "what is the range, and where in it am I".

The barcode is what makes it usable at scale. Most retail scrapers return a title and a price, and joining those to your own products means fuzzy string matching that is wrong often enough to be dangerous. An EAN is exact. In the categories that carry them, and electronics and appliances do, that turns Beslist from a website into a lookup table you can join against. The run summary reports the coverage so you never have to assume it.

### Input

| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| `query` | string | one of the two | `laptops` | What to look up. Dutch terms work best |
| `url` | string | one of the two | – | A beslist.nl category or search URL. Takes precedence |
| `limit` | integer | no | `50` | Products to return, 1 to 900. A page carries about 45 |
| `ean_only` | boolean | no | `false` | Drop rows with no barcode in the URL |
| `retries` | integer | no | `3` | Retry attempts per page |

### Output

```json
{
  "position": 2,
  "ean": "0199896035279",
  "url": "https://www.beslist.nl/p/hp-17-cn4853nd-laptop-17-3-inch/6/0199896035279/",
  "title": "HP - 17-cn4853nd - Laptop - 17.3 Inch - Intel Core 7",
  "price": 599.0,
  "lowest_offer": 599.0,
  "highest_offer": 729.0,
  "price_spread": 130.0,
  "price_text": "€599,- - €729,-",
  "currency": "EUR",
  "offer_count": 2,
  "structured_low": 599.0,
  "structured_high": 729.0,
  "is_popular": false,
  "image": "https://hwimages.beslist.net/...",
  "enriched": true,
  "query": "laptops"
}
```

### Use cases

**Finding where you sit in the market.** Run your category, join on `ean` against your own catalogue, and compare your price to `lowest_offer`. Every product where you are above it is one you are losing on price, and `price_spread` tells you how much room the market actually has.

**Finding products worth stocking.** A high `price_spread` with a high `offer_count` means a competitive product where shops still disagree on price, which is where margin hides. A zero spread means everyone charges the same and there is nothing to win.

**Building an EAN list for a category.** Set `ean_only` and raise `limit`, and one run gives you the barcodes for a whole category. Feed those to an Amazon, Google Shopping or bol.com lookup and you have the same products priced on every channel.

**Watching a competitor's price moves.** Schedule the same category daily and diff `lowest_offer` per `ean`. A drop in the minimum means somebody undercut, and `offer_count` tells you whether a new seller arrived.

**Sanity-checking your own feed.** If your product is on Beslist, its barcode appears here with the price the market shows. A mismatch against what you believe you charge usually means a stale feed.

### How it compares

| | this actor | `stealth_mode/beslist-product-search-scraper` | `harvestedge/dutch-supermarkets-all-11` |
|---|---|---|---|
| Per 1.000 products | **$2,00** | no per-item rate at all | $5,00 |
| Actor-start fee | **$0,002** | $0,005 | none |
| EAN per row | **yes, where the category has them** | not stated | no |
| Price range across merchants | **yes** | no | no |
| Number of shops per product | **yes** | no | no |
| Range verified against structured data | **yes** | no | no |
| Monthly users | new | 1 | 5 |

Honest about the other side: `harvestedge` has five monthly users and covers eleven Dutch supermarkets, which is a different job entirely and one this actor does not do. On Beslist itself the only competitor has one user and charges a flat fee per run with no per-row rate, so a large run there is cheaper than here and a small one is dearer.

### Pricing

Two events. `run_start` costs $0,002 per run. `product` costs $0,0020 per product written to the dataset, which is $2,00 per 1.000. Pages that come back as a challenge shell never reach the dataset and are never billed. All pricing is pay-per-event, with no per-compute-unit charges.

### Limits and gotchas

- **`lowest_offer` and `highest_offer` are a range, not a discount.** The card prints them as two prices side by side and they look exactly like a was/now markdown. They are not. The page's own structured data reports the same pair as `lowPrice` and `highPrice` of an aggregate offer. Treating the higher one as a former price would tell you half a category is on sale when none of it is.
- **Structured data covers the first ten products only.** `structured_low` and `structured_high` are present on those and absent on the rest. The DOM range is on every row either way; the structured pair exists to verify it, and `structuredMismatches` in the run summary is the check.
- **EAN coverage is a category property, not a quality one.** Beslist runs two id schemes in the same URL slot: a barcode for catalogue products and a `V4_<uuid>` for a merchant's own listing. Electronics categories return barcodes on essentially every row; **apparel searches return none at all**, because sneakers are listed per merchant rather than per catalogue entry. Check `withEan` in the run summary before building a join, and use `ean_only` to drop the rest.
- **An unknown search term returns HTTP 404**, because Beslist has no empty-results page. The run reports `no_results` and exits successfully rather than failing.
- **The card and the structured data occasionally disagree**, almost always on the from-price and by a few euros. Neither is a parse error; the card is what a shopper sees, so `lowest_offer` follows the card and `structured_low` is returned beside it. `structuredMismatches` in the summary counts them, typically one row in ten.
- **Class names are hashed and will change.** Beslist ships CSS modules, so `price--FX-nM` becomes something else on their next frontend build. Every selector here matches the prefix before the hash, which is what makes that survivable, but a large enough redesign still needs a new parser.
- **A 202 with a tiny body is a block, not an empty page.** It is retried with a fresh fingerprint and reported as `stub_page` if it persists, rather than being written out as zero products.
- **The offer count is what the card claims.** It comes from Beslist's own "Vergelijk N prijzen" text and reflects merchants in their index, not every shop in the country.

### FAQ

**Can I get EAN barcodes from Beslist without opening every product page?**
Yes, and that is the main reason to use this. The barcode is in the product URL on the browse page, so a single page yields about 45 of them.

**Is the second price a discount?**
No. It is the most expensive offer among the shops selling that product. `price` and `lowest_offer` are the cheapest, `highest_offer` the dearest, and `price_spread` the gap.

**Why does my apparel search return no barcodes?**
Because apparel is listed per merchant on Beslist, not per catalogue product, so those URLs carry a `V4_` identifier instead of an EAN. `product_id` still gives you a stable key. Electronics and appliance categories return real barcodes.

**Why do some products show the same price twice?**
Because every shop selling it charges the same, so the range has zero width. `price_spread` is 0 on those.

**How many products can I get in one run?**
Up to 900, which is about 20 pages. Beyond that, split by category.

**Does it return each individual shop's price?**
No. It returns the range, the count and the barcode from the browse page. The per-merchant breakdown lives on the product page, which this actor does not open.

### Related Actors

- [Google Shopping Scraper](https://apify.com/s-r/free-google-shopping-scraper---extract-offers-from-any-ean-sku) — every merchant's offer for an EAN or SKU
- [EAN to ASIN Converter](https://apify.com/s-r/free-ean-to-asin-converter---turn-any-ean-into-an-amazon-asin) — turn these barcodes into Amazon ASINs
- [Sitemap to Product Catalog](https://apify.com/s-r/sitemap-product-catalog) — the full product URL list for any single shop

# Actor input Schema

## `query` (type: `string`):

What to look up on beslist.nl. Dutch terms work best. Optional if you pass a URL instead.

## `url` (type: `string`):

A beslist.nl category or search URL to read instead of a term. Paste it from your browser after applying any filters. Takes precedence.

## `limit` (type: `integer`):

How many products to return, 1 to 900. A page carries roughly 45.

## `ean_only` (type: `boolean`):

Drop rows whose URL carries no barcode. Use this when the output feeds a catalogue join.

## `retries` (type: `integer`):

Retry attempts per page, each with a rotated user agent and TLS fingerprint.

## Actor input object example

```json
{
  "query": "laptops",
  "url": "https://www.beslist.nl/products/r/koffiezetapparaat/",
  "limit": 50,
  "ean_only": false,
  "retries": 3
}
```

# Actor output Schema

## `results` (type: `string`):

One row per product, with its EAN and its price range across merchants.

## `summary` (type: `string`):

Products returned, how many carried an EAN and an offer count, how many have a real price spread, and the cross-check against the page's structured data.

## `errors` (type: `string`):

Per-page failures with a code and a redacted message.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "laptops",
    "limit": 50,
    "retries": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("s-r/beslist-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "query": "laptops",
    "limit": 50,
    "retries": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("s-r/beslist-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "laptops",
  "limit": 50,
  "retries": 3
}' |
apify call s-r/beslist-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,s-r/beslist-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FwU0KSWhm4QjKEOcf/builds/njYkRKii7DrKJSbDb/openapi.json