EU legal-guarantee notice 2026: a merchant implementation guide

What to review for 27 September 2026

Current European Commission guidance says EU rules introduce harmonised consumer-guarantee information from 27 September 2026 for transactions within their scope and discusses sellers of consumer goods. That does not make every merchant, product or WooCommerce transaction automatically subject to the same display requirement.

Applicability depends on the product, buyer, transaction, target market and applicable national law. Merchants must assess that scope, national implementation, language, placement and any product-specific obligations. An implementation tool can place a supplied file consistently after that decision; it cannot determine whether an individual business or sale is legally compliant.

• Date to review against the rules that apply: 27 September 2026.
• Product scope to review: relevant consumer-goods transactions, not every catalogue item by default.
• Buyer, transaction, target market and national implementation remain part of the merchant assessment.
• Online presentation: the harmonised notice must use the colour version.
• The supplied design, including its QR code, is not a canvas for merchant edits.

Start from the official file, not a recreation

The Commission publishes practical guidance and high-resolution files for all EU languages. Use that distribution as the source of truth. Rebuilding the artwork in a page builder, translating text inside the graphic, changing colours or compressing it until the QR code becomes unreliable introduces avoidable risk.

Keep a small evidence record: the source URL, download date, chosen language, source-file checksum and the person who approved the storefront result. That record makes later reviews faster when the Commission updates guidance or when a theme change affects display.

• Download from the European Commission publication page.
• Preserve the full artwork and aspect ratio.
• Use meaningful alternative text without repeating every word in the image.
• Retest the QR code after image optimisation and responsive resizing.

Choose placements as a review exercise

Your Europe says the notice must be displayed prominently and gives a general website reminder as an e-commerce example. The right technical placement depends on the store’s purchase flow, theme and professional interpretation. Product, cart and checkout surfaces are useful review points because they sit close to the decision to buy; a site-wide location may also be appropriate.

Do not judge placement only from a logged-in desktop session. Check a guest journey, a narrow mobile viewport, the classic and block checkout experiences actually used by the store, translated routes, cached pages and any accelerated or headless storefront. A notice that exists in source code but is hidden by an accordion, clipped by CSS or absent from the active checkout template is not a reliable implementation.

A defensible merchant workflow

Assign one owner for source review and one for storefront verification. Record the pages and languages tested, keep screenshots, and set a review date before September. Repeat the check after theme, checkout or multilingual-plugin changes. For legal scope and country-specific interpretation, use qualified advice rather than a plugin settings screen.

Notice27 stable 1.2 is designed for the repetitive WordPress work in that workflow after a merchant determines that the notice applies to a consumer-goods journey: selecting a supplied language file, placing it on chosen WooCommerce surfaces and keeping the artwork self-hosted. It does not classify products or transactions, modify the notice, read orders, or represent an endorsement by the European Union.