Back to blog

Samir Kamnani

Samir Kamnani

July 14, 2026

EU Withdrawal Button Law: What Compliance Actually Requires

Since the EU's withdrawal button law took effect, most compliance guides still read like the deadline hasn't happened. Here's what the requirement actually demands, and the two ways merchants are getting it wrong.

Image

The Deadline Passed. The Confusion Didn't.

When the EU's withdrawal button law took effect on June 19, 2026, a lot of the guidance written to help merchants prepare for it still read like the deadline hadn't arrived. Directive (EU) 2023/2673 requires online retailers to give EU and EFTA shoppers a visible, always-available way to cancel or withdraw an order directly on their site, and it applies whether or not a merchant is ready for it.

That gap was telling. Plenty of merchants selling into Europe had been treating this as a future problem right up until it wasn't one, and the requirement turned out to be more specific than adding a withdrawal link to the site footer. It has to function a particular way, stay reachable for the full withdrawal window, and produce a refund that covers more than just the price of the item.

Get it wrong, and the exposure isn't hypothetical. Merchants face fines of up to €2 million or 4% of global annual turnover, depending on the member state enforcing it.

What Actually Changed (and What Didn't)

The right to change your mind isn't new. Since Directive 2011/83/EU, EU and EFTA shoppers have had 14 days after delivery to withdraw an online order for any reason, or no reason at all, according to the European Commission's consumer guidance. That part of the law has been stable for over a decade.

What changed this June is narrower and more technical. Directive (EU) 2023/2673 doesn't touch the 14 day window itself. It targets how shoppers exercise that right. Before, a merchant could route the withdrawal process through an email thread or a contact form. Now the option has to live on the site itself: a clearly labeled function, available the entire 14 days, that walks the shopper through two steps, intent and confirmation, and closes with an automatic confirmation email, per William Fry's summary of the requirement.

Member states had until December 19, 2025 to write the directive into national law. The requirement itself became enforceable across the EU and EFTA states, Norway, Iceland, and Liechtenstein, on June 19, 2026, according to GT Law.

The Bar Is More Specific Than Most Stores Assume

A button alone doesn't clear the bar. Under the new rules, the withdrawal function has to stay live and reachable for the entire 14 day window, not just at the moment of purchase. It can't require the shopper to create an account first. It has to be resolved in two steps, one to state the intent to withdraw and one to confirm it, followed by an automatic email confirming the request went through.

The refund side has its own fine print. A withdrawal isn't just the price of the item coming back. Under the general cooling off right, the refund has to include the original delivery charge the shopper paid, not just the product cost. Duties and taxes follow the same logic. Miss any piece of that refund calculation and the withdrawal technically wasn't handled correctly, even if the button itself worked fine.

Individually, none of these requirements are hard to build. Together, they're easy to get half right, which is exactly what turns this into a compliance risk instead of a straightforward website update.

Getting This Wrong Is Expensive in Two Different Directions

Miss the requirement entirely, and the downside is regulatory. Beyond the fines already mentioned, a merchant who fails to provide a working withdrawal function, or fails to properly inform shoppers of their rights, can see the standard 14 day cooling off window stretch automatically to 12 months and 14 days. A purchase made this month could legally be returned more than a year from now.

But there's a second, quieter risk that has nothing to do with regulators. In the rush to get compliant, some merchants are routing withdrawal requests through the exact same flow as a standard return: a prepaid label, the same upsell prompts, the same handling. That instinct is understandable. It's also unnecessary. Nothing in the directive requires a merchant to pay for return shipping on a withdrawal. Under EU law, that cost sits with the shopper by default, unless the merchant has chosen to cover it or failed to disclose the policy upfront.

Treat every withdrawal like a full service return, and a requirement that was supposed to cost nothing more than the refund itself quietly turns into a second, ongoing return channel, with none of the volume caps that make a returns budget predictable.

What a Deliberate Setup Looks Like

The brands handling this well tend to do three things.

  1. They keep the withdrawal link separate from the standard returns portal, so it doesn't become the default path for every EU order.
  2. They state clearly, upfront, that return postage on a withdrawal is the shopper's responsibility.
  3. And they preserve the standard returns experience as the better CX route: more options like exchanges and store credit, plus return reason data merchants use to spot patterns over time.

Loop's native EU Withdrawal Flow is one example of this pattern in practice: a dedicated link, no prepaid label, refunds handled automatically once a request comes in. It's not the only way to build this, but it's a useful reference point for what "compliant, and nothing more" looks like when it's done on purpose.

Two Ways to Find Out Where You Stand

If you're already selling into the EU, it's worth auditing your current setup against the points above this week, starting with Loop's EU withdrawal guide.
If you're evaluating a returns platform with EU coverage in mind, book time with Loop to see how the native flow works.

Background

Are you evaluation a returns platform with EU coverage in mind

Book time with Loop to see how the native flow works

Retain more revenue with Loop today