Edited by Solucom · June 19, 2026
The New online withdrawal requirement It has been in effect since June 19, 2026. All right: but in practical terms, what do you need to fix on your WooCommerce? Let’s get down to the nitty-gritty here, because there are a few details between «knowing there’s a regulation» and «actually complying with it» that you’d better not get wrong.
The three pieces of a standard recess
A well-made recess isn't just a button. It's three things that have to work together:
- The right of withdrawal. A clear process, usually two steps, accessible from the customer area or the order page: the customer indicates the order and confirms their wish to cancel.
- Confirmation on durable medium. Immediately after, the customer must receive a confirmation that lasts over time. Typically, this is an email, preferably with a PDF and a verifiable reference.
- The preserved evidence. From your end, you need to keep a record of what was requested and when, so you can retrieve it even months later.
Doing it by hand: it's possible, but there's a hidden cost
In theory, you can manage everything manually: a form, a handwritten email, a sheet where you note down requests. It works as long as the volume is low and no one disputes anything. The problem is that precisely when you need it – a dispute, a customer claiming they requested a withdrawal on time – the «hand-made» approach shows its cracks: emails that can't be found, uncertain dates, records that someone has altered. And you find yourself defending yourself without solid proof.
What does a well-made solution do
- Insert the withdrawal button at the right point on the path, without you having to touch code.
- Automatically generate confirmation on durable support (email + PDF + verifiable link) to the client.
- Write each withdrawal in a Immutable log with timestamp: your proof, uneditable.
- It works within the environments you already use, such as WooCommerce and FunnelKit, in Italian.
The part everyone underestimates: the proof
Let's repeat this point because it's what makes the difference in case of dispute. The button is what the customer sees; the immutable log it's what protects you. Without a reliable, timestamped record, you're in the weak position of having to prove something you haven't solidly documented.
Frequently Asked Questions
Do I need to know how to code?
No. The goal is precisely not to touch the code: you configure it from the settings, and the flow is ready.
Does this also apply to FunnelKit?
Yes: these are the two most common platforms for selling online on WordPress, and both need to be covered.
And the returns already managed by my management system?
The right of withdrawal is a consumer right with its own rules: having it tracked according to regulations is distinct from the logistical flow of the return.
Do you want to adapt without complications? We have released a free plugin that combines a button, durable storage confirmation, and an immutable log: Discover EU Right of Withdrawal.