Skip to main content

Blog Operations

Guide · E-commerce

Retrofitting a Shopware 5 shop for the legal duties of 2026 and 2027

Published on
Updated on
Reading time
27 min

With no update promised by shopware AG, Shopware 5 shops have to adapt to the new rules of 2026 and 2027 themselves. This guide shows where each duty sits in the shop code, from the withdrawal button to the GARAN label, and how we approach each one.

In short: shopware AG has not promised an update, so Shopware 5 shops have to adapt to the duties of 2026 and 2027 themselves, for example with plugins and theme changes. The places most affected are the way customers withdraw, the final checkout page, the order confirmation email, product texts and filters, deferred-payment methods and chatbots.

We are developers, not lawyers. Whether and how a duty applies to your shop is a question for your legal adviser. Each section shows where a duty sits in the shop code and how we go about it ourselves.

Why do Shopware 5 shops have to do this themselves?

In an announcement on the future of Shopware 5 published on 16 August 2022, shopware AG said that Shopware 5 was to be supported until July 2024. Its migration page sets out the support phases: bug fixes, minor improvements and legally required adjustments until the end of July 2023, then security updates until the end of July 2024.

The README of the official Shopware 5 repository on GitHub, which we read on 2 November 2026, says the repository is no longer actively monitored or maintained. Updates may occur occasionally, it adds, but this cannot be guaranteed.

The latest release is v5.7.20, published on 5 June 2025. Its composer.json allows PHP 7.4, 8.0, 8.1 and 8.2, so nothing newer than PHP 8.2. The table of supported versions on php.net shows security support for PHP 8.2 until 31 December 2026; active support ended on 31 December 2024.

For retrofitting, Shopware 5's hook manager lets you extend class methods by running code before, after or instead of the original method, provided the method is neither final nor static. Every controller can be hooked, because the base class Enlight_Controller_Action implements the interface Enlight_Hook. The core modules, including the basket module sBasket, implement it too, so they can be hooked as well.

Plan the changes as a plugin of your own or a self-contained theme change, not as edits to the Shopware core, and make any retrofitted code match your shop's PHP version. Our guide to the end of Shopware 5 support sets out the options for a live shop, and our Shopware 5 overview covers operation, compliance and migration.

What applies already, and what is still ahead?

Since 19 June 2026, Member States have applied the provisions transposing Directive (EU) 2023/2673, including those on the withdrawal function. The German act amending consumer contract law came into force on that date, subject to exceptions; two of its parts followed on 27 September 2026. Implementing Regulation (EU) 2025/1960, which sets the design and content of the legal guarantee notice and the guarantee label, has applied since 27 September 2026. Since the same date, Member States have applied the measures transposing Directive (EU) 2024/825, which also covers environmental claims. The German amendment to the Act against Unfair Competition (UWG) came into force then too, except for one provision that had already applied since 19 June 2026.

The AI Act has applied since 2 August 2026, except where Article 113 provides otherwise for particular parts; its transparency rules in Article 50 are not among those exceptions. The reporting obligations of the Cyber Resilience Act have applied since 11 September 2026.

Three further dates matter. From 20 November 2026, Member States apply the provisions transposing the new Consumer Credit Directive, and with them come new rules on deferred payment. For providers of generative AI systems placed on the market before 2 August 2026, the AI Act sets 2 December 2026 as the deadline for machine-readable marking. And the Cyber Resilience Act generally applies from 11 December 2027, including the duties of distributors.

Deal first with the duties that already apply, then turn to your deferred-payment methods. If you offer generative AI systems yourself, check the machine-readable marking too.

What does the law ask of the withdrawal button?

What shoppers see as a withdrawal button is, in law, an electronic withdrawal function. Directive (EU) 2023/2673 inserted it into the Consumer Rights Directive as Article 11a, for distance contracts concluded online. In Germany the rule is section 356a of the German Civil Code (BGB; source in German). The function must be labelled, in an easily legible way, 'Vertrag widerrufen' (withdraw from contract) or with another equivalent unambiguous wording. The English version of the Directive has its own label, 'withdraw from contract here', which is not a translation of the German one.

