cancellation button (withdrawal button)

[DRMasterChief]

Hello, ...the cancellation button will become mandatory from June 19, 2026 in EU countries.

So, this means, an electronic button is needed that allows consumers to cancel contracts online – simply, directly, and without detours. The goal: Cancellation should be as easy as signing the contract – with just one click.

How do we implement this in ThirtyBees? Has anyone already considered this, or is someone working on a solution?

It would be sufficient to use a copy the existing contact form and make it available for this purpose. This would also allow for the automatic sending of the email confirmation.

This means, we have to copy the Controller and the .tpl  from contact form to a new form?  What else is to be done?

Once again, the entire EU is affected, although the implementation in some countries seems to be less stringent.

More informations here:

The "cancellation button" (or withdrawal button) becomes a mandatory, simple, one-click feature for all EU online retailers for distance contracts starting June 19, 2026, due to EU Directive 2023/2673,

requiring an easily accessible, prominent, and clearly labeled button on websites/apps to make canceling online purchases as easy as making them, preventing complex email/form processes. 

Key Details of the 2026 Cancellation Button:
Mandatory Date: June 19, 2026.
Applies To: Online retailers (websites & apps) in the EU for distance contracts (e.g., online shopping).
Purpose: To allow consumers to withdraw from a contract with a single click, just as easily as they agreed to it.
Functionality: It must be a digital function that's simple, clearly recognizable, and available throughout the 14-day withdrawal period.
Requirements:
Easy Access: Prominently placed, not hidden behind multiple clicks or logins.
Clear Labeling: Clearly labeled (e.g., "Cancel Contract").
Confirmation: Clicking it leads to a confirmation page where the user submits the cancellation.
Legal Basis: EU Directive 2023/2673, amending the Consumer Rights Directive. 
Why it's Happening:
The EU aims to strengthen consumer rights and confidence in e-commerce by removing friction and complexity from the cancellation process, making it as easy as ordering. Non-compliance could lead to extended withdrawal periods (12 months + 14 days) or penalties. 

and also here are some informations: https://retjet.com/en/mandatory-return-button-in-online-stores-directive-2023-2673 

 

Maybe we can arrange an good solution (without an module) in team work here? 

[vir]

The module I'm using implements the contract withdrawal request button in the details of the order just completed (see attached screenshot). Therefore, the consumer will immediately find the button to access the contract withdrawal function in the details of the order just placed. It's already there, ready to be used. The login, which you see as a complication, will only be necessary to return to the order details at a later time and is an essential requirement (required by other regulations and directives) to ensure the appropriate level of confidentiality and security of the system in use. Avoiding the login to an e-commerce site that provides a personal customer area that collects personal and sensitive data would violate other equally stringent and stringent regulations, not only in Germany, such as the Privacy Act.
I repeat, therefore, the login cannot be seen as "a complication to access the procedure" but as a "conditio sine qua non" due to the Privacy Act.

 

 

On 3/21/2026 at 5:47 AM, vir said:

Hi.  Directive (EU) 2023/2673 does not require the withdrawal button to be accessible without logging in.

The directive (which amends Directive 2011/83/EU) introduces the requirement for a "digital withdrawal function" that must be:
easily accessible
clear and visible
simple to use
equivalent in simplicity to the purchasing process
Key point: Contract identification
The regulation requires that the consumer be able to:
identify the contract (order)
send the withdrawal declaration
In practice, this means: access to an area where the order is recognizable (order history - order details)
This module does all of this and is therefore fully compliant with the regulation.

What the module does is indicated in the module description in https://psitsolution.com/tools/en/thirtybees-ps-mandatory-withdrawal-button-module

The Thirtybees PS Mandatory Withdrawal Button module implements a digital function that allows customers to easily exercise their right of withdrawal directly from the store's personal area, as required by Directive 2023/2673 on withdrawal from online contracts.

The module records the request, sends a confirmation email, and makes the request visible in the merchant's back office for management, as required by the new regulation.

This module adds a withdrawal request button to the order detail page in the customer account.

When the customer uses this feature:

a confirmation page is displayed identifying the relevant order;

the customer confirms the withdrawal request through a dedicated button;

the request is recorded in the database including key data (order, customer, date and IP address);

a confirmation email is sent automatically;

the request becomes visible in the module back office.

In the back office, the merchant can review all withdrawal requests and access the related order directly for easier processing.

The module is designed to provide a simple and transparent withdrawal process for customers while maintaining a reliable record of all requests for the merchant.

exactly what is provided for in Article 11a of the law.

[Yabber]

@DRMasterChief  What you want to implement in your store doesn’t require any changes to Thirtybees or any additional modules.
You want a button that links to a contact form where the customer must submit a request to cancel their order. Just add a link or button anywhere in your store that leads to the standard contact form, and that’s it.
And since this solution has nothing to do with the functionality of the "Cancel order" button, has no integration with the store, and doesn’t automate any actions in the store (such as automatically changing the order status), that’s a different matter. What you’re proposing is just plain old email writing. The customer has to write an email providing all their details, then the store staff has to read that email and take some further action on the order.

And this whole "canceling orders without logging into the customer’s account" thing is total nonsense. Hackers will be canceling all the orders in the store every day. There are no safety measures in this solution.
Here’s an example of how it’s done in WooCommerce: https://woocommerce.com/products/customer-order-cancellation-for-woocommerce/ 
The customer logs into their account, sees a list of their orders, and on that list there’s a "Cancel order" button—they don’t have to spend an hour filling out confusing forms where they have to provide all their personal information.

In my module, I implemented this as follows: the "Cancel order" button is always visible in the store's navigation bar; when the customer clicks it, they are taken to their order list and can cancel the order with a single click. In the module’s configuration, you can exclude order cancellations for virtual products and customer personalized products; by law, such products are non-returnable. When the customer clicks the "Cancel order" button, the order status is automatically changed to "Order canceled". Many electronic payment gateways offer automatic refunds when the status is changed to the one specified in their configuration—in this case, we achieve 100% automation of store operations that require no action from store staff.