When comparing Wildberries products for buyers in Moscow and Saint Petersburg, check conditions in each city. Opening a product card once is not enough: its terms can depend on the selected delivery region.
Store the region beside the price so later comparisons have the right context.
One card, several results
In Akmelo's ready-made Wildberries solution, choose products and regions. The scenario processes each selected region separately. A card's price may vary, and the card might not appear in one region. A city preset uses a predefined delivery point; you can add a custom delivery code for a specific address.
Do not assume one city's result applies everywhere. To check Perm later, add it as another scenario region and collect separate records.
For comparison, keep SKU, region, price, and source link. If availability matters, decide whether you need overall card availability or variant-level details. They are different measures.
A missing value is not zero stock
A card without a price, a product not found in one region, and confirmed unavailability of a particular variant are different situations. The reason for the gap matters.
If the source temporarily returns no data, do not conclude that the product has disappeared. Check the run log and source card. The page may have changed by the next collection.
It is easiest to compare results from one completed run using the same product and region list. Requests within that run still happen at different times, so a small timing difference is unavoidable.
Filter to one SKU and view the city records side by side. Confirm that the variant and the price type match before interpreting differences.
Do not present regional observations as a guaranteed price for a particular buyer. A marketplace may depend on other conditions. Consistent collection rules and clear context matter most for monitoring.
See the Wildberries documentation for region settings, then choose a suitable collection schedule.
