Purchasing, logistics and advertising costs are rising for everyone, yet a price increase remains the decision put off the longest: fear of losing customers wins over a shrinking margin. This guide takes the fear out of price rises with a single calculation: it shows how much sales you can afford to lose and still come out ahead, which products to raise first and how to measure the effect on margin instead of staring at revenue.
The maths of courage
How much sales you can lose: the reassuring formula
An asymmetry few people calculate
A price increase acts on margin with leverage: with a 30% margin, raising the price by 5% increases unit margin by one sixth. That is why a shop can withstand a surprisingly large drop in units before the increase stops paying off.
An example in euros: a product priced at €25 with a purchase cost of €17.50 leaves €7.50 of margin. After an increase to €26.25 it leaves €8.75. So it is enough to keep 86% of previous unit sales for total margin not to fall; every unit above that threshold is pure profit from courage. The precondition for the whole calculation: margin per product in your data (where to get it: the guide to margin in e-commerce).
Choosing the target
Which products first: a price resilience map
You do not raise “everything by 5%”; you raise prices where the customer has no easy comparison. Two axes organise the catalogue: product comparability and its weight in revenue:
Map: where to start price increasescomparability × weight in revenue
Safe testing ground
The customer cannot compare the price directly, and any mistake costs little. The ideal place for a first round and for learning how customers react.
High stakes, plenty of freedom
Resilient products with a large share: an increase shifts the most margin, but only goes ahead once the reaction has been confirmed on the testing ground.
Check the price range first
Before acting: review competitor prices. Low weight allows testing, but comparison sites quickly punish overshooting.
Price war zone
Identical goods, a large share, customers click the cheapest. Here the game is about costs and logistics; a price rise without changing the offer switches off sales.
Protocol
Testing a price rise on part of the catalogue: step by step
Choose a test group from the testing ground
A dozen to several dozen hard-to-compare products with low weight in revenue. The rest of the catalogue stays unchanged as a reference point.
Raise once, clearly, and record the date
One change (e.g. 5–8%) instead of a series of micro-adjustments: easier to measure and easier to reverse. The date of the change marks the boundary between the comparison periods.
Wait for a full buying cycle
A week is noise; compare full, comparable periods before and after, adjusted for seasonality and promotions.
Measure units and total margin, not revenue
Revenue rises “by itself” after a price increase and masks losses. The decision is made on the test group’s total margin against the threshold from the formula.
Check for side effects
The price in the feed must match the website (a mismatch means disapproved products; the mechanics are covered in the guide to Merchant Center), and baskets may have shifted relative to the free delivery threshold (threshold calculation: a separate guide).
A formality that is easy to forget
After a price increase, every subsequent promotion is subject to disclosure obligations (including showing the lowest price from the period before the discount, under the rules implementing the EU Omnibus Directive). When planning an increase ahead of the sales season, factor this into the change calendar.
Reading
Reading the result: units fell, what about margin?
Two products from the same round of increases can produce two opposite verdicts (online beauty and pharmacy shop, weekly, illustrative data):
Sunscreen (own brand) price €22.25 → €24
Sonic toothbrush (well-known model) price €54.75 → €58.75
The sunscreen lost 9% of units against a formula threshold of around 23% (30% margin, 7.9% increase): total margin grew by 14% and the increase stays. The toothbrush is a product with a model number and a comparison-site presence: the 31% drop exceeded the threshold and weekly margin fell despite the higher unit margin. Same move, two different outcomes: that is why the resilience map comes before the increase and measurement settles it.
DataOrganizer
How DataOrganizer measures the effect of an increase
DataOrganizer does not change prices; it measures their effect using data it already has: unit sales, unit and total margin per product, and comparisons of the periods before and after the change, with a breakdown of how much of the revenue change came from price and how much from units. Settling a round of increases fits into a single conversation:
Test group after a full cycle:
| Product | Price change | Units | Total margin | Verdict |
|---|---|---|---|---|
| Sunscreen (own brand) | +7.9% | −9% | +14% | stays |
| Skincare set | +6.1% | −3% | +19% | stays; candidate for a second round |
| Sonic toothbrush | +7.3% | −31% | −5% | revert to €54.75 |
Two of the three products passed the formula threshold and the group’s total margin grew by 9% despite fewer units. The breakdown confirms that the growth comes from price with a moderate loss of volume; the exception is the toothbrush (a product comparable by model), where the unit loss exceeded the threshold. Recommendation: revert one price and run a second round on the sets.
Methodological note: the figures in the examples are illustrative, and the formula for the acceptable drop in units is calculated on product margin in percentage points of price and ignores second-order effects (advertising cost per order, delivery thresholds). Period comparisons need adjusting for seasonality and promotions; an increase on the eve of a sales peak will show a false success.
Key takeaway
A price increase is an experiment with a calculable safety threshold. The formula tells you how many units you can afford to lose; the resilience map tells you where to start; measuring total margin tells you what stays. Fear has no line in this calculation.
FAQ
Frequently asked questions about price increases
Should I raise prices?
The maths is kinder than fear: at a 30% margin, a 5% increase tolerates around 14% of lost units before total margin falls. Instead of agonising over “whether”: calculate the threshold, choose resilient products, measure the effect.
How many sales can I afford to lose?
Increase / (margin + increase), all as a percentage of price: a 30% margin and a 5% increase give around 14%; a 45% margin and an 8% increase give around 15%. A drop in units below the threshold means total margin grows despite lower sales.
Which products should go first?
Hard-to-compare products with a small share of revenue (the testing ground), then resilient ones with a large share. Products searched for by model and bought via comparison sites come last, after a review of the price range; there, an increase without context switches off sales.
How do I measure the effect?
Full periods before and after, per product: units, unit margin, total margin (revenue hides losses because it rises “on its own”). Plus the side effects: price consistency between the feed and the website, and basket behaviour around the delivery threshold.
How does DataOrganizer help?
It measures the effect: units and margin per product in before/after windows, a breakdown of the revenue change into price and volume, and a split by category. The “stays / revert” verdicts come from a single chat question, a few days after the cycle ends.
Cheat sheet for the whole guide
Price increases in three moves
1. Calculate your courage threshold. Acceptable drop in units = increase / (margin + increase). This one line turns fear into a numerical limit.
2. Start from the testing ground. Hard-to-compare products with a small share first, price wars last, with the feed and the delivery threshold under control.
3. Settle on total margin. Units almost always fall; the question is whether by less than the threshold. DataOrganizer compares the periods around the change on units and margin per product, so every round of increases ends with a verdict based on numbers.
DataOrganizer · price effects measured on margin
Connect your shop system: units, unit margin and total margin per product in the windows before and after the change, with a price/volume breakdown. Demo account available instantly; you pay only for connected sources.