Russian Marketplaces Scraper & Price Monitor

Scrape and price-monitor Ozon, Wildberries, Yandex Market, and Avito - one Actor, one unified schema.

Search product cards by keyword across all four major Russian marketplaces, or schedule a price monitor that reports only what changed. Built to survive the aggressive anti-bot on RU platforms - where most Western monitor actors simply don't go.

---

Why this Actor

Western price-monitor actors avoid Russian marketplaces because of hard anti-bot protection. Existing RU scrapers cover one platform each, with different output formats you have to reconcile yourself. This Actor does both jobs in one call:

• 4-in-1, one schema. Ozon + Wildberries + Yandex Market + Avito in a single run, identical fields on output. No stitching four different scrapers together.
• Price monitor with change tracking. State persists between runs in the KV Store. Each card gets changeType, previousPrice, priceChangePct.
• Fewer paid results in monitor mode. alertOnly returns only changed cards, keeping scheduled monitoring economical on expensive stealth traffic (you still pay platform usage for the full scan).

---

Features

• Unified output schema across all four marketplaces -

  platform, query, id, title, url, price, currency, scrapedAt
  .
• Two modes: search (find cards by keyword) and monitor (track price changes on schedule).
• RU residential proxy (Apify, country-RU) for access to RU platforms. The person who runs the Actor pays for the traffic.
• Anti-bot resilience: Camoufox (open-source, Firefox-based stealth browser), retry-with-new-IP on silent blocks (especially Wildberries), and honest stale-selector detection - the Actor tells you if a platform changed its markup instead of silently returning nothing.
• Normalized keyword filters: includeKeywords / excludeKeywords match across variants - "2 ТБ" catches "2TB" / "2ТБ" / "2 tb", part numbers across any separator.
• Price band + volume caps: minPrice, maxPrice, maxItemsPerQuery.
• Underpriced detector (flagUnderpriced): flags cards well below the query median, or below a supplied referencePrice. Brand-agnostic - works for any product.
• Optional webhook: POST a summary of changes (integrate with Telegram or your own service).

---

Supported platforms & output fields

Platform	Key	search	monitor
Ozon	ozon	yes	yes
Wildberries	wildberries	yes	yes
Yandex Market	yandexmarket	yes	yes
Avito	avito	yes	yes

Output fields (unified across all platforms):

Field	Type	Notes
platform	string	ozon / wildberries / yandexmarket / avito
query	string	the search query this card came from
id	string	marketplace card id
title	string	card title
url	string	card URL
price	number	current price
currency	string	RUB
scrapedAt	string	ISO timestamp
isUnderpriced	boolean	only when flagUnderpriced=true
deviationPct	number	deviation from median or referencePrice
changeType	string	monitor mode: new / price_up / price_down / removed
previousPrice	number	monitor mode: price on the previous run
priceChangePct	number	monitor mode: percent change

---

Use cases

• Seller repricing - keep your prices in the market across all platforms at once.
• Arbitrage / deal hunting - catch underpriced lots below the category median.
• SKU price monitoring with Telegram alerts - scheduled monitor, alertOnly + webhook.
• Category market research - one unified dataset across four platforms for a price landscape.
• Brand protection / anti-counterfeit signal - flag suspiciously low prices vs the official price (referencePrice) for a brand or rights holder.

See USE_CASES.md for detailed input examples for each.

---

Quick start

Search mode - find cards by keyword:

{
  "mode": "search",
  "platforms": ["ozon", "wildberries", "yandexmarket"],
  "queries": ["Samsung 990 Pro 2TB", "MZ-V9P2T0CW"],
  "includeKeywords": ["990 Pro", "2TB"],
  "minPrice": 10000,
  "maxItemsPerQuery": 60
}

Monitor mode - track changes on a schedule, alert only on changes:

{
  "mode": "monitor",
  "platforms": ["ozon", "wildberries"],
  "queries": ["Samsung 990 Pro 2TB"],
  "includeKeywords": ["990 Pro", "2TB"],
  "alertOnly": true,
  "notifyWebhookUrl": "https://example.com/hooks/price-alerts"
}

