How to Monitor Competitor Menu Price Changes

There is no universal answer to how often restaurant competitors change menu prices. A QSR team can measure change frequency only after it defines a price-change event, follows a stable set of restaurants, items and channels, and confirms that a new observation persists. Collection cadence should follow the event and the time available to respond. Two isolated snapshots can show a difference, but not when or how often the change occurred.

Five principles for useful competitor price tracking

Define the event before counting it.
Keep a stable observation panel.
Match collection cadence to the response window.
Confirm candidate changes and preserve uncertainty.
Store enough history to reproduce the result.

This turns a stream of menu captures into a record that pricing teams can use.

Two snapshots cannot show change frequency

Suppose an item costs £7.50 in April and £7.90 in July. The two observations show that the listed price differed. They do not show whether it changed once, changed several times, moved during a promotion, or returned to an earlier price between captures.

To answer “How often did this competitor change price?”, the team needs repeated observations and an event rule. It also needs to know when collection failed or the item was unavailable. Otherwise, a gap in evidence can be mistaken for stability.

Define a menu price-change event

A practical monitoring framework should distinguish:

Regular price change: a confirmed change in the non-promotional listed item price.
Promotional price event: a temporary offer or discount with separate eligibility and dates.
Modifier change: a change in the cost of a required or optional choice.
Assortment event: an item appears, disappears or becomes unavailable.
Product transition: a listing is renamed, resized or reformulated and may no longer be directly comparable.
Collection gap: the restaurant or item could not be observed.

These events should not all become “price changed”. Each has a different business meaning and evidence requirement.

Build a stable observation panel

Define the panel before calculating frequency. At minimum, record:

competitor brand;
restaurant identifier and address;
market and platform;
product, size and minimum valid configuration;
collection timestamp and time zone;
regular and promotional price;
availability and collection status;
match and review status.

Keep the denominator visible. If a panel begins with 100 restaurant-item pairs but only 72 have valid observations in a period, report change frequency against the eligible 72 and explain why the others were excluded.

When locations or products enter and leave the panel, report the stable-panel result separately from the wider changing sample.

Choose cadence from the event and response window

The right cadence depends on what the team wants to detect and how quickly it can act.

A short promotion may require frequent checks.
A regular menu-price review may need a daily or weekly observation, depending on the market.
A quarterly strategy review can use a slower summary, but it still benefits from more frequent source collection if the goal is to count events.

Do not promise a universal cadence. Test whether the chosen schedule can observe the shortest material event and still support the team's response process.

Confirm a candidate change

One changed observation can be a real event, a short promotion, a display issue or a collection error. Use a documented confirmation rule.

A simple process is:

mark the first changed observation as a candidate;
compare it with the previous valid observation;
check promotion, product, restaurant and customer-state fields;
repeat the capture under the agreed rule;
confirm, reject or leave the event unresolved;
preserve the observations and reviewer note.

Persistence rules should match the market and collection cadence. They are team-approved methods, not universal industry standards.

Set alert thresholds for size, breadth and confidence

Not every confirmed event needs an immediate alert. Define thresholds that reflect business importance.

An alert can consider:

absolute and percentage price movement;
number and share of eligible restaurants affected;
priority products or competitor groups;
number of channels or markets affected;
match confidence and confirmation status;
whether the observation is regular price, promotion or assortment.

Show the denominator beside any percentage. “Half the market changed” is not defensible when the eligible sample is unknown.

Store enough history to reproduce the event

A useful history keeps more than the latest price. It should retain the original listing, observed values, timestamp, availability, promotion state, matching version and confirmation record.

This makes it possible to answer:

what changed;
where it changed;
when it was first and last observed;
how broadly it appeared in the monitored panel;
whether the result survived review.

If the matching rule changes, record the version and review any resulting series break.

Measure change frequency inside the defined panel

Useful measures include:

confirmed regular price-change events per eligible restaurant-item pair;
share of eligible pairs with at least one confirmed change;
median days between confirmed events for pairs with enough history;
share of candidate events confirmed, rejected or unresolved;
time from first candidate observation to confirmed event;
breadth of each event across eligible restaurants.

State the geography, platform, period, eligible denominator and collection cadence with every result. Do not compare two competitors if their coverage or event rules differ materially.

Turn monitoring history into a pricing decision

Competitor history can help a QSR team identify where to investigate. It can show that a named item changed across many monitored restaurants, that movement was limited to one channel, or that a candidate change was actually a promotion.

It cannot explain competitor intent, margin or customer response on its own. Use first-party sales, margin and experiment data before changing your own prices.

Getplace's published McDonald's UK menu price analysis owns the specific April to July 2026 findings. This guide does not repeat those figures as a universal cadence. It explains the monitoring structure needed to produce a reliable event history.

Teams can use Getplace's restaurant pricing intelligence as one source of store-level observations and price history, then apply their own panel, event and response rules.

Frequently asked questions

How often should a QSR track competitor menu prices?

As often as needed to observe the shortest material event and act within the chosen response window. The cadence should be documented and tested.

Does every different observed price count as a change?

No. The item, restaurant, price component, customer conditions and promotion state must match, and the candidate should pass the agreed confirmation rule.

Should promotions count as menu price changes?

Track them as separate promotional events. Do not combine them with regular menu-price changes unless the analysis explicitly calls for that measure.

What is a restaurant price tier?

A price tier is a group of restaurants or items that follow the same approved price level. Define the membership and effective period before comparing movement between tiers.

Can a monthly comparison measure how often prices changed?

It can show differences between monthly snapshots. It cannot reliably count events that occurred and reversed between them.

Monitor the event, not just the latest price

Reliable competitor price monitoring begins with a stable panel and a clear event definition. Once those are in place, alerts and frequency metrics can show what changed, where it changed and how certain the team is. Without them, the latest price is only another isolated observation.

About the evidence

This is a method-led framework. Relevant Denis posts and the published McDonald's UK article informed the editorial question, but post-only figures were not reused as evidence. No universal competitor change rate or ideal collection cadence is claimed.

How to Monitor Restaurant Competitor Menu Price Changes