# HEMA Price Monitor - Product prices for the Netherlands (`mmdincer/hema-product-price-monitor`) Actor

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.

- **URL**: https://apify.com/mmdincer/hema-product-price-monitor.md
- **Developed by:** [Muhammet Mustafa Dincer](https://apify.com/mmdincer) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.80 / 1,000 product checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

> 💼 Looking for another Netherlands product price watch instead? 👉 [Praxis Price Monitor - Product prices for Netherlands](https://apify.com/mmdincer/praxis-product-price-monitor)

### 🤖 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.

```json
{
  "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 title | When the code charges it | Price (USD) |
|---|---|---|---|
| `product-checked` | Product Checked | One 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-changed` | Price Changed | Charged 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

| Field | Required | What the code does with it |
|---|---|---|
| Product URLs | Yes | HEMA product URLs. The path must be one https://www.hema.nl product URL. Home, search, account, cart, checkout, and login URLs are rejected. |
| Only changes | No | Off 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 name | No | Runs that share this name share one baseline. The prefill is `default`. The name must be 80 characters or fewer. |

```json
{
  "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.

```json
{
  "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"
}
```

| Field | Meaning |
|---|---|
| `recordType` | `observation` for one saved reading. |
| `status` | `baseline_saved`, `unchanged`, `changed`, `no_data`, `api_error`, `unreachable`, `rate_limited`, or `not_fetched`. |
| `changeType` | `baseline`, `unchanged`, or `changed`. |
| `name` | Product name from the page. |
| `sku` | SKU from the page. |
| `gtin13` | GTIN-13 when the page prints one. Otherwise null. |
| `price` | Price kept from the page. |
| `currency` | Currency code from the page. |
| `availability` | Schema.org availability from the page, or null when the page does not print one. |
| `productUrl` | Product page after the query string is removed. |
| `attribution` | `HEMA` when a price was kept. |
| `charged` | True only when Actor.charge covered the events for the row. |
| `chargeOutcome` | `succeeded`, `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`.

```javascript
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();
```

```python
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.

### ⚖️ Is it legal to scrape HEMA?

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.

### 🔗 Related actors

| Actor | What it does |
|---|---|
| [Praxis Price Monitor - Product prices for Netherlands](https://apify.com/mmdincer/praxis-product-price-monitor) | Watches public Praxis product prices in the Netherlands. |
| [Toolstation Price Monitor - Trade prices for the UK](https://apify.com/mmdincer/toolstation-product-price-monitor) | Public Toolstation product price and availability. |
| [Globus Baumarkt Price Monitor - DIY prices for Germany](https://apify.com/mmdincer/globus-baumarkt-product-price-monitor) | Public Globus Baumarkt product price and availability. |

# Changelog

This Actor's version history is a separate document: https://apify.com/mmdincer/hema-product-price-monitor/changelog.md

# Actor input Schema

## `productUrls` (type: `array`):

https://www.hema.nl product pages. Search, account, cart, and checkout URLs are rejected.

## `onlyChanges` (type: `boolean`):

Leave this off for the sample so a repeated run still writes the current reading. Turn it on after a baseline exists when the dataset should list a target only if the saved reading moved. A first read is always written.

## `monitorName` (type: `string`):

Runs that share this name share one baseline.

## Actor input object example

```json
{
  "productUrls": [
    "https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"
  ],
  "onlyChanges": false,
  "monitorName": "default"
}
```

# Actor output Schema

## `prices` (type: `string`):

Latest public price for each saved product.

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

Targets requested, baselines, changes, and how many events Actor.charge() billed.

# 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 = {
    "productUrls": [
        "https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"
    ],
    "onlyChanges": false,
    "monitorName": "default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("mmdincer/hema-product-price-monitor").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 = {
    "productUrls": ["https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"],
    "onlyChanges": False,
    "monitorName": "default",
}

# Run the Actor and wait for it to finish
run = client.actor("mmdincer/hema-product-price-monitor").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 '{
  "productUrls": [
    "https://www.hema.nl/mooi-gezond/gezondheid/tissues/zakdoek-40x40cm-katoen-strepen-blauw---3-stuks-1400260.html"
  ],
  "onlyChanges": false,
  "monitorName": "default"
}' |
apify call mmdincer/hema-product-price-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mmdincer/hema-product-price-monitor"
        }
    }
}
```

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/nGsmtrR9RUcBaXU5A/builds/2Kz6cWNdhBwpBxN57/openapi.json
