Skip to content
All articles

Wildberries collection: estimating 100,000 records

Estimate Wildberries collection costs from a sample, billable processing time, regions, and extra operations before expanding the catalog. No fixed price per record.

Akmelo Editorial TeamProduct and data collection
Wildberries collection sample, result count, and spendingImage unavailable

Start by measuring a small sample with your fields, regions, and processing rules. Wildberries collection has no universal price per 100,000 records: the same row count can require different amounts of billable processing time.

Actual spending depends on billable processing time, scenario contents, and extra operations. The same product count does not guarantee the same charge. Test a small sample with your settings before a large run.

Define what counts as a record

One hundred thousand SKUs and one hundred thousand results are not necessarily the same workload. A multi-region collection can produce separate records for one product. Sizes and variants also affect result structure. The number of HTTP requests need not equal saved row count.

Record the product list, delivery cities, and required fields. To compare prices across cities, store the region beside each value and check that prices have the same meaning.

See the regional collection guide. Check the delivery point too: a city name cannot represent every possible address within it.

Test a small sample

Run a limited selection and inspect the result. Are prices parsed correctly? Were distinct variants merged? How many records appeared? Trial mode is useful for checking but does not mean free processing.

Open the spending and transaction history afterward. Base your estimate on actual work and billable processing time. The ready-made Wildberries source accounts for waiting separately, so simply multiplying total run duration by a per-minute rate is misleading.

Record the sample, results, and spending for a preliminary Wildberries estimateImage unavailable

Save scenario settings, result count, billable time, and charges. Then increase the selection and compare them. A short run does not guarantee proportional growth for a large catalog.

Compare offers fairly

Ask what each estimate includes: regions, fields, retries, processing, and file preparation. A price per request cannot be directly compared with a price per product or successful record.

The team previously quoted a preliminary estimate of around 300 RUB per 100,000 records. There is no published reproducible measurement protocol behind that figure, so it does not establish the cost of your run and should not be used to budget or compare services. Base a regular collection decision on your own test and current billing terms. See the general collection cost guide.