A/B testing for pricing means showing different price points, tiers, or page layouts to separate groups of visitors. Then you measure which version earns more revenue. It’s one of the highest-impact tests you can run. Also one of the riskiest if you do it wrong.
Don’t start by testing different dollar amounts on different people. Start by testing how your pricing page presents the options you already have. Safer, faster, and (surprisingly) often more effective.
This guide covers why pricing is your biggest growth lever, what’s actually worth testing, and how to avoid the ethical landmines that tripped up Amazon, Instacart, and Sony.
Why pricing is the growth lever nobody pulls
Most businesses set their price once and never touch it again. That’s a problem, because pricing has a bigger impact on profit than almost anything else you could change.
McKinsey analyzed S&P 1500 companies and found something wild. A 1% price increase generates an 8% increase in operating profit. That’s 3x the impact of selling more units. ProfitWell’s research puts it even higher for SaaS: pricing improvements have nearly 8x the impact of acquisition improvements on your bottom line.
In plain terms: if your SaaS makes $50K/month in profit, a small pricing tweak could mean $4K more per month. That’s $48K per year from a change you can test in weeks.
And yet 52% of SaaS companies don’t test their pricing at all. Only 6% have done any real pricing research. Patrick Campbell (ProfitWell founder, now at Paddle) found that the average company spends fewer than 10 hours per year on pricing.
Ten hours. On the single biggest profit lever in the business.
Our take: You probably spent more time picking your website font than setting your price. That’s not a criticism. It’s an opportunity.
Companies that review pricing quarterly see 21% higher revenue growth. The gap between “how much pricing matters” and “how little attention it gets” is enormous. That’s exactly where A/B testing affects conversion rates the most.
What you can actually A/B test on a pricing page
When most people hear “pricing A/B test,” they imagine showing $29 to Group A and $39 to Group B. That’s one approach. But it’s the riskiest one, and often not even the most effective.
Here’s what’s worth testing first, roughly in order of impact and safety:
Tier highlighting and decoy pricing. Slap a “Most Popular” badge on your target plan. Research from Mida.so found it pushes mid-tier adoption from 40-50% up to 55-65%.
Dan Ariely’s Economist experiment shows why decoys work. Three options: web-only at $59, print-only at $125, print+web at $125. Nobody picked print-only. But with it present, 84% chose the expensive bundle versus 32% without. A 163% jump in revenue per subscriber. The price didn’t change at all.
Annual vs. monthly default. Which billing option shows first matters more than you’d expect. Defaulting to annual can boost annual plan adoption by 25-35%. And annual subscribers churn at 5-10% per year versus 30-50% for monthly. One toggle, completely different retention curve.
Then there’s price framing. “$4.99/day” feels different from “$149/month” even though the math is close. Pricing page changes produce 8-15% lifts where the same changes on landing pages produce 2-3%.
Price anchoring works on the same principle. Show the premium tier first and your target plan feels like a deal. ConversionXL found premium tiers increase mid-tier selection by about 40%.
Feature bundling is underrated. Which features go in which tier shapes how people perceive value. Often moves the needle more than changing the number on the price tag.
Don’t forget social proof on the pricing page. Testimonials and customer counts increase conversion by 15-25%. Most businesses put social proof on their homepage but skip the page where people actually pull out their credit card.
And risk reversal (free trial length, guarantees, “cancel anytime” language) is free to test. Opt-out free trials convert at 48.8% versus 18.2% for opt-in. A 2.7x difference from a change that doesn’t touch the price.
All of these avoid the ethical mess of showing different prices for the same product to different people. They work with less traffic and shorter timelines too. If you want to test this on your own pricing page, start here.
Our take: Test the price tag last. Test everything around it first. You’ll probably find that how you frame the price matters more than what the price actually is.
How to run a pricing A/B test (step by step)
Pricing A/B testing follows the same basic mechanics as any split test, but with a few important differences. Here’s the process:
Step 1: Research before you test. Don’t pick random price points. Start with the Van Westendorp Price Sensitivity Meter. It’s a short survey with four questions that maps your customers’ acceptable price range.
You’re looking for the boundaries: too cheap, acceptable, expensive-but-okay, too expensive. Then A/B test within that range. For packaging decisions, conjoint analysis (how buyers weigh price against features) is useful when designing a marketing experiment around tier structure.
Step 2: Pick your primary metric. This is where most pricing tests go wrong. Your primary metric should be revenue per visitor, not conversion rate alone.
A lower price might convert more people but earn less total revenue. Track both, but let revenue per visitor decide the winner.
Step 3: Calculate your sample size. Pricing tests need more visitors than a button-color test. The effect sizes are often smaller. Use a sample size calculator before you start.
If it says you need 20,000 visitors per version and you get 500 per week, that’s a 40-week test. Better to know upfront. Kirro uses math that works with less traffic (Bayesian statistics), which helps when you can’t wait months.
Step 4: Segment properly. Randomly assign visitors to groups. Never segment by demographics or behavior for a pricing test. And only test on new visitors. If someone comes back and sees a different price, you’ve created a trust problem.
Step 5: Run for at least two weeks. Pricing sensitivity shifts by day of week and time of month, especially around pay cycles. Two weeks is the minimum. For subscription products, Statsig recommends at least two full billing cycles. That’s 60 days for monthly plans.
Step 6: Watch secondary metrics. Conversion rate is the obvious one. But also track churn rate, lifetime value, support tickets, and other A/B testing metrics that show downstream effects. A price that converts well but attracts bargain-hunters who churn in 30 days? Not a win.
Step 7: Iterate. Harvard Business Review analyzed 1,117 pricing tests across 300+ retailers. Single test success rate: 72%. After three or more tests: 96%. Each test builds on what you learned from the last.
The ethics and legality of pricing A/B tests
Split testing for pricing is legal in most places. The price differences just can’t be based on race, gender, nationality, or other protected characteristics. But “legal” and “smart” aren’t the same thing.
Three cautionary tales:
Amazon, 2000. Amazon showed different DVD prices to different customers based on browsing history. A customer deleted their cookies and watched the price drop from $26.24 to $22.74. Backlash was instant. Amazon refunded 6,896 customers (averaging $3.10 each). Jeff Bezos publicly apologized. More than 25 years later, Amazon still won’t do personalized pricing.
Instacart, 2025. Instacart used an AI tool called Eversight to test prices for Albertsons, Kroger, and Safeway. Consumer Reports found basket prices varied by an average of 7%. Individual items? Up to 23%. The same Lucerne eggs showed up at five different prices ($3.99 to $4.79). The FTC stepped in. Instacart settled for $60 million in refunds and killed all AI price testing immediately.
PlayStation Store, 2025. Sony ran personalized discounts on 150+ games across 68 territories. Frequent buyers got worse deals than less active accounts. The backlash was bad enough that Sony excluded the US and Japan entirely.
Same story every time. People have a strong gut sense of price fairness. Nobel laureate Daniel Kahneman’s research found that 82% of people consider opportunistic price increases unfair. That reaction doesn’t care whether your test was technically legal.
Regulators are watching too. In January 2025, the FTC ordered eight firms (Mastercard, McKinsey, Accenture among them) to hand over documents about “surveillance pricing” tools. They called out “rapid A/B price testing… largely invisible to consumers.”
The EU’s Omnibus Directive goes further. Traders must disclose when prices are personalized using automated profiling.
The safe path: test price presentation (tiers, framing, anchoring, defaults). Not identical-product pricing.
If you do test different price points, only show them to new visitors who’ve never seen a previous price. Never run pricing tests on existing customers without telling them. Same logic behind A/B testing best practices for any test: keep the experience consistent for each person.
What to measure (and what most businesses get wrong)
Every competitor article says “measure revenue, not conversion.” They’re right. But none explain what to do when those two metrics disagree. And they will.
Say you drop your price 20%. Conversion goes up 15%. Looks like a win.
But revenue per visitor actually dropped. The price cut more than offset the conversion gain.
Worse, the cheaper price attracted bargain-hunters who churned within 60 days. Watch only conversion rate and you’d call this a winner. You’d permanently lower your revenue.
The HBR study of 1,117 pricing tests found some surprising numbers: 59% of winning prices were lower than the original. But 41% were higher or the same. Don’t assume lower is always better.
What to actually track in a pricing A/B test:
- Revenue per visitor (primary metric): total revenue divided by total visitors in each group. This accounts for both conversion rate and average order value.
- Average revenue per user (ARPU): what each paying customer contributes. Higher ARPU can offset a lower conversion rate.
- Churn rate: especially for subscriptions. The wrong price attracts wrong-fit customers. Check this at 30, 60, and 90 days if you can.
- Customer lifetime value (LTV): the gold standard, but it takes months to measure. Use 30-day engagement as a proxy.
The minimum detectable effect for your test matters here too. Pricing page changes produce bigger swings than typical landing page tweaks (8-15% lifts versus 2-3%). Good news for sample size. You still need enough traffic to detect the effect you’re after.
If you’re testing on your own site, set up conversion tracking that captures revenue events, not just clicks. “Clicked the buy button” and “actually paid” are two very different things.
Alternatives to direct price A/B testing
You don’t always need a live A/B test to make better pricing decisions. Sometimes a survey gets you there faster, cheaper, and without ethical risk.
| Method | Best for | Effort | Ethical risk | What you need |
|---|---|---|---|---|
| Van Westendorp | Finding the viable price range | Low | None | 150-400 survey responses |
| Gabor-Granger | Testing specific price points | Low | None | 100+ survey responses |
| Customer interviews | Understanding value perception | Medium | None | 15-20 conversations |
| Geographic testing | Market-specific pricing | Medium | Low | Traffic in multiple markets |
| Time-based testing | Avoiding simultaneous pricing | Medium | Low | Enough traffic for 2-week windows |
| A/B testing (presentation) | Pricing page layout and framing | Medium | Low | 1,000+ visitors per version |
| A/B testing (direct price) | Final price point validation | High | High | 5,000+ visitors per version |
Van Westendorp is the fastest starting point. Four questions: “At what price is this too expensive? Expensive but worth it? A good deal? So cheap you’d question the quality?” Plot the answers and the intersections show your viable range. Takes a day to run.
Gabor-Granger is even simpler. Show a price, ask “would you buy at this price?”, adjust up or down. You get a demand curve showing what percentage would buy at each price point.
For qualitative insight, talk to 15-20 customers about value, not price. Ask what outcome they’re after, what alternatives they’ve considered, and what would make the product worth twice as much.
Geographic testing means different prices in different markets. Avoids the fairness problem entirely.
Time-based testing runs Price A for two weeks, then Price B for two weeks. Less reliable because external factors change, but Amazon uses an advanced version called switchback experiments that cuts measurement error by about 60%.
The smartest workflow stacks these. Van Westendorp finds the range. Gabor-Granger maps the demand curve. Then Bayesian A/B testing validates the specific price point within a range you already know works.
Common pricing test mistakes (and how to avoid them)
Pricing tests are different from testing multiple things at once on a landing page. The stakes are higher. The traps are sneakier.
Measuring conversion instead of revenue. Worth repeating because almost everyone does it. A 20% price drop that lifts conversion by 10% is losing you money. Revenue per visitor is what matters.
Testing price before testing presentation. The right sequence: presentation (tiers, framing, badges) first, packaging (what’s in each plan) second, price points last. Jumping straight to dollar amounts skips the steps with the biggest impact and least risk. Same logic behind avoiding common A/B testing mistakes in general.
Running tests too short is another classic. Two weeks minimum for pricing. Buying behavior shifts around paydays and end of month. For SaaS with monthly billing, two full billing cycles (60 days) is safer.
Then there’s the question nobody thinks about until it’s too late: what happens after the test? What do you do with customers who paid the higher price? Grandfather them, offer a credit, or move everyone to the winning price. Decide before you start.
Stanford researchers found that standard A/B pricing estimators can point you in the wrong direction due to interference effects. Post-test analysis matters as much as the test itself.
Not enough traffic. A pricing test on a page with 200 visitors/month will take a year. If that’s you, use survey methods instead. Kirro’s approach to experimentation works with smaller samples, but even Bayesian methods have limits.
And don’t forget existing customers. Never include them in a price test without a plan. If someone paying $49/month sees $39/month on your site, you’ve given them a reason to ask for a discount. Or worse, feel cheated.
FAQ
Is it illegal to A/B test pricing?
Generally, no. A/B testing pricing is legal in most countries as long as price differences aren’t based on protected characteristics (race, gender, nationality). Random assignment to test groups is fine.
That said, regulators are getting more active. The FTC launched a surveillance pricing investigation in 2024. The EU requires disclosure when prices are personalized.
Safest approach: test pricing page presentation (layouts, badges, framing) rather than showing different prices for the same product. If you test different price points, only show them to new visitors.
How long should a pricing A/B test run?
Two full weeks minimum. That accounts for day-of-week variation and pay cycles.
For subscription products, Statsig recommends two full billing cycles (60 days for monthly plans). The HBR dataset of 1,117 tests averaged three weeks, but that was mostly ecommerce. SaaS takes longer because you need to see churn effects.
What if customers find out they’re paying different prices?
This is the biggest risk. Amazon, Instacart, and PlayStation all learned the hard way: public backlash, regulatory action, lasting trust damage.
Test presentation elements (tiers, framing, anchoring) instead of dollar amounts. If you must test prices directly, only test on new visitors. Keep the gap small (10-15%, not 50%).
Can you A/B test pricing on Shopify?
Yes. Intelligems is built specifically for Shopify price testing. They’ve processed over $500 million in tested GMV across 100+ brands. For testing pricing page presentation (layouts, badges, copy) on any platform, Kirro handles that without platform-specific integrations.
What do you do with customers who paid the higher price after the test?
Three options. Grandfather them at their current price (simplest, builds trust). Offer a prorated credit (fair but operationally messy). Or move everyone to the winning price going forward (cleanest long-term). Most companies grandfather existing customers and use the new price for new signups. Decide before you launch, not after.
What’s the difference between A/B testing pricing and dynamic pricing?
A/B testing splits visitors into groups, shows each group a different price, and finds which one performs better. The goal: one optimal price.
Dynamic pricing changes prices in real time based on demand, inventory, or customer data. Different thing entirely. A/B testing is a research tool. Dynamic pricing is an ongoing strategy. Some businesses use A/B testing to calibrate their dynamic pricing rules, but they’re separate concepts. More on the distinction in our A/B testing vs. split testing guide.
Randy Wattilete
CRO expert and founder with nearly a decade running conversion experiments for companies from early-stage startups to global brands. Built programs for Nestlé, felyx, and Storytel. Founder of Kirro (A/B testing).
View all author posts