EU cancel button: new requirement for online shops
The EU's new requirement is not just a new button in the design. An online shop must allow a consumer to withdraw from a purchase clearly, simply and verifiably.
EU Directive 2023/2673 amends the Consumer Rights Directive and adds a new Article 11a. It applies to distance contracts concluded through a web interface. In practice, this means that an online shop or other consumer contract concluded online must offer an electronic withdrawal function.
The requirement applies from 19 June 2026. In everyday language, this is referred to as the cancel button or withdrawal button.
What the online shop must have
Where a consumer has a statutory right of withdrawal and the contract was concluded online, the shop must provide a withdrawal function that is:
- easy to find;
- clearly visible;
- accessible throughout the entire withdrawal period;
- worded unambiguously;
- linked to a specific order or contract;
- confirmed with a second step, so the consumer does not accidentally withdraw.
The directive's example wording is "withdraw from contract here" and the confirmation step "confirm withdrawal". An English-language shop should use equally clear wording.
This is not the same as a standard returns form
Many online shops already have a returns page or an email address where customers can write. But the purpose of the new requirement is to make withdrawal as simple as the original purchase.
A contact page or PDF form may therefore not be enough. The shop must help the customer enter or confirm at least the necessary details: name, order or contract identification, and an electronic channel to which the withdrawal confirmation should be sent.
After confirmation, the trader must send the customer a withdrawal receipt on a durable medium — typically email. The receipt must show the content of the withdrawal, and the date and time of submission.
Who is most affected
In practice, all online shops and service providers who sell to EU consumers and conclude contracts online should review this. The requirement is especially relevant for shops where:
- customers can log in and view their orders;
- purchases go through a custom order workflow;
- returns are handled manually via email;
- the shop is connected to accounting, inventory, logistics or CRM;
- both goods and services are sold.
Not all purchases fall under the right of withdrawal. Exceptions may apply to perishable goods, custom-made products, or digital content where the consumer has agreed to waive the right. This is why it is worth mapping out which products and services actually require the button before starting development.
What could happen if the requirement is not met
The exact liability provisions depend on how each EU member state transposes the directive into national law. What is clear is that the directive obliges member states to establish effective and dissuasive penalties for infringements.
Where a shop does not give a consumer a statutory withdrawal opportunity clearly, or makes it unreasonably difficult to use, this may become a consumer protection issue. Depending on the nature of the infringement, risks may include:
- an order to cease the infringement and fix the website;
- consumer disputes and refund claims;
- supervisory proceedings;
- fines if the infringement qualifies as a consumer protection violation;
- reputational damage, especially if withdrawal has been deliberately made difficult.
What to plan technically
In web development, this is not just adding one button. The work may touch the order data model, user account, emails, permissions, logging and the admin view.
A useful first checklist:
- where should the withdrawal link or button appear;
- can a customer find the right order without a user account;
- what data must the customer confirm;
- how is the withdrawal date and time recorded;
- what email is sent to the customer;
- how does the information reach the shop manager, warehouse or accounting;
- which products or services are excluded as exceptions;
- how to test the entire workflow with Playwright or another browser test.
Drupal Commerce, WooCommerce, Magento, Shopify and custom-built shops will most likely solve this differently. A simple shop may only need a separate form and a confirmation email. A more complex system requires the withdrawal to be connected to the order, payment, inventory and customer service process.
What to do before development
Before ordering work, it is worth writing down which purchases carry the right of withdrawal, which exceptions apply and what the current returns process looks like. Only then does it make sense to decide whether a simple form, an account-based solution or full integration with order management is needed.
The legal wording must be reviewed by a lawyer or consumer law specialist. The developer's role is to make the solution clear to the user, technically traceable and verifiable with tests.
Useful references
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.