Home
>
Blog
Blog
>
Article

Data in the Service of
price elasticity.

Edouard Calliati

CMO - CRO

June 18, 2026

Price elasticity measures how much your demand changes when your prices change. Calculated using your actual data (sales, net price, promotions), it tells you where you can raise prices, where you need to lower them, and where a promotion will really work. The real challenge isn't the calculation—it's preparing the data.

Summary of the article:

Poor elasticity means a pricing decision worth €50,000 or €500,000 goes down the drain. And the problem rarely lies with the formula. It stems from hidden biases in the data: undetected stockouts, promotions mixed in with regular prices, ignored seasonality, and cannibalization between SKUs.

To turn your sales history into sound pricing decisions, you need to know how to calculate price elasticity accurately. Here, we’ll walk you through an 8-step method, the minimum columns you’ll need, three examples with actual numbers, and the most common pitfalls.

Reminder: What Is Price Elasticity (and What Is It Used For)?

Before we get into the method, let's lay the groundwork. Elasticity isn't just a concept from an economics textbook. It's a business metric that your pricing and catalog management teams can use every week.

Definition in 2 lines

Price elasticity measures how sensitive demand is to a change in price. In practical terms: if you raise your price by 5% and your sales fall by 10%, your price elasticity is -2.

It is almost always a negative number. The larger its absolute value, the more price-sensitive the product is. A coefficient of -3 indicates a highly price-sensitive product. A coefficient of -0.5 indicates a product that can be adjusted without significant negative impact.

The calculation is simple. The challenge lies elsewhere: isolating the effect of price from data that also includes seasonality, promotions, stockouts, and competition.

Use Cases: Margin, KPI, Promotion, Markdown

Elasticity serves four specific purposes.

  • Identify the products where you can increase your margin without losing sales volume (low elasticity).
  • Protect your KVI where a rise will break the price pattern (high elasticity + high visibility).
  • Tailor the scope of a promotion so that it generates incremental sales, not just a discount window.
  • Deciding on an end-of-season markdown: At what discount level will the inventory actually sell out?

Without quantified flexibility, these four decisions are based on intuition. With it, they become traceable and defensible in the face of financial pressures.

The data needed to calculate a reliable elasticity

Elasticity cannot be calculated using a rough Excel file. You need precise columns, with the correct grid size and the correct historical depth. This is where 80% of projects fail.

Required columns (date, SKU, quantities, net price, promotion, inventory, channel)

To calculate data elasticity correctly, your source file must contain at least the following:

  • date (day or week, depending on your level of management granularity),
  • SKU or unique product identifier (EAN, if available),
  • quantities sold (in units, not in revenue),
  • listed price AND net price (after immediate discounts),
  • promotion flag (yes/no) + promotion depth (in %),
  • inventory or availability (to detect stockouts),
  • channel (store, website, marketplace) and, if possible, store or area.

Optional but very useful: competitor prices (price index), purchase cost, target margin, and calendar of events (holidays, sales, promotional campaigns). A model with 18 to 24 months of its own historical data yields reliable results. With less than 12 months of data, you risk modeling noise rather than the signal.

List Price vs. Net Price: Calculating the "Effective Price"

This is the number one mistake in inventory calculations. The price displayed on the shelf or on the product label is not the price the customer paid.

Between the price tag and the checkout, there are often: immediate discounts, coupons, loyalty programs, bundle deals, promo codes, and cashback. The actual price is what appears on the receipt after all these discounts and promotions have been applied.

A product listed at €19.99 with a 20% discount at checkout has an actual price of €15.99. If you calculate the price elasticity based on €19.99, you’ll get an inaccurate result. If you calculate it based on €15.99, you’ll get the true market response.

Why Inventory/Shortages and Promotions Skew Everything

Two factors consistently cause elasticity calculations to fail if they are not handled properly.

Out-of-stock situations: If a product is out of stock for 5 days, its sales drop to zero. But that zero isn't due to the price; it's due to the product's unavailability. Including it in the calculation yields a false elasticity.

Promotions: A promotion creates a sales spike that far exceeds what standard price elasticity would predict. If you mix promotional and non-promotional periods, you end up with a vague average that isn't helpful at all.