It must also be continuously available on the online interface throughout the withdrawal period, prominently placed and easily accessible. The consumer must be able to provide or confirm their name, details identifying the contract or the part of it they want to withdraw from, and the electronic means of communication for the acknowledgement of receipt.

They must then be able to send the withdrawal statement through a confirmation function labelled 'Widerruf bestätigen' (confirm withdrawal) or with another equivalent unambiguous wording. Once it has been used, the trader must send an acknowledgement of receipt without undue delay, on a durable medium, containing at least the content of the withdrawal statement and the date and time of receipt.

Recital 37 of the Directive, an explanatory passage rather than a binding rule, adds that a consumer who has already identified themselves, for example by logging in, should be able to withdraw without identifying themselves again.

The explanatory memorandum to the German government bill (Bundestag printed paper 21/1856; source in German) goes further. It is the legislator's explanation, not statutory text. It says the function should be directly accessible from every subpage. For a function shown in the footer, for example, it calls for special measures for good legibility, such as the choice of colour or contrast and a prominent placement. As a rule, it says, the function must be reachable without logging in. Placing it only in the logged-in area is enough only if the contract can be concluded solely by setting up a customer account, and only to that extent. The Bundestag's legal affairs committee takes the view that section 356a BGB does not rule out hyperlinks or QR codes.

Under Article 246a section 1(2) no. 1 of the Introductory Act to the Civil Code (EGBGB), if there is a right of withdrawal, the trader must also tell the consumer, where applicable, that the withdrawal function exists and where it is placed. The model instructions on withdrawal in Annex 1 to the EGBGB include a text block on the online withdrawal function.

In Shopware 5, the instructions on withdrawal are a shop page, Shopware's name for a content page. In the standard template of the final checkout page, checkout/confirm.tpl, a text snippet links to it when the setting revocationnotice is active. Check that this shop page mentions the withdrawal function and says where to find it.

A new proposal also deals with the label. On 11 November 2026 the European Commission presented its proposal for a Digital Fairness Act. Under its Article 24(2), the withdrawal function would have to be labelled 'withdraw from contract here' or with an unambiguous corresponding formulation. This is a proposal, not law in force, and section 356a BGB still governs. Keep the button's label editable as a snippet rather than fixed in the template. Our radar entry on the Digital Fairness Act explains what the proposal would change.

How we added the withdrawal button

We added the withdrawal button using a purchased Shopware 5 plugin. In the theme, we put a placeholder into the footer block frontend_index_footer_column_service_hotline_content. The plugin replaces it through an output filter with the link 'Vertrag widerrufen', which leads to the plugin's own form page. Because the footer template inherits from the parent theme, the link appears on every page. We used the same pattern in other installations that are run separately; in one of them we put the link into the footer's service column and styled it as a button.

The placeholder sits in a wrapper element. A CSS rule using :has() hides the wrapper while the plugin is inactive, so the theme can safely be deployed before the plugin. In each theme we style the link as a prominent, clearly separated button and choose the hover and text colours by measuring their contrast and checking it against the WCAG AA threshold of at least 4.5:1 for text. We carried out the theme integration in several shops in mid-June 2026.

The plugin provides its own controller page with a form that looks up the order lines by surname and order number. Customers can then choose the items they want to withdraw from, and in a second step they confirm the withdrawal. The plugin then uses Shopware email templates to send two messages: an acknowledgement of receipt to the customer, showing the date and time of receipt, and a notification to the shop owner. Its text snippets come only in German and English; we translated them for the other shop languages ourselves, and a legal review of these translations is planned before they go live.

Decide first where your theme can show the link permanently and prominently. Then run the whole flow in every shop language, up to the acknowledgement of receipt, and have your legal adviser check the prominence of a footer link. Our radar entry on the withdrawal function covers the footer and the logged-in area in more detail.

Where does the legal guarantee notice go in Shopware 5?

