eCommerce

How to Use Price Elasticity to Protect Peak Season Margin

Balaji Kolli
Co-founder
Last updated:
November 20, 2026
15
min read
Not every SKU reacts to price the same way. Measure price elasticity by product and segment to protect margin before the next peak season discounting.
TL;DR
  • Price elasticity is the percentage change in quantity demanded divided by the percentage change in price, and it varies widely by product.
  • A uniform discount across every SKU can hit the revenue target while destroying profit, because part of that volume would have sold at full price anyway.
  • Raise prices where elasticity allows it (premium products), and hold or discount the elastic ones (commodity products).
  • Test the plan on a few SKUs, one from each tier, before peak season kicks in.
  • Go into peak season with 3 to 5 pre-modeled pricing scenarios, so you execute when demand signals arrive.

Price elasticity of demand measures how much the quantity you sell changes when you change the price. In ecommerce, it tells you which SKUs can carry a price increase and which ones need a discount to move. Measure it by product and customer segment before you set BFCM and peak season pricing, and you stop discounting the products that would have sold at full price anyway.

Here's what keeps you up at night: you're making a $5M+ pricing decision on an assumption. You're assuming that if you raise prices, volume will drop 15%, so you don't bother trying. You leave the margin on the table.

BFCM lands on November 27, and all your data lives in different places. Your accounting system has one view of profitability. Your merchandising team has inventory levels scattered across spreadsheets.

Your marketing team is tracking CAC by channel in Shopify. And by the time you pull all that together into one report, the season's already halfway done.

But here's the thing nobody tells you: for most of your products, elasticity isn't 0.15. It's 0.08. Which means a 10% price increase drops volume only 0.8% while margin jumps 9.2%.

On 10,000 units, that's $60,000 in additional profit from a single pricing decision.

The difference between a $200M brand and a $300M+ brand doesn't come down to better luck or harder work. It comes down to this: category leaders optimize price by product and customer segment. Everyone else runs the same pricing strategy on everything and wonders why their margins are getting squeezed.

‍

FOR $20M+ BRANDS

Is your data actually Decision-Grade?

9 questions. 3 minutes. Score your Profitability Visibility and Readiness for AI-driven growth.

Start Free Diagnostic
Data Decision Grade Report

‍

What Is Price Elasticity of Demand?

Price elasticity of demand is the percentage change in quantity demanded divided by the percentage change in price. Here's the model you need:

Price elasticity = percentage change in quantity demanded / percentage change in price

A product with an elasticity of 0.08 loses 0.8% of its volume when you raise the price 10%. A product with an elasticity of 0.22 loses 2.2% on the same increase. That one number belongs at the center of your pricing strategy.

For seasonal apparel, elasticity varies wildly by product:

Product type Elasticity What is going on
Premium/branded products 0.05 to 0.10 Customers are loyal to the brand, not price-shopping
Mid-tier products 0.08 to 0.12 Price matters, but brand matters more
Commodity/basic products 0.15 to 0.25 Price is almost everything

Why Uniform Peak Season Discounts Destroy Margin

Here's the thinking error that costs millions: you assume all your products respond to price the same way. So you price them uniformly. When promotions ramp up during peak season, you discount everything by the same percentage to drive volume.

You hit your revenue target. You call it a win. Your board is happy.

You don't see what you destroyed in the process: profitability.

Some products have price-sensitive customers (elastic demand). Others have brand-loyal customers (inelastic demand). Some channels have completely different economics than others.

Some products are high-margin (should protect price). Others are low-margin (can absorb discounts). That is why SKU-level profitability has to sit next to the elasticity number.

So you end up discounting your highest-margin products that could sustain a 10% price increase, while leaving your lowest-margin products at full price. You're optimizing in reverse. You're paying to drive traffic to products you can't even make money on.

Example: a uniform 20% discount across 50 SKUs

