From June 19, 2026, consumers must be able to withdraw from contracts directly via a withdrawal button in the online store - provided that a statutory right of withdrawal exists for the respective contract.
What initially seems like a minor UI adjustment will fundamentally change the way revocations are handled: the revocation will be transformed from an often manual background process into a visible, standardized function in the store.
Legal Background
The obligation is based on an amendment to the EU Consumer Rights Directive (EU) 2023/2673. The aim is to provide consumers with a simple, clear and directly accessible digital withdrawal channel - where the contract was concluded.
The decisive factor here is not the type of store, but the specific contract:
The obligation applies to contracts concluded online with consumers, provided there is a statutory right of withdrawal.
What Has Changed Compared to Today
Up to now, revocations could often be declared by email, form or via customer service. These methods may still be used, but will no longer be sufficient in future.
From 2026, a mandatory digital withdrawal channel in the store itself will be required. Withdrawal will thus become:
- Visibly integrated into the user guidance,
- can be used independently of support,
-
and clearly standardized.
Who is Affected?
Affected are online contracts that are concluded with consumers via digital user interfaces and to which a statutory right of withdrawal applies - for example for goods, services, digital content or subscriptions.
Contracts without a statutory right of withdrawal arenot affected, e.g:
- fully provided services with an effective waiver,
- customized goods, provided that the statutory exclusion applies.
What Specifically Needs to Be Considered During Implementation
Even when talking about a "button", the legislator makes clear specifications regarding accessibility, procedure and design:
- Not tied to a login:
Withdrawal must not depend on customers having a customer account or being logged in. Guest orders must also be able to trigger the withdrawal directly in the store. - Clear digital process:
After clicking on the revocation button, a page is called up where the required information about the contract can be provided. The withdrawal is then actively confirmed and automatically documented, including a confirmation of receipt by email. - Clear design and labeling:
The button must be easy to find, barrier-free and clearly labeled (e.g. "Revoke contract"). Misleading designations, hidden placements or unclear icons do not meet the requirements.
These points show: The decisive factor is not only the visibility of the button, but also a low-threshold, clearly understandable and technically reliable revocation channel.
Why Act Now?
The implementation is more extensive than often assumed. In addition to the visible function in the store, the following must also be implemented:
- Revocation periods must be correctly taken into account,
- revocations documented,
- and guest orders must also be reliably mapped.
Incorrect or incomplete solutions can lead to legal risks such as warnings. Those who plan for this topic at an early stage avoid time pressure and create a clean, stable solution.
Conclusion
The revocation button is more than just a mandatory element in the frontend. It stands for a clearly regulated digital withdrawal process that must be implemented in a legally correct, technically clean and understandable way for users.
We would be happy to support you with the technical implementation and UX integration of the revocation button - tailored to your store system and your processes. If you have any questions about the specific implementation, we will be happy to help.
The information provided by Blackbit is for general information purposes only. It does not constitute legal advice. For binding legal decisions, customers should consult a qualified lawyer.
Leave us feedback