We use two places: the final checkout page and the order confirmation email. On the final checkout page, we place the notice below the order button, in the block frontend_checkout_confirm_confirm_table_actions, so the customer sees it before placing the order. The email is built from the email template sORDER by the sendMail() method of the core class sOrder.

The duty itself is in the EGBGB. Under Article 246a section 1(1) no. 11, before a distance contract is concluded, the trader must prominently point out the legal guarantee for goods and its main elements, including the minimum duration of two years, using the harmonised notice in Annex I to Implementing Regulation (EU) 2025/1960. For distance contracts concluded through an online interface, the notice must be in colour. It carries a QR code; in our plugin, a clickable link next to the notice leads to the same destination, the EU's Your Europe portal in the language concerned.

The Commission's practical guidelines for sellers and producers add examples. Their disclaimer says they are a preliminary view of the Commission services, not an official Commission position, and that their examples are not exhaustive. Online, they say, the notice should be displayed prominently, for example as a general reminder on the seller's website; the Your Europe page on the notice and the GARAN label gives the same example. Another example in the guidelines is a sentence on the product check-out page about the consumer's legal guarantee rights, with the notice appearing on the first mouse click or mouse roll-over. The guidelines also say the notice should be included in the confirmation email, and that a clickable link to the same destination as the QR code should always be available.

How our plugin adds the notice

We built our own Shopware 5 plugin for the legal guarantee notice. At the end of September 2026 we deployed it in several shops and, on the same day, in another installation that is run separately.

An event subscriber on Enlight_Controller_Action_PostDispatchSecure_Frontend_Checkout passes the notice data to the view, but only in the confirm action. It picks the official graphic for the shop's locale, or a default language where no file is bundled for that language, and embeds it in full, in colour and unaltered, linked to the full-size file so it can be enlarged on small screens.

The plugin also attaches the notice as a PDF to the order confirmation email, through the filter event Shopware_Modules_Order_SendMail_Filter. If attaching the PDF fails, we log the error and send the confirmation anyway: a missing attachment must never stop it going out.

Where a one-page checkout plugin registers its own templates, we put the notice's template directory at the start of the template chain, so that other plugins do not override the extended block. With a narrow order column, we show the notice at full width below the checkout columns, so that its text stays legible.

Before adding anything, find out which plugins alter your checkout templates. Test the final checkout page on narrow screens, and test the order confirmation email with an attachment deliberately missing.

When does the guarantee label come into play?

The harmonised label, which the Commission calls the EU GARAN label, applies only in particular cases. Under Article 246a section 1(1) no. 11a EGBGB, the trader has to use it only where the producer gives the consumer a commercial guarantee of durability at no additional cost, covering the entire goods and lasting more than two years. A further condition is that the producer makes this information available to the trader. Under section 312j(2) BGB, in electronic commerce that information must be given clearly, comprehensibly and prominently immediately before the consumer places the order.

The design comes from the Implementing Regulation: the letters 'XX' in the label are replaced by the duration in years of the producer's guarantee. Shown as a nested display, the label must appear in full on the first mouse click, the first mouse roll-over, or the first touch or expansion on a touchscreen.

In this guide, "producer" means the maker of the goods who gives the guarantee. In Shopware 5, the record that holds the maker's data is called "manufacturer", and the next section uses that word.

How our guarantee label plugin works

Before building anything, we searched the active product texts in all languages for guarantee statements and asked the merchant, among other things, which producers in the range give a guarantee of more than two years, including producers not mentioned in any text.

The plugin adds free-text fields in Shopware 5. On the manufacturer record, they hold a guarantee period for all of that manufacturer's products and the guarantee conditions. On the product, per variant, they hold a different number of years, a "no guarantee" option and a model identifier. The value on the product overrides the one on the manufacturer record. The label appears only for guarantees of more than two years, stated in whole or half years, and only when guarantee conditions are stored. We use it only for free guarantees covering the entire goods. Lifetime guarantees get no label, because the label can only show a number of years; a plain notice with a link to the guarantee conditions can optionally appear instead.