The solution: Address these two cases before performing the calculation. Exclude days when the product is out of stock, and calculate two elasticities separately: one for regular prices and one for promotional prices.

Step-by-Step Guide: Calculating Price Elasticity Using Data (8 Steps)

Here is the operational method you can apply this week to a pilot category. Each step is necessary. If you skip one, you’ll introduce noise into the results.

1) Select a scope (category + products)

Start small. Don't run a calculation on 20,000 SKUs all at once. Choose a pilot category and 20 to 100 SKUs from it.

Ideally: a category with sufficient volume (otherwise price fluctuations will be lost in the noise), a clean historical data set covering at least 12 to 24 months, and several genuine past price movements (without price changes, as this would preclude the possibility of elasticity).

Once the method has been validated within this scope, we'll expand it. Not before.

2) Clean (outliers, errors)

No sales file is perfect. There are always odd entries: prices entered in cents instead of euros, negative quantities, and large sales linked to a B2B account that wasn't properly flagged.

Before performing any calculations, we filter out these outliers. A simple rule: exclude sales that exceed 4 or 5 standard deviations from the mean. Then, manually review the top 20 outliers to understand them.

It's less glamorous than AI models, but that's what separates reliable elasticity from a shot in the dark.

3) Handle out-of-stock items (exclude or correct)

A stockout is sure to distort price elasticity. The product isn't sold not because it's expensive, but because it's not available.

Two approaches:

  • Exclude break days from the calculation (the simplest method, recommended as a first step).
  • Adjust sales figures using a latent demand model (an advanced technique, useful if you have frequent stockouts and are losing too much data).

The process of elimination works in 90% of cases. If more than 30% of your order history is affected by stockouts, that means there’s a supply chain issue to address before you even start talking about pricing.

4) Distinguish between regular price and promotional price (2 elasticities)

The regular price and the promotional price do not have the same price elasticity. The promotional price is almost always higher in absolute terms.

A product with a regular price discount of -1.5 may have a promotional discount of -3 or -4. Why? Because during a promotion, you attract customers who wouldn't have bought the product at the regular price, and some of them stock up for later.

Calculate them separately. You'll end up with two different decisions: one for day-to-day pricing and one for the promotional strategy.

5) Create comparable periods (season/calendar)

Comparing December sales to February sales without adjusting for seasonal factors is guaranteed to produce misleading figures.

For each price comparison, choose two equivalent periods: the same number of days, the same days of the week if possible, excluding exceptional events (sales, holidays, national campaigns).

To get a strong seasonal benchmark, it is sometimes more effective to compare the same week from one year to the next than to compare two consecutive weeks.

6) Calculate %Δ price and %Δ quantity

Now that we have two comparable periods, we calculate the two percentage changes.

Price change = (price in period 2 − price in period 1) / price in period 1.

Quantity change = (quantity in period 2 − quantity in period 1) / quantity in period 1.

Example: Price increases from 10 € to 11 € → +10%. Quantity decreases from 100 units to 85 → -15%.

7) Calculate E = %ΔQ / %ΔP and interpret the result

Elasticity is the change in quantity divided by the change in price.

Using the previous example: E = -15% / +10% = -1.5. The elasticity for this product is -1.5.

How to interpret this number:

  • Between 0 and -1: low elasticity. You can raise the price with a limited impact on sales volume.
  • Between -1 and -2: medium elasticity. Limited flexibility; handle with care.
  • Greater than -2: high elasticity. Any price increase is offset by a corresponding drop in volume, sometimes more than proportionally.

Note: A single calculation does not provide a reliable measure of elasticity. Several comparisons are needed to confirm the value. Averaging over 6 to 12 price movements yields a usable figure.

8) Validate by segment (KVI, channel, store) + safeguards

An average price elasticity across the entire retail network often masks huge variations by channel or by store. A product may be price-elastic online but very price-inelastic in physical stores.

Review your results by segment:

  • by channel (web, store, marketplace): consumer behavior is never the same,
  • by store or geographic cluster: local competition is a game-changer,
  • by product status (KVI vs. non-KVI): KVI products exhibit greater price elasticity.

