From 19 June 2026, an electronic withdrawal function becomes relevant for many businesses that conclude contracts with consumers online. For WooCommerce shops, this is a good reason to review the existing withdrawal process.
This is not about simply adding another button somewhere. Customers should be able to declare their withdrawal directly online. The shop therefore needs a clear workflow: from starting the withdrawal and matching the order through to confirmation and further processing.
In short:
If contracts are concluded online, withdrawals must also be possible online – in a traceable, unambiguous way that fits the shop workflow.
This is exactly where it becomes important for WooCommerce shops: the withdrawal must not only be possible, but also work cleanly in day-to-day operations.
What exactly is the withdrawal button?
The term “withdrawal button” sounds like a single button. Legally, however, it is about more: an electronic withdrawal function through which consumers can withdraw from a distance contract concluded online.
From 19 June 2026, affected businesses must provide this function through their online user interface. The withdrawal function must be clearly labelled, for example with “Withdraw from contract”. In the next step, customers must be able to submit their withdrawal using an equally clear confirmation function, for example “Confirm withdrawal”.
After submission, receipt of the withdrawal must be confirmed electronically. That is why the withdrawal button is not just a single link, but a digital workflow:
Start withdrawal → enter details → confirm withdrawal → receive confirmation of receipt
For WooCommerce shops, the conclusion is clear: simply making a button visible is not enough. What matters is whether the withdrawal is then guided properly through the shop workflow.
The legal basis is the new Section 356a of the German Civil Code (BGB); the rules take effect on 19 June 2026.
Does this affect every WooCommerce shop?
Not automatically. The electronic withdrawal function is particularly relevant for shops through which consumers can conclude distance contracts online.
For WooCommerce shops, this means in practice: if you sell goods, services or digital offers online to consumers, you should have it checked whether and how the new withdrawal function needs to be implemented in your shop.
Important: not every contract and not every product is treated the same way legally. Special rules may apply, for example, to personalised products, digital content or other special cases. The legal assessment should therefore always be based on the specific shop.
For sales through marketplaces, it should also be clarified separately how the required withdrawal function is provided through the respective platform.
Rule of thumb:
Many B2C WooCommerce shops should now address the withdrawal button. Whether and how your specific shop is affected needs to be assessed individually.
Why a button alone is not enough
The biggest misconception about the withdrawal button is this:
Then we will just put a button in the footer.
The button is only the entry point. After that, there needs to be a clear workflow. Customers must be able to start the withdrawal, provide the required details and confirm the withdrawal unambiguously. Receipt of the withdrawal must also be confirmed.
The electronic withdrawal function must be continuously available, prominently placed and easy to access. The final declaration requires an unambiguous confirmation function, for example labelled “Confirm withdrawal”.
For a shop, this means:
- Where does the customer find the entry point?
- Which data is requested? How is the order matched?
- How is the withdrawal confirmed?
- Is a confirmation of receipt sent?
- Where does the case go afterwards?
- Who processes it internally?
This is the point where a single button becomes a real process.
What does this mean in practice for WooCommerce?
WooCommerce is flexible. That is exactly why shops can work in very different ways.
Some shops use customer accounts, while others allow guest orders. Some sell standard products, while others sell variations, bundles, digital products or personalised items.
For the withdrawal button, this means that simply creating a general page with a form is not enough.
A clear withdrawal process should answer these questions:
1. How is the order found?
Customers need a way to match their withdrawal to a specific order – for example using the order number and billing email address.
2. Does this also work for guest orders?
Many customers order without a customer account. The withdrawal process must therefore not work only for logged-in users.
3. Can individual items be selected?
A withdrawal does not automatically concern the entire order. Sometimes only one item from several is withdrawn.
4. What happens after submission?
The withdrawal should not simply end up somewhere as a loose email. For the shop, it is much better if the case can be processed in a structured way in the backend.
5. How are special cases handled?
Not every product is eligible for withdrawal. If a shop sells such products, the process needs to be able to handle this.
In depth: withdrawals for guest orders
Even without a customer account, a withdrawal must be matched clearly to the correct order. Our guide explains why this is particularly important for WooCommerce shops.
In depth: withdrawals for guest orders
Even without a customer account, a withdrawal must be matched clearly to the correct order. Our guide explains why this is particularly important for WooCommerce shops.
Link:
https://wm-plugins.de/en/guest-orders-and-withdrawals-in-woocommerce/
Contact form, email or a proper withdrawal process?
Many shops currently handle withdrawals through a general email address, a contact form or a PDF form.
That can work for a while in everyday operations, especially for small shops with only a few withdrawals.
It becomes difficult when several cases arrive at the same time, when details are missing, when only part of an order is affected, or when several people work in the shop and nobody knows exactly which withdrawal has already been processed.
That quickly creates the typical email chaos:
One customer writes to info@.
Another uses the contact form.
Someone else sends a message without an order number.
Support forwards emails internally.
The warehouse does not know what will be returned.
And in the end, someone has to piece everything together manually.
That is exactly why the withdrawal button should not be viewed only as an obligation. It can also help make an already confusing process much clearer.
A good withdrawal process ensures that the withdrawal:
- does not get lost in the inbox
- is clearly matched to the order
- contains the affected items
- is documented with date and details
- can be processed internally
In depth: why a contact form is not enough
A general form can transmit a message. But a structured withdrawal often requires an order reference, item selection and a clear processing workflow.
Link:
Why a Contact Form Is Not a Withdrawal Process
What does Widerrufsmanager for WooCommerce do?
Widerrufsmanager is a technical solution for WooCommerce shops.
It maps the withdrawal process directly in the shop. Not as a loose form, but as a structured workflow:
Start withdrawal → verify order → select items → confirm withdrawal → process in the backend
This means customers can start the withdrawal directly through the shop. The order is matched. Affected items can be selected. The withdrawal is confirmed. The case then appears in the WooCommerce backend and can be processed further there.
The advantage is not just the button itself. The advantage is the workflow behind it.
For shop operators, this means:
- fewer loose emails
- better matching to the order
- clearer processing
- better overview in the backend
- a process that takes place in WooCommerce
Widerrufsmanager therefore addresses the technical side of the topic. It does not replace legal review of your shop, your withdrawal information or your specific product cases.
Lite or Pro: which version suits which shop?
Not every shop needs the same scope.
For smaller or simpler shops, a basic solution may be enough to provide the technical entry point into the withdrawal process.
The Pro version becomes particularly interesting when withdrawals should not merely arrive, but be managed professionally.
Typical cases for Pro:
- you receive withdrawals regularly
- you want to exclude certain products, categories or tags
- you need records or exports
- you want to customise email templates
- several people work in the process
- you manage several shops
- you want to organise withdrawals in the backend rather than in the inbox
A simple rule of thumb:
Lite brings withdrawals into the shop.
Pro brings structure to the process.Which version is right for your shop?
Lite or Pro depends on how your shop works: from standard cases to partial withdrawals, special cases or several people handling requests.Link:
Widerrufsmanager Lite or Pro: Which Version Is Right for Your WooCommerce Shop?
Why agencies should address the topic early
For web agencies, WordPress freelancers and WooCommerce service providers, the withdrawal button is a topic that can be raised proactively with clients.
Many shop operators will only realise relatively late that this requirement affects them. Then things can quickly become rushed.
Agencies can include the topic much earlier in maintenance, ongoing support or shop checks:
- Is the shop B2C?
- Are contracts concluded online?
- Is there a right of withdrawal?
- How are withdrawals currently handled?
- Are guest orders allowed?
- Are there products with exclusions?
- Are the legal texts and withdrawal information up to date?
- Is there a technical withdrawal function?
This is not only a compliance topic. It is also a good reason to review existing client shops properly.
For agencies and WordPress service providers
Anyone managing WooCommerce shops for clients should now include the electronic withdrawal function in existing shop checks.
Link:
Why the Withdrawal Button Belongs in Every WooCommerce Maintenance Check
What about the withdrawal information?
Widerrufsmanager provides the technical withdrawal function. But that is only one part of the change.
Shop operators should also have it checked whether their withdrawal information and other legal texts need to be updated. If an electronic withdrawal function is available, it should be reflected properly in the shop’s legal information.
This matters because the technology and legal texts need to fit together.
A plugin can provide the technical workflow. But it cannot make a blanket judgement about which legal wording is correct for your specific shop, products and contract types.
Therefore:
Technical implementation: Widerrufsmanager.
Legal review: shop operator, legal adviser or legal-text provider.
Why you should not wait until just before the deadline
19 June 2026 may still sound some way off. Even so, it is worth clarifying the topic early.
Not because there is any need to panic, but because several points come together:
- technical implementation in the shop
- placement of the function
- wording
- confirmation emails
- backend workflow
- legal texts
- special cases in the product range
- internal responsibilities
Especially for WooCommerce shops with custom themes, page builders, additional plugins or special product types, you should not wait until the last day to test whether everything works properly.
The withdrawal button is not a design detail. It affects the workflow after purchase.
And workflows like these deserve to be thought through properly in the shop.
Conclusion: the withdrawal button is not just about a button
From 19 June 2026, the withdrawal button becomes relevant for many online contracts. For WooCommerce shops, this means reviewing now how withdrawals will be started online, confirmed and processed internally.
The most important point:‘
It is not just about a button. It is about a process.
A contact form or general email address can quickly become confusing in everyday operations, especially when orders need to be matched, items selected, special cases considered and cases processed internally.
The Widerrufsmanager for WooCommerce starts at exactly this point. It turns the withdrawal into a clear technical workflow in the shop: from the start and order verification through to backend processing.
If you use WooCommerce and want to prepare your shop technically in good time, take a look at Widerrufsmanager.
Also important: keep withdrawals and returns clearly separate
The withdrawal starts the legal declaration, while a return concerns the subsequent shipment of the goods back. Our dedicated guide explains why this distinction matters for shops.
Link:
Withdrawal Is Not the Same as a Return: What Shop Operators Should Keep Separate