How often should you refresh competitor price data?

Why one cadence never fits

A single refresh schedule treats every SKU as equally urgent, which wastes collection budget on stable products and starves the volatile ones. Consumer electronics prices can move several times a day around a launch; a specialty tool might hold its price for months. The cost of staleness is also uneven: on a 12 percent margin product, reacting to a two-day-old competitor price cut can mean selling at a loss you never intended.

Start by measuring actual price volatility per category: the share of SKUs whose price changes week to week, and the average size of the change. Categories above 15 percent weekly movement deserve intraday refreshes. Below 5 percent, daily or even twice-weekly is plenty. This one analysis usually cuts collection costs while improving freshness where it matters.

Building the tiered schedule

Tier one is your revenue concentration: the SKUs driving most of margin. These refresh hourly during business hours, more often during events. Tier two is the competitive set you price-match against: daily refresh, hourly during their promotions. Tier three is the long tail: twice weekly, which is enough to catch structural repricing without burning budget.

The tiers should be dynamic, not set once a year. Promote a SKU to tier one when its volatility spikes or when it enters a promotional window, and demote it when things calm down. A static tier list decays within a quarter as assortments and competitive pressure shift.

Event-driven acceleration

Scheduled refreshes miss the moments that matter most. Competitor flash sales, your own promotions, new product launches, and marketplace-wide events all deserve temporary cadence boosts. The trigger list should include competitor site changes (new banner, sale section updates), calendar events (holiday weekends, Prime-style events), and your own price changes, since repricing often provokes a response within hours.

The acceleration window matters as much as the trigger. Most competitive responses land within 6 to 48 hours of a move, so boost cadence for at least two days after an event, not just during it. Teams that snap back to normal cadence the morning after a sale miss the retaliation pricing that follows.

Knowing when the data is lying

Fresh data can still mislead. Personalized pricing, geo-based prices, and logged-in-only discounts mean the price your scraper sees may not be the price most shoppers see. Validate periodically with clean sessions from multiple locations, and flag SKUs where the scraped price diverges from what a manual check shows. A cadence is only as good as the accuracy of each refresh.

Also watch for bot-mitigation artifacts: prices that disappear behind challenges get recorded as nulls, and nulls averaged into dashboards look like price drops. Treat missing data as missing, not as zero, and alert on collection failure rates the same way you alert on price moves.

Is real-time price monitoring worth the cost?

Only for the SKUs where minutes matter: thin-margin, high-velocity products in volatile categories. For everything else, tiered scheduled refreshes get 95 percent of the value at a fraction of the cost.

How do you handle competitors that block scrapers?

Rotate collection methods, respect rate limits, and prioritize the sources you can collect reliably. A slightly slower cadence from a stable source beats an aggressive one that gets blocked weekly.

Should MAP products refresh on the same schedule?

No. MAP monitoring is compliance-driven, so it needs its own cadence tied to violation risk and enforcement windows, not general price volatility.