Also, put safeguards in place before making elasticity an automatic rule: a minimum margin, a maximum deviation per cycle, and human approval for the most sensitive decisions. Elasticity is a guideline—not a direct command to the pricing engine.

Examples with figures (3 mini-cases)

The theory becomes clear when it is applied. Here are three real-world examples to illustrate how an elasticity calculation is applied in pricing decisions.

Case 1: Regular Price Increase

A home improvement retailer is testing a price increase on a mid-range hammer drill. Previous price: 89 €. New price: 94 €. Price increase of +5.6%.

Over the next 8 weeks, average weekly sales: 142 units vs. 165 before the increase. A decrease of -13.9%.

Elasticity = -13.9 / +5.6 = -2.5. Moderate to high elasticity.

Conclusion: The price increase results in a greater loss in volume than the gain in unit margin. The total margin declines by 4%. Decision: Return to €89 and test a more moderate increase (+2.5%) in the following quarter.

Case 2: Regular Price Reduction

An online clothing retailer has lowered the price of a shirt from €49.90 to €44.90. That's a 10% discount.

Over a 4-week period, average weekly sales: 380 units vs. 280 before the decline. An increase of +35.7%.

Elasticity = +35.7 / -10 = -3.57. High elasticity.

Conclusion: The price reduction is generating a significant increase in volume. Although the unit margin is declining, the increase in volume more than offsets this. Total margin is up 18%. Decision: Approve the new regular price and extend it to four other similar products.

Case 3: Promotion (uplift + cannibalization)

A food retailer is launching a 25% off promotion on its private-label orange juice. Regular price: €2.40. Promotional price: €1.80.

During the two-week promotion: private-label sales increased 3.2-fold (a 220%uplift ). Promotional elasticity = +220 / -25 = -8.8. Very strong—this is typical during promotions.

But watch out for the catch: during that same period, sales of the equivalent national brand juice dropped by 38%. That’s cannibalization. Customers who would have bought the national brand switched to the store brand that was on sale.

Decision: Include cannibalization in the calculation of the promotion’s ROI. The net gain from the promotion, after deducting cannibalization and the cost of the discount, is a +9% increase in category margin. This is positive but far from the +60% one might have expected based solely on the uplift in private-label sales.

Table: data → role → error if data is missing

To make sure you don't overlook anything important before running an elasticity calculation, here is a list of the critical data and what happens if they are missing from your file.

Data Role in the calculation Error if missing
Date (day/week) Break down the historical data into comparable periods It is impossible to account for seasonality
SKU / Product ID Unambiguously identify each reference Mixing different products, incorrect calculation
Quantities sold (units) Measuring the volume response No calculation possible
List Price Reference for the advertised price The starting point is missing
Net price (after discounts) Actual price paid by the customer Elasticity calculated based on a fictitious price, resulting in an absurd outcome
Promotion Indicator + Depth Distinguish between regular and promotional discounts A mix of the two systems, vague averages
Inventory / Availability Exclude out-of-stock periods Zero sales confused with price sensitivity
Channel (store/website/marketplace) Segment by purchasing context An overall average that masks contrasting behaviors
Store / area Understanding Local Competition Location effect masked by the average
Competitor's price (optional) Monitor the market effect Price flexibility attributed to your company, even though it actually comes from a competitor

Common Biases (and How to Correct Them)

There are five pitfalls that consistently crop up in elasticity calculations. Knowing them in advance can save you weeks of debugging.

Bias Symptom in the data Correction
Out of stock Abnormal elasticity (-8 to -10) for non-commercial reasons Exclude days with zero inventory before calculation
Actual price not taken into account Unstable elasticity from one period to the next Recalculate the price paid after discounts and coupons
Cannibalization Among Substitutes Positive elasticity or an illogical result Incorporating the prices of substitute products (cross-elasticity)
Uncontrolled seasonality Elasticity varies by month or season Compare equivalent periods or add calendar variables
False competitor match Pricing decisions that don't work in production Improving the reliability of product matching based on EANs or structured attributes

