How much should a competitor's price move before it triggers an alert to your team?

The wrong threshold is the one everyone ignores

If your inbox gets forty alerts a day, the effective threshold is infinity because nobody reads them. Alerts exist to change what a person does that day; anything that does not clear that bar should be logged for the weekly review instead. Start from the decision, not from the data: what price move would actually make you change your price, your promo plan, or your purchase order?

That framing produces different thresholds for different products. A high-velocity item where a small gap shifts share deserves a tight trigger; a slow, differentiated product might not warrant an alert until the move is large. A single global percentage across the whole catalog is the most common mistake we see, and it is usually the first thing worth removing.

Keep reading: Competitive Intelligence for Small Brands, How to Read a Competitor's Promo Calendar, Price Positioning: Where You Sit in the Market. See how RivalPricr helps you competitor price and promo intelligence.

Set thresholds relative to the product, not a global number

Three inputs shape a good threshold: your margin room on the item (how far you could respond before it hurts), the historical volatility of that competitor's price on that item (how often it wiggles for no reason), and the item's weight in your revenue. High volatility plus low importance means a wide threshold or no alert at all. Low volatility plus high importance means even a small move is news. Related: Spotting a Price War Before It Starts

Express thresholds in both percent and absolute dollars and require both to be crossed. The percent test alone floods you with alerts on cheap items where a few cents is a big percentage, and the dollar floor is there to stop that. Size that floor per price tier rather than once for the whole catalog: a single floor set at a level that makes sense for your mid-priced products hides meaningful moves on low-priced goods. Give cheap items a small floor and expensive items a larger one, and the combined rule stays quiet on noise without going blind at the low end. Use direction as well: a competitor cutting price and a competitor raising price are different decisions with different owners. Related: Price Positioning: Where You Sit in the Market

Add duration and confirmation so blips do not page anyone

Most short-lived price dips are not strategy; they are repricers, flash events, or errors. Require that a move persists across at least two consecutive checks before it becomes an alert, and state in the alert how long it has held. This one rule typically removes a large share of the noise without hiding anything that matters, because a real repositioning stays put. Related: Building a Market Dashboard That Matters

Layer a second confirmation in front of expensive responses. If a move would trigger your own price change, require it to be confirmed by a person or by a second data point, such as another channel or a second competitor moving the same way. You trade a few hours of latency for far fewer wrong reactions, which is a good trade for almost every brand. Related: Turning Competitor Data Into Strategy

Review the alerts you sent, not just the ones you acted on

Once a month, pull the list of alerts that fired and mark each one: acted on, useful but no action, or noise. If most are noise, widen the threshold or add a confirmation step for that product group. If an important move slipped through with no alert, tighten it. Thresholds are a living setting, not a one-time configuration.

Keep a short changelog of threshold changes and the reason for each. When someone asks in six months why a certain competitor's moves on a certain line stopped generating alerts, the answer should be findable. It also stops the slow drift where thresholds get loosened to quiet a noisy week and never get tightened again.