On the product page, the label sits in the template block frontend_detail_index_buybox, below the buy button. Here we use the nested display: a small icon showing the number of guarantee years opens the full label in an overlay on the first click or tap, even after a variant switch that reloads only part of the page. In the basket and on the final checkout page, the label is attached to the line item concerned, in the block frontend_checkout_cart_item_details_inline, so it stays visible directly before the order is placed. The order confirmation email carries the completed label as a PDF for each product concerned, and the guarantee conditions once per manufacturer.

Orders entered in the backend or taken by phone are deliberately not covered: they get neither label nor attachments. Check whether such orders in your shop need a solution of their own.

Environmental claims in product texts and filters

The rules on environmental claims come from Directive (EU) 2024/825 on empowering consumers for the green transition and, in Germany, from the Third Act amending the UWG. The UWG annex lists practices that are always prohibited towards consumers. Among them are these three, which concern environmental claims:

  • displaying a sustainability label that is neither based on a certification scheme nor established by public authorities (point 2a);
  • making a generic environmental claim where the trader cannot demonstrate recognised excellent environmental performance on which the claim is based (point 4a);
  • claiming, on the basis of offsetting greenhouse gas emissions, that a product has a neutral, reduced or positive impact on the environment in terms of those emissions (point 4c).

Under the UWG, an environmental claim also covers text, images, graphic elements or symbols, such as labels, brand names, company names or product names, as long as they are not legally required. A generic environmental claim is one that is not contained in a sustainability label and whose specification is not given clearly and prominently on the same medium. In a Shopware 5 shop, such claims can therefore sit in descriptions, filter values, product names, manufacturer names and product images.

Recital 9 of the Directive gives examples of generic environmental claims, among them "environmentally friendly", "eco-friendly", "green", "climate friendly", "carbon friendly", "energy efficient" and "biodegradable". The list is not exhaustive. If your shop sells in German, search the filter values for the German equivalents.

Search all of these places in every shop language, including free-text fields that your templates print, as with the guarantee label. A complete list of matches gives your legal adviser a basis for assessing them.

What changes for pay by invoice from 20 November 2026?

Three points matter for pay by invoice: the payment term, the costs of late payment, and whether a third party is involved. Among other things, they decide whether your pay-by-invoice offer falls under an exemption from the consumer credit rules.

The rules come from the new Consumer Credit Directive (EU) 2023/2225 and Germany's transposing act of 12 May 2026.

In German law the exemption is in section 506 BGB. In the version applying from 20 November 2026, section 506(1), second sentence, lists contracts that are not financial accommodation, so the consumer credit rules do not apply to them. One is the case where the trader itself, without a third party and free of charge, gives the consumer up to 50 days after delivery to pay, and the consumer can incur only limited costs for paying late.

Section 506(1), third sentence, has a special rule for traders that are not micro, small or medium-sized enterprises within the meaning of Commission Recommendation 2003/361/EC and that offer information society services for which distance contracts are concluded. For these traders, the exemption applies only if the period for full payment is no longer than 14 days after delivery, and only if no third party acquires the claim arising from the deferred payment. A transitional provision in Article 229 section 71(1) EGBGB keeps the previous law for obligations relating to financial accommodation that existed before 20 November 2026.

The same act introduces a German supervisory law on sales financing, the AbsFinAG, under which creditors as defined in that act must be registered by the Federal Financial Supervisory Authority (BaFin). Suppliers that, as a secondary function, grant interest-free deferred payments only for their own goods and services are exempt from registration, but only if they are SMEs. Creditors covered by the act that were already in business before 20 November 2026 may carry on without registration for up to twelve months afterwards.

If your order confirmation email, built from the sORDER template, states a payment term, that term should match the rule that your legal adviser confirms applies to your shop. These steps help:

  1. Note every deferred-payment method and every place where its payment term appears.
  2. Check the late-payment costs in your texts and email templates.
  3. Clarify whether the claim (that is, the amount the customer owes) stays with your shop or passes to a third party, such as an external invoice service.
  4. Have your legal adviser assess the special rule for traders that are not SMEs, and the registration duty.

