TL;DR
Show the prior price (the lowest price you charged in the 30 days before the sale) right next to your sale price, clearly labelled, in the same block a shopper is already reading. Make sure any strikethrough or “% off” is calculated from that prior price, not from an RRP. Do it everywhere you announce the discount: product page, collection pages, search, cart, emails and product feeds. And do it per market, because each Shopify market has its own prior price.
This guide assumes you already know how to work out the prior price. If you do not, start with the Omnibus price guide, which covers the calculation and a cheat sheet of worked examples, then come back here for the display side.
What actually has to appear
Article 6a of Directive 98/6/EC (inserted by the Omnibus Directive 2019/2161) requires that whenever you announce a price reduction, you indicate the prior price: the lowest price you applied in the 30 days before the reduction. The European Commission's guidance (Notice 2021/C 526/02) adds the practical constraint that matters for display: the indication has to be clear. A prior price that is technically present but hidden, ambiguous, or contradicted by a bigger “% off” figure does not meet the standard.
In practice that means two things need to be right on screen:
- The prior price figure itself, shown alongside the reduced price.
- Any strikethrough price and any percentage or amount of saving, calculated from that prior price so the two agree.
Where to put it on a Shopify product page
Put the prior price in the same visual field as the current price, directly next to or beneath it, above the add-to-cart button. That is where the shopper's attention already is, and it is where a regulator or a mystery shopper will look first. A good pattern:
- Current (reduced) price, prominent.
- The prior price on the line directly below, clearly labelled (see wording below).
- Optional strikethrough and saving, both derived from the prior price.
Do not bury the prior price in a “details” accordion, a size-guide tab, a tooltip that only appears on hover, or the page footer. If the shopper has to work to find it, it is not a clear indication.
Exact wording and formatting
There is no legally mandated sentence, but the label has to make clear that the figure is the lowest prior price. Clear, tested phrasings include:
- “Lowest price before this sale: EUR 94.20”
- “Lowest price in the 30 days before the discount: EUR 94.20”
- “Previous price (before the sale): EUR 94.20”
Do not label it “lowest price in the last 30 days.” The reference window ends the moment your reduction starts, so the figure is the lowest price in the 30 days beforethe sale, not including it. During a live sale, “the last 30 days” would take in the current, lower sale price, which is both wrong and misleading. Always frame the label as the price before the reduction.
Formatting rules that keep it compliant and legible:
- Use the same currency and number format as the rest of your prices in that market, so the figure is unmistakably a price.
- Keep it in the shopper's language. A German-market page should read “Niedrigster Preis vor dieser Aktion”, not English.
- Make it legible on mobile. If your theme collapses it into tiny grey text below the fold, it fails the clarity test even though the figure is present.
The percentage trap
This is the mistake that turns an otherwise compliant page into a misleading one: showing the prior price correctly, but advertising a percentage saving calculated from a different, higher number.
The classic percentage error
Jeans normally sell at EUR 100. You discount them to EUR 70 for Black Friday, then to EUR 50 in December. Your prior price for the December sale is EUR 70, and you correctly display “Lowest price before this sale: EUR 70”.
But the theme still shows a “50% off” badge, calculated from the EUR 100 RRP. The badge and the prior price now contradict each other. The real reduction from the EUR 70 prior price is about 29%, so the “50% off” claim is the misleading part, even though the prior price line is right. Fix the badge, or drop it.
The rule of thumb: every number that implies a saving (strikethrough, “% off”, “save EUR X”) has to be consistent with the prior price. If you cannot make them agree automatically, it is safer to show the prior price and the sale price and drop the derived percentage.
Shopify Markets and multi-currency
The prior price is calculated per market, in that market's currency, from that market's actual prices. This trips up stores that use Shopify Markets to sell into several countries.
- If your German and French markets ran different promotions, they have different prior prices. You cannot show one figure across both.
- Do not calculate a prior price in one currency and FX-convert it into another. The prior price in the French market is the lowest price you actually charged in euros in France, not a converted figure from a different market.
- Rounding and price lists differ per market on Shopify, so the same product legitimately has different prior prices in different markets.
Every surface, not just the product page
Article 6a applies wherever the reduction is announced to the consumer. If a strikethrough, badge, or “% off” appears somewhere, the prior price logic has to hold there too:
- Collection and category pages that show sale badges or slashed prices.
- On-site search results and “sale” landing pages.
- The cart and checkout, if they restate a saving.
- Marketing emails and on-site banners that advertise the discount.
- Product feeds to Google Shopping and comparison sites. A feed that sends a strikethrough not matching the prior price is still a misleading announcement. See compare-at-price vs prior price for how the Shopify field leaks into feeds.
Display mistakes to avoid
- Using the compare-at-price strikethrough as if it were the prior price.
- Advertising a “% off” calculated from the RRP instead of the prior price.
- Hiding the prior price in a tooltip, tab, or the footer.
- Showing it only on the product page, while collection pages still show an inflated saving.
- FX-converting one market's prior price into another currency.
- Rendering it in tiny, low-contrast text that fails the clarity standard on mobile.
Doing it by hand vs automatically
To do this manually you would need to store a daily price snapshot for every product and variant in every market, compute the 30-day low each day, render the labelled figure in your theme, and keep every strikethrough and percentage on every surface in sync with it. That is a cron job, a database, a theme integration, and ongoing maintenance, redone for each market.
An app removes all of that. Complimus records every price change on every Shopify product automatically, computes the Article 6a prior price per market, and renders it next to your sale price without theme-code edits. It picks up your catalogue on install and starts tracking from day one.
Frequently asked questions
Can I show a price-history graph instead of a single figure?
Do I have to show the prior price when the product is not on sale?
Does it need to be in the local language?
What about products with several variants at different prices?
Is a strikethrough on its own enough?
