eMAG Scraper: Products, Prices and Stock

eMAG Scraper turns eMAG, the biggest marketplace in Romania with stores in Hungary, Bulgaria and Poland, into a clean product feed. Search by keyword, or paste any eMAG product or search link and the actor reads the storefront's own listing pages directly: current price and original price with the discount computed, category, seller and stock state, on every row without a second request. Turn on one toggle for the description, brand, specifications, image gallery, seller rating, rating summary, the full offer board of every other seller with their prices, financing plans, variant families and review texts. Export to JSON, CSV or Excel, or pull results straight into your app through the API.

Why This Scraper?

• Four stores in one actor. Search Romania, Hungary, Bulgaria or Poland from one picker, with each row priced in that store's currency, so cross-country price gaps are one run away.
• Two ways to find products. Search by keyword, or paste a product or search link; a pasted link decides its own scope, including its own store.
• The full price story on every row. Selling price, original price and the discount percentage arrive from the listing itself, with no second request and no toggle required.
• Seller and stock on every row. Seller name, stock state and badge flags come straight off the listing card.
• Details on demand. Turn on Fetch product details for the description, brand, specifications, image gallery, seller rating, stock state, rating summary, review texts, the other sellers' offer board and prices, financing instalments and the variant family picker.
• Built for monitoring. Incremental mode returns only new, changed and reappeared products on recurring runs, and a refused run fails loudly instead of returning an empty dataset.

Use Cases

• Cross-country price tracking: run the same search on all four stores and compare what the same product costs in each currency.
• Pricing and promo tracking: monitor a search for price cuts and new discounts over time.
• Assortment and availability research: get notified when a product appears, disappears, or changes stock state.
• Seller research: track which sellers list a product and how their ratings move.

Data You Get

Sample shape: values are illustrative placeholders, not from a live record.

