Buying online is done in a few clicks. Withdrawing was, in many shops, considerably more cumbersome: find the withdrawal notice, download a form, write an email, look up the order number and wait for a reply.
Exactly that is meant to change with the new withdrawal button.
The new obligation has a clear goal: consumers should be able to withdraw from contracts concluded online just as easily as they concluded them. For online shops this is not only a legal topic but also a technical and process task.
For Shopware shops in particular, the withdrawal button affects several areas: storefront, customer account, order history, email communication, ERP integration, return processes, legal texts and internal support handling.
What is the withdrawal button?
The withdrawal button is an electronic function that allows consumers to digitally withdraw from a contract concluded online.
Important: this is not just a simple link to the withdrawal notice. The function must make it possible to actually submit a withdrawal declaration electronically.
According to the published text of § 356a BGB, the withdrawal function must be clearly readable and labelled with “Vertrag widerrufen” (“Withdraw contract”) or another equally unambiguous wording.
In practice: the customer clicks a clearly identifiable withdrawal function, enters or confirms the necessary information, submits the withdrawal and then receives a confirmation.
When does the obligation apply?
The obligation to provide the withdrawal button applies from 19 June 2026. Several legal and consumer-protection sources name this date as the deadline for providing the mandatory electronic withdrawal function.
This date matters because the function should not first be designed on the deadline itself. Depending on the Shopware setup, the implementation can be much more than an extra button in the theme.
Who does the withdrawal button apply to?
In principle the obligation applies to companies that conclude online contracts with consumers — typically B2C distance contracts for goods, services or financial products. The German consumer-protection agencies (Verbraucherzentrale) describe that companies must offer a withdrawal button if contracts can be concluded via their website.
For Shopware shops this means in particular:
- Classic B2C shops
- D2C shops
- Shops selling goods to consumers
- Shops with digital products, where a right of withdrawal exists
- Shops with service contracts
- Hybrid B2B/B2C shops with a consumer sales channel
Important: the actual legal assessment depends on the business model. For pure B2B shops, individual custom manufacturing or products without a statutory right of withdrawal, the obligation needs to be reviewed more closely.
What must the withdrawal function be able to do?
A legally sound withdrawal button is more than a graphic element. The function must technically enable withdrawal and be easy for the consumer to use.
From a Shopware perspective, the implementation should at least cover these areas:
1. Clear labelling
The function should be unambiguously named, for example:
- “Withdraw contract”
- “Withdraw order”
- “Declare withdrawal”
Legally the obvious choice is “Vertrag widerrufen” (“Withdraw contract”) because it is explicitly named in the draft law and legal commentary.
2. Easy to find
The function must not be hidden. It should appear where consumers logically expect it:
- In the customer account with the order
- In the order overview
- On a central withdrawal page
- Optionally also in the footer
- Optionally linked from the order confirmation email
For guest orders it is particularly important that withdrawal is not only possible via a customer account. Many Shopware shops allow orders without an account — the withdrawal function then has to be usable without a login.
3. Capturing the necessary information
So that the merchant can assign the withdrawal, the function should capture structured data, for example:
- Name
- Email address
- Order number
- Affected items or order
- Order date
- Optional message
- Time of withdrawal declaration
Rule of thumb: as little as possible, as much as necessary. The process should not be made unnecessarily difficult.
4. Confirming the withdrawal
After submitting, an automatic confirmation should be generated. This should show the customer that the withdrawal declaration has been received.
Additionally, an email confirmation is sensible, including:
- Order number
- Time of withdrawal
- Summary of the information provided
- Note on next steps
- Contact option for follow-up questions
5. Internal processing
For merchants it is crucial that the withdrawal does not only “look nice” to the customer but is processed cleanly internally.
Possible requirements:
- Notification to support or returns team
- Entry in Shopware on the order
- Status or tag on the order
- Handover to ERP or inventory management
- Documentation for evidence purposes
- Handover to returns portal
- Connection to helpdesk system
Why Shopware merchants should tackle this early
In simple shops a withdrawal button can be implemented relatively lean. In grown Shopware setups the situation is often more complex.
Typical questions are:
- Are there guest orders?
- Are there multiple sales channels?
- Are there different countries and languages?
- Are there B2B and B2C in the same system?
- Are there products without a right of withdrawal?
- Are there digital products or services?
- Are there ERP or returns processes?
- Are there external fulfilment partners?
- Does the withdrawal have to be handed over to a ticket system?
- Is there already a returns portal?
The more of these questions are relevant, the less a simple theme tweak will suffice.
Implementation in Shopware 6: possible architectures
There are several sensible implementation paths for Shopware 6. Which one fits depends on the shop, the processes and the legal requirements.
Option 1: Simple withdrawal page with a form
A central CMS page contains a form for the withdrawal declaration. The customer enters order number, email address and further details.
Advantages: quick to implement, suitable for guest orders, independent of the customer account.
Disadvantages: less convenient, no direct item selection, more manual matching.
Option 2: Withdrawal directly in the customer account
On orders eligible for withdrawal, a “Withdraw contract” button appears in the customer account. The order is pre-filled.
Advantages: very user-friendly, fewer errors, good matching.
Disadvantages: not enough for guest orders if no additional solution exists.
Option 3: Combination of customer account and public withdrawal form
For many Shopware shops this is the best solution. Logged-in customers can withdraw directly from the order. Guest customers use a public form with order number and email address.
Advantages: good UX, more legally robust, practical for different order types.
Disadvantages: somewhat higher development effort.
Option 4: Integration into a returns or ERP process
The withdrawal is handed over directly to a returns portal, ERP, helpdesk or fulfilment system.
Advantages: scalable, cleaner process, less manual work.
Disadvantages: requires clear interfaces and process definition.
UX recommendation for Shopware shops
The withdrawal button should not be treated like an aggressive opponent of conversion. Anyone who hides it or designs it unclearly risks not only legal problems but also customer frustration.
A good UX would be:
- Footer link: declare withdrawal
- Customer account: button on the relevant order
- Public page for guest orders
- Form with few mandatory fields
- Clear confirmation page
- Automatic email confirmation
- Internal notification to support
This way withdrawal becomes transparent without negatively affecting the buying process unnecessarily.
SEO and GEO relevance
Even if the withdrawal button is primarily a legal topic, the implementation indirectly affects SEO and GEO.
Why?
A clean withdrawal process strengthens trust. Trust signals, clear legal texts, good UX, transparent processes and accessible information help users and search systems understand a shop better.
For AI search systems and generative answers, clear information pages are especially valuable. A good withdrawal page should therefore be not only legally correct but also clearly structured:
- What is a withdrawal?
- When can a customer withdraw?
- How does withdrawal work in the shop?
- What happens after submitting?
- How does the return work?
- When is the refund issued?
- Which exceptions exist?
This creates not just legal certainty but also better user guidance.
Checklist for Shopware merchants
Before 19 June 2026, merchants should check:
- Does the obligation apply to our business model?
- Are there B2C contracts with a statutory right of withdrawal?
- Are there guest orders?
- Where should the withdrawal button be placed?
- Which order data needs to be captured?
- How is receipt confirmed?
- Who receives the notification internally?
- Is the withdrawal documented in Shopware?
- Does an ERP, helpdesk or returns portal need to be connected?
- Do legal texts need to be updated?
- Does the withdrawal notice need to be updated?
- Does the solution work in all languages and sales channels?
- Is the process well usable on mobile?
- Is the function operable in an accessible way?
Common mistakes in implementation
Many merchants will implement the withdrawal button too late or too superficially. The critical mistakes are:
Mistake 1: Just a link to the withdrawal notice
A link to a PDF or a legal text is not a real electronic withdrawal function.
Mistake 2: Only available for logged-in customers
If guest orders are possible, the withdrawal function must not be hidden exclusively in the customer account.
Mistake 3: No automatic confirmation
After submitting, the customer should receive a clear receipt confirmation.
Mistake 4: No internal process integration
If withdrawals only arrive as emails somewhere, manual errors quickly creep in.
Mistake 5: No multilingual support
For international Shopware sales channels, the withdrawal function must be implemented in a linguistically and legally appropriate way.
Mistake 6: Not accessible
The function has to be usable on mobile, via keyboard and with screen readers. Forms, error messages and buttons in particular should be implemented cleanly.
Allers Technology perspective
We see the withdrawal button not just as a legal obligation but as part of a professional Shopware process. A good implementation combines legal certainty, technical stability, clean data processing and clear user guidance. For Shopware merchants now is the right time to review their architecture: customer account, guest orders, sales channels, ERP, returns process and legal texts have to be thought through together. Anyone who solves this cleanly and early avoids hectic last-minute adjustments.