Competitor Price Tracking: What to Watch and When to Respond

Why is price the weakest signal in ecommerce competitor analysis?

Rank the four things worth watching, from most to least reliable: overlap-weighted price moves first, then markdown share, then assortment changes such as new arrivals and new collections, then bestseller availability. Price only earns its place at the top of that ranking once it is weighted by overlap. A single, unweighted price change is the least reliable signal of the four, and that is exactly where most ecommerce competitor analysis stops looking.

A single list-price change is frequently noise: a seasonal adjustment, a one-SKU test, a correction of a pricing error. A rising markdown share reads differently. Markdown share is the share of a catalog listed below its compare-at price, and a meaningful rise in it reflects a deliberate discount posture spread across many products at once, not a single line-item decision. One data point can be an accident. A shift in the aggregate almost never is.

Assortment changes, new arrivals and new collections, show where a competitor thinks the category is heading, which matters over a longer horizon than any single price. Bestseller availability, whether their top sellers are in or out of stock, is the least price-related of the four but often the fastest-moving: a stockout on a shared bestseller can shift demand toward you within days, independent of anything either brand does on price.

What is competitor price monitoring? The actual thresholds worth setting

Competitor price monitoring is the automated half of price tracking: rules that check a competitor's public storefront on a schedule and surface a change only once it crosses a threshold worth your attention, instead of asking you to notice it yourself. A price move past 5%, or a markdown share rise of at least 15 percentage points, checked daily, is a defensible pair of thresholds to set for yourself. These also happen to be the production thresholds Kluck runs by default.

A pricing needs review card fires when a tracked product's price changes by more than 5%, or when a competitor's markdown share rises by at least 15 percentage points. Both detectors stay visible as evidence on the same card, so you can see whether one product moved or the whole catalog's discount posture shifted. Severity escalates when the price drop lands on a bestseller that overlaps your own catalog.

A separate detector compares the current catalog snapshot against the previous one and flags new products or new collections. When three or more new products share one new collection, they group into a single new-collection item instead of firing as separate alerts, which keeps a real assortment shift from looking like ten unrelated notifications.

A third detector watches only the competitor's top 20 best sellers and flags any that flip from available to out of stock, or back. It is deliberately limited to the top 20 rather than the full catalog; a stockout on a slow-moving SKU is not worth an alert, and widening the watch list would mostly add noise.

The overlap set: price index and revenue-weighted price index

You do not need every price a competitor publishes. You need the matched set: the products where you and the competitor compete for the same purchase. Everything outside that set is context, not signal.

On a matched item, a price index above 1.05 means you are positioned at a premium, 0.95 to 1.05 is parity, and below 0.95 you are undercutting. A single matched item's index is a data point. What you actually want is the weighted picture across the whole matched set, because an average that treats every item equally can hide exactly the item that matters most.

The unweighted average says you are at parity and there is nothing to look at. The weighted figure says your exposure sits almost entirely in one product: the tee is 45% of matched-set revenue and the only item where the competitor is meaningfully cheaper. A 16% premium on a product carrying 45% of your matched-set revenue is a different problem than the same premium on a long-tail SKU, and only the weighted figure shows it. Run this on a spreadsheet with your own matched set before trusting any single item's index in isolation.

What is markdown share, and why does a 15-point rise matter?

Markdown share is the share of a competitor's live catalog currently priced below its own compare-at price. It is the aggregate view a single price index cannot give you: whether a competitor's whole catalog is drifting toward a more aggressive discount posture, not just one product.

The margin cost of matching a price cut

A competitor cutting price is not an instruction. Matching is a decision with a computable cost, and the cost is knowable before you touch your own price. You hold total contribution only if your unit sales rise by at least m0 ÷ m1. Put the other way, you can afford to lose up to 1 − (m0 ÷ m1) of unit sales if you hold your price instead of matching.

The thinner your margin, the more expensive matching becomes, and the thinner-margin brand is exactly the one most tempted to match, because the competitor's absolute price gap looks scariest from there. Never predict how volume will actually move; this is a guardrail, not a forecast. State the floor plainly too: never take a price below your own cost per item.

Three worked examples, and four responses that are not matching

A fashion brand at 55% gross margin facing a competitor's 20% sitewide markdown on eight overlapping SKUs, priced at $80 with a $36 cost: matching to $64 cuts unit margin from $44 to $28, and m0 ÷ m1 = 1.57, so holding contribution flat needs unit sales up 57%, not a modest bump.