Set a schedule under Schedules in the Apify Console to run monitor mode periodically. State carries over between runs via the KV Store.

---

Pricing and cost control

This Actor uses Apify's Pay-per-event pricing model. You are charged per result written to the default dataset, and Apify platform usage costs (compute + residential proxy) are billed to the account that runs the Actor.

For a low-cost test run, start with one platform, one query, and a small maxItemsPerQuery. For scheduled monitoring, use alertOnly=true to write (and pay for) only new or changed cards. Set a max cost per run in the Apify Console before larger jobs to keep spending predictable.

---

Honest limitations (please read)

• Matching is done by the marketplace's own fuzzy search. Your precise control is includeKeywords, which narrows results down to the SKU you want. A part number is the best identity key. Example: a search for "Samsung 990 Pro 2TB" / "MZ-V9P2T0CW" returned the whole 990 Pro family (1/2/4 TB, box/OEM) on Ozon; the marketplace matched the model to the right SKU.
• flagUnderpriced is noisy on mixed results. If one query mixes 1/2/4 TB variants, the median blurs. Use one variant per query, or set referencePrice.
• Wildberries has the toughest anti-bot and is currently best-effort. It serves an active JS challenge that the Actor does not reliably pass on Apify's residential pool, so Wildberries may return empty. Ozon, Yandex Market, and Avito return results reliably.
• Cross-platform comparison of the same product by a single id is not automated yet (part-number matching is planned). Platforms are collected in parallel into one dataset.
• Residential traffic is paid (on Apify). For high-volume production monitoring you need a paid plan.

---

Keywords

ozon scraper, wildberries scraper, yandex market scraper, avito scraper, russian marketplace price monitor, ru marketplace scraper, price tracking, price change alerts, ozon price monitor, wildberries price monitor, competitor price monitoring, brand protection russia.

---

RU / На русском

Один актор для сбора и мониторинга цен на Ozon, Wildberries, Яндекс.Маркете и Avito - единая схема полей на выходе.

Западные монитор-акторы обходят жёсткий антибот RU-площадок стороной, а существующие RU-скрейперы покрывают по одной площадке каждый, с разным форматом. Этот актор делает обе задачи разом:

• 4-в-1, единая схема - все четыре площадки за один прогон, одинаковые поля.
• Мониторинг изменения цен - состояние между прогонами в KV Store, по каждой карточке changeType / previousPrice / priceChangePct.
• Меньше платных результатов в мониторе - режим alertOnly пишет (и тарифицирует) только изменившиеся карточки; usage за полный скан всё равно платит запускающий.
• Устойчивость к антиботу - Camoufox (open-source стелс-браузер на базе Firefox), ретрай с новым IP при «тихих» блокировках (особенно Wildberries), честный сигнал о смене вёрстки площадки.
• Фильтры - нормализованные includeKeywords / excludeKeywords («2 ТБ» ловит «2TB»/«2ТБ»/«2 tb»), minPrice/maxPrice, maxItemsPerQuery.
• Детектор низкой цены (flagUnderpriced) - ниже медианы выдачи или ниже эталонной referencePrice; работает по любому товару.

Честные ограничения: матчинг делает фаззи-поиск площадки (точный контроль - через includeKeywords, лучший ключ - партномер); на смешанной выдаче детектор низкой цены шумит; Wildberries сейчас best-effort - отдаёт активный JS-челлендж, который на residential-пуле Apify проходится нестабильно (может вернуть пусто), а Ozon, Яндекс.Маркет и Avito отдают данные надёжно; кросс-площадочное сравнение одной SKU по единому id пока не автоматизировано; residential-трафик РФ платный. Оплата - по модели Pay-per-event: тарифицируются результаты в dataset, а platform usage/proxy начисляются отдельно по правилам аккаунта Apify. Подробные примеры входа - в USE_CASES.md.