TL;DR
Shopify's compare_at_price is a free-text field merchants set to whatever number they want. Shopify themes render it as a strikethrough next to the selling price. EU Omnibus Article 6a requires the strikethrough on any announced discount to be the trader's actual lowest selling price in the 30 days before the reduction. The two are unrelated. Treating compare-at-price as if it were the Article 6a prior price is the single most common Omnibus violation on Shopify stores worldwide. This article explains why, what regulators look for, and how to fix it.
What each field actually is
Shopify's product model has a price field (the current selling price) and a compare-at-price field (an optional reference price displayed as a strikethrough). The compare-at-price field is editable by the merchant at any time, takes any value, and has no built-in relationship to historical pricing. Shopify documentation describes it as the price “before the markdown,” with no further constraint.
Article 6a of EU Directive 98/6/EC (as inserted by the Omnibus Directive 2019/2161) defines the prior price as 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. Whenever a trader announces a price reduction, the prior price has to be indicated. The directive's definition is mechanical: lowest, in the 30 days before the reduction, applied by the trader.
These are two different concepts. Compare-at-price is a marketing field. The Article 6a prior price is a legal definition with a specific calculation. There is no mechanism in the Shopify product model that links the two.
Why they diverge in practice
Merchants typically set compare-at-price using one of four heuristics. None of them match the Article 6a definition.
- Manufacturer's suggested retail price (MSRP). The merchant uses the MSRP supplied by the brand owner as the strikethrough. Article 6a requires the merchant's own lowest price in the 30 days before the reduction, not the manufacturer's recommendation.
- Original launch price. When the product first launched, the merchant set compare-at-price to the launch price and has not updated it since. Article 6a looks at the 30 days before the reduction only; the launch price from 14 months ago has no legal relevance as a reference.
- Aspirational anchor. The merchant chose a number that looks good next to the selling price (often 30–50% higher) to create the appearance of a discount. This is the regulatory worst case. AGCM's Yoox decision found exactly this pattern (fictitious “market prices”) and imposed EUR 5.25 million in fines.
- Last-known-high. The merchant remembers the highest price they ever charged and sets compare-at-price to that. Article 6a is forward-looking from the discount date, not retrospective to any earlier peak; the past-30-days window is what counts.
Once the divergence is set up, it persists indefinitely. Every time the merchant runs a promotion (a flash sale, an end-of-season clearance, a marketing-driven temporary markdown), the compare-at-price stays static while the actual selling price moves. Each promotion drives the 30-day low further from the compare-at-price figure. Within a few months of normal commercial activity, the strikethrough on a typical Shopify product is no longer the Article 6a prior price by a substantial margin.
The drift, in numbers
A merchant launches a product at EUR 100. They set compare-at-price to EUR 130 (a 30% aspirational anchor). The product sells well at EUR 100 for the first few months. The compare-at-price stays at EUR 130; the strikethrough always displays EUR 130.
In April the merchant runs a one-week flash sale at EUR 80. After the sale, the price returns to EUR 100. The compare-at-price stays at EUR 130.
In May the merchant runs an end-of-spring clearance at EUR 75 with a “25% off EUR 100” sticker. The compare-at-price stays at EUR 130.
Under Article 6a, the prior price for the May sale is the lowest in the previous 30 days, which includes the April flash at EUR 80. So the prior price is EUR 80, not EUR 100, and certainly not EUR 130. The store's strikethrough at EUR 130 is off by EUR 50. The “25% off” sticker is also wrong; the actual reduction from the prior price is roughly 6%. Both the strikethrough and the percentage figure are misleading announcements.
What regulators look for
Investigators do not need access to your Shopify admin to spot this pattern. The method they use is straightforward:
- They pick a discounted product on your storefront on the day of the inquiry.
- They check your past 30 days of price history for that product. Sources they use include the Wayback Machine, archived sitemaps, your own published price feeds (if accessible to comparison sites), and consumer complaint records that include screenshots.
- They identify the lowest price applied in those 30 days.
- They compare that figure against your strikethrough.
If the strikethrough is higher than the 30-day low, the regulator has a per se Article 6a violation. The case can then be expanded across more products and longer time periods using the same method.
This is what produced the AGCM cases against Yoox Net-a-Porter and PoltronesofĂ , and the UOKiK cases against Zalando and Temu. In each, the regulator identified a consistent pattern: the displayed reference price was systematically higher than the trader's own actual selling prices in the relevant window. The pattern was visible from outside the store.
How to fix the divergence
You have three paths to compliance. They differ in effort and quality of result.
- Path 1: Drop strikethroughs entirely. If you stop displaying any price reduction announcements (no strikethroughs, no percentage stickers, no “sale” labels), Article 6a does not apply. Some merchants choose this for short windows while they build proper tracking. Commercially it usually costs conversion and is rarely a long-term answer.
- Path 2: Build a tracking system in-house. Store daily price snapshots for every product in a database, compute the 30-day low daily, and override compare-at-price (or render a separate field on your theme) with the computed figure. This requires engineering work (a daily cron, a database, a theme integration) and ongoing maintenance. It also requires multi-market awareness if you use Shopify Markets.
- Path 3: Install an app that does this. Apps that track 30-day prior prices automatically (Complimus is one) run on top of Shopify, record price changes daily without merchant intervention, and render the computed Article 6a figure in your theme alongside the selling price. Install is typically under 10 minutes; no development work required.
The transition between non-compliant and compliant is the awkward middle: from the day you start tracking, you have 30 days before the system can display a fully-verified prior price. During that 30-day bridge, options are to pause strikethroughs, display the figure with a disclosure that tracking just started, or backfill historical prices from your Shopify admin (if reliable).
Frequently asked questions
Can I still use compare-at-price for other purposes after fixing this?
What about strikethroughs in product feeds I send to Google Shopping or comparison sites?
Does this apply if I am a US store selling to EU shoppers via Shopify?
Can I display MSRP alongside the legal prior price?
What if I am only running a small temporary promotion, not a full sale?
