Dynamic Pricing Comes to QSR: The Uber Surge Model Hits Drive-Thrus

The Earnings Call That Shook an Industry

On February 15, 2024, Wendy's freshly installed CEO Kirk Tanner held his first earnings call as the company's leader. Amid the standard discussion of same-store sales growth and breakfast daypart performance, Tanner dropped a line that would consume the fast-food news cycle for weeks.

"We are planning to invest approximately $20 million to roll out digital menu boards to all U.S. company restaurants by the end of 2025," Tanner told analysts. "Beginning as early as 2025, we will begin testing more enhanced features like dynamic pricing and daypart offerings along with AI-enabled menu changes and suggestive selling."

The comment was aimed at investors. It landed with consumers like a grease fire.

Within 48 hours, "Wendy's surge pricing" was trending on social media. Headlines screamed about Uber-style pricing coming to the drive-thru. Customers joked about hoarding Frostys before summer price hikes. Consumer advocacy groups pounced. The narrative was set: Wendy's wanted to charge you more for a Baconator at noon than at 3 p.m.

It didn't matter that Tanner hadn't actually said that.

By February 27, Wendy's Vice President of Communications Heidi Schauer was issuing statements: "To clarify, Wendy's will not implement surge pricing, which is the practice of raising prices when demand is highest." The company published a blog post emphasizing that digital menu boards would enable discounts during slower periods, not surcharges during busy ones. The framing pivoted entirely—from "dynamic pricing" to "value offers."

The damage was done. Wendy's stock dipped. Late-night hosts had material for a week. And an entire industry learned a brutal lesson about the gap between what operators mean by "dynamic pricing" and what consumers hear.

What Tanner Actually Meant—and Why It Matters

Strip away the headlines and the Wendy's incident reveals a genuine strategic question that every QSR operator with more than a handful of units is now grappling with: should menu prices be static numbers printed on a board, or should they be responsive variables managed by software?

The answer depends enormously on which version of "dynamic pricing" you're talking about. The industry has been sloppy with terminology, and that sloppiness is exactly what turned Tanner's anodyne investor comment into a PR crisis.

Time-of-day pricing (also called daypart pricing) adjusts prices on a predictable, published schedule. Happy hour at Applebee's. McDonald's breakfast menu. Taco Bell's late-night box. Consumers have accepted this model for decades because it follows a simple psychological principle: the schedule is transparent, the discount feels like a reward for flexibility, and the "regular" price remains the anchor.

Demand-based pricing adjusts prices in real time based on current traffic, order volume, or other signals. This is the Uber surge model—the thing consumers thought Wendy's was proposing. Prices go up when demand is high and down when it's low. Airlines, hotels, and ride-hailing companies have normalized this in their categories. Restaurants have not.

Cost-based dynamic pricing is the newest variant, adjusting prices in response to input costs—commodity prices, labor expenses, or supply chain disruptions. A startup called WookAI has built its entire model around this approach, offering real-time price adjustments pegged to actual supply chain costs rather than demand signals.

The distinction matters operationally. A McDonald's franchisee running a $5 meal deal from 2 p.m. to 5 p.m. is doing daypart pricing. A cloud kitchen on DoorDash that raises its burrito bowl price by $1.50 during the Friday dinner rush is doing demand-based pricing. They are fundamentally different strategies with fundamentally different risk profiles.

What Tanner described on that earnings call was closer to the first category—daypart offers, AI-enabled menu changes, suggestive selling based on weather and time of day. But he used the phrase "dynamic pricing," and in a consumer environment still bruised by three years of food inflation, that phrase was radioactive.

The Technology Stack Behind the Menu Board

Whatever you call it, the infrastructure required to adjust QSR prices programmatically has matured rapidly. Five years ago, dynamic pricing in restaurants was a theoretical exercise. Today, the technology stack exists, integrates with major POS systems, and has demonstrated measurable P&L impact.

The foundation is the digital menu board—the hardware layer that makes real-time price changes visible to customers. Wendy's $20 million investment wasn't about pricing strategy; it was about installing the screens that make any pricing strategy possible. Static menu boards printed at a sign shop can't change a price without a truck roll. Digital boards can update in seconds, centrally managed across thousands of locations.

The penetration of digital menu boards across QSR has accelerated dramatically. McDonald's has been deploying them globally as part of its "Accelerating the Arches" strategy. Taco Bell, Burger King, and Popeyes have all expanded digital board installations. The hardware is no longer the bottleneck—it's the intelligence layer on top that remains nascent.

That intelligence layer is where a small but growing ecosystem of pricing engine startups operates. The two most prominent names have been Juicer and Sauce Pricing, both founded around 2021-2022 to bring algorithmic pricing to restaurants.

