Dynamic pricing in quick service: where is the line?

Few topics in quick service are as charged. When one national chain floated “surge-style” menu pricing, the public reaction was severe enough to force a clarification and a retreat within days — and the episode has hung over every pricing conversation in the category since. Digital menu boards make variable pricing technically trivial. Diner trust makes most versions of it commercially dangerous.

But writing off dynamic pricing entirely misreads the lesson. The backlash was against a specific mechanism — paying more because you came when it is busy. Several adjacent mechanisms carry none of that risk and most of the value.

Why did surge pricing fail in QSR?

Because quick service sells predictability. The category’s core promise — the same order, the same price, every visit — is precisely what surge pricing breaks. Diners experience a price that rises at lunch as a penalty for showing up, and in a category where value perception drives traffic more than any other factor, that perception spreads faster than any clarification. Airlines can surge because flights are considered purchases; a burger is a habit. You do not tax a habit you spent decades building.

What forms of dynamic pricing do work?

The ones diners read as rewards, and the ones they never see as “dynamic” at all:

• Off-peak offers. Discounted bundles in quiet dayparts move demand into spare capacity. Same mechanism as surge pricing, opposite framing — and diners embrace it.
• Personalised loyalty pricing. Targeted offers through the app price-discriminate at the individual level, invisibly and by consent. The diner sees a perk, not a price change.
• Elasticity-led list pricing. Item-level POS history shows which prices carry headroom and which items are traffic drivers to be protected — so periodic price moves land on data, not intuition.
• Channel pricing. Delivery menus already price differently from the counter. Diners accept it because the context differs visibly.
• LTO price architecture. Limited-time offers introduce price points without touching the core menu — a testing ground with a built-in expiry date.

“Diners punished pricing that penalises the rush. They embrace pricing that rewards the quiet hours.”

What infrastructure does responsible pricing require?

Three things, in order: item-level transaction data to read elasticity from real behaviour; centrally controlled menu boards so a price decision reaches every screen, receipt and app simultaneously; and closed-loop measurement so every move is validated against traffic, mix and margin — not just the item’s own revenue. A price change that lifts one item and quietly bleeds combo attachment is a loss wearing a win’s clothes, and only the loop catches it.

This is how pricing works inside a coordinated operating loop: menu and pricing decisions draw on the same item-level data as forecasting and media, deploy through the same screen infrastructure, and are read at the same transaction. Pricing stops being an annual committee exercise and becomes a measured, reversible instrument.

The chains that win this decade will not be the ones with the boldest pricing algorithm. They will be the ones whose pricing diners never think about — because every change either rewarded them or was too well-judged to notice.