How Do Customers React to Dynamic Pricing?
Customers accept dynamic pricing as an off-peak discount and resist it as a peak surcharge. Here are dated backlash examples and how to measure your own customers' reaction by segment.
Customers tend to accept dynamic pricing when it shows up as a discount at quiet times, and push back when it shows up as a surcharge at busy ones, often before any price has changed. In surveys most diners say they dislike it; what they actually do differs by segment, and in the worked example below it is the regulars who visit most who react. To know how your own customers will react, measure what each segment did after a pilot or a past price change, against locations that did not change, and read what they wrote alongside. That measurement, across reviews, surveys, app chats and loyalty transactions for every location, is the work Dimension Labs was built to do for a multi-location chain.
Below: dated public examples of dynamic pricing backlash, what the survey numbers do and do not tell you, and a worked example on synthetic sample data, a fictional 60-location fast-casual chain that piloted daypart pricing in 20 locations.
Will customers accept dynamic pricing at a restaurant?
Asked directly, most say no. In a survey of 1,000 U.S. adults fielded in March 2024 for the restaurant software company HungerRush, 64% said they react negatively to restaurants using surge and dynamic pricing, and 81% said they would either stop going to a restaurant or change when they eat out to avoid peak prices (HungerRush, April 2024).
Those are answers about a word. "Dynamic pricing" covers both a happy hour and a Friday night surcharge, and customers hear the second. When Wendy's explained what it had meant, it described the first: menuboards that "could allow us to change the menu offerings at different times of day and offer discounts", "particularly in the slower times of day" (RetailWire, February 2024). Stonegate, the UK pub group, made the same argument for its peak-time drink prices: the extra let it keep happy hours and two-for-one cocktails at other times. One reply on X summed up how that landed: "How about charging 20p less when they are less busy?"
So acceptance depends on three things you control: whether the change reads as a discount or a surcharge, whether the price is shown clearly before the customer commits, and which customers it lands on. The first two are framing. The third you can only learn from your own customers' behavior, because what people say they will do is a weak guide to what they do (churned vs retained customers shows why records beat stated intent). The reliable test is a pilot, or a past change, measured against comparable locations.
What are real examples of dynamic pricing backlash?
Three cases with dates and published coverage, two from hospitality and one from live events.
Wendy's, February 2024. On its earnings call, the new CEO described $20 million to put digital menuboards in every U.S. company-operated restaurant by the end of 2025, and said the company could test "dynamic pricing and daypart offerings" from as early as 2025 (Nation's Restaurant News). Coverage read it as surge pricing. Senator Elizabeth Warren called it "price gouging plain and simple", and Burger King's U.S. president said, "I will never support surge pricing or charging people more when they're hungry." Within two weeks Wendy's said it "will not implement surge pricing" (Axios, 2024-02-28). No price had changed.
Stonegate pubs, September 2023. The UK pub group raised drink prices on Friday nights and Saturdays at about 800 of its venues, by about 20p a pint at some and up to £1.50 a drink, and told customers with a small table sign that did not state the size of the increase or the hours (Raconteur; Fortune). The reaction ran to calls for a boycott.
Oasis tickets on Ticketmaster, 2024 to 2025. Fans who queued for the reunion tour saw prices rise while they waited, some standing tickets going from $100 to $466 before fees, and the UK's Competition and Markets Authority opened an investigation within days (NPR, September 2024). A year later the regulator said it "has not found evidence" that dynamic pricing was used; the issue was that standing tickets came in two price tiers fans were not told about, and Ticketmaster agreed to show the range of prices in the queue and say when cheaper tickets sell out (Music Business Worldwide, September 2025).
Public examples, dated
In three public cases, the backlash came from the word and the framing, before any customer data was in
What was announced, how people reacted, and what each case shows for a restaurant or venue weighing dynamic pricing.
| Case | What happened, and the reaction | What it shows |
|---|---|---|
| Wendy's, Feb 2024 | Described digital menuboards that could let it test "dynamic pricing and daypart offerings". Read as surge pricing; a U.S. senator called it price gouging | The word did the damage. Wendy's said it meant discounts at slower times |
| Stonegate pubs, Sep 2023 | Charged more for drinks at peak times in about 800 UK pubs. Calls for a boycott; the table sign did not state the increase or the hours | A surcharge at busy times, with vague notice, reads as unfair |
| Oasis tickets, 2024 to 2025 | Prices rose while fans queued. A regulator found no evidence of dynamic pricing, but two standing price tiers fans were not told about | Customers react to surprise and to how the price is shown |
The common thread is useful for any operator: customers reacted to surprise and to feeling charged more for being hungry or loyal, whatever the pricing mechanism. That is good news, because framing and notice are within your control, and the size of the reaction in your own customer base can be measured before you roll anything out.
How do customers react to dynamic pricing, segment by segment?
Unevenly, and an average across all customers hides the segment that matters. In the sample, the chain's 20 pilot locations raised Friday and Saturday dinner prices 6% and took 15% off weekday afternoons for 13 weeks, while 40 locations kept their prices. Each segment's change in visits per member is measured against the same segment at the comparison locations, so season and weather that hit every location cancel out.
Sample data, labelled
In the sample, weekly regulars cut their visits by about 9%; other segments barely moved
Change in visits per loyalty member after the pilot (peak prices up 6%, weekday afternoons 15% off), against 40 locations that kept their prices. 90% intervals from resampling locations.
No change
Weekly regulars made 9.1% fewer visits (90% interval 7.5% to 10.7% fewer). Monthly visitors made slightly more visits, +2.9% (+0.7% to +5.2%), which fits customers using the afternoon discount. For occasional guests and delivery app customers the intervals include zero, so the data cannot tell their change from no change.
The regulars are 11% of members but 47% of visits at the pilot locations. Their drop alone, about 12.4 visits per location per week (136.8 visits × 9.1%), is larger than the net change across all segments, -11.3 visits, or -3.9%. A chain-wide average of about 4% fewer visits would hide that the people paying the surcharge most often are the ones leaving.
Survey answers like the 81% in the HungerRush study describe what all diners say they would do. Your own data tells you which of your customers actually change their visits, by how much and at which locations, which is what turns a pricing debate into a decision.
How do I measure the customer reaction before and after a price change?
Define segments before you look. Frequency (weekly, monthly, occasional), channel (in store, delivery app, catering), and daypart habit, all from loyalty or card data. Fix them from the months before the change so no customer moves segment because of it.
Keep comparison locations. Run the pilot in some locations and not others, chosen so the two groups looked alike before. If the change already went out everywhere, use the locations or regions that changed later as the comparison; how to backtest a decision you already made covers how to grade that kind of estimate honestly.
Measure behavior per segment. Visits per member, check size, and the share of visits at peak. A segment that shifts from Friday to Tuesday has accepted the pricing; a segment that stops coming has not.
Read what customers wrote, by segment. Tag reviews, surveys and app chats for price fairness (words like surge, unfair, trick, charged more), separately from complaints about the price level. Join the comments to loyalty IDs where you can, so you see who is complaining as well as how many.
Hold the confounders fixed. Weather, season, local events and foot traffic move visits whether or not prices changed. The comparison locations handle what hits every location; local factors need to be in the model.
Report ranges, and the segments whose ranges include zero. An effect you cannot tell from zero is not an effect to act on yet.
In the sample, comments calling a price unfair or a surge went from 9.0 to 29.0 per 1,000 comments at pilot locations and from 9.0 to 11.8 at comparison locations.
Sample data, labelled
Price-fairness complaints tripled at pilot locations and barely moved elsewhere
Comments (reviews, surveys and app chats) that call a price unfair, a surge or a trick, per 1,000 comments, in the 13 weeks before and after the pilot began.
BeforeAfter
Joined to loyalty IDs, 73 of the 161 complaints at pilot locations after the change, 45%, came from weekly regulars, the same segment whose visits fell. The comments and the behavior agree, which makes the result easier to trust and gives you the customers' own words on what felt unfair. For how to separate price-level complaints from value and fee complaints, see how to tell whether customers think you are too expensive from their comments.
What should I check before rolling dynamic pricing out to every location?
Which segment carries the reaction. If it is the regulars, test a version that protects them, such as a member price that does not rise at peak, and measure again.
Whether the discount half works. Count the visits that moved into quiet dayparts, not only the ones lost at peak. In the sample the monthly visitors' gain was real but too small to offset the regulars.
How the price is shown. The Ticketmaster outcome turned on notice: what buyers were told, and when. Menuboards, apps and delivery listings should show the same price at the same time.
Locations that differ. Results from downtown stores with lunch rushes may not carry to suburban ones; group locations by type first, as in how to compare restaurant locations using guest reviews.
A date to look again. Write down the range you expect for each segment and check it at 8 and 13 weeks.
Put together, that is a rehearsal of the decision on your own customers: what they said and did after a comparable change, by segment, with a range. A customer world model is the name for keeping that record joined and current, so the next pricing question starts from what your customers have already shown you. How to test a business decision on customers before you make it walks through the same method for a straight price increase and a location closure, and for a flat increase that reaches every customer, how to predict customer reaction to a price increase reads two dated Peacock increases in public reviews and backtests the estimate.
What does Dimension Labs measure when a chain tries dynamic pricing?
Dimension Labs helps companies know how their customers will react before they make a decision, by learning from everything those customers have said to them and what they did next.
For a pricing pilot, that comes down to four things the platform does today:
It reads every channel where customers react: reviews for each location, post-visit surveys, app and website chats, delivery app comments and support emails, so a surge complaint counts wherever it was written.
It connects those channels to the operating data that shows what customers did: loyalty and card transactions, location lists, the dates and sizes of price changes, with weather and the calendar alongside. That join to CRM and revenue data, with effects and confidence intervals, comes with Prove ($2,999 a month) and higher plans.
It enriches every comment with Dimensions written for your business, such as price fairness, price level, value and daypart, so finance, operations and marketing read the same labels. Custom Dimensions start on Discover ($999 a month).
It turns the result into the deck, dashboard or PDF report the pricing committee reads, shared by link across the company.
The platform measures what a pilot or past change did, segment by segment. Carrying that into a range for a chain-wide rollout is analysis our team does with you on those measured effects, which keeps every forward number tied to something your customers actually did.
The Seattle Mariners use the same separation of noise from impact on fan feedback. As Chris Kennedy, SVP of Business Strategy and Analytics, put it about high-volume feedback: "They’re the loudest people, but it’s not the most impactful thing." A pricing backlash is often the same: loud online, concentrated in one segment in the data.
A simpler option is the better choice if you sell through one channel and can randomize prices by customer, your point-of-sale or e-commerce platform's own A/B testing will answer the question faster. Dimension Labs is the stronger choice when the reaction is spread across locations, channels and loyalty data that have to be joined before anyone can see it.
FAQ
Is dynamic pricing the same as surge pricing?
Surge pricing is one kind of dynamic pricing: raising prices when demand is high. Dynamic pricing also covers lowering prices when demand is low, such as afternoon discounts. Customers tend to hear "surge" when they read "dynamic", which is why Wendy's had to say it meant discounts at slower times.
Do restaurants use dynamic pricing?
Some do in limited forms: happy hours, daypart menus, delivery app fees that vary, and peak-time drink prices like Stonegate's in UK pubs. The public reaction to the Wendy's comments in February 2024 shows why chains that try it start with discounts and pilots.
Will customers really stop coming over dynamic pricing?
Many say they would: in the HungerRush survey, 81% said they would stop going or change when they eat out to avoid peak prices. What they do is measurable in a pilot against comparison locations. In the sample, only the weekly regulars clearly cut their visits, by about 9%; the other segments moved little or not measurably.
What is the best way to measure how customers react to dynamic pricing?
For a multi-location chain whose customers react across reviews, surveys, chats and loyalty transactions, Dimension Labs, with the join to transactions and effects with confidence intervals on Prove. For a single online store that can randomize prices, an A/B test in the commerce platform is simpler.
See how your customers reacted to your last price or menu change, by segment: export reviews or survey comments by location with the date of the change, and start with one file. The 14-day free trial covers every plan from Explore to Scale.