HEMA Price Monitor - Product prices for the Netherlands avatar

HEMA Price Monitor - Product prices for the Netherlands

Pricing

from $2.80 / 1,000 product checkeds

Go to Apify Store
HEMA Price Monitor - Product prices for the Netherlands

HEMA Price Monitor - Product prices for the Netherlands

Watches public HEMA product pages and records the price and availability. Returns the product name, SKU, price, currency, and stock state. One run accepts up to five https://www.hema.nl product URLs. Results as JSON, CSV or Excel. Access through API or MCP.

Pricing

from $2.80 / 1,000 product checkeds

Rating

0.0

(0)

Developer

Muhammet Mustafa Dincer

Muhammet Mustafa Dincer

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Features

Limited permissions

Share

💼 Looking for another Netherlands product price watch instead? 👉 Praxis Price Monitor - Product prices for Netherlands

🤖 What does HEMA do?

HEMA reads a public product page and keeps the price and the availability. The source is www.hema.nl. The first saved reading is a baseline. A later run compares the new reading with that baseline.

It can scrape:

  • Public HEMA product pages you paste, up to five in one run
  • The name, SKU, price, currency, and availability printed in Product JSON-LD
  • A later change when the saved price or availability is different

HEMA does not search the catalogue. HEMA does not log in. HEMA does not ask for an API key. A row stores the URL, the product name, the SKU, the GTIN-13 when the page prints one, the price, the currency, and the availability. The description, the images, reviews, and a person's name are not stored.

The sample page is https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html. On 10 November 2026 that page showed 5.99 EUR and InStock for zakdoek 40x40cm katoen strepen blauw - 3 stuks, SKU 01400260. InStock is the availability the page printed with that price. The seller in the page JSON-LD is the shop organization, and it is not copied into the dataset. A later run stores the price and availability the page shows then. Do not treat that figure as a permanent HEMA value.

💡 Why scrape HEMA?

People scrape HEMA when the same public page would otherwise be opened by hand. The fields support a price check, a stock check, and a change log. They do not support a review export or a full catalogue dump.

  • Watch one HEMA product on a schedule and keep the reading.
  • Feed a sheet. The dataset opens as JSON, CSV, or Excel.
  • Call HEMA from the Apify API with the same input.
  • Hand the same input to an agent through Apify MCP.
  • Start from the prefilled HEMA sample, which is one real product URL.

HEMA is for the URL you already have. It is not a site search, and it does not walk category pages.

🚀 How to scrape HEMA

  1. Click Try for free.
  2. Keep the prefilled product URL, or paste up to five www.hema.nl product URLs.
  3. Leave Only changes off for the sample so a repeated run still writes the current reading. The schema default is on, and the prefill is off.
  4. Leave the watchlist name as default, or type another name when this list should not share the old baseline.
  5. Click Run. Download the dataset as JSON, CSV, or Excel.
{
"productUrls": [
"https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"
],
"onlyChanges": false,
"monitorName": "default"
}

A second run with the same input writes the current HEMA reading again while only changes stays off. Turn only changes on after a baseline exists when a quiet check should add a row only if the saved reading moved. A first read is still written.

⚠️ Limits

HEMA enforces the limits below. Anything not listed is not a limit this code applies.

  • The path must be one https://www.hema.nl product URL. Home, search, account, cart, checkout, and login URLs are rejected.
  • At most five URLs per run. A duplicate URL is skipped.
  • The query string is removed, so a tracking parameter is not a second product.
  • Requests are one at a time. The HTTP timeout is 30 seconds.
  • HTTP 403 is an error and is not retried. HTTP 429 stops further products. A challenge page with no JSON-LD is not bypassed.
  • A page with no JSON-LD price is no_data and is not charged.
  • If the maximum charge cannot cover a check, the page is not requested. If a change cannot be covered, the new price is not stored and the baseline stays.
  • HEMA does not log in, does not store personal data, and does not read a membership price that is not in the public JSON-LD price it keeps.

Default memory is 512 MB. There is no proxy setting in the input.

💳 How much will it cost to scrape HEMA?

Pay per event. The table copies the live pricingInfos for the events this code passes to Actor.charge. The amounts are the live tier prices, not a rounded marketing price.

Event name (Actor.charge)Event titleWhen the code charges itPrice (USD)
product-checkedProduct CheckedOne saved product page included a price. A first baseline and a later unchanged reading both use this event.FREE 0.004 / BRONZE 0.0036 / SILVER 0.0032 / GOLD 0.0028 / PLATINUM 0.0028 / DIAMOND 0.0028
price-changedPrice ChangedCharged in addition to the product check when the price or availability differs from the saved baseline. The first baseline is not this event.FREE 0.006 / BRONZE 0.0054 / SILVER 0.0048 / GOLD 0.004 / PLATINUM 0.004 / DIAMOND 0.004