Juicer, co-founded by CEO Ashwin Kamlani, built software that analyzed historical transaction data—every item sold, every daypart, every channel—and made automatic, incremental price adjustments on third-party delivery apps. When business was slow, prices went down. When demand spiked, they went up. Kamlani publicly cited average sales increases of 10% to 15% for restaurants using the platform on delivery channels.

But Juicer's story also illustrates the headwinds. In late 2024, the company shut down its dynamic pricing product entirely. The Wendy's backlash had poisoned the well. "We did find that the more companies we spoke with, we started to hear, 'I don't want to become the next Wendy's,'" Kamlani told Restaurant Business Online. As a venture-backed startup with finite runway, Juicer couldn't afford to wait for sentiment to shift.

The company pivoted to a competitive pricing intelligence tool called Compete, which now accounts for 80% of its revenue. The product helps franchisees of large chains track competitors' pricing and promotional activity at the local level—useful, but a far cry from the automated pricing engine Kamlani originally envisioned.

Sauce Pricing has continued to operate in the dynamic pricing space, primarily on delivery channels. Ohio-based Piada Italian Street Food reportedly doubled its delivery margins using Sauce's platform, according to the company's published case studies. The key difference: delivery pricing happens in an app, not on a public-facing menu board. The consumer experience of seeing different prices at different times is far less visceral when you're scrolling DoorDash at home than when you're staring at a drive-thru screen with a car behind you.

This points to an important nuance in the technology landscape: dynamic pricing on delivery platforms has already arrived and is working. The resistance—the part that torpedoed Wendy's and killed Juicer's core product—is specifically about applying the same logic to the in-restaurant and drive-thru experience.

The Integration Challenge

For operators considering any form of price optimization, the technology integration requirements are non-trivial. A functioning dynamic pricing system needs to connect at minimum four layers:

POS system — the source of truth for transaction data and the endpoint where price changes must be reflected at the register. Toast, Square, Oracle MICROS, NCR Aloha, and other major POS platforms have varying levels of API openness for third-party pricing tools.

Digital menu boards — the customer-facing display layer. These must sync with POS in real time to avoid the nightmare scenario of a customer seeing one price on the board and getting charged another at the window.

Pricing engine — the algorithmic layer that ingests data (historical sales, weather, local events, competitor pricing, input costs) and outputs pricing recommendations or automatic adjustments. This is where AI and machine learning models live.

Third-party delivery platforms — DoorDash, Uber Eats, Grubhub each have their own menu management APIs. Middleware providers like ItsaCheckmate have partnered with both Juicer and Sauce to bridge pricing engines to delivery platforms.

The multi-unit operator running 200 franchise locations across three states faces a real systems integration challenge. The POS might be standardized, but digital board hardware varies. Delivery platform contracts differ by market. And the pricing engine needs clean, consistent data to function—a tall order in an industry where many locations still struggle with basic inventory accuracy.

The Psychology Gap: Why Happy Hour Works and Surge Fails

The consumer psychology research on dynamic pricing is remarkably consistent, and it explains precisely why Wendy's got burned.

The core finding, replicated across dozens of studies in the Journal of Revenue and Pricing Management, the Journal of Business Ethics, and the Journal of the Association for Consumer Research, is this: consumers evaluate price fairness not based on the absolute price, but based on whether the pricing mechanism violates their sense of a "reference price" norm.

When a restaurant offers a discount during off-peak hours, the reference price is the regular menu price. The consumer perceives a deal—a reward for being flexible. This is psychologically identical to a coupon or a limited-time offer. It feels like gaining something.

When a restaurant raises prices during peak hours, the reference price is what the consumer expected to pay—the price they saw last time, the price their friend paid yesterday. Even if the absolute dollar amount is identical in both scenarios (a $10 regular price, discounted to $8 off-peak, versus an $8 base price surging to $10 at peak), the consumer experience is radically different. One feels like a reward. The other feels like punishment.

This asymmetry is not irrational. It's deeply embedded in how humans process gains and losses—what behavioral economists call prospect theory. Daniel Kahneman and Amos Tversky documented it decades ago: losses loom larger than equivalent gains. A $2 surcharge hurts more than a $2 discount pleases.

For QSR operators, the implication is architectural. The identical pricing curve—lower prices at 3 p.m., higher prices at noon—can be positioned as either a discount or a surcharge depending on where you set the published "base" price. Wendy's mistake wasn't the strategy; it was the framing. Tanner said "dynamic pricing" when he should have said "value windows" or "off-peak rewards."

This framing problem extends to transparency. Research published in the International Journal of Hospitality Management has found that consumers tolerate time-based pricing when it's predictable and published in advance, but reject it when it feels algorithmic and opaque. A sign that says "Happy Hour: 2-5 PM, 20% off appetizers" is fine. An app that shows you a different price than your coworker sees at the same time triggers fairness alarms.

