Blog · 28 August 2026 · 8 min read

EU Guarantee Notice 2026: what Magento 2 merchants need to change

From 27 September 2026, traders selling goods to consumers in the EU must show a harmonised notice about the legal guarantee of conformity. It is a small piece of artwork with a very specific set of rules attached, and most of the work in a Magento shop is not displaying it — it is displaying it in the right language, in the right places, and only in the store views where it belongs.

What the Regulation actually requires

Commission Implementing Regulation (EU) 2025/1960 introduces a harmonised notice informing consumers of the legal guarantee of conformity — the statutory right, already in force everywhere in the Union, to a remedy when goods turn out not to match what was promised. The right is not new. What is new is the obligation to tell people it exists, in a form the Commission has designed, so that it looks the same in every shop in every member state.

Three properties of the obligation shape everything else:

It sits at shop level, not per product. You are not labelling individual items. The notice belongs to the shop as a whole, which is why it can be satisfied once rather than on thousands of product pages.
It has to be prominent. A link in a legal menu that nobody opens is not the point; the notice is meant to be seen by someone who is buying.
It applies to consumer sales. The Regulation builds on consumer law, so it follows from selling goods to consumers rather than from any particular product category. A shop selling only to other businesses is a different case, and worth confirming with an adviser rather than assuming either way.

The date

27 September 2026. That is not far away, and it is the kind of deadline that looks comfortable until you notice it lands inside the pre-Christmas code freeze that most merchants run from October. If your shop has a release process worth the name, the practical deadline is earlier than the legal one.

The part everyone underestimates: 24 languages

The notice exists in all 24 official EU languages, and the consumer is entitled to see it in the language of the shop they are buying in. The Commission publishes the artwork; you do not get to typeset your own.

For a single-language German shop this is one file. For anyone running a multi-store Magento installation it is the whole problem in miniature: a store view per country, a locale per store view, and a notice that has to follow the locale automatically. Doing that by hand means sourcing 24 files, keeping them unaltered — no cropping, no recolouring, no stretching to fit a column — and wiring each one to the right store view. Doing it once is tedious. Doing it again every time the storefront grows a market is the actual cost.

Where the notice goes in a Magento storefront

The Regulation says "prominently, at shop level" rather than naming CSS selectors, so there is judgement here. In a Magento shop there are four places that are defensible, and they are worth thinking about separately:

Checkout, immediately before the order is placed. The strongest position: the customer is about to commit, and the information is in front of them at that moment.
A footer link on every page. The cheapest and least intrusive, and the one most likely to be considered a minimum rather than a maximum.
A product-page tab, beside Details and More Information, where a shopper comparing items will find it.
The order confirmation email, which is the record the customer keeps.

How prominent to be is a commercial decision as much as a legal one, and the honest answer is that nobody has case law yet. A shop that wants the lightest footprint keeps the footer link. A shop that wants to be obviously beyond argument keeps the checkout placement too.

What to change, concretely

Work out which store views are in scope. A store view selling outside the EU should not show an EU consumer notice, and switching it off per store view is easier than explaining it later.
Map locale to notice language. Whatever you build has to pick the file from the store view's locale, not from a global setting.
Pick your placements from the four above and decide them per store view, because prominence expectations differ by market.
Check the theme. Luma and Hyvä are different frontends, and an implementation written for one usually does not work on the other — see showing the notice on a Hyvä storefront.
Check whether the GARAN label also applies to you. It is the Regulation's second visual and a genuinely different obligation — see notice or GARAN label.
Test the confirmation email. It is the placement most often forgotten, because it is the one nobody sees while clicking around the storefront.

Build or buy

None of this is difficult. It is just wide: 24 files, per-store-view scoping, four placements, two themes, an email template, and a switch for the markets where it does not apply. A shop with one locale and one theme can reasonably do it in an afternoon. A multi-store, multi-language installation is a project, and it is a project that has to be redone the next time a market is added.

We build EU Guarantee Notice, a Magento 2 extension that puts the official notice on a Luma or Hyvä storefront in all 24 languages.

This article explains how we read Regulation (EU) 2025/1960 while building an extension for it. It is not legal advice. Whether, when and where the notice applies to your business remains your responsibility, and is worth confirming with a qualified adviser.