HEMA Scraper

Scrapes products from hema.com, the popular Dutch/Belgian variety store. Supports the Belgian (nl-be, fr-be) and Dutch (nl-nl) storefronts with a single configuration.

What makes this scraper different

HEMA embeds product data in data-gtmproduct attributes on product tiles, which means the scraper can extract structured data (name, price, product ID, stock status, rating, category) directly from listing pages without visiting every product page. This makes it significantly faster.

Set scrapeProductPages: true if you need full descriptions, image galleries, and specs.

Input

Field	Type	Required	Description
startUrls	Array	No	HEMA category or product page URLs
searchQuery	String	No	Search term (e.g., "lamp", "handdoek")
maxResults	Integer	No	Max products (default: 100)
country	String	No	Storefront: nl-be (default), nl-nl, or fr-be
scrapeProductPages	Boolean	No	Visit detail pages for descriptions and specs (default: false)
proxyConfiguration	Object	No	Proxy settings

Output

Field	Type	Example
name	String	"handdoek 50x100 zware kwaliteit roze"
brand	String	"HEMA"
price	Number	7.00
originalPrice	Number	9.00
currency	String	"EUR"
productId	String	"60211304"
sku	String	"60211304"
inStock	Boolean	true
rating	Number	4.1
category	String	"Bad"
imageUrl	String	Product image (600px)
language	String	"nl"

With scrapeProductPages: true, you also get: description, imageUrls, specs.

Pagination

HEMA uses start= and sz= URL parameters. The scraper reads the total item count from the page (e.g., "85 artikelen") and automatically generates next-page URLs in batches of 24.

Cost

Without detail pages: ~$0.10 per 1,000 products (very fast, data from listing tiles). With detail pages: ~$0.40 per 1,000 products.

Notes

• Product page URLs end with -DIGITS.html (e.g., /nl-be/handdoek-60211304.html)
• The scraper auto-upgrades product tile images to 600px high-res versions
• GTM product data includes a category path like "PARTY|Party|PARTYGOODS" which is parsed into readable names

Why use HEMA Scraper

• Price monitoring — Track prices, stock, and promotions across HEMA at scale
• Competitive intelligence — Compare your catalog against HEMA pricing and assortment
• Market research — Analyze category trends, new arrivals, and rating distributions
• Lead generation — Build product datasets for affiliate sites, comparison tools, or feeds
• No login or cookies required — Authenticated access not needed; works out of the box

How to use HEMA Scraper

1. Open the Input tab and provide a search query, category URL, or product list
2. Adjust optional filters such as maxResults or proxy settings
3. Click Start and wait for the run to complete
4. Download results from the Output tab in JSON, CSV, Excel, XML, or HTML
5. Schedule recurring runs from the Schedule tab if you need ongoing data

How to scrape HEMA data

This Actor automates the process of extracting structured product data from HEMA. You can run it directly from the Apify console, the Apify API, or any of the official SDKs (JavaScript, Python). The scraper handles pagination, retries, and rate limiting so you can focus on the data, not the plumbing.

Typical workflows:

• One-off export: paste a category URL or keyword, set maxResults, and run
• Scheduled monitoring: set a daily cron in the Schedule tab to track prices over time
• Programmatic integration: trigger runs from your backend via the Apify API and pull the dataset when finished
• Webhook automation: receive a callback the moment a run completes and pipe the results into Zapier, Make, n8n, BigQuery, or Google Sheets

Tips for best results

• Start small — run with maxResults: 10 before launching large jobs
• Use proxies — residential proxies reduce blocking on protected sites
• Throttle on big jobs — keep maxConcurrency modest (5–10) for stability
• Schedule runs — daily runs are usually enough for price monitoring
• Inspect the dataset schema — the Storage tab shows the full output structure

FAQ and support

Is it legal to scrape HEMA? This Actor extracts publicly available data. Always review the website's Terms of Service before scraping at scale, and respect rate limits.

Why am I getting fewer results than expected? Some categories have hidden pagination or load more on scroll. Increase maxResults and verify your filters.

Can I extract data for a single product? Yes — provide the full product URL in startUrls and the scraper will return one item.

The site blocks me — what should I do? Enable Apify residential proxies in the input. Datacenter IPs are blocked by many e-commerce sites.

For issues, feature requests, or bug reports, open a ticket in the Issues tab on the Actor page or contact support@apify.com. We monitor every actor and ship fixes quickly when sites change.