Withdrawal button: a new obligation for online stores in the EU

A withdrawal button is a feature in an online store’s interface that lets a consumer back out of an online purchase as easily as they made it. The obligation comes from EU Directive 2023/2673 on EUR-Lex, which amends Directive 2011/83/EU on consumer rights. I’m writing for owners and admins of small and medium stores running WordPress with WooCommerce or PrestaShop. Status as of July 2025: the EU rules are adopted, but Poland has not yet passed its implementing act.

What is the withdrawal button and where does it come from?

It’s a clearly labelled element of a website or app that the customer uses to submit a statement of withdrawal from a distance contract. That’s it. Directive 2023/2673 adds a new Article 11a to Directive 2011/83/EU, and that article requires sellers to provide this feature. Why? So that backing out of a purchase is as convenient as the purchase itself, and the form stops getting lost somewhere on page twelve of the terms and conditions (anyone who has ever hunted for that form knows what I mean). The right of withdrawal itself is nothing new. What’s new is how you exercise it: it has to be available directly in the store’s interface.

When does the withdrawal button requirement apply?

Stores have to apply the new rules from 19 June 2026. Member states have until 19 December 2025 to transpose them into national law. Both dates are set out in the final provisions of Directive 2023/2673. As of July 2025, Poland still has no implementing act, so national details may differ a little, mainly on things like penalties or supervision. My advice? Follow the legislative work, but don’t wait to prepare until the act is published in the Journal of Laws (Dziennik Ustaw). Otherwise things will get hectic.

How should the withdrawal button work in a store?

It has to be easy to find, clearly described and available for the whole time the customer can withdraw from the contract. Specifically, the directive requires the feature to be:

• clearly labelled, e.g. with the words „withdraw from contract here” or another equally unambiguous phrase,
• available continuously throughout the withdrawal period,
• placed in a visible and easily accessible part of the interface.

After clicking it, the consumer enters or confirms their details: name, information identifying the contract and the channel where they want to receive confirmation. Then they submit the statement with a second function, labelled e.g. „confirm withdrawal”. So two steps, not one. And the store must promptly send an acknowledgement of receipt on a durable medium, for example by email, with the content of the statement and the date and time it was submitted.

Who does the obligation apply to, and which contracts?

Every trader that concludes distance contracts with consumers through an online interface: a store, a website or a mobile app. Company size doesn’t matter. A small store on WooCommerce or PrestaShop is covered too, just like with GPSR in your online store, so don’t count on any leniency. On the other hand, the rule doesn’t extend the right of withdrawal itself. Goods and services that are already excluded from it today (such as products made to individual order) stay excluded. The feature has to cover the contracts the customer can actually withdraw from.

Online store returns after the changes: what to prepare before June 2026

I’d start by tidying up your current returns process and only then pick a tool. In practice, the order looks roughly like this:

1. Review your current returns process: where the customer gets the form, where they send it, who handles it and when.
2. Choose a place for the feature, e.g. the customer account or the order details page.
3. Set up automatic emails confirming receipt of the statement.
4. Update your terms and conditions and pre-contractual information with the new way to withdraw.
5. Test the whole path as a customer, from placing an order to receiving the confirmation.

On the back end, you’ll want request handling with statuses, team notes and tracking of refund deadlines. And then there are guest orders without an account. That’s a separate headache. If the feature only works after logging in, guests need another route, e.g. access with the order number and email address.

How to add a withdrawal button in WooCommerce and PrestaShop

In WooCommerce you have two options: a custom solution or a plugin. Whatever you choose, check it against the list of requirements in the section above: labelling, constant availability, a confirmation step, an email on a durable medium. And check what happens with orders placed without an account, because that’s where things most often go wrong.

In PrestaShop, one option is the One Return module from K4.pl, built for the requirements of Directive 2023/2673. It shows the withdrawal form on the order details page in the customer account, where the buyer picks a return reason and adds a comment. The administrator handles requests in the Back Office: filters them, changes statuses, adds internal comments the customer can’t see. Both sides get automatic emails when a request is submitted and on every status change (pending, confirmed, rejected). You can also exclude selected products or categories, and the module comes with Polish and English translations.

Technically, it’s a small change. But it’s better to roll it out calmly before 19 June 2026 than in a rush a week before the deadline. Review your returns process now, choose a solution for your platform, and go over the changes to your terms with a lawyer once the Polish act is passed.

Frequently asked questions