EAN to bol.com Product ID Converter

Convert EAN to bol.com product IDs (BPIDs) and resolve bol.com product IDs back to EAN barcodes, in bulk. Supply a list of EAN, UPC, GTIN or BPID codes and receive the verified mappings that bol.com publishes for those products. Sellers, brands and catalogue teams use it to link their own product data to bol.com product pages. You can mix both directions in a single run.

The converter helps connect a retailer's catalogue to the identifiers used on bol.com. A BPID identifies a bol.com product page, while an EAN, UPC or GTIN identifies a product barcode. These identifiers serve different purposes, so matching them is a useful first step before comparing catalogue records, preparing inventory exports or linking product information across systems.

EAN to bol.com conversion

For a barcode, the actor searches bol.com and checks the product specifications of up to three candidate products. A candidate is returned only when the EAN in its specifications matches the searched barcode. This verification matters because a search can suggest similar products when the exact barcode is unavailable. An unrelated search suggestion is not a conversion.

For a bol.com product ID, the actor reads the EAN from that product's specification table. A product group can contain several variants with different barcodes. The result refers to the requested product page and its own specifications.

Input

The required input is codes, an array of strings. You can submit between one and 1000 codes, mixing BPIDs with EAN, UPC and GTIN codes. Keep codes as strings so leading zeros remain intact. There is no input default; enter the codes you want to convert.

This input was tested against the published actor and the current implementation:

{
  "codes": [
    "9300000220200424",
    "9300000226818476",
    "5702017829241",
    "8718924810217"
  ]
}

The run found three mappings. The last barcode had no verified product available on bol.com during the measurement. Availability can change after that measurement, so a previous match does not guarantee a future one.

BPIDs contain sixteen digits and begin with 9. Barcode inputs may contain eight, twelve, thirteen or fourteen digits. For the lookup, punctuation and surrounding whitespace are removed; eight-digit and twelve-digit barcodes are padded to thirteen digits. The original input is retained in the result. Codes starting with the normalized prefix 17505 are rejected, and other unsupported formats are listed as invalid. The actor does not perform a barcode checksum test.

Duplicate codes are processed separately. Their results retain the order of the submitted codes. This is useful when each code corresponds to a separate row in an inventory file.

Output

Only verified conversions become dataset rows. Each result retains the original five string fields:

• request_type: BPID or EAN, depending on the input direction.
• input_code: the exact string submitted by the user.
• bpid: the bol.com product ID, retaining the original string for BPID input.
• ean: the barcode, retaining the original string for barcode input.
• timestamp: the conversion time, in the existing format without a timezone suffix.

Additional fields make the results easier to join with other catalogue data. product_id holds the normalized BPID, gtin and ean_normalized hold the verified barcode, and url links to the product page. source identifies this converter, country is NL, and fetched_at supplies a UTC timestamp with a timezone suffix.

This is a real row from the run with the input above, for the barcode 5702017829241:

{
  "request_type": "EAN",
  "input_code": "5702017829241",
  "bpid": "9300000227400169",
  "ean": "5702017829241",
  "timestamp": "2026-10-03T10:43:33.666000",
  "source": "ean-to-bol-com-product-id-converter",
  "fetched_at": "2026-10-03T10:43:33.666Z",
  "product_id": "9300000227400169",
  "gtin": "5702017829241",
  "ean_normalized": "5702017829241",
  "country": "NL",
  "url": "https://www.bol.com/nl/nl/p/-/9300000227400169/"
}

The same run converted the bol.com product ID 9300000220200424 to the EAN 8721082896108.

The default key-value store contains an OUTPUT record with counts for found products, genuine misses, invalid codes and failed requests. RUN_STATS includes the total, counts for each conversion direction and the match rate. An errors record is written when individual codes fail or are invalid. Codes with no match do not become empty or speculative dataset rows.

Batch processing and limits

Larger inputs are processed automatically in smaller parts. Submit your full list to the actor; you do not need to manage continuation yourself on Apify. Every completed part preserves the input order, and duplicate conversions remain separate rows. If a source request fails, its error is recorded and successful conversions remain available.

A run that finds no conversions completes with an empty dataset. The output counts distinguish missing products from invalid input and source failures. When investigating an empty result, check these counts and the errors record before deciding that the barcode is unavailable.

Use cases for an EAN to bol.com converter

• Sellers listing on bol.com. Match the barcodes in your supplier feed or ERP to existing bol.com product pages before you create offers, so you know which products already exist on the platform.
• Brands and manufacturers. Check which of your EANs are live on bol.com and collect the product page URL for each one, for distribution reports or retail audits.
• Price and assortment monitoring. Many bol.com tools work with BPIDs. Convert your EAN list once, store the product_id, and feed it to the monitoring step that reads prices or offers.
• Reverse lookup. You found a bol.com product page in a report or a competitor feed and need the barcode for your own catalogue. Submit the BPID and receive the EAN from that page's specifications.

How it compares with other ways to look up a bol.com EAN

Searching bol.com by hand works for a few products, but it does not scale to a full catalogue and a search result may be a similar product rather than the exact barcode. The official bol.com retailer API returns identifiers for your own offers once you have a seller account and API credentials; it does not map arbitrary barcodes for products you do not sell yet. General barcode lookup sites tell you what a product is, but not which bol.com product ID it has. This EAN to bol.com converter accepts any list of codes, needs no bol.com account, verifies every match against the barcode in the product specifications, and returns rows you can join directly on gtin or product_id.

Pricing

The price is $0.004 per delivered dataset row, so converting 1,000 codes that all match costs $4.00. Codes that do not match cost nothing. Apify charges the dataset-item event automatically. There is no additional per-run start charge. A barcode that is not found, an invalid code, or a request that fails produces no dataset row and no result charge. Two successfully converted duplicate inputs produce two rows and are charged as two results.

Users without a paid Apify plan receive up to ten found results per run. Missing products do not consume those ten result places. The input list is still checked, and the summary records count all found conversions before the delivery cap. Use the delivered-result counts to see what was actually added to the dataset.

FAQ

Can I mix EANs and bol.com product IDs?

Yes. Put both kinds of code in the same codes array. Each returned row identifies its conversion direction through request_type.

Why does a barcode return no row?

The product may not be sold on bol.com, none of the candidate specifications may match the barcode, the input may be invalid, or a source request may have failed. OUTPUT and the errors record distinguish these outcomes. A suggested product with a different EAN is deliberately excluded.

Are duplicate inputs removed?

No. Duplicate codes are processed and delivered separately when a verified conversion is found. Input order is preserved, and every delivered duplicate is a separate result for pricing purposes.

Which barcode field should I use for joining catalogues?

Use gtin or ean_normalized. The legacy ean field retains the original barcode input, including any spaces or punctuation, so existing integrations keep their original values. The normalized fields provide the verified digits for catalogue joins.

Does this return prices or stock levels?

This actor returns identifier mappings. Its dataset does not promise prices, seller details or stock levels. Use the returned product ID and URL to connect the mapping to the product data needed by your own workflow.

Do I need a bol.com account or API key?

No. The converter reads the public bol.com product pages. You only need an Apify account to run it.

Does the EAN to bol.com conversion work for Belgian products?

The lookup uses the Dutch bol.com catalogue, and country is NL in every row. The Belgian storefront is not checked separately.