If your business sells online to consumers in the EU, you may have heard about an “EU withdrawal page” or “withdrawal button”. The first thing to get right is the subject: this is about withdrawing from an online consumer purchase contract. It is not a new cookie-consent withdrawal page.
Directive (EU) 2023/2673 amends the EU Consumer Rights Directive and introduces a withdrawal function for certain distance contracts concluded through an online interface. The relevant requirement applies from 19 June 2026. This guide explains the practical implications for UK and US businesses selling to EU consumers.
What the EU withdrawal function is
Under Directive (EU) 2023/2673, a trader must provide a consumer with an electronic way to withdraw from a distance contract when the contract was concluded through an online interface and a right of withdrawal applies. The function must be clearly labelled with “withdraw from contract here” or an equally clear formulation, be prominently displayed, and remain easily accessible throughout the withdrawal period.
The function should let the consumer send an online withdrawal statement and easily provide or confirm their name, the contract they want to withdraw from, and the electronic address to which confirmation should be sent. The Directive does not prescribe one software product. A well-designed form, account flow or service integration can be used if it meets the legal and operational requirements.
Who should prepare
Start with your customer processes, not a generic “EU website” label. Review whether you conclude distance contracts with EU consumers through a website, app or another online interface, and whether those contracts carry a statutory right of withdrawal. The exact scope can depend on the product, service, contract type and exceptions in the applicable consumer law.
- UK businesses selling to EU consumers should map EU-facing checkout and post-purchase processes rather than assume UK rules answer every question.
- US businesses should identify EU consumer sales, the contracting entity, delivery countries and the process used for cancellation, return and refund requests.
- Marketplaces and technology suppliers should clarify which party is the trader and who operates the withdrawal interface.
This is not a rule that every business must create a page for every sale, nor does the Directive remove the statutory exceptions. Obtain advice on your product and sales model where the scope is unclear.
What the page or button should do
A compliant design should make the route findable and the request unambiguous. The customer should not have to search through a privacy policy, start a chat, or guess whether “cancel order” has the same legal effect as withdrawal.
Use direct wording
Use wording such as “Withdraw from contract” or “Withdraw from contract here”. Do not rely on a vague “Help” or “Returns” link as the only route. The wording should be understandable in the language used for the consumer processes.
Keep it accessible during the withdrawal period
The function must be continuously available throughout the withdrawal period and prominent enough to find. Test it on mobile, from order confirmation and account pages, and for customers who do not have an account. Accessibility does not mean the trader loses the ability to verify the contract or assess an exception; it means the customer can initiate the statement without unnecessary friction.
Capture and confirm the request
Collect only what is needed to identify the customer and contract, including the confirmation email address. Give the consumer a clear final action and a durable confirmation showing when the statement was received and what it relates to. Keep an audit trail so customer service can explain what happened.
What happens after submission
A withdrawal function is a route for exercising a right. It is not automatically the same thing as a refund engine, a returns label or an order-cancellation switch. Your operating process should timestamp the statement, match it to the contract, check whether an exception or timing issue applies, and route the case to the team responsible for fulfilment and refunds.
- Send a confirmation to the consumer and retain the request record.
- Check the applicable withdrawal period and any lawful exception for the contract or goods.
- Explain return, collection or repayment steps clearly; do not promise a refund before the relevant checks are complete.
- Keep customer-service scripts aligned with the online form and terms.
- Restrict access to request data and set an appropriate retention period.
Withdrawal is also different from a commercial returns policy. A voluntary “30-day returns” offer may be broader than the statutory right, while a statutory withdrawal request has its own legal conditions and consequences. Keep the labels and workflows distinct.
Practical implementation checklist
- Map EU consumer contracts concluded through each online interface.
- Record which contracts have a withdrawal right and which exceptions need specialist review.
- Choose a clear, translated label and a prominent location that remains available during the period.
- Design the statement flow to capture the consumer, contract and confirmation details.
- Test logged-out, mobile and assisted-customer processes.
- Connect submissions to fulfilment, returns, refunds and customer support without treating the tool as the decision-maker.
- Log receipt times, actions and confirmations with appropriate access controls.
- Review pre-contract information and confirmation messages, including the location of the withdrawal function.
- Re-test after checkout, theme, app or payment-provider changes.
How this differs from cookie-consent withdrawal
There is no general new “EU cookie withdrawal page” mandate created by Directive (EU) 2023/2673. Cookie consent is a separate data-protection issue. Under GDPR Article 7(3), where processing is based on consent, the data subject can withdraw consent at any time and it must be as easy to withdraw as to give it. That normally means your cookie or privacy interface needs a practical way to revisit choices and stop consent-based processing, subject to the wider ePrivacy and data-protection analysis.
In short: a contract-withdrawal button helps a consumer exercise a consumer-law right about a purchase. A consent control lets a person change a data-protection choice. Do not combine the two into one vague “withdrawal” promise.
FAQ
Is this a cookie-consent withdrawal page?
No. The Directive concerns withdrawal from an online consumer contract. GDPR Article 7(3) separately requires consent withdrawal to be as easy as giving consent when processing relies on consent.
Does every online sale need a withdrawal button?
Do not assume that. First establish whether the contract is within the Directive’s scope and whether a right of withdrawal applies. Product and contract exceptions matter.
Does the function automatically cancel the order or issue a refund?
No. It enables the consumer to send a withdrawal statement. Your process must assess the request and handle returns, cancellation and repayment under the applicable rules.
Can customers be required to log in?
The Directive requires an easily accessible online route and the statement details needed to identify the contract. A forced login may create avoidable friction. Test whether your design lets a customer initiate the request without unnecessary barriers.
Next steps for managers
Nominate one owner for the customer-law workstream, one for the technical processes and one for fulfilment and refunds. Then walk through a real EU order from checkout to request confirmation. If the customer cannot find the route, understand its effect or receive a reliable record, the implementation needs more work before 19 June 2026.
For the separate cookie-consent question, start with your existing cookie guidance and review the consent-management processes independently. For legal scope, use the primary Directive text and take advice on your specific contracts.
Sources
- Directive (EU) 2023/2673, EUR-Lex.
- Regulation (EU) 2016/679 (GDPR), EUR-Lex.
- Consentmo vendor example (illustrative product implementation, not legal authority).
