How to Run a Sale Without Wrecking Your Margin
The safest way to run a sale without wrecking your margin is to test the discount against your product's actual demand curve before applying it, and to make sure the promotional period gets excluded from your pricing data afterward so it doesn't distort future recommendations. Most of the damage from a bad sale isn't the discount itself, it's the corrupted signal that discount leaves behind in your sales history.
Key Takeaways
- A sale's biggest risk often isn't the discount itself, it's the corrupted pricing signal it leaves behind if the promo period isn't excluded from future data.
- Test a discount against your product's own demand curve before applying it, rather than picking a round percentage that feels generous.
- Promotional sales spikes should be flagged and excluded from your baseline elasticity, since customers respond more aggressively to visible discounts than to normal price changes.
- A post-sale dip in demand is often temporary (customers who stocked up buying less afterward), not a sign your regular price is wrong.
A Sale's Real Cost Has Two Parts
The obvious cost of a sale is the margin given up during the discount window. The less obvious cost is what that promotional period does to your pricing data afterward. A spike in sales at a low price during a sale doesn't reflect how customers behave at your normal price. If that spike gets treated as ordinary sales history, it skews your elasticity estimate going forward, and future recommendations end up built on a distorted picture of customer behavior.
Test the Discount Before You Apply It
Rather than picking a discount percentage that feels aggressive enough to move inventory, a what-if simulator lets you preview the projected profit impact of a specific sale price against your product's actual demand curve, using elasticity calculated from your own sales history. If your data suggests demand is fairly inelastic for a product, a deep discount may cost you more in margin than it gains in volume. If demand is highly elastic, a meaningful discount can genuinely lift total profit, not just total units sold.
| Elasticity signal | What it suggests for a sale |
|---|---|
| Low elasticity (customers not very price-sensitive) | A deep discount likely costs more in margin than it gains in volume; a smaller discount may make more sense |
| High elasticity (customers very price-sensitive) | A meaningful discount can plausibly lift total profit through volume, worth testing with the simulator first |
Either way, the point is testing against your own data rather than picking a round number because it sounds generous.
Not Every Product Needs the Same Discount
Bestsellers already converting at full price rarely need a discount to move units, so discounting them mainly gives away margin you didn't need to give up. Slow-moving inventory has more room for a deeper cut, since unsold stock sitting in a warehouse often costs more over time than the margin given up to clear it. Treating every product in a catalog with one blanket discount percentage ignores this difference entirely.
Flag the Promotional Period, Don't Let It Slip Into Your Baseline Data
This is the step most sellers skip, and it's the one with the longest tail of consequences. If a sale period isn't excluded from the data your future pricing decisions are built on, it teaches the model, and effectively teaches you, the wrong lesson about how price-sensitive your customers really are. Promotional elasticity is typically higher than baseline elasticity: customers respond more aggressively to a visible discount than they would to the same percentage change at your regular price, and treating that as your normal elasticity overstates how much a future price cut would actually help.
Zorin's model automatically detects statistical outliers in your sales history, most commonly promotional spikes, and flags them for exclusion so your baseline elasticity estimate reflects ordinary buying behavior, not sale-week behavior. You can also manually confirm or override a flag if you know a spike had a different cause.
Watch for the Post-Sale Dip
A real pattern worth expecting: customers who stock up during a sale often reduce their normal purchasing for a period afterward, since they already bought what they needed at a discount. If you misread that natural dip as a sign your regular price is suddenly too high, you risk cutting a price that didn't actually need to change. Give the post-sale period a reasonable window before drawing conclusions from it.
Pricing Back Up When the Sale Ends
Resetting to "whatever it was before" without checking anything is a missed opportunity in one direction and a real risk in the other. If your baseline demand data (properly excluding the promo period) suggests the pre-sale price was already below the profit-maximizing point, the reset is a chance to correct that, not just restore the status quo. Run the same check you'd run on any price decision: does the current elasticity estimate, cleaned of promotional noise, support this specific number.
A Simple Sequence for Running a Sale
- Check elasticity before picking a discount instead of choosing a round percentage that feels right.
- Segment bestsellers from slow movers rather than applying one blanket discount catalog-wide.
- Use the simulator to preview projected impact at a specific sale price before it goes live.
- Let the promo period get flagged as an outlier once the sale runs, so it doesn't corrupt future recommendations.
- Give the post-sale period time before reading a temporary dip as a signal your regular price is wrong.
If you're pricing across more than one storefront, the same discipline applies per channel, see should you price differently on Shopify vs Amazon. And if you haven't checked your baseline elasticity recently, start with how to know what to price your products.
Frequently Asked Questions
How do I run a sale without wrecking my margin?
Test the discount against your product's actual demand curve before applying it, and make sure the promotional period gets excluded from your pricing data afterward so it doesn't distort future recommendations.
How do I decide which products to discount and by how much?
Check elasticity per product rather than applying one blanket percentage. Bestsellers usually need little or no discount; slow-moving inventory can typically absorb more.
Do promotions mess up my future pricing recommendations?
Yes, if the promotional sales spike isn't excluded from the data. It inflates apparent demand at an artificially low price and can distort your baseline elasticity estimate going forward.
How does a tool know a spike in sales was a promotion and not real demand?
Statistical outlier detection flags unusually high sales relative to the fitted model as likely promotional activity, which you can confirm or override manually.
Why do sales sometimes dip right after a promotion ends?
Customers who stocked up during the discount often buy less than usual for a period afterward. That's a temporary pattern, not necessarily a sign your regular price is too high.
How do I price back up after a sale ends?
Check your baseline elasticity, with the promotional period excluded, against your planned reset price rather than assuming the pre-sale price is automatically correct.
Can I preview the impact of a discount before applying it?
Yes. A what-if simulator lets you test candidate sale prices against your product's demand curve and see the projected impact before anything goes live.
A sale's biggest risk usually isn't the discount you can see, it's the corrupted signal it can leave behind if the promotional period bleeds into your regular pricing data. Test the discount against your own demand curve, flag the promo period afterward, and give the post-sale window time before drawing conclusions from it.
Written by Dexter
Dexter is part of the team at Zorin, building tools that help ecommerce merchants price with data instead of guesswork.