The restaurant industry already has abundant proof that the discount frame works. McDonald's has run daypart promotions for decades. Starbucks' Happy Hour campaigns—typically 50% off Frappuccinos from 2-5 p.m., promoted via the app—have driven measurable traffic shifts without backlash. Chili's, Applebee's, and virtually every casual dining chain runs happy hour drink and appetizer pricing. None of these operators would describe what they do as "dynamic pricing," even though the economic function is identical.

The Regulatory Question Nobody's Asking Yet

While consumer sentiment has been the primary barrier to dynamic pricing adoption in QSR, a quieter but potentially more consequential challenge is building in the regulatory space.

The Robinson-Patman Act, a 1936 federal law, prohibits certain forms of price discrimination—but it applies to goods sold between businesses, not to consumer-facing retail prices. There is no general federal prohibition against a restaurant charging different prices to different customers or at different times of day. Airlines, hotels, and sporting venues have operated under demand-based pricing for decades without running afoul of price discrimination statutes.

But the legal landscape is shifting. The Federal Trade Commission under Chair Lina Khan signaled increased scrutiny of algorithmic pricing practices before Khan's departure, commissioning a study of "surveillance pricing" in 2024. The FTC's concern focused on whether companies were using personal data—purchase history, location, income proxies—to charge individual consumers different prices for the same product. Eight companies, including Mastercard and McKinsey, received orders to provide information about their pricing surveillance practices.

At the state level, the terrain is more complex. California, Colorado, and several other states have passed comprehensive privacy laws that could constrain the data inputs available to pricing algorithms. If a pricing engine uses a customer's order history, location data, or app behavior to personalize prices, it may trigger consent requirements under state privacy statutes—even if the same pricing applied uniformly to all customers at a given time would be perfectly legal.

The class action bar is watching. While no major restaurant dynamic pricing lawsuit has been filed to date, the precedents from other industries are instructive. In 2023, a class action was filed against Ticketmaster over its "dynamic pricing" of concert tickets, alleging that the practice constituted deceptive trade practices under state consumer protection statutes. The case's theory—that consumers were misled about the "face value" of tickets when prices fluctuated algorithmically—could be adapted to a restaurant context if an operator implemented opaque demand-based pricing.

For multi-unit QSR operators, the practical regulatory risk is less about existing law and more about the trajectory. State attorneys general have demonstrated willingness to investigate consumer-facing pricing practices that generate public outcry. A major QSR chain implementing visible surge pricing during a period of already-elevated food costs would be an irresistible enforcement target, regardless of whether the practice technically violates any statute.

The safer legal posture—and the one the industry appears to be converging on—is the same one that works psychologically: transparent, time-based discounts rather than opaque, demand-based surcharges. Published schedules. Consistent pricing within a daypart. No personalization based on individual consumer data. This approach threads the needle between revenue optimization and regulatory risk.

Where the Industry Lands

The Wendy's episode will be studied in business schools for years as a case study in stakeholder communication failure. But the underlying question it raised—should QSR pricing be static or responsive?—has already been answered by the market. It's going to be responsive. The only open questions are how, how fast, and how transparently.

The delivery channel has already crossed the Rubicon. Restaurants routinely charge 15% to 30% more on DoorDash and Uber Eats than in-store, and consumers have largely accepted this as the cost of convenience. Dynamic pricing on top of that markup—adjusting delivery prices by a few percentage points based on demand—is happening now, at scale, with minimal consumer pushback.

The in-restaurant and drive-thru experience is where the friction lives. The technology is ready. Wendy's $20 million digital menu board investment is just one example—the industry is collectively spending hundreds of millions on the hardware that makes flexible pricing possible. But the consumer psychology demands that operators frame the capability as a discount tool, not a surcharge mechanism.

The operators who will extract the most value from this technology are the ones who understand that dynamic pricing is not a revenue strategy—it's a demand management strategy. The goal isn't to charge loyal lunch customers more for their usual order. It's to shift demand from overcrowded peak windows into underutilized dayparts, smoothing labor requirements, reducing wait times, and improving the customer experience for everyone.

Kamlani, even after shutting down Juicer's pricing product, remains convinced the concept will return. "There's this allergic reaction to the term dynamic pricing," he told Restaurant Business Online. "I think there's a form of it that will be very consumer-friendly."

He's probably right. The form it takes will look less like Uber surge and more like what airlines figured out years ago: a complex, algorithmically managed pricing structure that consumers experience as a series of deals, fare classes, and loyalty rewards rather than as prices that punish them for wanting to fly on a Friday.

For QSR operators evaluating the technology today, the playbook is becoming clear. Invest in digital menu boards—the table stakes infrastructure that enables any form of pricing flexibility. Experiment with daypart promotions using data-driven tools to identify the optimal discount windows. Test dynamic pricing on delivery channels where consumer tolerance is higher. Build the data pipeline that a pricing engine will eventually need. And whatever you do, don't call it surge pricing on an earnings call.