What do chatbots and AI images have to disclose?

For chatbots, the duty lies with the provider. Under Article 50(1) of the AI Act, providers must ensure that AI systems intended to interact directly with people are designed so that those people are informed they are interacting with an AI system. The exception is where this is obvious to a reasonably well-informed, observant and circumspect person, given the circumstances and the context of use. Under Article 50(5), the information must be clear and distinguishable, given at the latest at the first interaction or exposure, and conform to the applicable accessibility requirements.

The AI Act defines both roles. A provider develops an AI system, or has one developed, and places it on the market or puts it into service under their own name or trademark. A deployer uses an AI system under their authority, except in the course of a personal non-professional activity.

The current version of the Commission's guidelines on these obligations, C(2026) 7702 final, is dated 5 November 2026. By their own account they are non-binding, and only the Court of Justice of the European Union can ultimately interpret the AI Act authoritatively. They list chatbots in customer support and e-commerce among the examples covered by Article 50(1). The obviousness exception, they say, should be limited to cases that leave almost no doubt about the nature of the interaction for an average person in the targeted audience. It does not apply, in their example, to chatbots on online platforms or helpdesk tools whose replies users may perceive as human-generated.

As one way of informing people in writing, the guidelines describe a chatbot that starts the conversation by mentioning that it is based on AI technology. They also count a company as a provider if it develops a chatbot in-house and puts it into service for its own use, under its own name or trademark.

Under Article 50(2), providers of AI systems that generate synthetic audio, image, video or text content must ensure that the outputs are marked in a machine-readable format. The marking duty does not apply where the system performs an assistive function for standard editing or does not substantially alter the input data. For providers of generative systems placed on the market before 2 August 2026, the Digital Omnibus on AI sets a deadline of 2 December 2026 to comply with Article 50(2).

Deep fakes are a matter for deployers. Under Article 50(4), deployers of an AI system that generates or manipulates image, audio or video content constituting a deep fake must disclose that the content has been artificially generated or manipulated. The guidelines give an AI-generated product image in advertising or on packaging as an example of a deep fake where it can mislead about the actual product's appearance, characteristics or use. The disclosure, they say, should be perceivable without technical tools, for example through visible or audible labels.

The guidelines speak of advertising and packaging. In our reading, a product image in an online shop raises the same question, but that is our inference, not a statement of the guidelines. For your shop, that leaves four questions:

  • Does every chat tool open with a notice that the customer is dealing with an AI system?
  • Have you asked the suppliers of tools that generate texts or images about machine-readable marking? Under Article 50(2) it is the provider's duty.
  • Do AI images or videos that could mislead about the real product carry a visible label?
  • Are you a provider or a deployer for each tool? That is a question for your legal adviser.

Our radar entry on AI transparency obligations has further examples involving chatbots and AI images.

Does the Cyber Resilience Act reach your plugins?

Under the Cyber Resilience Act (CRA), a product with digital elements is a software or hardware product and its remote data processing solutions, including components placed on the market separately. A manufacturer develops such products, or has them developed, and markets them under their own name or trademark, whether for payment, monetisation or free of charge. So anyone who develops Shopware 5 plugins, or has them developed, and markets them to others under their own name can be a manufacturer.

There are limits. According to recital 12, websites that do not support the functionality of a product with digital elements fall outside the scope of the Regulation. The Commission's FAQs point to the Blue Guide, under which a product manufactured for one's own use is not considered to be placed on the market. Recital 18 says that making available free and open-source software that is not monetised should not be considered a commercial activity.

Shops that sell other manufacturers' products with digital elements can have a different role. Under Article 3(17), a distributor is any person in the supply chain, other than the manufacturer or the importer, that makes such a product available on the Union market without affecting its properties. From 11 December 2027, distributors must verify that a product bears the CE marking before making it available.

For manufacturers, the reporting obligations have applied since 11 September 2026, including for products within the CRA's scope that were placed on the market before 11 December 2027. A manufacturer that becomes aware of an actively exploited vulnerability must notify it to the CSIRT designated as coordinator and to ENISA at the same time. The CRA requires an early warning notification without undue delay and in any event within 24 hours of the manufacturer becoming aware of it.