A home goods brand at 30% gross margin facing a competitor's smaller 10% discount on three overlapping SKUs, priced at $120 with an $84 cost: matching to $108 cuts unit margin from $36 to $24, and m0 ÷ m1 = 1.50, a 50% unit increase, even though the competitor's discount depth was far shallower than the fashion example above. The thinner margin does more damage than the deeper discount.

A skincare brand at 60% gross margin facing a competitor's 15% discount on five overlapping SKUs, priced at $40 with a $16 cost: matching to $34 cuts unit margin from $24 to $18, and m0 ÷ m1 = 1.33, a 33% unit increase. A meaningfully higher margin than the other two examples still does not make matching free; it only raises the bar at which matching starts to look reasonable.

Four responses do not require matching. Hold and defend on real differentiators, right when your differentiation is genuine and defensible rather than assumed. Counter with a focused, time-boxed offer on the overlapping products only, right when the pressure is real but you do not want to reset your whole price architecture. Shift spend toward products where you hold an advantage, right when the competitor's cut is isolated to SKUs where they now have room and you do not. Do nothing and record the observation, right when the move is small, plainly temporary clearance, or barely overlaps your catalog at all.

The monitoring cadence, and choosing the three competitors worth tracking

Daily: the overlap set's prices and bestseller availability. These move fast enough, and matter enough, to check every day.

Weekly: assortment, promotions, offers, and ad activity. These shift more slowly and rarely need a same-day reaction.

Monthly: pricing architecture and positioning drift, plus a review of whether the tracked set is still the right three brands. A competitor that shifted category or price tier six months ago may no longer belong in your set at all.

Checking prices more often than daily does not produce more decisions worth making. It mostly produces more looking, and a habit of reacting to noise that would have resolved itself by the next real check.

Choose the three on shared customer, category, price position, market, or creative strategy, not on fame or size. A brand ten times your size is a case study, not a competitor; you are not fighting for the same purchase decision. A simple rejection test: if you would not plausibly lose a specific customer to this brand this quarter, it does not belong in your three.

What to look for in a competitor monitoring tool

Evaluate a competitor monitoring tool on criteria that hold up regardless of which product you end up choosing. Change detection over a static dashboard: a tool that only shows you today's snapshot makes you do the comparison yourself, every time. Thresholds you can reason about, not a black-box alert: you should be able to state, in one sentence, exactly what triggered a notification.

Overlap mapping against your own catalog, not just a competitor's catalog in isolation: a price change on a product you do not compete on should never carry the same weight as one on a matched item. Multi-surface evidence, catalog, promos, social, and ads together, rather than price alone, because price without context is the weakest of the four signals covered above.

Stated data freshness, not an implied promise of real time: you should always be able to see when a given piece of evidence was last collected before making a time-sensitive call on it. And a clear, explicit statement of what the tool does not know, because a tool that only tells you what it can do will eventually cost you a decision made on a gap it never disclosed.

Competitor intelligence: what public signals can and cannot prove

Competitor intelligence, at its most useful, is a synthesis of what a competitor puts into public market: storefront, pricing, promotions, social presence, and advertising activity, read together instead of separately. That synthesis is genuinely valuable, and it is also bounded in a way worth stating plainly.

Public signals are not private performance data. What you can observe is what a competitor chooses to show a customer. You cannot observe their actual sales, their profitability, their inventory position, or whether a campaign you can see is actually working for them. A competitor running a large volume of ads is evidence they are spending, not evidence those ads are profitable.

This is a boundary worth stating without hedging, not a disclaimer to bury: everything you can gather this way is public information, collected from pages a customer could see without logging in. Nothing here is a substitute for real performance data you do not and cannot have about someone else's business.

Price index, markdown share, overlap rate, and unit margin: what each one tells you

These are the five numbers this page actually runs on. Each one answers a different question, and each stands on its own if you only need one of them right now.

None of these five replace each other. Price index and revenue-weighted price index tell you where you stand; markdown share and overlap rate tell you how much any of it matters; unit margin tells you what a reaction would actually cost. A response decided from only one of the five is a guess dressed up as analysis.

Should you match a competitor's price?

