Why a checklist — and why now

Since 19 June 2026, the electronic withdrawal function under Article 11a of the Consumer Rights Directive (Directive 2011/83/EU as amended by Directive (EU) 2023/2673) has been mandatory for online shops selling to consumers. Each Member State has transposed it into national law; in Germany, the implementation is § 356a BGB. Most shops have built in “something” by now. Whether it actually meets the requirements is another question: a contact form with a “Submit” button, a returns portal behind a login, or a link labelled “Returns” does not fulfil the obligation.

This checklist helps you audit your own shop in about 15 minutes. It is organised into five areas: the button itself, the two-step flow, the acknowledgement of receipt, the legal texts, and your internal processes. At the end, you will find all points again in a compact list to tick off.

The legal background is explained in detail in the article EU Withdrawal Button 2026: Requirements, Scope, Implementation.

Part 1: The button

1. The label is unambiguous

The button must be labelled “Withdraw from contract here” or an equivalent, unambiguous wording. Terms such as “Contact”, “Service”, “Returns”, or “Cancel” are ambiguous and not sufficient.

Check: Does the element your customers click say “Withdraw from contract here” verbatim, or use an equally clear wording?

2. The button is continuously available

The function must be available throughout the entire withdrawal period — not just on a subpage that customers first have to find. In practice, a link in the footer of every page works well, supplemented by a dedicated withdrawal page or a floating button.

Check: Can the button be reached with one click from the homepage, from product pages, and from the cart?

3. The button is prominently placed and easily accessible

“Prominently placed” means: the button must not be hidden in body text or set in tiny light-grey type. “Easily accessible” also means: no login required. Customers who ordered as guests must be able to withdraw just as easily as customers with an account.

Check: Does the withdrawal work on a smartphone and without a customer account?

4. The button works in every market you sell to

If you sell to several EU countries, the withdrawal function should appear in the language of the respective storefront — including the label, the form, and the acknowledgement email. A German button on the French version of your shop is hardly understandable for French customers.

Check: Switch the shop language and run through the withdrawal once per language.

Part 2: The two-step flow

5. Step 1 only asks for permitted information

In the first step, you may only require the information needed to identify the withdrawal: name, a contract identifier (for example the order number), and a means of communication for the acknowledgement (usually the email address).

Check: Are there any further mandatory fields — such as phone number, address, or customer number? If so, make them optional or remove them.

6. A withdrawal reason is never mandatory

Consumers do not have to give a reason for withdrawing. A dropdown with reasons is permitted as a voluntary field and useful for analysis — as a mandatory field, it hinders the withdrawal and is not permitted.

Check: Can the form be submitted without selecting a reason?

7. Step 2 is a genuine confirmation

After the input, a second button labelled “Confirm withdrawal” (or an equivalent wording) must follow. Only this click submits the withdrawal declaration. A simple form with a “Submit” button does not represent this two-step flow.

Check: Are there two separate steps — entering the details, then explicitly confirming?

Part 3: The acknowledgement of receipt

8. The acknowledgement arrives immediately and on a durable medium

After the confirmation click, the shop must acknowledge receipt without delay — on a durable medium, which in practice means by email. A success message in the browser alone is not enough, because it is not durable.

Check: After a test withdrawal, does an email arrive within a few minutes — and does it stay out of the spam folder?

9. The acknowledgement contains the content, date, and time

The email must reproduce the content of the withdrawal declaration as well as the date and time of receipt. The timestamp should be generated server-side so that it is traceable and cannot be manipulated. It matters because a withdrawal confirmed before the deadline counts as timely — even if you only process it later.

Check: Does the acknowledgement include the name, order reference, email address, and the date and time?

10. The acknowledgement confirms receipt only

The acknowledgement confirms that the declaration has been received — not that the withdrawal is substantively valid. Phrases such as “Your withdrawal has been accepted” or “Your refund has been initiated” are problematic at this point.

Check: Is the text worded neutrally (“We received your withdrawal on … at …”)?

Part 4: The legal texts

11. The withdrawal policy mentions the electronic withdrawal function

Your withdrawal policy must refer to the electronic withdrawal function, typically with wording such as (example): “You can also exercise your right of withdrawal online at [URL].” If this reference is missing, the worst case is an extended withdrawal period of 12 months and 14 days. More on this in the article Ignoring the Withdrawal Button: Warnings, Fines, 12-Month Risk.

Check: Has the policy been updated in all language versions — including order confirmations and terms and conditions?

12. Privacy policy and DPA are up to date

The withdrawal function processes personal data. Your privacy policy should describe the purpose, legal basis, and retention period. If you use a service provider for this, you additionally need a data processing agreement (DPA) under Art. 28 GDPR.

Check: Is the service provider named in your privacy policy, and do you have a DPA in place?

Part 5: Your internal processes

13. Withdrawals reach a responsible person

A withdrawal sitting in an unread inbox helps no one. Decide who handles incoming withdrawals, and keep an eye on the refund deadline: as a rule, the refund must be made no later than 14 days after the withdrawal is received.

Check: Who is notified of a new withdrawal, and where can you see its processing status?

14. Withdrawals are documented traceably

For follow-up questions, disputes, or a warning letter, you should be able to prove when each withdrawal was received and how it was handled. An export or a record per case saves a lot of time when it counts.

Check: Can you prove the time of receipt and the handling for any withdrawal from the past few months?

15. You have tested the flow yourself

Run a complete test withdrawal: on a smartphone, as a guest, with a real order number and an external email address. Repeat the test after every theme change — theme updates occasionally remove embedded blocks or links.

Check: When did you last run through the withdrawal yourself?

Common mistakes in practice

  • Contact form instead of a withdrawal function: no two-step flow, no acknowledgement with timestamp.
  • Returns portal behind a login: guest customers cannot withdraw.
  • Mandatory “reason” field: hinders the withdrawal in a way that is not permitted.
  • Just one sentence in the withdrawal policy: without a button in the shop, the function does not exist.
  • Relying on Shopify's built-in tools alone: why Shopify's cancellation feature does not cover every point is explained in the article Shopify Cancellation vs. EU Withdrawal Button.

The checklist to tick off

  1. Button labelled “Withdraw from contract here” or equivalent
  2. Button reachable from every page throughout the entire period
  3. Button prominently placed, usable on mobile, no login
  4. Button, form, and email in all shop languages
  5. Step 1 only requires name, order reference, and email
  6. Withdrawal reason voluntary at most
  7. Step 2 with a “Confirm withdrawal” button
  8. Acknowledgement sent immediately by email
  9. Acknowledgement with content, date, and time (server-side)
  10. Acknowledgement only confirms receipt
  11. Withdrawal policy mentions the electronic withdrawal function
  12. Privacy policy updated, DPA with the service provider in place
  13. Responsibility and refund deadline settled internally
  14. Withdrawals documented traceably
  15. Flow tested yourself, including after theme updates

How Revoq covers the technical points

Points 1 to 10, as well as 13 and 14, are technical requirements that Revoq handles for Shopify shops: a clearly labelled button as a dedicated page, section, or floating button; a two-step form without login; optional withdrawal reasons; an acknowledgement with a server-side timestamp in all 24 official EU languages; plus a dashboard, status workflow, and export. A DPA under Art. 28 GDPR is included in every plan. The Free plan fully covers the legal obligation — see pricing.

You need to update the legal texts (points 11 and 12) yourself or together with your legal-text provider.

Note: This checklist provides a practical overview and does not constitute legal advice. For binding statements about your shop, consult a law firm specialising in e-commerce or your legal-text provider.