TL;DR
When discounts follow each other, the prior price you must display depends on one question: did the price ever go back up? Inside a single campaign whose reduction is progressively increased, Article 6a(5) lets every step keep referencing the price charged before the first step. The moment the price rises again, that anchor is gone: the campaign is over, and the lowest promotional price you just applied becomes the binding reference for the next 30 days. This guide gives the methodology for progressive ladders, stacked site-wide discounts, and back-to-back campaigns, plus a decision procedure you can run per product.
The default rule, and the question it leaves open
Article 6a of Directive 98/6/EC, inserted by the Omnibus Directive, states the baseline in two sentences.
Any announcement of a price reduction shall indicate the prior price applied by the trader for a determined period of time prior to the application of the price reduction. The prior price means the lowest price applied by the trader during a period of time not shorter than 30 days prior to the application of the price reduction.
Almost every explainer stops here, which is fine if you run one discount and then leave the product alone for a month. Real trading does not look like that. A product goes into a mid-season sale, then a clearance ladder, then a site-wide weekend promotion, then Black Friday, all inside a few weeks. Each of those is an announced price reduction in its own right, and each one needs its own prior price computed at the moment it goes live.
The mechanics of a single reduction are covered in our 30-day prior price rule guide. This page answers the follow-up question: what is the prior price on the second, third, and fourth discount?
Two rules do all the work, and they are in tension with each other:
- Article 6a(2), the default. Every announced reduction looks back at least 30 days and takes the lowest price actually applied. Earlier promotional prices are prices you applied, so they count.
- Article 6a(5), the progressive exception. Where the reduction is progressively increased, the prior price is the price without the reduction before the first application of the reduction. Inside such a campaign, the anchor does not move.
Everything below is a matter of deciding which of the two applies to the discount you are about to publish.
Progressive campaigns: the ladder that keeps its anchor
Member States may provide that, when the price reduction is progressively increased, the prior price is the price without the price reduction before the first application of the price reduction.
This is the provision that makes clearance ladders workable. Without it, a campaign that cuts a product from EUR 100 to EUR 90, then EUR 80, then EUR 70 would have to re-anchor at every step: the second step would advertise 11% off EUR 90, the third 12.5% off EUR 80, and a genuinely deepening sale would look like it was getting shallower. Article 6a(5) fixes the reference at the pre-campaign price for the whole ladder, so each step can be announced against EUR 100: 10%, then 20%, then 30%.
Three conditions have to hold for the exception to apply:
- One continuous campaign. The steps are part of a single announced sale with an uninterrupted run, not a series of independent promotions that happen to share a product.
- The reduction only ever increases. Each step must be deeper than the last. A step that holds flat is harmless; a step that goes back up ends the campaign.
- Your market adopted the option. Article 6a(5) is a Member State option rather than a mandatory rule. Most transpositions include it, but check the market you sell into in our Omnibus rules by country table before you rely on it.
✓All three steps anchor to EUR 100
The reduction is progressively increased and never interrupted, so Article 6a(5) fixes the reference at the price charged before step 1.
!Label the campaign as one sale
The exception rests on the steps being a single continuous campaign. Presenting them as separate promotions puts you back under the default 6a(2) rule.
Worked example: the ladder
A coat sells at EUR 100 through October. On 1 November a three-week clearance ladder starts: EUR 90 for week one, EUR 80 for week two, EUR 70 for week three. The price is never raised during the campaign.
The prior price displayed on every one of the three steps is EUR 100, and the badges may read 10%, 20% and 30%. The strikethrough shows EUR 100 throughout. What you may not do is anchor step two against step one: EUR 80 next to a struck-through EUR 90 is not what Article 6a(5) permits, because the provision fixes the reference at the pre-campaign price, not at the previous step.
The reset trap: one step up ends the anchor
This is the single most expensive misunderstanding in successive discounting. Article 6a(5) applies only while the reduction is progressively increased. If the price moves back up at any point, even briefly, even back to your ordinary price, the progressive campaign has ended. Any reduction announced after that is a new reduction, governed by the default rule in Article 6a(2), and the default rule looks back at the last 30 days of prices you actually charged. Those 30 days now contain your promotional prices.
The consequence is counter-intuitive but unavoidable: the deepest price you reached in the campaign becomes the ceiling for your next campaign, for 30 days after you applied it.
âś•"25% off, was EUR 100"
The return to EUR 100 closed the progressive campaign. EUR 100 is no longer the legal reference, because a lower price was applied inside the window.
âś“"Was EUR 80, now EUR 75"
EUR 80 is the lowest price actually applied in the 30 days before the new sale, so the honest announced reduction is 6.25%.
Note what the chart does not say. It does not say the second sale is unlawful. Selling at EUR 75 is fine. What is unlawful is announcing it against EUR 100. If the arithmetic of a 6.25% badge is commercially unattractive, the answer is to change the campaign calendar, not the reference price: either extend the original ladder downward without ever raising the price, or wait until the EUR 80 promotional price has aged out of the 30-day window.
Why a brief return to full price does not reset anything
Merchants often assume that putting a product back to its normal price “clears the history” and lets the next campaign start fresh from the recommended retail price. The opposite is true. Restoring the full price is precisely the act that ends the Article 6a(5) exception, while doing nothing at all to the 30-day look-back, which counts the lowest price applied and is completely indifferent to what the price was on the day before the sale. A one-day return to EUR 100 between two promotions buys you nothing and costs you the progressive anchor.
Overlapping and stacked discounts
The second hard case is not sequential but simultaneous: a product-level markdown and a site-wide promotion applying to the same item at the same time. A jacket is marked down from EUR 100 to EUR 80, and a weekend banner offers a further 25% off everything, so the customer pays EUR 60.
The question “what price was applied?” has one answer, and it is the practical one: the price the consumer could actually pay. During that weekend the product was applied at EUR 60, not at EUR 80. EUR 60 therefore enters the price history, and it is EUR 60 that will constrain the next announced reduction for the following 30 days.
Working forward from that principle resolves most stacking questions:
- Announce the total, not the layers.If the storefront shows EUR 60, the prior price displayed next to it is the 30-day low computed for that moment, and the percentage is the reduction from that figure to EUR 60. Advertising “20% off, plus an extra 25%” without a single clear prior price and a single resulting price is where stacked promotions usually go wrong.
- General discount codes count. A code published on the site, in a banner or in a newsletter to the whole list is a general reduction available to all customers, so the resulting price is a price you applied. A code issued to one named customer, or a personalised loyalty rate, is an individualised reduction and sits outside Article 6a (see member prices and loyalty discounts).
- Automatic cart discounts count too. If the reduction is applied without the customer needing anything you did not give everyone, the reduced price is the applied price, whether Shopify applies it on the product page or at checkout.
- Conditional offers are treated with care.Volume offers such as “three for two” are not straightforward single-unit price reductions, and are generally assessed as combined offers rather than as an Article 6a announcement on the unit price. If in doubt, keep them out of your unit-price history and do not use them to justify a lower reference either.
Worked example: the stack that bites later
A jacket sits at EUR 100. On 1 March it is marked down to EUR 80 with a “20% off” badge, correctly anchored on EUR 100. On 8 March a site-wide “extra 25% off everything” weekend runs, so the jacket sells at EUR 60 for two days. On 10 March the site-wide offer ends and the jacket returns to EUR 80.
From 10 March onward, the storefront may not show EUR 80 as a reduction from EUR 100 anymore, because EUR 60 is now the lowest price applied in the last 30 days. In fact EUR 80 is a higher price than the window low, so it is not a reduction at all and should carry no discount badge or strikethrough until 9 April, when EUR 60 leaves the window.
Back-to-back campaigns inside 30 days
The third case is the most common in practice: two separate campaigns less than a month apart. Because the previous promotional price is still inside the new look-back window, it becomes the prior price, and the second campaign's headline percentage shrinks even though the customer is paying less than ever.
Worked example: why the second campaign looks smaller
A product is normally EUR 100. Campaign A runs 1 to 7 May at EUR 70, announced as 30% off EUR 100, which is correct. The product returns to EUR 100 on 8 May. Campaign B launches on 25 May at EUR 65.
The window for Campaign B is 25 April to 24 May, and it contains the EUR 70 price from Campaign A. The prior price is therefore EUR 70. The lawful announcement is “was EUR 70, now EUR 65”, a reduction of 7.1%. A “35% off” badge would be a misleading commercial practice.
Two ways out, both planning decisions rather than display decisions. Push Campaign B to 7 June or later, once the EUR 70 price has aged out of the window and EUR 100 is again the lowest price applied. Or run one continuous progressive campaign from 1 May, stepping EUR 100 to EUR 70 to EUR 65 without ever restoring EUR 100, in which case Article 6a(5) keeps EUR 100 as the reference throughout.
The second option is worth dwelling on, because it is the strategic lesson of this entire article. Two campaigns of the same depth, run on the same products at the same prices, can be lawful at 35% off or capped at 7% off purely on the basis of whether the price was restored in between. The pricing calendar, not the badge, determines what you are allowed to advertise.
Which price do I show? A decision procedure
Run this per product and per variant, on the day the reduction goes live, and separately for each market and sales channel where your price differs.
- Is this an announced reduction at all?A strikethrough, a percentage, a “was” figure, a sale badge or a promotional banner all count. Simply lowering a price with no comparative claim does not trigger Article 6a, though the new lower price still enters your history.
- Is this the continuation of a live progressive campaign? That means one uninterrupted campaign in which this step is deeper than the previous step and no price increase has occurred since the first step. If yes, the prior price is the price charged immediately before the first step, and you are done.
- If not, list every price actually applied in the last 30 days. Include earlier sale prices, general discount-code prices, automatic cart discounts and the net effect of any stacked promotion. Exclude RRP, compare-at values and individualised reductions.
- Take the lowest of those prices. That is your prior price, whatever your ordinary price happens to be and whatever the price was yesterday.
- Check the price you are about to charge is actually lower. If it is not, you have no reduction to announce and the badge has to come off.
- Compute the percentage from the prior price. Not from RRP, not from the previous step of a broken ladder, not from the pre-campaign price you would prefer to use.
- Display the prior price next to the reduced price on every surface where the reduction is announced: product page, collection page, search results, cart and any ad creative that carries the claim.
- Record the new price, with its date. It is an input to every reduction you announce over the following 30 days.
Steps two through four are exactly what our free Omnibus prior-price calculator does: enter the price history, and it returns the prior price and the maximum discount you may advertise.
Five mistakes that produce a wrong reference
- Resetting to RRP between campaigns. Restoring the recommended retail price does not clear the 30-day history. It only ends any progressive-campaign anchor you were relying on, making your position worse rather than better.
- Using the Shopify compare-at price as the reference. It is a free-text field with no connection to what you charged, and themes render it exactly where the legal prior price belongs. See compare-at price vs prior price.
- Treating the window as rolling from today. The window closes when the reduction starts. It never contains the sale price itself, so the reference does not drift downward while a sale is running, and it does not need to be recomputed daily during a campaign.
- Anchoring a ladder step on the previous step. Article 6a(5) fixes the reference at the pre-campaign price. Re-anchoring on the previous step understates the reduction and, more importantly, is not what the provision says.
- Computing one reference for the whole catalogue. The prior price is per product, per variant, per market and per channel. A site-wide percentage applied to a catalogue of products with different histories will be correct for some of them and wrong for the rest.
If you want to test your current setup against these, work through the Omnibus self-audit or keep the prior price cheat sheet next to your promotions calendar.
Frequently asked questions
If I run three discounts in a row, can each one reference my normal price?
What exactly ends a progressive campaign?
After a progressive campaign ends, what is my prior price for the next sale?
A site-wide code stacks on top of a product markdown. Which price counts?
Do discount codes count toward the prior price?
Can I raise the price for a few days to reset the 30-day window?
Does the second campaign really have to advertise a smaller percentage?
Is Article 6a(5) available in every EU country?
