Home
>
Blog
Blog
>
Article

Price elasticity by product, store, and cluster:
Why the same price doesn't work everywhere

Profile photo Fabrice Decroo

Fabrice Decroo

Director of Consulting

August 16, 2026

Price elasticity varies significantly from one store to another within the same chain. According to an NBER study, uniform pricing results in a 7 to 9 percent loss in profit compared to store-specific pricing.

The store cluster offers the best balance between analytical precision and operational manageability.

A single price elasticity per reference is a practical convenience, not an economic reality. The same product does not respond to price in the same way in a dense downtown area as it does in a suburban area facing three competitors. This guide explains why granularity—product, store, cluster —changes pricing decisions, and how to implement it without creating unmanageable complexity.

Setting a single national price per SKU is convenient: one number, one decision, one export to stores. However, in most multi-store chains, this is also an approximation that erodes profit margins—because customers’ actual price sensitivity varies greatly from one store to another, depending on local competition, the socioeconomic profile of the catchment area, and foot traffic levels.

A uniform price is not a beginner’s mistake: it is a widely used default option, chosen for reasons of operational simplicity and perceived consistency. The question is not whether it should be abandoned everywhere, but where it actually proves costly.

A landmark study by Stefano DellaVigna (UC Berkeley) and Matthew Gentzkow (Stanford), published in the Quarterly Journal of Economics and released by the NBER, analyzed the pricing behavior of major U.S. retail chains. The finding: most of them charge a virtually uniform price across their entire network, even though actual price elasticity varies significantly from one store to another within the same chain.

-2.28 → -2.98

This is the price elasticity gap measured between stores in the 10th and 90th percentiles within the same U.S. grocery chain—one network, two very different realities in terms of price sensitivity (DellaVigna & Gentzkow, Quarterly Journal of Economics / NBER).

The numerical implication is clear: according to the same study, charging a uniform price rather than a flexible, locally optimized price reduces the chain’s profit by 7 to 9 percent on average, compared to a scenario of store-specific pricing.

7–9%

lower profits for retailers that use a uniform price rather than store-specific pricing, according to estimates by DellaVigna & Gentzkow (NBER, Quarterly Journal of Economics).

A discrepancy of this magnitude, when applied to a network of several hundred or thousand stores, represents a margin point that no supplier negotiation can easily make up for.

  • The product. The elasticity of a product depends on its category, its positioning (KVI or long tail), and its role in the shopping basket—a loss leader does not have the same price sensitivity as a shelf-filler.
  • The store. The same product performs differently depending on the local competition within a few minutes’ walk, the neighborhood’s sociodemographic profile, and the store’s foot traffic.
  • The store cluster. Grouping stores with similar characteristics (competition, customer base, store format) allows for the application of a common price elasticity without having to manage different prices for each store—a trade-off between precision and manageability.

In practice, the cluster is the level most commonly used by mature retailers: granular enough to capture most of the variation, yet aggregated enough to remain manageable by a team of people—see also cross-elasticity, cannibalization, and the halo effect, the other dimension to cross-reference with store-level granularity.

1

Selecting clustering variables

Direct competition (number and type of stores in the vicinity), the area’s socioeconomic profile, and the store’s format and size—not just administrative boundaries.

2

Validate the clusters using actual sales data

Two stores that appear similar on paper may exhibit very different purchasing patterns once their sales histories are compared.

3

Limit the number of clusters

Segmenting into 4 to 8 clusters remains manageable for a pricing team. Beyond that, the operational complexity often outweighs the gain in accuracy.

4

Reevaluate periodically

The arrival of a competitor or changes in a neighborhood can cause a store to shift clusters—segmentation is never set in stone.

