Competitor Price Increases: The Pricing Signal Most Operators Ignore

Ask an operator what their price monitoring is for and the answer is nearly always some version of "so I know when a competitor drops price." The alert rules, the thresholds, the weekly review, the gut reaction to a notification: all of it is tuned for downward moves. Increases get a lower priority, a longer cooldown, and a glance in the digest if they are noticed at all.

That is backwards in one important respect. A price drop is the noisiest event in a competitor's storefront. Sales, flash promotions, clearance, coupons expressed as list price, a repricing rule reacting to someone else: most drops are temporary and most of them are not decisions about you. A price increase is rare, it is almost never promotional, and it usually reflects a deliberate choice or a real cost change on the other side. When a competitor raises a price and leaves it there, they have told you something true about their business that they would not have said out loud.

This guide is about reading that signal properly. It covers what an increase usually means, how to tell a genuine list price change from a promotion ending, how to make the follow-or-hold decision without guessing, and how to configure increase alerts so that they survive contact with a feed full of drops. The pricing signals framework and the activity feed reference each touch on increases in passing. This is the full treatment.

Why Increases Are a Cleaner Signal Than Drops

Consider what has to be true for a competitor to raise a price. Someone had to decide that the product would still sell at the higher number, or that it had to sell at the higher number to be worth stocking. Either way, the increase came with a cost: fewer conversions, at least in the short term, and a visible change that every returning customer can see. Nobody pays that cost casually.

Compare that to a drop. Drops are cheap to make and easy to reverse. They are used to clear stock, hit a weekly revenue target, test a price point, match a marketplace, or simply because the calendar says it is a sale weekend. A large share of the drops in any monitoring feed will be reversed within days, and the promotional cadence of a store often explains most of them on its own.

This asymmetry is why increases deserve more attention per event than drops, not less. A single sustained increase on an overlapping product carries more information about a competitor's intent than a dozen drops that will revert by Monday. The fact that increases arrive in smaller numbers is a feature. They are easier to read one at a time.

What a Competitor Price Increase Usually Means

An increase does not come with a reason attached. Public storefront data shows the old price, the new price, and the date, and everything else is inference. But the inference is usually tractable, because there are only a handful of common causes and they leave different traces.

Cost pass-through. Supplier prices went up, freight went up, duties changed, or a currency moved against them. The signature is breadth: the increase lands across many products at once, often at a similar percentage, and frequently across a whole vendor or category rather than a curated handful. If several competitors in your set raise prices on the same brand in the same fortnight, you are almost certainly looking at a cost change that will reach you too, if it has not already.

Margin recovery. The competitor has decided that a product or line was priced too low and is correcting it. This tends to be narrower than cost pass-through and less uniform in percentage. It often follows a period of heavy discounting, and it often shows up on products that were selling well, because those are the ones where a few points of margin are worth the most. A store recovering margin is a store that has stopped chasing volume on that product, which is useful to know.

A promotion ending. The most common cause of an apparent increase, and the one that makes increase monitoring feel noisy if it is not handled. The list price was never lowered. A sale price was applied for a period and then removed, and the product returned to where it started. This is not an increase at all in the sense that matters, and the next section is about filtering it out.

Deliberate repositioning. The competitor is moving a product, a line, or the whole brand upmarket. The signature is coherence rather than breadth: increases concentrated in a specific collection, often accompanied by other changes in the same window, such as new imagery, a rewritten description, a new bundle, or the removal of the cheapest items in the range. Repositioning is the rarest cause and the most consequential, because it changes who the competitor is trying to sell to.

You will not always be able to tell these apart from a single event. You can nearly always tell them apart after a week, with a look at breadth and at what else changed on the same store. That is the discipline the rest of this guide builds.

Telling a Real Increase From a Sale Ending

Every increase you act on should first pass three checks. They take about a minute each with a monitoring tool and are almost impossible to do reliably by hand.

Check the compare-at price

