Concepts referenced in this article, defined.
Run rigorous A/B tests and personalize every visit on Shopify or any storefront — no engineers required.
Price A/B testing is the practice of showing different prices, discounts, or pricing displays to separate groups of shoppers simultaneously to determine which version generates more revenue. Done correctly, it is the most direct way to find the price point that maximises revenue per visitor — without guessing or relying on competitor benchmarks. This guide covers how to run price tests, what to measure, and real examples from Indian D2C brands.
Price A/B testing is a controlled experiment in which two or more price variants are shown to randomly assigned groups of website visitors at the same time. The goal is to identify which price (or price display) produces the highest revenue per visitor, not just the highest conversion rate.
This is an important distinction. A lower price almost always increases conversion rate. But if it reduces your gross margin per order, you may be converting more customers at a loss. RPV and gross margin per order are the correct north-star metrics for pricing experiments.
What price testing covers:
What price testing is not:
Most D2C founders set prices based on cost-plus calculation, competitor benchmarking, or intuition. All three methods leave money on the table because they do not account for actual customer price sensitivity on your specific audience.
The problem with intuition-based pricing:
The problem with competitor benchmarking:
Why RPV is the right metric: Consider two scenarios for a ₹500 product with 10,000 monthly PDP visitors:
| Price | CVR | Orders | Revenue | RPV |
|---|---|---|---|---|
| ₹500 | 3.5% | 350 | ₹1,75,000 | ₹17.50 |
| ₹599 | 3.0% | 300 | ₹1,79,700 | ₹17.97 |
The higher price generates more revenue despite fewer conversions. Price testing surfaces these non-obvious optima.
India-specific context: Indian D2C shoppers are value-conscious but not uniformly price-sensitive. Festive seasons (Diwali, Holi, wedding season) create natural windows for premium pricing. COD availability, free shipping thresholds, and BNPL options interact with price display in ways that require testing, not assumption.
Before building a test, answer:
Different objectives require different test designs and success metrics.
Display tests (lower risk): Change how the price is shown — e.g., "₹799 (was ₹1,065)" vs. "₹799 (25% off)" — without changing the actual transaction price. These tests are safe, fast to run, and often generate surprising lifts.
Absolute price tests (higher risk, higher reward): Show two different actual prices to two visitor segments. ₹799 vs. ₹849 vs. ₹899. These tests require careful segment isolation and short run times to minimise customer awareness risk.
Bundle pricing tests: Show "Buy 1 for ₹499" vs. "Buy 3 for ₹1,199 (₹400 saving)" to test AOV impact.
Using CustomFit.ai's visual editor:
Check the dashboard weekly, not daily. Early data is noisy. Calling a winner before reaching statistical significance is the leading cause of pricing test errors.
A price test does not end at "add to cart." Track:
Ship the winning variant permanently. Document the test in your experiment log with: hypothesis, test setup, results, RPV impact, revenue impact, and lessons learned.
₹999 vs. ₹1,000 — the "charm pricing" effect is well-documented in Western markets but worth verifying on your Indian audience. Some D2C brands find that round numbers (₹1,000) signal premium quality vs. "bargain" (₹999). Test your specific category and audience.
Show a higher "original" price struck through next to the current price. Test variables:
Price anchoring tests are display-only — no actual price change — making them low-risk with high upside.
Test different bundle configurations:
Changing the free shipping threshold is effectively a price test. "Free shipping on orders above ₹499" vs. "Free shipping on orders above ₹599" — test which threshold maximises RPV while maintaining acceptable AOV.
For products priced above ₹1,000, displaying "or ₹166/month (0% EMI)" can dramatically increase conversion rate by reducing perceived price. Test:
During sale events (Diwali, end-of-season):
1. Always measure RPV, not just conversion rate. A test that increases CVR but reduces revenue is a losing test. Set RPV as your primary success metric in every price experiment.
2. Run display tests before absolute price tests. Price framing and anchoring tests are lower risk, faster to complete, and often generate lifts as large as actual price changes. Start here before testing different price points.
3. Test during representative traffic periods. Avoid running price tests during major sale events (Diwali, Big Billion Days) when shopper behaviour is atypical. Test during normal trading periods to get results that generalise.
4. Keep absolute price tests short. Run absolute price point tests for 2–3 weeks maximum. The longer a higher-price variant runs, the higher the risk of price comparison by customers. Display tests can run for the standard 3–4 weeks.
5. Segment results by new vs. returning visitors. New visitors are often more price-sensitive (they have no prior brand loyalty). Returning customers may be less price-sensitive and respond better to premium anchoring. Analyse these segments separately.
6. Account for seasonality in your significance calculation. Week-on-week sales can vary 20–30% for Indian D2C brands due to payroll cycles, weekends, and micro-events. Ensure your test spans complete weeks and avoid tests that cross major calendar inflection points.
7. Never test more than two absolute price variants simultaneously on low-traffic PDPs. Multivariate price tests require 3–5x more traffic to reach significance. A/B (two variants) is the right format for most Indian D2C brands with moderate traffic volumes.
8. Document everything — including losses. A test that shows a higher price reduces RPV is valuable data. It tells you where your price ceiling is. Log all results, including inconclusive and losing tests.
9. Combine price tests with social proof updates. A higher price variant that is accompanied by more prominent social proof (review count, certifications) often outperforms a higher price alone. Run paired tests to understand the price × trust signal interaction.
10. Validate winners with a follow-up test before permanent rollout. A single winning test may have been a false positive. Run a confirmation test at 80/20 split (80% on the new winner) before making the price permanent.
| Platform | Price Test Support | No-Code Editor | RPV Tracking | Shopify Native | Starting Price |
|---|---|---|---|---|---|
| CustomFit.ai | Full (display + absolute) | Yes | Yes | Yes | $99/mo |
| VWO | Display tests primarily | Partial | Partial | Partial | $200+/mo |
| Optimizely | Full (enterprise) | No | Yes | No | $50,000+/yr |
| Convert | Full | Partial | Partial | Partial | $99+/mo |
| Shopify native | No A/B testing | N/A | Limited | Yes | Included |
See CustomFit.ai vs VWO for a detailed feature comparison. For enterprise options, see CustomFit.ai vs Optimizely.
Why CustomFit.ai for price testing:
Chargebee tested bundle vs. individual pricing across their subscription management add-ons. The bundle variant — offering three features as a "Complete Growth Bundle" at a 25% discount vs. purchasing individually — produced a 40% increase in average order value.
The key insight: customers perceive bundles as higher value even when the per-unit cost is lower. The anchoring effect (showing the total of individual prices vs. the bundle price) drove the lift.
Applicable to D2C: A skincare brand offering individual serums at ₹599 each could test a "Complete Routine Kit" at ₹1,499 (vs. ₹1,797 if bought individually). The bundle price increases AOV while appearing to offer savings.
Kapiva found that showing the MRP (₹999) alongside the selling price (₹749) with a "Save ₹250" callout outperformed showing only the selling price on their wellness supplements. The test produced a 9.48% CVR improvement — not from a price reduction, but from making the existing discount more visible.
Takeaway: Many Indian D2C brands are already offering discounts. The question is whether you are communicating them effectively. Price display tests are the lowest-risk, fastest-win category of pricing experiments.
Consider a hypothetical Indian D2C home care brand planning for Diwali:
Control: "₹799 per unit" Variant A: "₹799 (was ₹999) — 20% Diwali discount | Free gift wrapping above ₹1,500" Variant B: "₹799 per unit | Buy 3, get 20% off (most popular during Diwali)"
Variant B typically wins during festive periods because it increases AOV while tapping into the gifting occasion. The "most popular during Diwali" social proof cue also adds urgency and reduces decision paralysis.
Mistake 1: Testing only conversion rate, ignoring RPV. A ₹50 price reduction that increases CVR from 2.5% to 3.5% feels like a win — but if it reduces monthly revenue, it is a loss. Always track revenue, not just conversions.
Mistake 2: Running price tests during sale periods. Shoppers in sale mode behave differently. A price test that "wins" during Diwali may not hold during January. Always run confirmation tests during normal periods.
Mistake 3: Making price tests public. Do not announce that you are running a price test. Do not use price test data in marketing communications ("We found our customers prefer ₹799!"). Price tests are internal optimization tools.
Mistake 4: Ignoring the checkout impact. A price test that increases add-to-cart rate but increases checkout abandonment rate is not a winner. Monitor the full purchase funnel.
Mistake 5: Testing too many price points simultaneously. Testing four or five price points at once requires enormous traffic and extends test duration. Start with two variants (A/B), not multivariate price tests, especially on moderate-traffic PDPs.
Mistake 6: Not accounting for organic price sensitivity signals. Before running any price test, look at your data: do customers who apply discount codes convert at significantly higher rates? Do they have lower LTV? This tells you something about your existing price positioning before you test a change.
Not all visitors are equally price-sensitive. Segment your price test results by:
For brands with a product range, test a tiered pricing architecture:
The middle tier typically sees the biggest CVR boost when the "good" and "best" options are added as anchors. Test different configurations and price gaps.
Price testing is not limited to your website. Test:
These tests are often faster to run and analyse than website A/B tests because email flows have concentrated, measurable conversion events.
Price tests, product page tests, and checkout tests should not run in isolation. Build a quarterly CRO calendar that sequences:
Is price A/B testing legal? Yes, price A/B testing is legal in most markets including India, as long as you are not running discriminatory pricing based on protected characteristics. Showing different prices to different anonymous visitor segments for testing purposes is standard ecommerce practice.
What is the difference between price testing and dynamic pricing? Price A/B testing runs controlled experiments to find the optimal price point for all customers. Dynamic pricing changes prices in real time based on demand, competition, or customer segment — it is operational, not experimental.
Will price testing upset customers who paid more? The risk is low if you run tests on anonymous traffic segments. Most customers never compare notes. Set a short test duration (2–3 weeks max) and avoid testing prices on social-media-savvy product categories where customers actively share prices.
What should I measure when testing prices? Measure revenue per visitor (RPV) — not just conversion rate. A higher price may reduce conversion rate while increasing RPV and profit. AOV and gross margin per order are equally important metrics for price tests.
Can I test prices without a dedicated A/B testing tool? You can manually rotate prices on alternate weeks, but this introduces seasonal noise and makes it impossible to control for other variables. A proper A/B testing tool like CustomFit.ai runs simultaneous controlled splits, giving cleaner data.
How do I test prices on Shopify without a developer? CustomFit.ai's no-code visual editor lets you change displayed prices, add discount badges, or modify price framing on any Shopify page without touching your theme code.
What types of price tests generate the most revenue? Bundle pricing tests, price anchoring (showing a higher crossed-out price), and psychological pricing (₹999 vs. ₹1,000) consistently generate strong revenue lifts with minimal risk compared to testing absolute price changes.
Want to start testing your pricing without a developer? CustomFit.ai gives Shopify brands a no-code visual editor, RPV tracking, and AI-powered segmentation — first test live in under 30 minutes.