1,000 product-checked events at the FREE unit price of 0.004 USD are 4 USD. The lowest unit price on the live price list is 0.0005 USD for apify-actor-start on FREE, which is 0.5 USD for 1,000 events. These figures are copied from the live price list. They are not rounded.

apify-actor-start is on the live price list at 0.0005. This code does not call Actor.charge for that name. The platform can still bill Actor Start from the price list.

A page without a price, an HTTP error, a challenge page, a skip after HTTP 429, and a target the spending limit cannot pay for are not charged. charged is true only when Actor.charge returns a chargedCount that covers every event for that row. An ignored charge is stored as charged false and is not a spending limit. The row can still be kept.

📝 Input

FieldRequiredWhat the code does with it
Product URLsYesHEMA product URLs. The path must be one https://www.hema.nl product URL. Home, search, account, cart, checkout, and login URLs are rejected.
Only changesNoOff in the prefill, so a repeated sample still writes the current reading. On, after a baseline exists, writes a row only when the saved reading moved. A first read is always written. The schema default is on.
Watchlist nameNoRuns that share this name share one baseline. The prefill is default. The name must be 80 characters or fewer.
{
"productUrls": [
"https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"
],
"onlyChanges": false,
"monitorName": "default"
}

📊 Output

One shortened record from the dataset schema example for the sample page. The field names are the names the code writes.

{
"recordType": "observation",
"status": "baseline_saved",
"name": "zakdoek 40x40cm katoen strepen blauw - 3 stuks",
"sku": "01400260",
"price": 5.99,
"currency": "EUR",
"availability": "InStock",
"productUrl": "https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html",
"attribution": "HEMA"
}
FieldMeaning
recordTypeobservation for one saved reading.
statusbaseline_saved, unchanged, changed, no_data, api_error, unreachable, rate_limited, or not_fetched.
changeTypebaseline, unchanged, or changed.
nameProduct name from the page.
skuSKU from the page.
gtin13GTIN-13 when the page prints one. Otherwise null.
pricePrice kept from the page.
currencyCurrency code from the page.
availabilitySchema.org availability from the page, or null when the page does not print one.
productUrlProduct page after the query string is removed.
attributionHEMA when a price was kept.
chargedTrue only when Actor.charge covered the events for the row.
chargeOutcomesucceeded, ignored, rejected, or not_charged.

🔌 Integrations and API

Run this Actor with the Apify API, a schedule, or the Apify MCP server. Apify can send the dataset to Make, Zapier, or a webhook. This Actor does not implement a custom integration of its own.

The input object uses keys from the input schema. The slug is mmdincer/hema-product-price-monitor.

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('mmdincer/hema-product-price-monitor').call({"productUrls": ["https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"], "onlyChanges": false, "monitorName": "default"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("mmdincer/hema-product-price-monitor").call(run_input={"productUrls": ["https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"], "onlyChanges": false, "monitorName": "default"})
items = client.dataset(run["defaultDatasetId"]).list_items().items

❓ FAQ

How do I scrape HEMA with a small first run?

Keep the prefilled URL, leave only changes off, and leave the watchlist name as default. That is one product page. Run it twice: the first row is a baseline, and the second is unchanged while the price and availability stay the same.

Does HEMA search the shop?

No. HEMA reads only the product URLs in the input. Home, search, account, cart, and checkout URLs are rejected before a request.

What does HEMA skip without a charge?

no_data, HTTP errors, challenge pages, and targets skipped for the spending limit do not call Actor.charge for product-checked or price-changed. The first baseline is a product check, not a price change.

Can I keep two HEMA lists apart?

Yes. The watchlist name is the baseline key. Use a new name to start over without deleting the old snapshot.

Is an owner run Store QA?

No. An owner run of the sample is not Store QA.

HEMA reads a public product page. It does not log in, and it does not store a person's name, a review, or an image. The terms page that was read is the Thuiswinkel consumer contract at https://www.hema.nl/algemene-voorwaarden. The text does not mention scraping, robots, spiders, crawlers, reuse, or a database right. The word automatisch on that page is about a trial magazine subscription ending. There is no written open licence for the price. The robots file allows / and disallows search and checkout paths.

Not affiliated with HEMA. HEMA does not endorse this Actor.

This is not legal advice. You are responsible for the source's terms and, if you process personal data, for GDPR. Apify's overview: https://blog.apify.com/is-web-scraping-legal/.

The dataset field message says what changed, or why the row was not stored.

ActorWhat it does
Praxis Price Monitor - Product prices for NetherlandsWatches public Praxis product prices in the Netherlands.
Toolstation Price Monitor - Trade prices for the UKPublic Toolstation product price and availability.
Globus Baumarkt Price Monitor - DIY prices for GermanyPublic Globus Baumarkt product price and availability.