EU Withdrawal Button 2026: What Webshops Need to Change

From 19 June 2026, webshops selling to consumers in the EU need to provide a clearly visible electronic withdrawal function. Most merchants call it the “withdrawal button”, but the important part is broader than a button in the footer.

The 14-day cooling-off period already existed. The practical change is that customers must be able to exercise that right digitally, through an easy-to-find function on the same online interface where they bought.

This article is not legal advice. It is the implementation view: where the requirement touches your webshop platform, return flow, cancellation logic, email confirmation, ERP, WMS and customer service process.

What actually changes?

Under EU Directive 2023/2673, online B2C sellers need an electronic withdrawal function for contracts concluded through an online interface. Shopify’s own help documentation summarises the key parts:

• a clearly visible button or link;
• a two-step confirmation flow;
• enough order or contract details to identify what is being withdrawn;
• automatic confirmation to the customer on a durable medium, such as email;
• applicability to businesses selling online to EU consumers, even if the business is not based in the EU.

So this is not just a new policy page. A hidden paragraph in your returns policy is not the same as a usable withdrawal flow.

Why this matters beyond Shopify

Shopify has published guidance because many Shopify merchants sell to EU consumers. But the requirement is not Shopify-specific.

It can affect webshops running on:

• Shopify;
• Lightspeed;
• WooCommerce;
• Magento / Adobe Commerce;
• Shopware;
• BigCommerce;
• custom storefronts;
• headless commerce builds.

The technical question is simple: can the customer trigger a withdrawal request clearly, and can your systems process it correctly without manual confusion?

That is where standard platform settings often stop being enough.

The flow you need to check

A compliant-looking button is easy. A reliable flow is harder.

Review the full path:

• Entry point: where does the customer find the withdrawal function?
• Eligibility: does the flow handle exceptions, partial orders and expired windows?
• Order lookup: can guest customers identify an order without a full account login?
• Confirmation: does the customer actively confirm the withdrawal?
• Email: is an automatic timestamped confirmation sent?
• Operations: does support, ERP, WMS or finance receive the right status?
• Refund logic: is the refund workflow consistent with your current return and cancellation process?

If these pieces live in different tools, a standard app may only solve the visible part.

Where standard tools can fall short

For smaller stores, a platform feature or app can be enough. But edge cases appear quickly:

• B2C and B2B customers use the same storefront;
• customers can check out as guests;
• partial cancellations are allowed;
• orders are already exported to ERP or WMS;
• custom products or exempt product groups need different rules;
• the store operates in multiple EU countries;
• returns, cancellations and refunds are handled in separate systems.

In those situations, the withdrawal function becomes a workflow problem, not just a theme change.

What to do now

Start with an audit before adding another app.

1. Map how withdrawal, return and cancellation requests currently enter the business.
2. Check whether your platform already supports the required electronic function.
3. Test guest checkout, partial orders, edge cases and email confirmation.
4. Decide where the source of truth lives: webshop, ERP, WMS, helpdesk or middleware.
5. Document what happens after the request is submitted.

The goal is not a pretty button. The goal is a clear customer flow and clean back-office handling.

Duxly’s angle

Standard settings are useful when the process is standard.

But when your webshop connects to ERP, warehouse software, fulfilment partners, marketplaces or custom customer service flows, the withdrawal requirement touches more than the storefront. It affects order status, cancellation timing, refund handling and operational visibility.

That is where Duxly usually comes in: not to replace a standard feature, but to connect the parts standard tooling does not cover.

If your Shopify, WooCommerce, Magento, Lightspeed or custom webshop needs the withdrawal flow tied into ERP, WMS, support or finance, review it before the issue becomes a support queue problem.

Useful starting points:

• Shopify’s EU right of withdrawal guidance
• Directive (EU) 2023/2673 on EUR-Lex