Most feed-driven creative templates build a discount badge the same way: take price, take sale_price, print the difference as "-30%" and strike through the regular price. That logic is fast, and in the EU and Turkey it is often wrong. EU law requires any announced price reduction to be measured against the lowest price you charged in at least the previous 30 days, and when the European Commission and authorities from 23 Member States plus Iceland and Norway checked traders during Black Friday and Cyber Monday, one in three displayed discounts incorrectly (30% of 314 traders reviewed). Turkey rewrote its own rule in July 2026.
This playbook is for e-commerce teams and agencies generating catalog, dynamic or banner creative from a product feed. By the end you will be able to add a prior-price field per SKU and per channel, compute a defensible discount, suppress badges that cannot be justified, and QA the result before Black Friday creative ships.
Why the feed's price field is not your legal reference price
In a Google or Meta feed, price is the current regular price and sale_price is the discounted one. Neither attribute knows what you charged two weeks ago. If a product ran on promotion earlier in the month, its lowest recent price may be well below price, and a badge calculated from price overstates the saving.
That is exactly the scenario the Court of Justice of the EU ruled on in Aldi Süd (C-330/23, 26 September 2024). Aldi advertised a "price highlight" against a pre-offer price of €1.69, but the lowest price in the previous 30 days had been €1.29, the same as the "reduced" price. The Court held that a reduction stated as a percentage or as a promotional claim must be based on the lowest price applied during the prior 30 days. The case concerned printed brochures, which matters for us: the rule follows the advertisement, not just the product page.
The Commission's guidance on Article 6a says the same thing from the other side: the rule applies to price reduction announcements "in all distribution channels" (section 1.1), percentage reductions must be calculated from the prior price (section 2.1), and where channels charge different prices, each channel's own 30-day low applies (section 2.1).
The rules a discount template has to satisfy, market by market
Four separate rule sets touch the same badge. Two are law, two are platform display rules, and they do not agree with each other.
| Rule set | Reference price | Window | Channel scope | Notable exceptions |
|---|---|---|---|---|
| EU, Directive 98/6/EC Art. 6a | Lowest price you applied, including earlier promotional prices | Not shorter than 30 days | Each sales channel separately | Member States may set rules for perishables, shorter periods for goods on sale under 30 days, and a carry-over for progressive reductions |
| Turkey, Regulation on Commercial Advertising and Unfair Commercial Practices, as amended in Official Gazette No. 33297, 1 July 2026 | Lowest price applied, shown struck through as the pre-discount price | Last 10 days before the discount starts | Only the channel where the discount runs (Erdem & Erdem summary) | Perishables and services use the last price before the discount; conditional offers are covered by the discount rules |
| Google sale price annotation (Merchant Center Help) | Your submitted price | Base price valid 30 days in the past 200 in FR, DE, IT, NL, ES, UK and others | Google's own surfaces | Discount must be between 5% and 90% |
| Meta discount overlay (catalog reference) | Reads price and sale_price | None | Meta catalog ads | sale_price is required to use a discount overlay |
Two corrections to what you will read elsewhere. First, many Turkish guides still quote 30 days. That was the 2022 rule; the July 2026 amendment replaced it with 10 days, in force from 1 August 2026 according to press and law-firm summaries. Second, a Google sale annotation appearing on your ad is not evidence that your discount is lawful. Google checks a different window against a different reference price.
Step-by-step: building compliant discount creative from a feed
Step 1: Inventory every place a discount is rendered
List each template and each layer that makes a reduction claim: percentage badges, struck-through prices, "was/now" pairs, "save €20" stickers and generic "Sale" frames. Generic frames count too. The Commission guidance treats "sales" and "special offers" that imply a reduction as announcements (section 1.1), although for a general announcement the prior price can sit on the product page price field rather than on the banner (section 2.2). Mark each layer as specific claim (a number) or general claim (a word).
Step 2: Build a per-channel price history and derive prior prices
You need, for each SKU and each channel, the lowest price over the legal window ending the day before the discount starts. The best source is your e-commerce platform or ERP price log. If you do not have one, store a dated snapshot of price and sale_price every time the feed refreshes. In Feedance that is up to daily on Essentials and up to hourly on Business, per the pricing page; a price that existed only between two snapshots will be missed, so treat snapshot history as a backstop, not the record.
Compute two fields: prior_price_30d for EU storefronts and prior_price_10d for Turkish ones. Bring them into the creative pipeline through a supplementary feed matched on ID, so the source catalog stays untouched. Keep these fields out of your Merchant Center and Meta exports; they are inputs for the template, not channel attributes.
Step 3: Compute the displayable discount
The formula is (prior_price - sale_price) / prior_price, rounded down to a whole percent. Rounding down is our house rule: rounding 7.8% up to 8% is a claim you cannot fully support. Here is a worked set for a Black Friday campaign starting 27 November 2026.
| SKU / market | price | sale_price | Price history | Prior price | Naive badge | Compliant output |
|---|---|---|---|---|---|---|
| KB-1001 / DE | 129.00 EUR | 89.00 EUR | Flat for 60 days | 129.00 EUR (30d) | -31% | -31%, strike 129.00 |
| KB-1002 / DE | 79.00 EUR | 59.00 EUR | 64.00 EUR promo, 6 to 12 Nov | 64.00 EUR (30d) | -25% | -7%, strike 64.00 |
| KB-1003 / DE | 49.00 EUR | 45.00 EUR | 44.00 EUR promo, 11 Nov | 44.00 EUR (30d) | -8% | No badge, plain 45.00 |
| KB-2001 / TR | 4999.00 TRY | 3499.00 TRY | 3999.00 TRY promo, 11 to 12 Nov | 4999.00 TRY (10d: 17 to 26 Nov) | -30% | -30%, strike 4999.00 |
KB-2001 shows why the market matters. The 11 November promotion falls outside Turkey's 10-day window, so the full -30% is supportable there. Sold in a German store with the same history, the 30-day low would be 3,999 and the badge would drop to -12%.
Step 4: Gate the badge with rules, not designer judgment
Turn the calculation into fields the template can read. With feed rules or any equivalent if-then logic, apply per channel:
- If
sale_priceis empty orprior_priceis less than or equal tosale_price, setdiscount_badge = offandstrike_priceempty. - If the computed discount is below 5%, set
discount_badge = off. This threshold is not legal; it matches Google's 5% floor so your creative and your Shopping annotation tell the same story. - Otherwise set
discount_badge = on,discount_pct_displayto the rounded-down value andstrike_pricetoprior_price, never toprice.
The resulting row for KB-1002 looks like this:
<item>
<g:id>KB-1002</g:id>
<g:price>79.00 EUR</g:price>
<g:sale_price>59.00 EUR</g:sale_price>
<g:sale_price_effective_date>2026-11-27T00:00+01:00/2026-11-30T23:59+01:00</g:sale_price_effective_date>
<prior_price_30d>64.00 EUR</prior_price_30d>
<strike_price>64.00 EUR</strike_price>
<discount_pct_display>7</discount_pct_display>
<discount_badge>on</discount_badge>
</item>
Step 5: Rebind the template layers
In the creative template, bind the struck-through layer to strike_price and the badge to discount_pct_display, and show both only when discount_badge = on. Design a second state for off that still looks finished: current price, campaign frame, no reduction claim. Tools like Feedance's Image Creative read g:price and g:sale_price for the price layer, so the rebinding to your new fields is the step teams most often skip.
Scale makes this urgent. Karaca produced 10,000 Black Friday creatives in two hours from one template. A wrong binding at that scale is not one bad ad; it is the whole catalog.
Step 6: Handle timing and stepped campaigns
Calculate prior prices from the day before the discount starts, and regenerate creative when sale_price changes, not on a fixed weekly cycle. Do not raise regular prices in the weeks before Black Friday: the lowest price in the window still governs, so a pre-sale increase gains nothing and is the practice the rule targets. If the discount deepens from Black Friday to Cyber Monday without interruption, the EU allows Member States to let you keep the prior price from before the first step (Art. 6a(5)), and the Commission reads that exception narrowly (section 4.3). Check whether your target country uses it before relying on it.
Step 7: QA before the campaign goes live
| Check | Pass condition |
|---|---|
| Strike-through source | Every struck price equals prior_price for that channel |
| Badge arithmetic | Recomputed percentage on a 50-row sample matches discount_pct_display |
| Suppression | No badge where prior_price is at or below sale_price |
| Market window | EU rows use 30-day history, TR rows use 10-day history |
| Channel separation | Marketplace prices are not mixed into webshop history |
| Landing page match | Product page shows the same prior price and sale price as the creative |
| Off state | Rendered fallback reviewed for at least five SKUs |
What this playbook doesn't cover
This is an operational method, not legal advice, and it has limits. Member States implement Article 6a with their own options for perishables, new arrivals and progressive reductions, so a pan-EU rule set needs a country-by-country check. Services and digital content fall outside Article 6a (guidance section 1.1), while "buy three, get 30% off" style conditional offers sit outside it in the EU but inside Turkey's discount rules. The UK is not covered: it has no Article 6a, and reference pricing there is judged under CMA and ASA guidance, as Lewis Silkin outlines.
The weakest link is price history. A feed tool sees prices only when it syncs, so your platform or ERP price log is the better legal record, and if your team already keeps price history in a dedicated pricing or BI system, compute the prior price there and pass it in. Marketplaces such as Trendyol run their own discount displays, which this method does not control.
FAQ
Does the EU 30-day rule apply to ad creative or only to the product page?
It applies to price reduction announcements in all distribution channels, according to the Commission guidance. The Aldi Süd ruling itself concerned advertising brochures. A percentage badge on a catalog ad is an announcement.
Can I strike through the regular price if the product was cheaper two weeks ago?
Not in the EU. The struck-through prior price must be the lowest price you applied in the 30 days before the reduction, including earlier promotional prices. In Turkey the same logic applies over the last 10 days.
What changed in Turkey in 2026?
The amendment published on 1 July 2026 replaced the 30-day lookback with a 10-day one, made the reference channel-specific and brought conditional offers under the discount rules. Perishables and services use the last price before the discount.
Is a Google sale price annotation proof that my discount is compliant?
No. Google requires your base price to have been valid for 30 days in the past 200 in many markets and a discount between 5% and 90%. It does not check your lowest price over the legal window.
What about products launched less than 30 days ago?
Member States may allow a shorter reference period for new goods but cannot exempt them entirely. Seasonal goods returning after a break are not new arrivals under the Commission guidance.
Does a generic "Black Friday Sale" frame need a prior price?
Under the Commission guidance, a general announcement can be supported by the prior price shown at the point of sale, such as the online price field, rather than on the banner. Any specific number on the creative needs the full calculation.
How often should prior prices be recalculated?
At minimum daily, and always on the day before a discount starts. Recalculate whenever sale_price changes so the badge and the landing page never drift apart.
See the conditional badge setup in a live template
If you want to see how a prior-price field, rule-driven badge states and a no-discount fallback work together in a feed-driven template, request a Feedance demo and bring one of your Black Friday templates.

Co-founder of Feedance, where he leverages his background as a computer engineer and marketer to drive analytical insights. With a strong focus on transforming data into actionable strategies, he is dedicated to helping brands achieve significant growth in the digital landscape.
LinkedIn



