Out of Stock & Availability

Symptom: A reference shows an absurdly high elasticity value, such as -8 or -10, even though there is no reason for it.

Probable cause: The product was out of stock during the period analyzed. The zero sales figures resulting from the product's unavailability were interpreted as a reaction to the price.

Correction: Systematically cross-reference sales with inventory data and exclude days when store or online inventory was zero.

Promotion/coupon/bundle (actual price)

Symptom: A product's elasticity varies significantly from one period to the next, with no identifiable business-related cause.

Probable cause: You're basing your calculation on the listed price without factoring in loyalty coupons, immediate checkout discounts, or bundles that changed the actual price paid.

Correction: Reconstruct the actual price using point-of-sale data or the coupon database, and recalculate. The figure will then stabilize.

Cannibalization & substitution

Symptom: A product appears to exhibit strong, positive elasticity (sales fall when the price falls), which makes no sense.

Probable cause: A substitute product saw its price drop at the same time and captured the sales volume. Your product hasn't become less attractive; it's the competing product that has become more attractive.

Correction: Include the prices of substitute products in the model, or calculate cross-price elasticity. Pricing analytics tools do this natively.

Season/Events

Symptom: A product exhibits different elasticity in March and September, with no significant change in price.

Probable cause: an uncontrolled seasonal or event-related factor (back-to-school season, holidays, weather events). It is not the price that drives demand; it is the context.

Correction: Enhance the analysis with a timeline of events and exclude or adjust for atypical periods.

Competition (optional) and false matching

Symptom: The calculated elasticity appears reliable, but the decisions based on it do not work in production.

Probable cause: You are comparing your price to a competitor's price for a product that is not exactly the same (incorrect product matching), or you are completely ignoring the competitor's impact.

Correction: Improve the reliability of product matching (by EAN or structured attributes), and incorporate the competitor price index as a control variable.

Turning Elasticity into (Actionable) Pricing Decisions

A correlation in an Excel file is meaningless. It's the decision you make based on it that matters. Here's how to interpret your results and turn them into action.

Low elasticity: margin + cautious increases

Elasticity between 0 and -1. The product is not very price-sensitive.

Recommended action: Test gradual increases of 2 to 5% and measure the actual impact. This is the range where you can improve your margin without hurting sales volume.

Note: A product with low elasticity can still be a KVI with a strong visual impact. Check its visibility before raising the price.

Average elasticity: tests + segmentation

Elasticity between -1 and -2. The product reacts, but only to a limited extent.

Recommended action: Segment by channel and store cluster. Often, an overall average elasticity masks low elasticity in one area and high elasticity in another.

A/B testing allows you to validate changes before a full-scale rollout. Low cost, quick to learn.

High flexibility: KVI protection + competitor monitoring

Elasticity greater than -2. The product is very price-sensitive.

Recommended action: Do not raise prices without taking precautions. If it is a KVI, continuously monitor the competition and maintain a controlled price differential. If it is a non-KVI benchmark, investigate why it is so price-elastic (close substitutes? Perceived quality?).

Promotions are particularly effective for these products. But be careful of cannibalization, which is usually significant as well.

Safeguards: price floors, price ranges, validation

Regardless of the flexibility, never let an automated system adjust prices without safeguards.

The three essentials:

  • Minimum margin: A price never falls below a margin level defined for each category.
  • Amplitude range: no more than +/- 8% variation per cycle, no more than +/- 15% cumulatively over 30 days.
  • Human review of sensitive trading decisions (KVI, new product launches, high-volume listings).

Without these safeguards, flexibility becomes dangerous. With them, it becomes a tool for industrial management.

Checklist: Before drawing conclusions about elasticity

A calculated elasticity is good. A correctly calculated elasticity is better. Before turning a number into a decision, go through this checklist.

  • My history spans at least 12 months (ideally 18 to 24).
  • I have at least 6 significant price movements over this period.
  • I clearly distinguished between the regular price and the promotional price (two distinct elasticities).
  • I excluded the days when the item was out of stock.
  • I based my calculation on the actual price (after discounts), not on the listed price.
  • I controlled for seasonality (comparable periods or control variables).
  • I verified that the substitutable products did not change at the same time.
  • I segmented the data by channel and store cluster to check for consistency.
  • I put safeguards in place (minimum margin, range) before implementing any automation.
  • I had a business expert review the result before implementing it.

