Withdrawal Button

Why do I need a withdrawal button?

EU Directive (EU) 2023/2673 adds a so-called withdrawal function to the Consumer Rights Directive: consumers should be able to withdraw from contracts concluded via an online interface as easily as they entered into them. The background is a digital imbalance: ordering takes a few clicks, while withdrawing has often required considerably more effort. The directive came into force in December 2023, the national transposition deadline ended on 19 December 2025 – and for retailers the obligation takes effect on 19 June 2026. It affects anyone concluding contracts with consumers in electronic commerce; pure B2B shops without consumer access are exempt. However, as soon as private customers can also order, the obligation applies.

Practical relevance for shop operators

The button must be permanently visible, easy to read and unambiguously labelled – wording such as "withdraw from contract" is recommended. The process has two steps: clicking the button opens a form in which the customer provides the necessary order details; after submitting, they automatically receive a confirmation. The button does not replace the existing right of withdrawal, it merely makes exercising it easier – deadlines and exceptions remain unchanged. For common shop systems such as Shopware, plugin solutions can be expected; depending on the setup, a custom implementation may be necessary, for example with heavily customised checkouts. We have summarised the requirements and implementation details in our article on the withdrawal button requirement 2026.

Typical mistakes

• Ambiguous labels such as "cancel order", "abort" or "service request" – the label must unambiguously refer to withdrawal
• Offering the button only inside the logged-in customer account, even though it must be easily accessible – including for guest orders
• Not sending an automatic confirmation of receipt to the customer
• Assuming the obligation does not apply to mixed B2B/B2C shops, even though consumers can place orders
• Planning the implementation at the last minute without allowing time for testing, process adjustments and legal review

What to look out for

The withdrawal button is not just a frontend topic: incoming withdrawals must be processed cleanly internally – from returns handling and refunds to integration with merchandise management or ERP. It therefore makes sense to look at the button together with the existing returns process and to clarify responsibilities. A well-designed process can also be aligned with checkout and conversion optimisation: transparent handling of withdrawals and returns tends to strengthen customer trust. Violations risk cease-and-desist letters under unfair competition law, and the missing function may also be subject to fines – timely implementation is therefore advisable.