Segmentation isn't free. Here are three specific risks to consider before introducing multiple price tiers:

  • Unmanageable complexity. Having a different price for each store, without a tool to streamline the process, amounts to multiplying the amount of manual work—the opposite of the intended goal.
  • The inconsistency perceived by the customer. A shopper who compares two stores of the same chain on their phone does not always understand a price difference that seems unjustified to them, even if it is economically justified.
  • Signal dilution. Too many clusters, based on too little data per store, results in statistically unreliable elasticities—it is better to have a broad, robust cluster than a fine-grained, noisy segmentation.

A mature pricing analytics tool does not calculate a single elasticity per SKU: it provides a multi-level view, capable of drilling down from the national level to the cluster level, and even to the store level for the most strategic SKUs, while maintaining centralized governance over rules and limits. It is this structure—a consolidated view at the top, with granularity available at the bottom—that makes it possible to leverage variations in elasticity without losing overall control.

At Barbotteau Group, a multi-brand retail player in the French Caribbean, the pricing maturity journey documented with Booper illustrates this principle: price is treated as one decision-making factor among many, not as the sole lever—the approach combines local elasticity factors with operational research to transform forecasts into decisions, without a “black box” or a one-size-fits-all price imposed on market realities that vary significantly from one retail location to another.

Before segmenting your prices by store

  • Do I have enough sales data per store to estimate a reliable elasticity, or just a few weeks of historical data?
  • Are my clusters validated based on actual sales, or just on a geographical hunch?
  • Can I explain to a category manager why two stores have different prices?
  • Do I have a tool capableof automating this level of granularity, or does it rely on yet another file?

The questions we're asked most often before getting started.

This is rarely done in practice. Most established retailers use clusters of stores with comparable characteristics rather than setting prices on a store-by-store basis, to keep the system manageable.

A group of retail locations with comparable characteristics (local competition, customer profile, store format) to which a common price elasticity and common pricing rules are applied.

No. It remains relevant for certain categories that are not very location-sensitive, or when brand consistency takes precedence over marginal profit gains. The issue is identifying where it’s costly, not banning it everywhere.

There is no universal number, but beyond 8 to 10 clusters, the operational complexity often outweighs the gain in accuracy for most organizations.

By cross-referencing several variables (competition, socioeconomic profile, format) and then validating the groupings based on actual sales data, not just on self-reported criteria.

Sources: Stefano DellaVigna (UC Berkeley) & Matthew Gentzkow (Stanford), “Uniform Pricing in U.S. Retail Chains,” Quarterly Journal of Economics / NBER Working Paper No. 23996 — nber.org · Booper × Barbotteau Group webinar (case study published by Booper).

Articles
similar
Building a data-driven pricing team: the B2B model

Building a high-performing pricing team requires adopting a hybrid model that combines centralized strategy with local agility. This transition replaces intuition with data-driven decisions, guided by specialized roles and strict governance.

This proactive management directly improves financial performance, enabling companies to aim for an increase in profitability of between 100 and 500 basis points.

August 7, 2026
Read the article →
Read the blog post
Best pricing tool for retail in 2026

Facing a sudden drop in conversion rates because your competitors are adjusting their prices in real time means you need to equip yourself with the best data-driven retail pricing strategy tool for 2026 to stay competitive. Price transparency in 2026: Retailers are automating pricing to protect their margins against inflation, improve omnichannel responsiveness, and generate a quick ROI.

Discover how these tools automate your specific business rules while ensuring complete strategic control over your brand image and delivering a measurable return on investment in less than six months.

This detailed comparison analyzes specialized platforms capable of predicting price elasticity and managing your omnichannel inventory to turn every piece of raw data into immediate, tangible profit.

August 7, 2026
Read the article →
Read the blog post
How can you improve the accuracy of your product matching?

Product matching is the foundation of competitive monitoring because it prevents the comparison of non-equivalent products. Reliable matching safeguards margins by basing repricing on real-time, multi-source data.

Key finding: According to the Diamart study, 50% of French retailers still consider this challenge to be unresolved.

August 7, 2026
Read the article →
Read the blog post
Ready to
 boost
your margins?

The smart pricing solution for retail leaders. Accuracy, speed, and instant profitability.

Let's talk about your project