Case Study 24.2 — The Word "Surge": Wendy's, Dynamic Pricing, and the Fairness Constraint
A real, public case, and a contested decision rather than a clean failure. Facts are drawn from public earnings-call statements, the company's own subsequent public clarification, and the contemporaneous press coverage. No financial figures are attributed beyond what was publicly reported, and none are reconstructed.
Background
In February 2024, on a quarterly earnings call, the chief executive of Wendy's — a very large, publicly traded quick-service chain — described a program of investment in digital menu boards across the company's U.S. restaurants, and said that the capability would allow the company to begin testing dynamic pricing starting in 2025.
Digital menu boards are unremarkable technology. They replace printed or backlit static panels with screens, and every large chain has been installing them for years. What they enable is the ability to change a displayed price without a printer, which means prices can vary by daypart the way an electronic road sign varies a speed limit.
Coverage of the call picked up two words that were not, as far as the public record shows, said on it: surge pricing. Within days the story had moved from the trade press to national news and then to a broad, loud, and almost entirely negative public reaction — the general shape of which was that a hamburger chain intended to charge more for lunch at lunchtime.
On February 27, 2024, the company issued a public statement clarifying its intent. In substance: it had never planned to raise prices when demand was highest, the reporting had mischaracterized the plan, and the flexibility of digital menu boards was intended to support discounting and value offers during slower dayparts.
The operating issue
Here is what makes this a case study for Chapter 24 rather than a media story.
The two policies are the same instrument. Whether you set a base price of \$8 and raise it to \$10 at noon, or set a base price of \$10 and drop it to \$8 at three in the afternoon, the customer at noon pays \$10, the customer at three pays \$8, and the company's revenue is identical. The spread is the instrument. The base price is a labeling decision.
The chapter states this as an asymmetry and it is worth restating here as an operating fact: identical economics, opposite reception. Nobody has ever objected to a happy hour. Restaurants have discounted slow periods in the United States for the better part of a century — early-bird menus, weekday lunch specials, two-for-one Tuesdays, Restaurant Week, late-night bar menus — and none of it has ever been a scandal. The same differential, described as an increase at peak, became a national news cycle in under two weeks.
The second issue is subtler and it is about who bears the price. Quick-service demand peaks at mealtimes, and the people eating at a quick-service restaurant at 12:15 on a Tuesday are, in very large part, people on a fixed lunch break. They are not choosing 12:15 over 3:00 the way a traveler chooses Tuesday over Friday to save on airfare. They are choosing 12:15 because that is when their break is. A peak-price scheme therefore charges the most to the customers with the least schedule flexibility, and schedule flexibility is not randomly distributed across incomes.
That is the fairness problem in its sharpest form, and it is the reason the reaction was disproportionate to the dollars. People did not object to a possible fifty-cent differential. They objected to being on the wrong end of a mechanism they could not opt out of.
What it shows
One: framing is not cosmetic; it is most of the product. An operator who believes the two policies are "the same thing, really" has made a real analytical error, not a semantic one. The customer's response is part of the economics. A pricing scheme that produces an extra 2% of revenue and a 4% decline in visits has lost money, and the decline in visits is caused by the framing.
Two: the risk is asymmetric and cheap to avoid. The downside of the discount framing is bounded — you gave away some margin during hours you were not selling. The downside of the surcharge framing is unbounded, because it is reputational: reviews, social media, a segment on the evening news, competitors running advertising about how they would never do that. Given a choice between two instruments with identical revenue and wildly different tail risk, there is only one professional answer.
Three: it shows how little of this is about the price. Note that the company had not raised a single price and had not tested anything. The reaction was to a capability described on an earnings call. That tells you something important about how much latitude guests extend to restaurants on pricing: not much, and less than they extend to airlines, hotels, ride-hailing services, and concert promoters, all of which do far more aggressive versions of this in public without comment. Food is different. It is bought frequently, by everyone, at a low price point, and people have a strong intuitive sense of what a hamburger costs.
Four: it is a large-chain story with a direct small-restaurant application. Bellwether will never install a digital menu board. But Bellwether will face the question in a smaller form — a holiday prix fixe priced above a normal Saturday, a peak-window reservation fee, a service charge, a delivery-menu price that is higher than the dine-in price. Every one of those is the same decision at a smaller scale, and every one of them is subject to the same asymmetry.
Outcome
The company clarified its position publicly, the news cycle passed, and there is no public record establishing that peak surcharging was ever implemented. What the episode contributed to the industry was a widely known cautionary reference point: several operators and analysts have since discussed demand-based pricing specifically in terms of how it is described, which was not a common framing before 2024.
It landed in the middle of a broader and continuing public argument about restaurant pricing transparency. Through the early 2020s, mandatory surcharges of various kinds — "kitchen appreciation" fees, wellness fees, temporary inflation fees, credit-card surcharges — became common in American restaurants and then became controversial. Several U.S. jurisdictions have moved on how mandatory fees must be disclosed in advertised prices, with California's 2024 legislation and the restaurant industry's response to it the most publicized instance. That is a live area of law, it varies enormously by state and city, and any operator adding a fee needs to check where they are before they print a menu.
It is also worth noting, for anyone who assumes discounting is always the safe side: discounting alcohol is regulated too. Massachusetts banned happy-hour drink discounting in 1984, and a number of states restrict two-for-ones, unlimited-time drink pricing, and volume-based drink promotions. A food discount that is entirely routine may be unlawful applied to drinks in your jurisdiction. Verify locally, every time.
The lesson
Set your menu price at what you intend the peak to pay, and build every demand-shifting instrument as a discount from it.
You give up nothing financially. The spread is the same, the revenue is the same, and the fence works the same way. What you avoid is an entire category of risk that is very cheap to avoid and very expensive to survive.
The deeper lesson is the one §24.6 declines to resolve. The efficiency argument for demand-based pricing is strong — capacity really is scarce at peak and free at trough, and charging one price for both is itself a cross-subsidy that somebody pays. But dinner, and lunch, are not airline seats. They are bought by people whose schedules are set by their employers, and a mechanism that charges more for inflexibility is charging more for something most people did not choose.
The workable test — can the guest see the rule and choose the cheaper side of it? — is a compromise, not a solution. It is enough to run a restaurant by. It is not enough to feel finished with, and you should not pretend otherwise when someone asks you about it.
Discussion questions
- Restate the two policies from this case as a single instrument with a base price and a spread. Show that the revenue is identical. Then explain, in commercial rather than moral terms, why one version is worth adopting and the other is not.
- Airlines, hotels, ride-hailing services, and concert promoters all practice far more aggressive demand pricing than any restaurant, publicly and without much objection. Propose two explanations for why food is treated differently, and say what each explanation would predict about a restaurant that tried it anyway.
- Apply the chapter's test — can the guest see the rule and choose the cheaper side of it? — to a quick-service lunch surcharge. Does it pass? Does your answer change if the price difference is posted on the menu board a week in advance?
- Bellwether's plan contains a holiday prix fixe priced above a normal Saturday. Is that a peak surcharge? Defend your answer against someone who says it obviously is.
- A mandatory 4% "kitchen fee" and a 4% across-the-board menu price increase raise the same money. Name three reasons an operator might prefer the fee, and then name the reasons the chapter would tell them not to. What does your jurisdiction require in terms of disclosure — and do you actually know, or are you guessing?
- This case is about a company with thousands of units and a communications department. Bellwether has two partners and a social-media account. Does that make a pricing misstep less dangerous, because nobody is watching, or more dangerous, because there is no way to recover? Argue it with reference to Chapter 23's material on reviews.