Testing Your Prices Without Losing Customers: The Method
The fear of testing a price change is almost always disproportionate to the actual risk: customers remember prices less precisely than we fear, and actual price elasticity is often lower than anticipated. A limited, reversible, and measured testing protocol (even with limited data) allows you to verify the effect of a price before rolling it out more widely.
This guide debunks that concern with data, then outlines a practical protocol for testing a price change without jeopardizing customer relationships—even when you don't have high traffic or a dedicated data team.
The fear that prevents any price change
The reasoning behind not testing a price can be summed up in a phrase heard in almost every organization: “If it goes wrong, we’ll see it right away—it’s better not to take the risk.” This statement contains both a truth and a fallacy.
The truth: A price change that is poorly received quickly shows up in sales figures—and sometimes in customer returns. The mistake: Never testing a price comes at an equally real cost, albeit an invisible one—the cost described in the first two articles of this series: the lost margin resulting from a price that has never been challenged, and the cost of a price that has remained fixed since its launch.
This asymmetry in perception (a visible risk versus an invisible cost) explains why so many companies prefer to do nothing, even though the available data show that fear is almost always exaggerated relative to the actual risk.
This fear is also fueled by a classic availability bias: the only example of a price test that sticks in people’s minds is almost always a resounding failure—a price increase that was poorly received, widely discussed, and has become a classic internal case study. Successful tests, on the other hand, leave no memorable trace: they blend into normal business operations, precisely because they did not provoke any notable reaction. This asymmetry in memory distorts the collective perception of risk far more than the actual data would justify.
What Customers Really Notice
The implicit assumption behind the fear of testing a price is that customers compare, remember, and penalize every price change. The reality, as documented by research, is much more nuanced.
This is, roughly speaking, the percentage of shoppers who can accurately recall the price of an item when they select it from the shelf—a figure that is significantly lower than one might imagine, with academic literature reporting widely varying results depending on the study (Journal of Retailing, Jensen & Grunert, “Price Knowledge During Grocery Shopping,” 2014).
This finding does not mean that price is unimportant—it is, and very much so. It means that accurately recalling a previous price—a necessary condition for a customer to “notice” a price increase in the strict sense—is much rarer than we assume internally, where every price is constantly scrutinized.
Given the decline in volume observed in 2021 following a 10% price increase—compared to the 23% decline expected before the COVID-19 pandemic for the same increase—customers’ actual price sensitivity is often lower than organizations fear, and it changes over time (NielsenIQ, Everyday Analytics, “Busting Pricing Myths,” 2021).
This discrepancy between the feared elasticity and the actual elasticity is precisely what a test allows us to measure, category by category, rather than assuming it once and for all.
These two findings reinforce each other. If a significant proportion of customers do not recall a price precisely, and if actual price sensitivity is often lower than feared, then the perceived risk of a well-conducted test is structurally overestimated—without, however, falling into the opposite extreme: certain categories remain genuinely price-sensitive, and only a rigorous test can determine which category a product falls into.
The Five-Step Testing Protocol
Choose a limited and reversible scope
A portion of the catalog, a geographic region, or a channel—but never the entire product line all at once. It must be possible to restore the scope to its original state without causing lasting damage.
Establish a clear hypothesis before you begin
“A X% increase in this benchmark will not cause the volume to drop by more than Y%”—a verifiable assumption, not just a “we’ll see.”
Cover the Entire Purchasing Cycle
A time frame that is too short captures a novelty or seasonality effect rather than the market's actual reaction—the most common pitfall of poorly designed tests.
Isolate the interfering factors
A competing promotion or an external event during the test period may skew the results; these should be identified and documented before drawing any conclusions.
Decide Before Generalizing
Compare the result with the initial hypothesis, and explicitly decide whether to generalize, adjust, or abandon it; never let the test peter out without reaching a formal conclusion.
Test with a small amount of data or traffic
The most common objection to price testing comes from companies that believe they lack the volume needed for a statistically reliable test—such as a single store, a limited catalog, or low traffic. This reasoning isn’t entirely wrong: a traditional A/B test, in which two groups are compared simultaneously, does indeed lose statistical power when volumes are low.
But the lack of large volumes doesn't mean we can't test; it just requires us to adapt our approach:
- The sequential test compares a period before and a period after a price change within the same population, rather than two simultaneous groups; this is useful when it is not possible to isolate two comparable segments in parallel.
- A price sensitivity survey directly asks a sample of customers about their perception of a price before any actual change is made—a method that requires only a small sales volume to be useful.
- The deferred reference test adjusts the price of a handful of representative products rather than an entire category, to limit exposure while maintaining a usable signal.
In any case, the rule remains the same: an imperfect test conducted methodically is better than no test at all—the same rule already stated in the article on price as a dynamic variable in this issue.
In fact, a lack of traffic isn't always the obstacle one might imagine. A company with few SKUs but a clean sales history can often learn more from a well-conducted sequential test than a large retailer with thousands of SKUs but data scattered across several unconnected systems. Volume helps, but the quality of the method matters more than the sample size.
What to Measure After a Test
| Indicator | What it reveals | A Common Pitfall |
|---|---|---|
| Volume | The Direct Effect of Price on Demand | Confusing a decline in sales volume with a loss of customers (a customer may simply be buying less often) |
| Net Margin | If the price gain offsets the loss in volume | Focusing solely on revenue, which may rise even as margins fall |
| Redemption | Whether the effect is temporary or long-lasting | Drawing conclusions too soon, before observing a second purchasing cycle |
| Qualitative signal | Complaints, Feedback, and Returns from Customer Service | Overweight a few noisy returns at the expense of the overall quantitative signal |
This table is sufficient for evaluating a single test. To go further—to accurately calculate a price elasticity coefficient, choose among various measurement methods (before/after, A/B testing, modeling), and avoid statistical biases (discontinuities, mixed promotions, seasonality)—Booper has published a dedicated guide: How to Measure Price Elasticity? Method. This guide deliberately focuses on the early stages—the decision to conduct a test and the minimum protocol—while the other guide covers the calculations and statistical rigor.
GENIUS Predict: Simulate Before Testing Under Real-World Conditions
The GENIUS Predict module projects the impact of a price change based on three scenarios— Conservative, Balanced, and Aggressive—even before launching a field test. Each simulation measures the expected effect on sales AND inventory, not just on margin, to reduce the uncertainty that fuels the fear described above.
An "AI Explanation" section details the factors that influenced the prediction, so that testing decisions are based on explicit reasoning rather than intuition alone. Discover the platform on our MPS page , the Booper Modular Pricing Solution .
Errors That Skew a Price Test
- Testing the entire range all at once. This eliminates the possibility of comparison and turns the test into a blanket guess—exactly what a test is supposed to avoid.
- Stopping the test too early. An immediate reaction is not always a lasting one; drawing conclusions before the end of the purchasing cycle almost always skews the result.
- Ignore external factors. A competing promotion during the test period may cause the price to be attributed an effect that is not its own.
- Never make a decision. A test whose results do not lead to any decision—whether to generalize, abandon, or adjust—serves no purpose other than to postpone the issue yet again.
A Checklist Before Launching a Price Test
- Is the scope of the test limited and reversible, or does it affect the entire range all at once?
- Was a clear hypothesis established before beginning?
- Does the duration cover an entire purchasing cycle?
- Are external factors (competitor promotions, seasonality) identified in advance?
- Will a decision be made and documented at the end of the test, regardless of the result?
Want to test a price change without any stress?
Spend 30 minutes with our team to develop an initial testing protocol tailored to your catalog and your volume.
FAQ
Because the impact of a poorly received price change is immediately apparent (a drop in sales is evident right away), whereas the cost of never testing—the profit margin lost year after year—remains invisible. This asymmetry in perception leads people to favor the status quo, which is mistakenly perceived as the risk-free option.
Less than is generally feared. Academic studies show that only about one in two shoppers is able to accurately recall the price of an item at the moment they select it. A moderate and consistent price increase very often goes unnoticed by the customer’s conscious mind.
By testing on a limited scale (a portion of the catalog, a geographic area, or a channel) before any full-scale rollout, by measuring the actual impact on sales volumes over a defined period, and by retaining the option to revert to the previous setup if the results are negative.
Yes, provided the method is adapted: with a small sample size, a traditional A/B test lacks statistical power. Alternatives exist, such as price sensitivity surveys conducted directly with customers, or sequential tests over longer periods rather than simultaneous groups.
Raising a price across the entire product line without prior data is like betting the entire business on a single move. Testing involves verifying the effect within a limited and reversible scope before rolling it out across the board.
It depends on the purchase cycle of the product in question, but setting the time frame too short is the most common pitfall: you need to cover at least one full purchase cycle, and ideally account for the effects of seasonality or competing promotions that could skew the results.
See also in this feature
- Why Do So Few Companies Really Manage Their Prices?
- The price isn't set in stone: why it's a dynamic variable
Sources: NielsenIQ, Everyday Analytics, “Busting Pricing Myths,” 2021 · Journal of Retailing, Jensen & Grunert, “Price Knowledge During Grocery Shopping: What We Learn and What We Forget,” 2014
A franchisor cannot impose a resale price: the law prohibits it from doing so; it can only recommend a price or set a maximum. A franchisee’s margin is therefore governed by a documented target, defined by network segment rather than on a store-by-store basis, and applied uniformly to all retail locations within the same segment. Three tiers are usually sufficient: aggressive pricing online, geopricing in-store, and an optimized margin for the franchisee.
Optimix merged with Maxxing in July 2025, and PricingHUB was acquired by Akeneo in June 2026. In less than a year, two of the three software providers most frequently used by French retailers underwent changes in ownership, raising the question of alternatives for their customers.
This comparison evaluates Optimix XPA, PricingHUB, Mercio, Yieldigo, and BOOPER based on what truly sets a pricing solution apart in France: native support for French regulations, pricing by store or by zone, the approval process before a price changes at the register, and roadmap independence.
A manufacturer that raises its list price does not set the price on the shelf. Between the negotiated list price and the displayed price lie the retailer, its markup, and its promotions. What is measured is the price elasticity of each product, retailer by retailer.