If you are a manufacturer of plugins in this sense, set up a reporting route. Keep a list of which plugin version runs in which shop. And add a fixed step to your processes for checking the CE marking. Our radar entry on the Cyber Resilience Act covers roles, deadlines and exemptions in more detail.

A checklist of places in your shop

These are questions about places in the shop, not legal questions. A test order in every shop language helps with the checkout items.

  • Footer link: does it carry the right label, appear on every page, stay available for the whole withdrawal period and work without logging in? If it sits only in the customer account, can contracts be concluded only with an account?
  • Withdrawal form: can the customer give their name, the contract or the items, and an electronic address for the acknowledgement? Are logged-in customers spared identifying themselves again?
  • Confirmation and acknowledgement: is the confirmation step labelled 'Widerruf bestätigen' or with equivalent unambiguous wording, and does the acknowledgement show the date and time of receipt?
  • Instructions on withdrawal: does the shop page mention the withdrawal function and where it is?
  • Final checkout page: is the notice there, in colour and prominent, including in a one-page checkout and on narrow screens?
  • Order confirmation email: does it carry the notice, and does it still go out without the attachment?
  • Producer data: do you know which producers give a guarantee of more than two years?
  • Guarantee label: does it appear on the product page, in the basket and on the final checkout page?
  • Environmental claims: have you searched texts, filter values, seals and images?
  • Pay by invoice: what are the payment terms and late-payment costs, and who holds the claim?
  • AI: does the chat window open with an AI notice, and do misleading AI product images carry a visible label?
  • Plugins you market to others under your own name: is there a reporting route?

If you want help looking after an existing Shopware 5 shop, or are thinking about moving to Shopify, our online shops page describes how we work with both.

Further reading: where each rule stands

Links marked "in German" lead to German-language pages.

Frequently asked questions

Will shopware AG still ship an update for the withdrawal button?
The vendor, shopware AG, has not promised one. The README of the official Shopware 5 repository says the repository is no longer actively monitored or maintained; updates may occur occasionally, but this cannot be guaranteed. The latest published release is v5.7.20 of 5 June 2025. Plan the withdrawal function as a plugin or theme change of your own.
Is a link to the withdrawal form in the footer enough?
There is no simple yes or no answer. Section 356a BGB requires the withdrawal function to be continuously available throughout the withdrawal period, prominently placed and easily accessible. The Bundestag's legal affairs committee takes the view that the provision does not rule out hyperlinks. According to the explanatory memorandum, a function shown in the footer needs special measures for good legibility, such as colour or contrast and a prominent placement. Whether your footer meets this is for your legal adviser to judge.
Where does the legal guarantee notice go in Shopware 5?
We use two places. One is the final checkout page, below the order button in the block frontend_checkout_confirm_confirm_table_actions. The other is the order confirmation email built from sORDER, where we attach the notice as a PDF. The Commission's practical guidelines give examples such as a general reminder on the website, a sentence on the check-out page and inclusion in the confirmation email.
What should you check for pay by invoice from 20 November 2026?
Check the payment term, the late-payment costs and whether a third party acquires the claim. From 20 November 2026, a trader's own deferred payment of at most 50 days, without a third party, free of charge and with only limited late-payment costs, is not financial accommodation under section 506 BGB. For traders that are not SMEs and offer information society services for which distance contracts are concluded, the exemption applies only if full payment is due no later than 14 days after delivery and only if no third party acquires the claim arising from the deferred payment. Have your legal adviser assess which rule applies.
How does a shop chatbot disclose that it is AI?
Under Article 50(1) of the AI Act, the provider must ensure that people are informed they are interacting with an AI system, unless this is obvious to a reasonably well-informed, observant and circumspect person. The information must be clear and distinguishable and given at the latest at the first interaction. The Commission's guidelines describe a chatbot that opens the conversation by mentioning that it is based on AI technology. Check that your chat window starts with such a notice.
Does the Cyber Resilience Act affect your own shop?
That depends on your role. Anyone who develops Shopware 5 plugins, or has them developed, and markets them to others under their own name can be a manufacturer under the CRA, and the reporting obligations have applied since 11 September 2026. A shop that sells other manufacturers' products with digital elements can be a distributor, and from 11 December 2027 distributors must verify the CE marking. Recital 12 says websites that do not support a product's functionality fall outside the scope. Your legal adviser can assess your case.

