Aller au contenu principal

Webflow compliance

The withdrawal solution for Webflow

Last reviewed on

If your Webflow site sells online to consumers in the EU, the withdrawal button has been mandatory since 19 June 2026 (Directive (EU) 2023/2673, across the 27 EU member states). If your site does not yet have one, you are already past the deadline: every sale concluded without a button extends your customers' right of withdrawal to 12 months and 14 days. Webflow lets you inject code, so adding it is straightforward, with one caveat: it only becomes active after publishing. BackToMe gives you the line to paste.

0 € today · Cancel in one click · 30-day money-back guarantee

Why Webflow does not do it for you

Webflow is a web design tool distributed all over the world. The withdrawal button meets a European obligation (Directive (EU) 2023/2673), harmonised across the 27 EU member states by the Consumer Rights Directive (2011/83/EU). Webflow does not offer a native feature compliant with this framework: bringing your site into compliance is down to you.

BackToMe adds to your Webflow site to collect the withdrawal request, acknowledge receipt with an email the customer keeps, and archive it with a timestamp: proof that holds up (before a judge or the CCPC in Ireland). The button appears across all your pages, as the regulation requires.

How to install it on Webflow

Via the global Head Code

Project Settings > Custom Code > Head Code. You paste the BackToMe tag, which applies to the whole site. It is the Webflow equivalent of an injection into the <head>.

A paid Site plan is required

Custom code in production is not available on the free plan. You need a Site plan (Starter, Basic, CMS, Business). To sell to consumers, you have a paid plan with a custom domain anyway, so nothing changes.

Detailed installation guide for Webflow (steps, pitfalls, screenshots)

The Webflow pitfall to know about

Custom code is only active after publishing. Webflow distinguishes between Designer changes and the published version. Until you have clicked Publish > Publish to Selected Domains, the code is neither on the *.webflow.io subdomain nor on your custom domain. Republish after every addition, then check on the production URL, not in the Designer. This is the most common source of confusion on Webflow.

What BackToMe takes care of

The compliant button across the whole site

A visible, permanent withdrawal button, with a clear label, displayed on all your Webflow pages as required by European regulation.

The automatic acknowledgement of receipt

Every request triggers an acknowledgement of receipt sent to the customer by email, which they keep as evidence of their action.

Archiving that stands as proof

Every request is timestamped and archived in a way that is impossible to alter afterwards: solid proof, ready to present to a judge or an inspector in the event of a dispute.

The merchant notification

You are notified of every withdrawal. The refund is still carried out by you in your e-commerce solution (Webflow Ecommerce, Foxy, Shopify Buy Button) or your payment gateway: BackToMe never touches your payments.

The risk if you do nothing

Since 19 June 2026, the withdrawal button has been mandatory across the whole EU. Without a compliant mechanism, a B2C Webflow site is exposed to two cumulative risks: a penalty from the regulator in the buyer's country (in Ireland, the CCPC can impose fines up to €60,000 under the Consumer Rights Act 2022, and up to 4% of annual turnover (€2,000,000) for widespread infringements under the EU Omnibus Directive (EU) 2019/2161) and the extension of the withdrawal period to 12 months and 14 days for poorly informed customers.

A customer can then cancel an order up to a year after the purchase and obtain a full refund. The potential cost quickly exceeds that of getting compliant.