Conclusion: Moving from Measurement to Action

Calculating data elasticity is less a matter of mathematical formulas than a matter of data discipline. The %ΔQ / %ΔP division is trivial. The real work lies in data preparation and managing biases.

Three key principles to remember: Always work with the actual price, never the listed price. Always distinguish between the regular price and the promotional price. Always validate by segment before converting a coefficient into an automated decision.

Once these principles are in place, flexibility becomes a key management tool. You can identify areas where you can increase margins without any pain, protect your sensitive KPIs, and tailor your promotions based on a precise ROI calculation rather than a rough estimate.

To take this a step further, you can supplement this approach with forecasting models that anticipate demand beyond the price effect, and with a governance framework that transforms elasticity into automated rules with safeguards. This marks the transition from artisanal pricing to industrial pricing.

If you want to see how this would work for your business, the BOOPER team can conduct a pricing assessment for a pilot category in just a few weeks. You’ll walk away with your price elasticities, areas where you can recover margins, and a detailed action plan.

For more information:

Frequently Asked Questions

The questions that come up most often when starting an elasticity analysis project.

Elasticity = % change in quantity divided by % change in price. That is, E = %ΔQ / %ΔP.

Example: If a 5% price increase causes sales to fall by 10%, the elasticity is -10 / 5 = -2. It’s a simple formula; the pitfall lies in the quality of the data used, not in the division itself.

Always the net price—that is, the price actually paid by the customer after all immediate discounts, coupons, and loyalty program benefits have been applied. The listed price gives a distorted impression of price elasticity.

A product listed at €19.99 with a €3 discount at checkout has an actual price of €16.99. Calculating the elasticity based on €19.99 would be like analyzing a transaction that never took place.

We calculate two separate elasticity values: a standard one (excluding promotions) and a promotional one. They are almost always very different.

When analyzing promotional elasticity, be sure to factor in the cannibalization of substitute products. A 200% uplift for a private-label product on promotion may be accompanied by a drop in sales of the equivalent national brand, which reduces the actual gain.

The simplest approach is to exclude days when the product is out of stock from the calculation. A zero sale is not due to the price but to the product’s unavailability. Including it results in an aberrant elasticity.

If you have a high number of stockouts—affecting more than 30% of your sales history—you must first address the supply chain issue. No calculation method can salvage a sales history that has deteriorated to that extent.

Yes, and it's actually essential as soon as you have multiple channels or geographic regions. An overall average elasticity often masks very different patterns of behavior.

The same product may have an elasticity of -1.5 online, where price competition is fierce, and -0.8 in a physical store, where the customer base is more captive. The pricing decisions that should be drawn from these figures are radically different.

At least 12 months of historical data to capture seasonality; ideally, 18 to 24 months. For slow-moving products, allow for more time to ensure you have enough usable data points.

The number of price changes also matters: if your product has been priced at €9.99 all year, you cannot calculate its price elasticity because there are no price changes to analyze. You need 6 to 10 significant price changes to obtain a reliable coefficient.

There is no such thing as "good" or "bad" elasticity in absolute terms. It is a characteristic of the product and its market, not a measure of performance.

A low elasticity, such as -0.5, for a niche product may be normal. A high elasticity, such as -3, for a KVI is to be expected. What matters is what you do with this information: protect sensitive products, promote less sensitive products, and tailor promotions accordingly.

Elasticity does not directly provide the optimal price. It tells you how volume will respond to a change in price. It’s up to you to factor this information into your constraints: minimum margin, competitive positioning, price image, and product line consistency.

In practice, we simulate several pricing scenarios along with their associated elasticities, calculate the projected total margin for each, and select the best trade-off based on business objectives. Pricing analytics tools automate this type of simulation on a large scale.

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.

May 13, 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 retail pricing 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.

June 9, 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.

June 9, 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.

Request a demo