Ceneo Price Scraper — Poland Price Comparison

Search Ceneo.pl, Poland's price-comparison site, by keyword and get one clean row per product: lowest price, number of offers, rating, review count, brand, product link and image. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per product found on the Ceneo search page.

Field	Description
name	Product name
brand	Brand, when Ceneo lists it
url	Link to the product page on Ceneo
image_url	Product image URL
price	Lowest price on the page
currency	Currency code (PLN by default)
original_price	Higher reference price, when the page lists one
discount_pct	Percentage difference between original_price and price (only when original_price is higher)
offer_count	Number of shop offers
rating	Average rating
review_count	Number of reviews/ratings
rank	Position of the product in the results
product_id	Product identifier from the page (SKU / product ID / MPN, whichever is present)
site	Always ceneo
query	The search keyword used
page_number	Results page the row came from
scraped_at	ISO 8601 timestamp of the run

The row also carries unit_price, lowest_store and category. Ceneo's search page does not provide them, so for this actor they are empty (null). The field list is identical across our price-comparison actors, so you can feed several sites into one pipeline.

How to use

1. Open the actor and type a search keyword in Search query (Polish or English, for example iphone or pralka).
2. Set Max products to the number of rows you want.
3. Leave Proxy configuration on the default (Apify Residential, Poland). It is already set up; you need no extra account.
4. Click Start. When the run finishes, open the Products Overview table or export the dataset as JSON, CSV or Excel.

The actor reads the first results page of the search for your keyword.

Input

Field	Type	Default	Description
query	string (required)	iphone (prefill)	Keyword to search on Ceneo.pl
maxItems	integer	100	Maximum products to return (0 = no cap). You are charged per product returned
proxyConfiguration	object	Apify Residential, country PL	Proxy settings. The default is recommended for reliable access

Example input:

{
  "query": "iphone",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "PL"
  }
}

Output example

Values below are illustrative.

{
  "name": "Apple iPhone 15 128GB Black",
  "brand": "Apple",
  "url": "https://www.ceneo.pl/123456789",
  "image_url": "https://image.ceneostatic.pl/data/products/123456789/f-apple-iphone-15.jpg",
  "price": 3199.0,
  "currency": "PLN",
  "original_price": 3899.0,
  "discount_pct": 18.0,
  "offer_count": 42,
  "unit_price": null,
  "lowest_store": null,
  "rating": 4.7,
  "review_count": 215,
  "category": null,
  "rank": 1,
  "product_id": "123456789",
  "site": "ceneo",
  "query": "iphone",
  "page_number": 1,
  "scraped_at": "2026-10-02T09:30:00+00:00"
}

Use cases

• Price monitoring for Polish e-commerce: track the lowest market price for a product over time.
• Competitor benchmarking: see how many shops sell a product and how it is rated.
• Assortment research: list the top results for a keyword with brand and rating data.
• Market entry analysis: compare Polish price levels across product categories.

FAQ

Do I need an API key or my own proxy? No. The residential proxy (Poland) is built in. You do not need any API keys or external accounts.

How is it priced? Pay per result. See the Pricing tab for the current price per product.

Does it return every shop's offer? No. You get one row per product with the lowest price and the offer count, not a list of individual shop offers.

How many products can I get per run? The actor reads the first results page of your search, so a single keyword returns up to a few dozen products. Use more specific keywords, or several runs, to cover more of the catalogue.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.