How to Monitor Competitor Prices (Without Burning Out Your Team)

Tracking competitor pricing used to mean a spreadsheet, a Friday-afternoon tab-switching ritual, and a best-guess Slack message before the weekend. The teams that win on margin today have replaced that ritual with continuous, automated competitor monitoring.

Why weekly manual checks stopped working

A competitor's catalog rarely changes once a week. Catalogs churn hourly — flash promos land mid-morning, MAP resets on Mondays, replenishment restocks reset list prices overnight. By the time a Friday check surfaces a move, four trading days have already happened at the wrong price.

• Promo stacking. A category-wide 15% off compounds with a competitor's loyalty discount and your own MAP — manual monitoring catches the headline number, not the composite.
• SKU drift. Three competitors quietly raise on the same Tuesday, none far enough to flag individually, but the basket median moved 6%. A per-SKU check misses the basket shift.
• Stock-driven repricing. "Out of stock" drives a competitor's price 12% before they refill. If your scraper only fetches in-stock SKUs, every out-of-stock spike becomes an invisible floor.

What to actually monitor

A useful competitor monitor treats the four following prices per SKU as separate signals:

1. List price. The headline number on the PDP. North-star signal — every other field is a modifier on this.
2. MAP price. Minimum advertised price, where retailers are contractually bound. MAP resets often announce a structural reprice three to four weeks later.
3. Promo / cart price. What the buyer actually pays. The list-vs-cart delta is the elasticity raw material.
4. Stock state. In-stock / out-of-stock / low-stock. A product that is out-of-stock raises your effective demand without lowering your price — that doesn't always mean you should raise (price floors and competitor distance still apply).

In practice this means scraping each competitor PDP for the same SKU on a schedule that matches the category — electronics catalogs churn faster than apparel, and a single global cadence will over-sample one and under-sample the other.

Scraper cadence

Price moves are bursty, not Gaussian. A twice-daily scrape misses the burst; a 5-minute poll wastes budget on quiet hours. The pragmatic split that most teams settle on:

• Headline SKUs (top decile by revenue) — polled every 15 to 30 minutes during your category's business hours.
• Mid-tail SKUs — twice daily. Enough resolution to detect a category-wide promo; cheap enough to cover thousands of SKUs.
• Long-tail SKUs — weekly, just enough to keep replacement pricing honest.

From observation to action

A monitor that only fires alerts buys you noise. A monitor that fires alerts AND surfaces the margin-aware recommendation buys you a workflow. The shape of that recommendation is where the value lives — not in the alert itself.

Every competitor price move should arrive at the merchant tagged with one of four recommendations: hold, raise, drop, or unavailable. "Hold" is not "do nothing" — it means "your margin protects you, no move required." Two of those four are signals. Two are guards.

Surface the recommendation, not just the move

A raw alert ("Competitor X dropped 4%") forces the merchant to do the math: do I have headroom above my margin floor? Can a 1% undercut stay profitable? A margin-aware recommendation — the one PriceSense generates — answers that with the merchant's own COGS and their configured margin floor already baked in.

Concretely, an undercut lands at competitor price × 0.99 — a 1% discount, not a 5% discount, because polite undercutting wins the buyer without collapsing the margin. Whether the undercut is reachable depends on the floor: if the resulting price would land below the merchant's configured marginFloorPct, the recommendation flips to a guarded hold with a floor_unreachable flag.

Closing the loop

Continuous monitoring without a margin-aware action layer hands you a faster spreadsheet. With one, you get a pricing engine that defends your floor on slow weeks and captures margin on rally weeks. The first half is plumbing; the second half is pricing.

For a worked end-to-end example — submit a product URL, get back a personalized report with a competitor basket and a recommended price — see our pricing report tool, or compare the tier that includes scheduled monitoring on the pricing page.