On most storefronts a promotion is expressed by lowering the selling price while leaving a higher reference price in place. When the promotion ends, the selling price returns to the reference and the reference is cleared. That pattern, an increase that lands exactly on the previous compare-at value and clears it, is a sale ending. It is a return to baseline, not a new baseline. The discount depth guide covers how to read compare-at data in detail.

A genuine list price increase looks different. The selling price rises above any previous reference, or the product had no reference price before and after, or the compare-at price itself moves up alongside the selling price. When the reference price rises, the store is not ending a sale. It is redrawing the anchor.

Check the breadth

Pull up every increase from the same store in the same few days and look at the shape. A single product moving is a product decision or a data correction. A handful of products in one collection is a line decision, and possibly a repositioning. Dozens of products across categories at a similar percentage is a cost or policy change, which the pricing policy monitoring guide treats as its own subject.

Breadth also helps you catch sale endings that the compare-at check misses. If twenty products all rose on the same morning and all of them had been discounted for exactly the same fourteen days beforehand, that is a promotion closing, whatever the reference prices say.

Check that it holds

An increase that reverts within a week was a test, an error, or a stock-out placeholder. An increase that holds for seven days is a decision. An increase that holds for a month is a new price. Do not respond to an increase until it has held for at least a week, and be aware that some stores run short repricing experiments that look exactly like a real change for the first few days.

This is the check that makes increase monitoring practical. Persistence turns a stream of events into a short list of confirmed changes, and the confirmed list is usually small enough to read individually.

The Response Decision: Follow, Hold, or Wait

Once an increase has passed the three checks, you have a real signal and a real decision. There are three honest options, and the right one depends on why the competitor moved.

Following is safest when the cause is cost pass-through. If the whole market is absorbing the same supplier increase, holding your price does not win share, it just makes you the store that absorbed the cost. Customers comparing across stores will see similar moves everywhere, and your margin is the only thing that changes if you stay put. Follow, and do it within the window while the comparison set is still moving, because a lagging increase after everyone else has settled is more visible than one made alongside them.

Holding wins share when the increase is margin recovery or repositioning on a product where you are genuinely comparable. The competitor has chosen to earn more per unit and sell fewer. If you can sustain your current price, that is an opening to capture the buyers they have decided they do not need. This only works when the product is truly comparable in the customer's eyes and when you were not already the lower price by a wide margin. If you were, the increase widens a gap that already existed and changes little.

Waiting is correct more often than either. If the cause is unclear, if the increase is on a product at the edge of your overlap, or if it landed during a period when the competitor is changing many things at once, the cost of waiting another week is small and the information you gain is large. Most increases that turn out to matter are still there a week later. The ones that are not were not worth acting on.

On timing: the window for a decision is longer than for a drop, but it is not unlimited. Customers recalibrate to a new price within a few weeks. If you intend to follow, do it inside that period so the move reads as market movement rather than as your own independent increase. If you intend to hold, the share you gain arrives gradually and is easiest to measure if you note the date of the competitor's move and compare your conversion on the overlapping products before and after.

Whichever you choose, record it. The weekly operator review has a place for exactly this: the signal, the decision, and a date to check the outcome.

Setting Increase Alerts That Survive the Drop Feed

The reason increases go unnoticed is rarely that the monitoring tool missed them. It is that the increase was the ninth item in a digest that opened with eight drops, and it got the attention of a ninth item. Fixing that is a configuration problem, and a small one.

Separate the threshold. Drops and increases need different thresholds because they have different noise profiles. A drop threshold has to be high enough to filter out routine promotions. An increase threshold can be much lower, because there is far less routine noise above it. Where drops might warrant a threshold of ten percent to stay readable, increases of five percent on an overlapping product are usually worth seeing. Set the two rules independently rather than using one percentage for all price changes. The thresholds and cooldowns guide covers the mechanics.

Scope to the products that matter. An increase on a product you do not compete on is trivia. Put your overlapping products into a watchlist, organised by the category or price band you actually sell into, and read increases through that lens first. The full-store feed is still there for breadth checks, but the watchlist is where the increase that changes a decision will appear.

