Empik Scraper
We do not have a dedicated Empik data API. What we do have is an AI scraper that reads a empik.com page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.
- empik.com
How to scrape Empik
Empik publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. Empik is a Polish category leader in books and media that has added a marketplace, so its pages now mix own-retail and third-party pricing. The way to get the data is to read the page the way a customer sees it: point the AI scraper at a empik.com URL, declare the columns you want in plain English, and schedule it. A broad-range retailer prices thousands of unrelated categories on different logics, so the useful scrape is narrow and deep rather than catalogue-wide.
What the AI scraper does with a empik.com link
The same three steps as any other page you point it at. Nothing about Empik is pre-built, which is exactly why it works on pages nobody wrote a connector for.
Paste the link
Give it a empik.com product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.
Declare the columns
Name each field, give it a type and write a line telling the AI what to look for. “product_title” and “brand” are the two most people start with. The schema is yours and you can change it between runs.
Schedule it and collect
Run it hourly, daily or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.
Set it up once. The data keeps coming.
Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.
Set it up once
Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.
Runs on your schedule
Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.
Saved in your database
Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.
Use it your way
Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.
Ask your AI assistant about your own data
Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.
- Which of my ASINs lost the Buy Box this week?
- Which competitor cut prices the most since Monday?
- Show the keywords where I dropped out of the top 10.
What you send and what you get
You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.
- Link to a Empik pagerequired
Open the product or category page in your browser and copy the address. Any Empik country domain works the same way.
https://www.empik.com/ - Your column listrequired
Field name, type and one line of plain English per column. Written once, reused on every run.
product_title, brand, sku, price - How often it runsoptional
Hourly, daily, weekly or on demand through the API. Daily is what most price monitoring uses.
Daily at 06:00 UTC
One row per product on the page, 12 columns each
- product_title
- brand
- sku
- price
- was_price
- currency
- availability
- delivery_estimate
- rating
- review_count
- product_url
- checked_at
REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.
The columns a Empik run comes back with
We are not going to print a table of invented general merchandise prices and call it real output. Empik answers an ordinary request with Cloudflare rather than a product page, so we have no run of our own to quote from. So what is published here is the column list you declare before the run, which is the same list every run comes back with.
product_titleProduct title as the site writes itbrandBrand as the site labels itskuSite's own article numberpricePrice the site is charging todaywas_priceStrike-through price, only where the page shows onecurrencyCurrency the page quotedavailabilityStock state as the page states itdelivery_estimateDelivery window shown on the pageratingAverage rating, where shownreview_countHow many reviews back that ratingproduct_urlLink back to the page the row came fromchecked_atWhen this run collected the page (UTC)Every column here is one you name yourself in the schema. If a field is not on the page on the day of the run, it comes back empty rather than guessed.
What a Empik page costs
Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count.
Measured on 3 October 2026, not assumed. A plain request for a empik.com page returns a document rather than a refusal, but Cloudflare is in front of it, and the parts of the page that carry price are filled in by JavaScript after load, so a browser is what makes the run reliable.
500 Empik pages checked once a day for a month is 15,000 pages.
about EUR 22.50 for the month
You are charged for what a run actually used, not what it was expected to need, and your balance never expires.
See the full price list →What this page is not promising
We would rather say this here than in a support ticket.
No dedicated Empik endpoint
There is no Empik API in our catalogue and no pre-built Empik schema. The AI scraper reads the page you point it at — that is the whole mechanism, and it is why it works on pages nobody built a connector for.
Nothing behind a login
It reads what a visitor can see. Account pricing, contract pricing and anything behind a sign-in are out of scope.
No field the page does not show
If the page does not print it, the scraper cannot return it. Identifiers like EAN or GTIN only come back where the retailer publishes them.
A price is a point in time
Every row carries the timestamp of the run that collected it. A price without one is not evidence, which is why the column is in the default schema.
Empik has one specific trap
A product page can show an Empik price and a marketplace price for the same item, and the cheaper one is not always the one in the buy box.
Not a bulk dump of the catalogue
You give it the URLs you care about. It does not crawl empik.com end to end, and a schedule that tried to would cost more than the answer is worth.
Typical fields the AI scraper extracts from a Empik page
Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.
Price and promotion
On a broad-range retailer the promotion mechanic varies by category, so capture the wording rather than trying to parse it into a number.
- Current price
- Strike-through or was-price where shown
- Promotion or voucher wording as printed
- Multibuy conditions, where stated
- Currency and market the price belongs to
Stock and fulfilment
A cheaper competitor who cannot deliver this week is not a cheaper competitor.
- Stock state as the page states it
- Delivery window shown
- Click-and-collect availability, where exposed
- Delivery charge, where quoted
- Seller or fulfiller, where the page names one
Product identity
Broad catalogues mix branded and own-label lines, so the retailer's own code is the one field always present.
- Site's own article number
- EAN or GTIN, where published
- Brand, or own-label name
- Category breadcrumb
- Rating and review count
- Product image URLs
The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →
What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when Empik publishes them.
What people use Empik data for
Daily competitor price tracking
A list of product URLs, a daily schedule, and a table you can diff against yesterday rather than a tab somebody checks by hand.
Own-label versus brand price gap
The gap between a retailer's own label and the branded equivalent on the same shelf, measured rather than estimated.
Promotion calendar reconstruction
Which lines go on promotion, when, and how deep. Public information that is only visible if you collected it.
Availability and delisting alerts
Whether your lines are listed, in stock and findable. Suppliers usually discover delisting late.
Price-index reporting
A fixed basket of lines read daily is a price index you own, rather than one you buy with a lag.
Feeding your own pricing rules
The export is a normal REST API or CSV, so it drops into whatever pricing logic you already run.
What makes Empik harder than an ordinary storefront
Here is what the scraper is actually up against on empik.com, measured rather than assumed.
Access
- Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
- Named protection on the response: Cloudflare
- robots.txt publishes sitemaps, which is the cheapest way to build the URL list a run works through
Breadth is the difficulty
- Different categories use different promotion mechanics, so one parsing rule does not fit the catalogue
- Own-label lines carry no manufacturer identifier, so cross-retailer matching needs titles or your own mapping
- Catalogues run to hundreds of thousands of lines, so scope the page count deliberately rather than sweeping
- Category pages are paginated and lazily loaded, so a sweep is a list of URLs rather than one request
What the page publishes
- Structured data is published but not at product level (SearchAction, WebSite), so price comes from the rendered page rather than a feed
- A product page can show an Empik price and a marketplace price for the same item, and the cheaper one is not always the one in the buy box.
- Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number
Keeping a history
- A single read is a snapshot; the value is in the series, which means the run has to be scheduled and the rows kept
- Every row carries the timestamp of the run that produced it, so two days can be compared without guesswork
- Columns stay stable between runs, so a dashboard written once does not break when the site redesigns
Empik scraping — questions
What people ask before pointing the scraper at empik.com.
Empik publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.
Ready to pull Empik data into your stack?
Start free — or talk to our team about your exact fields, refresh cadence and volume.