Field	Example
recordId / pnk / rowType	"ro:ABC12XY34" / "ABC12XY34" / "product" (the store's own stable product code)
store / currency / position / searchTerm	"ro" / "Lei" / 3 / "telefon" (store, price currency, search rank and the term that produced the row)
title	"Sample Phone Model X, 256GB, 5G"
price / priceText	6399.99 / "6.399,99 Lei" (the current selling price, as a number and as shown)
originalPrice / onSale / discountPercent	7999.99 / true / 20.0
category / categoryTrail / categoryId	"Telefoane Mobile" / the full breadcrumb trail / the category id
sellerName / availabilityText	"Sample Seller" / "In stock"
hasGenius / isMarketplace	true / false (badge flags off the listing card)
imageUrl / imageUrls / url	product image, the full gallery and the product page link (gallery with Fetch product details on)
description / brand / manufacturer / specifications	with Fetch product details on: the text, the maker and label-to-value pairs off the spec table
sku / mpn / ean	with Fetch product details on: the store's code, the manufacturer part number and the barcode (the barcode only when the store lists one)
sellerId / sellerSef / vendorType / sellerRating / sellerPositiveShare	with Fetch product details on: the seller's id, slug, vendor class and rating record
availability / inStock	with Fetch product details on: the stock state code and the orderable flag
offersCount / multipleOffersCount / usedOffersCount	with Fetch product details on: how many offers the product has, new and used
offers / minPriceOffers / maxPriceOffers / usedMinPrice	with Fetch product details on: up to 20 other sellers with their asking prices, plus the price span
priceNet / recommendedRetailPrice / lowestPrice30Days	with Fetch product details on: the VAT-exclusive price, the maker's recommended price and the pre-discount 30-day low, each when the store discloses it
averageRating / reviewCount / ratingDistribution / recommendationRate	with Fetch product details on: the rating summary, its per-star spread and the share of customers who recommend the product
reviews / questionCount	with Fetch product details on: up to Max reviews per product (default 20) review texts with rating, author and date, plus buyer questions. Reviews bill one details surcharge unit per started block of 10
badges / breadcrumbUrls / keywords / itemCondition	with Fetch product details on
fulfilledByEmag / hasFreeDelivery / hasPickup / hasVideo / hasImage360 / hasEcredit	with Fetch product details on: fulfilment, delivery, media and financing flags
ecreditInstallments / ecreditProviders	with Fetch product details on: the financing plan and the finance houses offering it
isFamily / familyId / familyVariants	with Fetch product details on: the variant family this listing belongs to and its option picker
productNumericId / isBfPrice	with Fetch product details on: the store's internal product id and the Black Friday pricing flag
scrapedAt / detailCarriedForward	"2026-01-01T00:00:00Z" / true only when a failed detail read was repaired from the previous run's snapshot
changeType / changedFields / firstSeenAt / lastSeenAt	incremental mode only: "UPDATED" / ["price"] / when a record was first and most recently seen

How to Use

1. Pick a mode: search (by keyword) or url (paste a product or search link).
2. Fill in the field for that mode, pick the store, and narrow with the ordering and price filters; they apply in both modes, and a pasted product link is the one exception, it returns that single product in full.
3. Turn on Fetch product details if you need the description, specs, gallery, seller rating or rating summary.
4. Set Max items to control run size and cost, then click Start.

Search by keyword:

{
  "mode": "search",
  "searchTerms": ["telefon"],
  "maxItems": 20
}

Search another store, cheapest first:

{
  "mode": "search",
  "searchTerms": ["telefon"],
  "store": "hu",
  "sortBy": "priceasc",
  "maxItems": 50
}

Paste a search link, with details on:

{
  "mode": "url",
  "urls": ["https://www.emag.ro/search/telefon"],
  "fetchDetails": true,
  "maxItems": 100
}

Paste a single product link:

{
  "mode": "url",
  "urls": ["https://www.emag.ro/telefon-mobil-sample-x-256gb-5g/pd/ABC12XY34/"]
}

Run it from your code

Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/emag-com-scraper").call(run_input={"mode": "search", "searchTerms": ["telefon"], "maxItems": 20})
for product in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(product["title"], product["price"], product["originalPrice"])

JavaScript:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/emag-com-scraper').call({ mode: 'search', searchTerms: ['telefon'], maxItems: 20 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.

How Max items and Max pages shape a run

Max items is the single cap on a run, across every search term and URL; set it to 0 for unlimited. With more than one search term or URL, the cap is shared out evenly up front: each source gets at most its equal share (for example 20 each for two sources and Max items 40), and a share one source does not use is not handed to the others. Max pages is an optional safety bound per source, on top of that cap. The store serves 60 products per page: when a page holds more fresh candidates than the budget left for that source, only the first candidates on that page, in the store's own order, are read this run, and the run's log names how many of that page were kept. The rest of that page is not read this run, and a product cut off this way is also skipped if a later search term or URL in the same run lists it, so overlapping search terms can return fewer rows than Max items allows.

This matters most with Incremental mode on a small, recurring Max items. The budget counts returned rows across pages (an unchanged row that is suppressed does not use it up, so the walk moves on to the next page), but within one page it is a cut by position: the candidates after the first N on a page are never classified at all this run, even when the first N all turn out unchanged and nothing is returned. A genuine price or stock change on one of them is missed, and the run's summary message does not say it was capped (a run where every candidate it did classify was unchanged reports "N product(s) scanned, nothing changed", the same message a fully complete, unchanged scan produces). Because every run starts from the top of the results again, a later run with the same Max items cuts the page at the same place, so while the products ranked ahead of it stay unchanged, that change can stay unreported run after run. For a recurring, monitored search or URL, set Max items to 0 or to at least the size of the tracked scope so a page is never sliced mid-way.

Resume and recurring updates

• Resume (resumeFromRunId) continues one interrupted or capped run: paste its run or dataset ID and the actor skips everything already collected there, so you don't pay twice.
• Incremental mode (incrementalMode) is for running the same search or URL again and again (for example daily) and getting only what changed. Each record classifies NEW, UPDATED (with changedFields; a price move, a stock change or a new rating on a storefront IS reported as UPDATED, since that is exactly what a monitor watches for), UNCHANGED (suppressed and not billed unless emitUnchanged is on), REAPPEARED, or EXPIRED (only after a run that scanned the whole tracked scope: never when Max items or Max pages capped the walk short, never with Resume, and never after a refusal). Image URLs never mark a row UPDATED on their own. stateKey names or shares the stored state, so two differently configured searches never mix their history.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record, not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Input Parameters

Parameter	Type	Default	Description
mode	string	search	search (by keyword) or url (paste store links).
searchTerms	array	["telefon"]	Search mode: one or more terms to search for, each scraped independently.
urls	array	sample	URL mode: product or search links; each pasted URL decides its own scope, including its own store.
store	string	ro	Which country store to search in search mode: ro, hu, bg or pl. Rows are priced in that store's currency.
sortBy	string	relevance	The store's own server-side ordering: relevance, priceasc, pricedesc, reviewsdesc, discountdesc or popularity.
minPrice	integer	(none)	Only keep rows whose selling price is at least this much, in the store's currency.
maxPrice	integer	(none)	Only keep rows whose selling price is at most this much, in the store's currency.
onSaleOnly	boolean	false	Only keep rows with a discount (selling price below the original price).
fetchDetails	boolean	false	Fetch each item's product page: description, brand, specs, gallery, seller rating, stock state and rating summary. Charged once per record.
maxItems	integer	20	The single cap on this run, across all search terms and URLs. 0 = unlimited.
maxPages	integer	0	Safety bound on result pages walked per search term or URL. 0 = no page limit (Max items still applies).
maxReviews	integer	20	How many reviews to keep per product record, with Fetch product details on. Reviews are read from the product page already fetched for the details, so the cap adds no page read; every started block of 10 reviews bills one extra details surcharge unit. 0 = skip reviews.
ignoreFieldsForChanges	array	(none)	Incremental mode only: extra field names to keep out of the change fingerprint. Price, stock and rating fields are never ignored.
resumeFromRunId	string	(none)	Continue one interrupted run without returning or charging for records it already collected.
incrementalMode	boolean	false	Turn on for recurring monitoring of the same search or URL: later runs return only new, changed and reappeared records.
stateKey	string	(none)	Name or share an incremental-mode monitoring campaign's stored state.
emitUnchanged	boolean	false	Also return (and bill) records that have not changed since the last run.
emitExpired	boolean	false	Also return (and bill) records that were tracked before but are no longer found, once a run fully scans the tracked scope.
ignoreFieldsForChanges	array	(none)	Incremental mode only: extra field names to keep out of the change fingerprint. Price, stock and rating fields are never ignored.
mcpConnectors	array	(none)	Optional: send a summary of each record to apps you authorized under Integrations.
notionParentPageUrl	string	(none)	Notion connector only: page under which record pages are created.
maxNotifyListings	integer	50	Cap on records written to each connector per run.
proxy	object	Apify Proxy	Connection settings. Residential is recommended for the most reliable results.

Output Example

Sample shape: values are illustrative placeholders, not from a live record.

{
  "recordId": "ro:ABC12XY34",
  "rowType": "product",
  "store": "ro",
  "pnk": "ABC12XY34",
  "productId": "100000001",
  "offerId": "200000001",
  "url": "https://www.emag.ro/telefon-mobil-sample-x-256gb-5g/pd/ABC12XY34/",
  "title": "Sample Phone Model X, 256GB, 5G",
  "brand": "Sample Brand",
  "manufacturer": "Sample Brand",
  "category": "Telefoane Mobile",
  "categoryTrail": "Laptop, Tablete and Telefoane/Telefoane Mobile",
  "price": 6399.99,
  "priceText": "6.399,99 Lei",
  "currency": "Lei",
  "originalPrice": 7999.99,
  "onSale": true,
  "discountPercent": 20.0,
  "sku": "SKU-ABC12XY34",
  "mpn": "MPN-XYZ-90",
  "ean": "6000000000000",
  "itemCondition": "NewCondition",
  "description": "A sample phone with a large display and a long lasting battery.",
  "specifications": {
    "Memorie interna": "256 GB",
    "Memorie RAM": "8 GB"
  },
  "imageUrl": "https://images.example.com/products/sample-phone/ABC12XY34-1.jpg",
  "imageUrls": [
    "https://images.example.com/products/sample-phone/ABC12XY34-1.jpg",
    "https://images.example.com/products/sample-phone/ABC12XY34-2.jpg"
  ],
  "sellerName": "Sample Seller",
  "sellerId": 12345,
  "sellerSef": "sample-seller",
  "sellerRating": 4.8,
  "sellerPositiveShare": 96,
  "vendorType": 2,
  "availability": "in_stock",
  "availabilityText": "In stock",
  "inStock": true,
  "offersCount": 8,
  "multipleOffersCount": 7,
  "usedOffersCount": 0,
  "minPriceOffers": 6199.99,
  "maxPriceOffers": 7249.99,
  "offers": [
    {"offerId": 300000001, "vendor": "Other Shop", "vendorSef": "other-shop", "price": 6199.99, "type": 1}
  ],
  "priceNet": 5289.25,
  "averageRating": 4.8,
  "reviewCount": 303,
  "ratingDistribution": {"5": 87, "4": 5, "3": 3, "2": 2, "1": 3},
  "recommendationRate": 92,
  "questionCount": 11,
  "badges": ["badge-genius", "commercial-badge"],
  "fulfilledByEmag": false,
  "hasFreeDelivery": false,
  "hasPickup": true,
  "hasVideo": false,
  "hasImage360": false,
  "hasEcredit": true,
  "ecreditInstallments": {"count": 24, "value": 322},
  "ecreditProviders": ["Sample Finance"],
  "isFamily": false,
  "familyVariants": [{"name": "Memorie interna", "options": ["256 GB", "512 GB"]}],
  "position": 3,
  "searchTerm": "telefon",
  "productNumericId": 100000001,
  "hasGenius": true,
  "isMarketplace": false,
  "detailCarriedForward": null,
  "scrapedAt": "2026-01-01T00:00:00Z"
}

With Incremental mode on, a row also carries changeType, changedFields, firstSeenAt and lastSeenAt.

Plan Requirement

The default proxy setting works out of the box: residential is recommended for the most reliable results, since the storefront answers residential exits most consistently. The actor rotates connections automatically when one is refused; change the Proxy configuration only if a run reports it could not read any results. Fetch product details adds a paid surcharge: one unit per enriched record plus one unit per started block of 10 delivered reviews; the price pair, category, seller and stock state are on every row either way.

FAQ

How much does it cost?

You pay per product record returned, plus an optional surcharge when Fetch product details is on: one unit per enriched record plus one unit per started block of 10 delivered reviews (a record with the default 20 reviews bills 2 surcharge units; Max reviews: 0 bills 1). The Pricing tab shows the current rates. Use Max items to cap the cost of any run.

Is it legal to scrape eMAG?

This actor collects only publicly available product data. You are responsible for how you use it: follow the store's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Product names, prices and stock levels are generally facts, but images and descriptions may be subject to third-party rights.

Can I get only new or changed products on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared records; unchanged ones are suppressed and not billed unless Emit unchanged is on.

Why did a run return fewer products than I expected?

Max items is the single cap on a run, across every search term and URL, and with several sources it is split evenly between them up front: with two search terms and Max items 40, each term returns at most 20, even if the other term finds nothing. When a page holds more fresh candidates than a source's remaining budget, only the first candidates on that page, in the store's own order, are read, and a product cut off that way is also skipped by any later search term in the same run that lists it. Raise Max items, or set it to 0, to read further. With Incremental mode on for a recurring search, keep Max items at 0 or at least the size of the whole tracked scope: a candidate cut off mid-page is not classified at all that run, so a genuine change on it can be missed without the run looking capped from its own summary message, and later runs with the same Max items cut the page at the same place, so it can stay missed until the products ranked ahead of it change or Max items is raised.

Why did my run fail instead of returning an empty dataset?

If the store refuses every request, the run stops with a clear message so "nothing matched" is never confused with "nothing could be read". The storefront sometimes answers with a bot check in waves; run it again in a few minutes, or change the Proxy configuration. If only some search terms or URLs could be read, you still get what was found, and the run's log shows which source could not be read (when nothing at all was found, the status message also gives the count of sources that could not be read).

What's the difference between Resume and Incremental mode?

Resume (resumeFromRunId) continues ONE specific interrupted or capped run: paste its run or dataset ID and this run skips everything it already collected there. Incremental mode is for running the SAME search or URL again and again (for example daily) and getting only what changed; it keeps its own state per search, independent of any one run.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

Why are category pages not supported?

Category pages on this storefront answer automated readers with a bot check even when search and product pages serve normally, so pasting one fails loudly instead of returning an empty dataset. Search for the same products by keyword, or paste a search link, and you get the same catalogue.

🔗 More scrapers you might like

Pair this actor with these related scrapers from the same team:

🧩 Joom Scraper Scrape Joom products by keyword or URL. Extract product names, prices, discounts...	🧩 ASOS Scraper Scrape ASOS by keyword, category or URL. Every row carries the selling price and the...
🧩 Miravia Spain Scraper Scrape Miravia Spain by keyword, seller store or URL. Every row carries the selling price...	🏷️ OLX Scraper Fast OLX scraper across 9 countries, including Poland, Romania, Portugal, Ukraine...
🛒 Americanas Brazil Scrape Americanas Brazil (americanas.com.br) by keyword, department or pasted link...	🛒 Thegioididong Scraper Scrape thegioididong.com products with full specifications, current & original price...

👉 Browse all abotapi scrapers

💬 Support

• 🐞 Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
• 🛠️ Need another site, extra fields or a private build? Email contact@abotapi.com.
• ⭐ Enjoying it? A quick review on the actor page helps other users find it.