Require persistence before acting. Do not turn a raw increase event into a task. Turn a confirmed increase into a task. Whether you do that with a follow-up review a week later or by simply reading increases in the weekly review rather than the daily digest, the effect is the same: you act on changes that held, not on changes that happened.

Read them together, not one at a time. Breadth is only visible in a group. A weekly view of all increases from a store, sorted by collection, shows in seconds whether you are looking at one product, one line, or the whole catalog. That view is also where cross-store patterns appear, when three competitors move the same brand in the same week.

A Worked Example

A mid-price kitchenware brand monitors five competitors. On a Tuesday, one of them raises prices on eleven products by between six and nine percent. The daily digest shows the events under a run of drops from two other stores running a mid-month sale, and the operator nearly skips past them.

The compare-at check shows that none of the eleven products had a reference price before or after, so this is not a sale ending. The breadth check shows that all eleven are from a single cookware vendor, and that the competitor's other categories are untouched. A quick look at the other four stores shows two of them have also raised prices on the same vendor's products within the same week, by similar amounts.

The operator waits. Eight days later all three increases have held. The read is now clear: the vendor has raised its wholesale prices, the market is passing it through, and the brand's own cost notice from the same vendor is presumably in someone's inbox. The decision is to follow within the next week, before the comparison set stops moving, and to note that the two competitors who have not yet moved are worth a second look in a fortnight, because either they are absorbing the cost or they buy through a different channel.

That whole read took a few minutes across two weekly reviews. Without the separate increase rule and the persistence check, the same information would have been eleven items in a Tuesday digest.

Where Bonesaw Fits

Bonesaw records competitor price increases as their own change type, with the previous price, the new price, the percentage, and the date, alongside the compare-at values that let you tell a sale ending from a genuine increase. Alert rules are configured per store and per change type, so increase alerts can carry their own threshold rather than sharing one with drops, and watchlists let you narrow the view to the products you actually compete on. Sale start and sale end events are recorded separately, which takes most of the promotion noise out of the increase feed before you read it.

What Bonesaw sees is the publicly accessible storefront: listed prices, reference prices, availability, and how those change over time. It does not see a competitor's costs, their margins, or their sales volume, and neither does any tool that works from the outside. Every inference in this guide is built on what a shopper could see by visiting the store, made useful by seeing it consistently and remembering what it looked like last week.

If you have been monitoring drops and ignoring increases, the change is a small one: add an increase rule with its own threshold, put your overlapping products on a watchlist, and read the increases in your weekly review with the three checks above. The getting started guide walks through the first store if you are starting from nothing.

Frequently Asked Questions

How often do competitors actually raise prices? Far less often than they lower them, which is the point. A typical mid-size storefront in a stable category might generate a few genuine list price increases a month against dozens of drops. That scarcity is what makes each one worth reading.

Is a small increase worth an alert? On an overlapping product, usually yes. Increases carry less noise than drops, so a lower threshold is sustainable. Five percent is a reasonable starting point for products you compete on directly, and higher for the rest of the catalog.

What if the increase happened while the product was out of stock? Treat it with caution. Some stores raise prices on unavailable items to discourage backorders or to reflect the cost of the next batch. Wait until the product is back in stock and see whether the higher price holds before reading anything into it.

Should I raise my price every time a competitor does? No. Follow when the cause is a cost change reaching the whole market. Hold when the competitor is recovering margin on a product where you are genuinely comparable and can sustain your price. Wait when you cannot yet tell which it is.

How long should I wait before deciding? One week is the minimum to confirm the increase has held. Two weeks gives you time to see whether other competitors follow, which is often the clearest indicator of a cost-driven move. Beyond a month, the market has usually settled and the decision is about your own margin rather than their move.

Can monitoring tell me why a competitor raised a price? Not directly. Public data shows the change, the breadth, the timing, and whether the reference price moved. Those four things narrow the cause to one or two likely explanations most of the time. The cause itself remains an inference.

---

Bonesaw is a product of MoonsLink. Monitoring capabilities described in this guide reflect publicly accessible product and storefront data collected through standard web protocols. Bonesaw does not access private or authenticated data. All data collection respects robots.txt directives and site access policies.