Petrovich Building Materials Scraper
Pricing
from $3.00 / 1,000 results
Petrovich Building Materials Scraper
Scrape Petrovich (petrovich.ru) - a major Russian building-materials and DIY retailer. Search products, browse by category, and fetch full product detail pages including price, specs/characteristics tables, brand, images, and availability.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Crawler Bros
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Scrape Petrovich (petrovich.ru) — a major Russian building-materials and DIY retailer. Search products, browse any catalog category, or fetch full product detail pages with price, brand, specs/characteristics tables, images, and availability. Uses a residential proxy to reliably load pages.
What this actor does
- Search — run a free-text search (e.g.
кабель,цемент,дрель) and collect matching products. - Browse a category — give one or more
petrovich.ru/catalog/<id>/...URLs and collect every product listed in that category, with sort order control. - Fetch product pages — give one or more
petrovich.ru/product/<id>/URLs (or bare numeric IDs) and get the full detail record for each, including specs, gallery, and category-tree links. - Merged extraction — combines each page's structured
Product/BreadcrumbListdata with DOM fallbacks, so records stay populated even on pages missing structured data. - Empty fields are omitted — a field only appears on a record when Petrovich actually exposes that data for the product.
Output per product
Each item in the output dataset is a single product.
productUrl— canonical product page URL; always present.sku— product SKU / item code; always present.title,description,brand— product name, description, and brand, when exposed.price,currency— current price and currency (alwaysRUB), when available.oldPrice— the crossed-out "was" price, present only when the product is discounted and the old price is genuinely higher than the current price.discountPercent— derived fromprice/oldPricewhen both are present.clubPrice— the "Клуб Петрович" loyalty-member price, present only when the page shows one and it's at or below the listed price.availability— stock status label (e.g.In stock,Out of stock), when exposed.unit— unit of measure / package label (e.g.шт,уп,м2), product-detail mode only.city— the region/city the session's price and stock are resolved for, product-detail mode only.promotions[]— marketing badges shown on the product page (e.g. "Акция", "Хит продаж"), product-detail mode only.images[]— the product image gallery; on product pages this is a de-duplicated merge of the structured data and the on-page thumbnail strip, while search/category listing records carry whatever image the listing card exposes.breadcrumbs[]— the full breadcrumb trail text (including the current product/page), when exposed, product-detail mode only.category,categoryPath[]— the immediate category name and full ancestor category path, derived from the breadcrumb trail, product-detail mode only.categoryPathUrls[]— the catalog URL for each ancestor category incategoryPath, letting you re-crawl the category tree from a product page, product-detail mode only.offerUrl— the canonical offer URL reported by the page's own structured data, when present, product-detail mode only.specifications[]— array of{name, value}pairs from the product's characteristics table, product-detail mode only.ratingValue,reviewCount— average rating and number of reviews, when the product has reviews.recordType— always"product".scrapedAt— UTC timestamp the record was written.
oldPrice, discountPercent, clubPrice, unit, city, promotions, breadcrumbs, category, categoryPath, categoryPathUrls, offerUrl, and specifications are only populated in mode=productDetails; search/byCategory listing records carry a lighter subset (productUrl, sku, title, price, currency, brand, images, availability, ratingValue, reviewCount when available).
Why is residential proxy required?
petrovich.ru is protected by the QRATOR WAF, which blocks every request from a datacenter IP with a persistent "access temporarily restricted" page, regardless of cookies or challenge state. Residential IPs load the site transparently. The actor fails fast if no residential proxy is configured, so proxyConfiguration is a required input.
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | search | search / byCategory / productDetails |
searchQuery | string | – | Free-text query (required for mode=search) |
categoryUrls | array | [] | One or more full catalog URLs (required for mode=byCategory) |
productUrls | array | [] | One or more product URLs or bare numeric IDs (required for mode=productDetails) |
sortBy | string | popular | popular / price_asc / price_desc / new — applies to mode=byCategory only; ignored in mode=search, which is always served in the site's default relevance order |
maxItems | integer | 30 | Hard cap on emitted records (1–500) |
proxyConfiguration | object | Residential | Apify proxy configuration; a residential proxy is required |
Example: search for products
{"mode": "search","searchQuery": "кабель","maxItems": 50,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Example: browse a category, cheapest first
{"mode": "byCategory","categoryUrls": ["https://petrovich.ru/catalog/100131139/"],"sortBy": "price_asc","maxItems": 100,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Example: fetch specific product pages
{"mode": "productDetails","productUrls": ["https://petrovich.ru/product/1181179/", "1181180"],"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Example: newest items in a category
{"mode": "byCategory","categoryUrls": ["https://petrovich.ru/catalog/100131139/", "https://petrovich.ru/catalog/100131200/"],"sortBy": "new","maxItems": 200,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Use cases
- Price monitoring — track price, old price, discount %, and loyalty price for building-materials SKUs over time.
- Assortment research — pull every product in a Petrovich catalog category to analyze range and coverage.
- Procurement & sourcing — bulk-fetch product specs and availability for construction/DIY purchasing decisions.
- Competitive benchmarking — compare Petrovich pricing and promotions against other Russian building-materials retailers.
- Catalog enrichment — feed specs, images, and category trees into a downstream product catalog or PIM.
Other Russian marketplace actors by CrawlerBros
FAQ
What is the data source? All data comes directly from petrovich.ru's own product, category, and search pages — the same pages a shopper would see in a browser.
Is this affiliated with Petrovich? No. This is an independent, third-party actor that reads publicly visible pages on petrovich.ru; it is not affiliated with or endorsed by Petrovich.
Why do I need a residential proxy?
petrovich.ru blocks datacenter IPs outright at the network/WAF level. A residential proxy is the only way to reliably load any page on the site, which is why proxyConfiguration is a required input.
Why does sortBy have no effect in mode=search?
petrovich.ru's own search endpoint doesn't support sort parameters reliably — applying one silently discards the search query and returns unrelated results. To avoid returning wrong data, the actor always uses the site's default relevance order for search and only honors sortBy when browsing a category.
Why are some fields missing from certain products? Petrovich doesn't expose every field (e.g. specs table, promotions, club price, rating) for every product. Fields are only included on a record when the source page actually has that data — nothing is invented or filled with placeholders.
Why do listing records (search/category) have fewer fields than product-detail records?
Search and category pages show a lighter card view, while product detail pages expose the full page (specs, breadcrumbs, gallery, promotions, etc.). Use mode=productDetails on the productUrl from a listing record to get the full set of fields.
How fresh is the data? Every run fetches pages live from petrovich.ru at request time — there is no caching, so prices and availability reflect what the site shows at the moment of the run.
Can I look up a product by just its numeric ID?
Yes — in mode=productDetails, productUrls accepts bare numeric IDs (e.g. 1181179) in addition to full product URLs.
What happens if a product no longer exists?
If a productUrls entry resolves to Petrovich's own "page not found" page, the actor skips it rather than emitting fabricated data for a nonexistent product.