Most brands should not match a competitor's price, and the ones most tempted to match are the ones who can least afford it. A competitor cutting price feels like an emergency, and matching feels like the obvious response. The math usually says otherwise.

Take the same example as above: price $50 to $45, cost $20. m0 = 30, m1 = 25, m0 ÷ m1 = 1.20. Matching requires 20% more units just to hold contribution flat, before it produces a single extra dollar of profit. On a thinner-margin product, the same size of cut produces a far larger required increase, which is exactly backwards from where most brands feel the pressure hardest: thin-margin brands feel the most urgency to match and can least afford the arithmetic of matching.

There is a real exception, stated plainly so this does not read as an absolute rule: if you are structurally the low-cost operator in the category, meaning your cost basis is genuinely lower and durably so, you can hold a lower price indefinitely without the same margin damage. That is a cost-structure advantage, not a pricing decision, and most brands reading this are not in that position.

This is also why Kluck's pricing recommendations are computed from your margin and your cost basis, and not from a competitor's price. Kluck will tell you a competitor dropped 12% across eight overlapping SKUs, show you exactly which of your products are affected, and hand you the margin math above. It will not tell you to match. That is a design choice, not a missing feature: a pricing engine built to chase competitor prices would be optimizing for the wrong input.

The competitor price tracking decision framework: a competitor just dropped price, now what?

Run this sequence the moment a pricing needs review card fires, before changing anything.

1. 1

   Confirm it crossed a real threshold.

   More than a 5% price move on a tracked product, or markdown share up 15 or more percentage points. Check whether severity is escalated for landing on a bestseller overlap.

2. 2

   Map the overlap.

   Identify which of your own products actually compete for the same purchase as the item that moved. Ignore the change if nothing in your catalog overlaps with it.

3. 3

   Compute your price index and revenue-weighted price index on the affected match.

   A single item's index tells you your position on that product. The revenue-weighted figure across the whole matched set tells you whether it is a real problem or a rounding error.

4. 4

   Run the margin cost of matching before deciding anything.

   m0 ÷ m1 on your own price, cost, and the matched price. This number, not the size of the competitor's headline discount, is what should drive the next step.

5. 5

   Choose hold, counter, shift, or do nothing, and record the decision.

   Pick based on the margin math from step 4 and how defensible your differentiation genuinely is, not on how uncomfortable the competitor's move feels.

6. 6

   If you hold price and the real problem turns out to be conversion or acquisition cost rather than the price itself, that is a different diagnosis.

   A competitor's move can trigger a review that finds your own funnel or ad performance is the actual issue. Run the recovery process built for that.

   Run the 30-Day ROAS Recovery Playbook

Shopify competitor analysis: what Kluck actually tracks

Kluck's live data connections are Shopify and Meta. Everything below is the Competitors surface, built from public sources only; nothing here is inferred beyond what is listed.

Before you start

• Your cost basis per SKU, so the margin math on this page means something the moment a competitor moves.
• Shopify and Meta both connected; the Competitors surface requires both.
• Each competitor's public storefront URL, plus optionally an Instagram handle, Facebook Page ID, or Meta Ads search term.
• Owner or admin access, since adding a competitor is restricted to those roles.

Keep in mind

• Public signals are not private performance data. Kluck shows what a competitor puts into market; it cannot prove their private sales, profitability, inventory position, or whether a campaign you can see is actually working for them.
• Three competitors per workspace, currently. Treat that as a real constraint that pushes toward a focused, genuinely comparable set rather than a wide one, not as a gap to work around.
• Not a live feed. Evidence refreshes through background collection, an almost real-time operating view rather than a live one. Check the displayed sync status before any time-sensitive decision.
• Kluck will not set your price off a competitor's price. Pricing recommendations are computed from your margin and cost basis, not competitor prices; competitive pricing is not part of the pricing engine, by design.
• Kluck never writes a price on its own. Competitor rules are notify, or notify-and-suggest. Every price change is a separate action you approve.
• No marketplaces, no price feeds. Coverage is public DTC storefronts, Instagram, and the Meta Ad Library, not Amazon, eBay, Walmart, or Google Shopping feeds.
• Meta Ad Library only for paid signal. No Google Ads and no TikTok visibility into a competitor's advertising.
• Nothing behind a login. Public pages only, no accounts, no gated data, and nothing a customer could not also see themselves.

Frequently asked questions