One apparel brand discovered this too late. They ran a uniform 20% discount across 50 SKUs during peak season to hit their $5M revenue target. They hit it, and they celebrated.

Three months later, their finance team analyzed the profitability by product:

  • Premium Sweater (Product A): 20% discount drove $1.2M revenue, but 60% of that volume was cannibalization (people who would've bought at full price anyway). Actual incremental profit: $80K.
  • Premium Jacket (Product B): 20% discount drove $900K revenue, but only 10% was cannibalization. Actual incremental profit: $720K.
  • Basic Tank (Product C): 20% discount drove $1.8M revenue, but 85% was cannibalization. Actual incremental profit: -$50K (they destroyed profit on this one).

They'd been discounting their most profitable products and protecting their least profitable ones. Their CFO realized: we hit our revenue target but destroyed $300K in margin doing it.

And by November, it was too late to fix. We cover the broader question, are ecommerce discounts profitable, in a separate post.

How to Measure Elasticity by SKU

Here's the math that changes everything. Take two products with very different elasticity and run the same 10% price increase on each.

Product A (Premium Sweater): MSRP $60, elasticity 0.08

Here is what a 10% increase does:

  • You raise price 10% to $66
  • Volume drops 0.8% (not 15%)
  • On 10,000 units: you lose 80 units, keep 9,920
  • Revenue: (9,920 × $66) = $654,720 vs. (10,000 × $60) = $600,000
  • Revenue gain: +$54,720 on the same customer base

Product B (Basic Tank): MSRP $20, elasticity 0.22

Here is the same move on a commodity product:

  • You raise price 10% to $22
  • Volume drops 2.2% (much higher elasticity)
  • On 50,000 units: you lose 1,100 units, keep 48,900
  • Revenue: (48,900 × $22) = $1,075,800 vs. (50,000 × $20) = $1,000,000
  • Revenue gain: +$75,800, but you lose 1,100 customers

The second one is riskier. The first one is almost free profit.

But here's the insight your team is missing: you don't have to raise prices uniformly. You raise prices on products where elasticity allows it (the premium ones). You hold or discount the elastic ones (the commodities), and you protect margin on what actually matters to your bottom line.

What an elasticity model requires

Here's the brutal truth: building an elasticity model is what you'd hire a $150K data analyst or pay a consultant $50K+ for. It requires:

  • Historical pricing data across products, channels, and time periods
  • Volume data at each price point
  • Cannibalization analysis (which sales are truly incremental?)
  • Customer segmentation (which segments are price-sensitive?)
  • Scenario modeling (what happens at 5%, 10%, 15% increases?)

One more input is worth a look before you reprice a SKU: how returns distort contribution margin.

How to Build a Tiered Pricing Plan

One apparel CFO did something radical. Instead of a uniform peak season strategy, they built a tiered pricing approach. They tested this on 3 SKUs (one from each tier) before peak season kicked in.

The table shows each tier, the price move and the test result:

Tier Elasticity Price move Test SKU Result
Tier 1 (Premium/brand products) 0.06 to 0.10 Raise prices 12 to 15% Sweater Volume down 1.1%, revenue up 12.8%, margin up $220K
Tier 2 (Mid-tier) 0.10 to 0.15 Raise prices 8 to 10% T-shirt Volume down 2%, revenue up 8%, margin up $95K
Tier 3 (Commodity/basic) 0.18 to 0.25 Hold price or discount 5% Basic Tank Volume down 4%, revenue down 3%, margin down $50K (so they discounted instead)

Net across all 50 SKUs during peak season: +$400K in incremental profit without losing meaningful volume.

That CFO locked in the strategy. When peak season hit and the pressure to discount was intense, they had numbers to back up their pricing.

No scrambling. No guessing. They executed.

What peak season could look like

"We tested 10% price increase on Sweaters. Lost 0.8% volume, gained 9.2% margin dollars. On 10K units, that's $60K more profit."

Go into peak season with 3 to 5 pre-modeled pricing scenarios. Not guesses. Not "we'll see what happens."

Models based on your actual elasticity.

Here are three scenarios to model:

  • Scenario 1: Demand is normal. Prices protect margin. Target: 18% margin on peak season sales.
  • Scenario 2: Demand spikes 30%. Some elasticity tolerance. Prices optimize for both volume AND margin. Target: 20% margin on elevated volume.
  • Scenario 3: Demand is weak. Protect high-margin products, strategic discounts only on low-margin. Target: 22% margin on lower volume.

When demand signals arrive, whether that is the first days of BFCM this year or the opening weeks of next year's peak season, you already know which scenario matches. You execute immediately. Your competitors are still debating pricing, and you've already captured the profit.

How Saras iQ Models Elasticity From Your Sales History

You don't have a data analyst. Your team is already drowning in spreadsheets. By the time you could manually build this, peak season will be over.

This is what Saras iQ does. You ask it: "What price maximizes profit if volume drops 5%?" It analyzes your sales history, calculates elasticity by product and segment, and models scenarios.

You get the answer in minutes, not months. You don't learn the math. Saras iQ understands the math, and you make the decision.

Ask Saras iQ

"What are the top SKUs that have a margin between 20 and 30%?"

To see how it handles the profit side of the same question, look at Saras iQ contribution margin.

Next step

You're leaving $500K on the table during peak season because you haven't modeled elasticity by product. Stop guessing. Start with data.

Book a demo and talk to us about how Saras iQ builds elasticity models from your actual sales history, so you go into peak season with pricing strategies, not prayers.

Frequently Asked Questions (FAQs)

What is price elasticity of demand?
+

Price elasticity of demand is the percentage change in quantity demanded divided by the percentage change in price. It tells you how much volume you give up when you raise a price, or gain when you cut one. A low number means customers keep buying after an increase, and a high number means they are price-shopping.

How do you calculate price elasticity for a product?
+

Divide the percentage change in units sold by the percentage change in price, using your own sales history at different price points. For example, if a 10% price increase is followed by a 0.8% drop in volume, elasticity is 0.08. Calculate it per product and per customer segment, because the numbers differ widely.

What is a good elasticity for premium ecommerce products?
+

There is no single target, but in seasonal apparel, premium and branded products tend to sit around 0.05 to 0.10, because customers are loyal to the brand and not price-shopping. Mid-tier products run 0.08 to 0.12 and commodity basics 0.15 to 0.25. The lower the number, the more room you have to protect price.

Should you discount everything for Black Friday?
+

No, because a uniform discount treats every product as if it responds to price the same way, and it usually does not. Protect price on premium, high-margin products with loyal customers, and keep discounts for the elastic, commodity products where price drives the purchase. Decide SKU by SKU, not with one percentage for the whole catalog.

How much data do you need to estimate elasticity?
+

You need historical pricing data across products, channels and time periods, plus volume at each price point. Add cannibalization analysis and customer segmentation to separate truly incremental sales from sales you would have made anyway. If history is thin, test a price change on a few SKUs, one from each tier, before peak season.

+

What to do next?

See Saras in Action
If you're ready to stop pulling reports manually and centralize your eCommerce data, see exactly how Saras does it in a 25-minute demo. No prep required.
Book a Demo
Test your Data Readiness
Take the Quiz
Take a quick 5-min quiz and find out how future-proof your stack really is.
Check out Saras Analytics × 9 Operators Podcast
Listen to how top eCommerce operators think about data, growth, and analytics
Listen Now
Table of Contents
Heading one of the blog
Heading one of the blog
Heading one of the blog
Heading one of the blog
Heading one of the blog
Heading one of the blog
Get instant, trusted answers across your business functions
Meet Saras iQ: The AI analyst for your e-commerce business

Must read resources

Get instant, trusted answers across your business functions

Meet Saras iQ: your e-commerce AI analyst, powered by your business data, certified by us