Does your Shopware 5 shop need retrofitting?

Tell us about your shop, its payment methods and the plugins it runs. We will tell you which places in the code are affected and how they can be retrofitted.

Sources

  1. § 356a BGB Elektronische Widerrufsfunktion bei Fernabsatzverträgen (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  2. README.md, Branch 5.7 (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  3. Verordnung (EU) 2024/1689 (KI-Verordnung), Originalfassung vom 13. Juni 2024 (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

  4. Künstliche Intelligenz: Leitlinien zu Transparenzpflichten veröffentlicht (20. Juli 2026) (opens in a new tab)

    Europäische Kommission, Vertretung in Deutschland accessed

  5. Verordnung (EU) 2024/2847 (Cyber Resilience Act) vom 23. Oktober 2024 (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

  6. FAQs on the Cyber Resilience Act implementation (Markdown-Fassung) (opens in a new tab)

    Europäische Kommission, GD CONNECT accessed

  7. Migration zu Shopware 6 (Seite ohne Datum) (opens in a new tab)

    shopware AG accessed

  8. Commits im Repository shopware5/shopware (GitHub-API) (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  9. Latest release (GitHub-API) (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  10. composer.json im Tag v5.7.20 (opens in a new tab)

    shopware AG (GitHub, shopware5/shopware) accessed

  11. Supported Versions (opens in a new tab)

    The PHP Group (php.net) accessed

  12. UPGRADE-5.7.md (CHANGELOG for Shopware 5.7.x), Branch 5.7 (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  13. Richtlinie (EU) 2023/2673 vom 22. November 2023 (ABl. L, 2023/2673, 28.11.2023) (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

  14. Richtlinie (EU) 2024/825 vom 28. Februar 2024 (ABl. L, 2024/825, 6.3.2024) (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

  15. Richtlinie (EU) 2023/2225 vom 18. Oktober 2023 (ABl. L, 2023/2225, 30.10.2023) (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

  16. Einführungsgesetz zum Bürgerlichen Gesetzbuche, Art. 246a § 1 Abs. 2 (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  17. themes/Frontend/Bare/frontend/checkout/confirm.tpl, Branch 5.7 (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  18. engine/Shopware/Core/sOrder.php, Branch 5.7 (opens in a new tab)

    shopware AG (GitHub shopware5/shopware) accessed

  19. Art. 246a § 1 EGBGB Informationspflichten (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  20. Gewährleistungslabel und GARAN-Label (opens in a new tab)

    Europäische Kommission, Your Europe accessed

  21. § 312j BGB Besondere Pflichten im elektronischen Geschäftsverkehr gegenüber Verbrauchern (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  22. § 2 UWG Begriffsbestimmungen (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  23. UWG Anhang (zu § 3 Absatz 3) (opens in a new tab)

    Bundesministerium der Justiz (gesetze-im-internet.de) accessed

  24. Konsolidierte Fassung der Verordnung (EU) 2024/1689 (KI-Verordnung), Stand 27.07.2026 (opens in a new tab)

    Amtsblatt der Europäischen Union (EUR-Lex) accessed

Share on LinkedIn

Related articles

Case study · E-commerce

One QR code on every appliance: from EU obligation to service portal

Since 2021, every EU energy label has had to point via QR code to the European product database, EPREL. For an international household-appliance manufacturer, we turned that into more than a compliance box-tick: a QR platform that routes every scan to the right destination depending on context, and a multilingual service portal covering over 600 products, both living off the same data foundation.

Search the website

Popular topics

All results