The mandatory online withdrawal function: prepare your store for the new EU rules
From 19 June 2026, online interfaces used to conclude covered distance contracts in the EU are due to provide consumers with a straightforward online withdrawal function. For e-commerce teams, this is both a legal change and a technical process involving the interface, form, confirmation, order logic and customer communication.
Many stores still handle withdrawal requests manually through email, PDF forms or disconnected customer-service tools. A compliant and usable implementation may therefore require a controlled end-to-end workflow rather than a single footer link.
Not sure whether your store needs changes? We can analyse the current withdrawal process, identify gaps and define the technical scope of the new function.
Arrange a technical e-commerce consultation to identify what should be implemented before the new rules apply.
Quick checklist: is your store ready?
Before adding a button, review the complete journey from both the customer’s perspective and the administrative workflow.
Your store should allow the customer:
- access to the panel or order history,
- the selection of the specific contract concerned by the withdrawal,
- an indication of the products or services covered by the notification,
- filling in the online form,
- passing through the second step of confirmation,
- receipt of confirmation by e-mail,
- retention of confirmation with the date and time of dispatch of the notification.
On the administration side, it is worth checking whether:
- service of the store receives a clear notification notice,
- the application is linked to a specific order,
- the status of the order or return changes in accordance with the shop process,
- the application is recorded in the customer’s history or order,
- the shop employee sees exactly what the withdrawal is about,
- the process does not require manual search for emails, PDFs or notes in the system.
If any answer is “no”, “I don’t know” or “we handle that manually”, the store may need technical changes. This is particularly important where WooCommerce, PrestaShop, Shopify or a custom platform connects the withdrawal process with customer accounts, order history, automated messages or external systems.
Check whether your store is ready for the withdrawal function
We can analyse the current withdrawal process, including customer accounts, order history, forms, confirmations, internal notifications and any external integration.
After the review, you will receive a defined list of technical changes to consider before 19 June 2026.
Check whether your store requires a withdrawal button
It is more than a button
A common mistake is to treat the requirement as a purely visual change: a link, button or clause in the policy. The interface control is only the beginning of the withdrawal journey.
In practice, implementation should include several elements:
1. A clearly visible withdrawal function
The customer should be able to find and start the process easily. It should not exist only inside terms and conditions, a footer link or a generic contact form.
2. An online form
The form should identify the consumer, the relevant contract or order and the scope of the withdrawal. Where appropriate, known details can be filled from the authenticated account and order history.
3. A confirmation step
The process should clearly confirm that the consumer intends to submit the withdrawal declaration and allow obvious mistakes to be corrected.
4. Confirmation on a durable medium
After submission, the consumer should receive confirmation containing the relevant details and time of the request.
5. Order and case-status logic
The store needs a defined response: record the request, mark the order, create the relevant case and route it to the responsible workflow.
6. A customer-account view
Showing the submitted request against the relevant order can reassure the customer and reduce follow-up questions about whether it was received.
7. An administrative view
The store team should see the order, customer, scope, submission time and current status in one clear record.
Implementing the withdrawal function is not a content-editing task. It is a technical, user-experience and operational change.
Legal basis and scope of the new rules
Directive (EU) 2023/2673 amended the consumer-rights framework by introducing an online withdrawal function for covered distance contracts concluded through an online interface. Its purpose is to let consumers submit a withdrawal declaration through a clear digital process.
In practice, the online interface needs a clear and easy-to-find withdrawal function throughout the applicable withdrawal period. The exact period and exceptions depend on the type of contract and circumstances.
The Directive covers a broad range of consumer distance contracts, including many online sales of goods and services. Scope and exceptions should be checked for the specific offer, particularly for digital content and financial services.
Businesses concluding covered B2C distance contracts through an online interface should review the requirement in the law applicable to their market. The Directive sets 19 December 2025 as the transposition deadline and 19 June 2026 as the application date for the new provisions.
Who is affected?
The obligation to provide an unambiguous withdrawal button applies to all distance sellers (mainly via the internet) to consumers in the EU. In other words, online stores selling goods or services to natural persons, including shops offering:
- Physical goods(clothes, electronics, house, hobbies, etc.),
- Digital services and online content (e-books, streaming, apps, etc.),
- Subscriptions and subscription services (e.g. video streaming, delivery of boxes, subscriptions),
- Online financial services (consumer credit and insurance sold remotely).
The rule concerns covered consumer contracts. A transaction concluded solely between businesses does not use the consumer withdrawal right, although mixed B2B/B2C stores still need the correct logic.
Implementation deadline
Member states were required to transpose the Directive by 19 December 2025. The relevant provisions are due to apply from 19 June 2026. Stores should confirm the final national rules and complete legal, technical and operational changes before the application date.
Requirements for the withdrawal function
The function must be prominent and continuously available during the applicable withdrawal period. The interface should use clear wording and place the control where a consumer can reasonably find it, such as the relevant order view.
The consumer should be able to submit the withdrawal declaration online without having to print a document, send a separate email or call customer service.
Specifically, the seller must:
- Provide a clearly visible ‘Withdraw from contract’ button(or equivalent) in an online store,
- Guarantee that the button will be active and available throughout the statutory withdrawal period (normally 14 days from receiving the goods or concluding the contract),
- After clicking the button automatically confirm withdrawal(e.g. by sending an e-mail on a durable medium) and removing goods from customer orders,
- Adjust the rules and return policy – inform that the return of goods in the online store is possible by a new button and describe the whole procedure.
In summary, the withdrawal function must be easy to find and must start a complete, recordable process. Implementation may require changes to order management, customer accounts, messages and staff procedures.
Is an off-the-shelf return module enough?
In simple stores, a ready plugin or module can solve part of the problem. However, it is not always enough to add the function itself if the store has a custom customer panel, modified checkout, own order status, integrations with ERP, CRM, complaint system or manual returns service.
Before installing an off-the-shelf module, check whether it fits the current order and customer-service workflow. A visible button is not enough if the request becomes difficult to identify, route or complete after submission.
Use the change to review the whole store
The implementation of the withdrawal button often shows the technical condition of the entire shop. If the customer panel is illegible, the order statuses are random, the forms work manually and the service must complement the data outside the system, the problem usually does not end with the button itself.
This is a good time to check also checkout, cart, customer panel, automatic messages, complaint process, integrations, speed of operation and way of handling orders. Sometimes it’s enough single implementation. Sometimes it’s more worth ordering most of the store instead of sticking another feature to a system that already makes it harder to sell.
In Hypercon we look at such changes more widely: not only as a technical obligation, but as an opportunity to improve the purchasing process and customer service. If it turns out that the current store needs more modernisation, we can propose a specific plan: from quick improvements to remodeling or implementation of a new online store.
How does implementation differ by platform?
The scope of the works depends on which system the store operates, what the current order process looks like and whether the store uses ready-made modules, custom integration or dedicated customer panel.
WooCommerce
In WooCommerce-based stores, implementation is mostly about my account panel, order history, order status and automatic emails.
Possible technical work:
- adding the withdrawal function at the selected order,
- creation of a form linked to a specific order,
- service of partial withdrawal from the contract,
- adding new status or metadata of the order,
- sending automatic confirmation to the customer,
- notifying the store administrator,
- record the application in the history of the order.
In WooCommerce a lot depends on the theme, used plugins, how to handle returns and integration with external systems.
PrestaShop
In PrestaShop, implementation can include customer panel, order details, email templates and handling of applications in the administration panel.
Possible technical work:
- adding the withdrawal function at the order,
- preparing the online form,
- adapting the customer view,
- establishing a link between the application and the order,
- configuration of e-mail messages,
- identification of the application by the administrator,
- adapting the process to current order statuses.
In the case of PrestaShop you need to pay attention to the system version, template, returns modules and possible modifications made previously by other developers.
Shopify
In Shopify the scope of implementation depends on the configuration of the store, the type of customer accounts, used applications and the possibility of adjusting the theme and processes after purchase.
Possible technical work:
- adding a visible start of withdrawal function,
- preparing the online form,
- linking the application to the order number,
- use of tags, notes or automation,
- sending confirmation to the client,
- forwarding the application to the store,
- integration with return application or external system.
In Shopify it is particularly important to check whether the current process is based on application, manual operation, enquiry form or external return system.
Custom e-commerce platform
In dedicated stores, implementation is the most dependent on system architecture. On the one hand, it gives greater flexibility, on the other hand, it requires careful analysis of code, database and administrative processes.
Possible technical work:
- design of the full withdrawal path,
- adding a button in the appropriate interface location,
- creation of a form and a second step of confirmation,
- record of reports in the database,
- linking the application to the client and the order,
- support for statuses and notifications,
- preparation of a view for the administrator,
- integration with ERP, CRM, storage system or return tool.
In dedicated stores it is worth start by auditing the process, because there is no one universal module that can be simply installed and run.
Possible consequences of non-compliance
Non-compliance may lead to civil or administrative consequences under the applicable consumer-protection framework. The exact authority, procedure and sanction depend on the national implementation and the nature of the infringement.
Existing consumer law already provides consequences for missing or incorrect information about the right of withdrawal, including an extension of the withdrawal period in defined circumstances. Legal advice should confirm how those rules interact with the new online function.
For the retailer, this can mean a longer period of uncertainty, additional handling costs and regulatory exposure. Do not rely on a generic penalty figure: assess the final Polish implementation and the existing consumer-protection rules with legal counsel.
We can implement the technical process
We can implement the technical withdrawal process in WooCommerce, PrestaShop, Shopify or a custom e-commerce platform.
We will define where the function should appear, how the form and confirmation should work, what the customer sees and how the request reaches the store team.
Let’s talk about implementation before 19 June 2026.
How to implement the withdrawal function
Implementing the withdrawal function combines legal interpretation, technical development and user experience. First confirm whether the platform can support the required interface, data capture, confirmation and operational workflow. Keep the function available and easy to find throughout the applicable withdrawal period.
Hypercon provides the technical e-commerce implementation: forms, interface controls, confirmations, statuses, customer-account views and order-system integrations. We can prepare the implementation scope for review by the client’s legal adviser.
The result is a controlled technical process aligned with the agreed legal requirements and clear customer communication.
What can we implement in your store?
The implementation of the withdrawal button does not always mean the same work. In a simple shop, a visible withdrawal function, form and automatic confirmation may suffice. In a more extensive e-commerce you may need to connect to the customer panel, the history of orders, the status of return, the complaint handling system or the logistics tool.
- analysis of the current return process in the store,
- design of the location and way of displaying the button,
- implementation of the withdrawal form,
- automatic confirmation sent to the customer,
- linking the application to the order,
- return statuses in the administration panel,
- integration with a return or CRM system,
- forwarding amendments to the update of the Rules of Procedure and the Return Policy.
The store receives more than a button: it gains an operational process that works for the customer, administration and service team.
Send us the store address and we will outline the likely implementation scope.
Common implementation mistakes
The implementation of the new function may seem simple, but in practice many shops make mistakes that make it difficult for the customer to exercise the right of withdrawal.
The most common problems are:
Link only in the Rules of Procedure
If a customer needs to look for information in a long regulation, the process is not intuitive. The withdrawal function should be easy to find in the shop interface.
A downloadable PDF only
A PDF may be an additional channel, but it should not replace the required online process. Downloading, printing, scanning and sending a document creates unnecessary friction.
Email-only handling
Manual email makes requests harder to track. Messages may remain in a shared inbox, reach the wrong person or lose their connection with the order.
No second confirmation step.
The process should clearly indicate that the customer makes a declaration of withdrawal. The second step helps to avoid accidental clicks and arranges the entire path.
No automatic confirmation.
The customer should be informed that the application has been accepted. Without confirmation, the number of enquiries to handle the store is increasing.
No connection between the application and the order
If the administrator has to manually check which order the client message relates to, the process is susceptible to errors and delays.
No information for store service
The application should go to the right place: administration panel, CRM system, service box or return management tool.
No process history
Record the date, time, scope and current status. A complete history supports consistent service and reliable evidence of submission.
Do not wait until the change becomes urgent
A new obligation related to the withdrawal button may require changes in the interface of the store, forms, order statuses, automatic messages and customer service procedures. The more extensive the store, the greater the risk that implementation will not consist solely of adding one button.
If you are unsure whether the current process is ready, we can analyse the customer and administrative journey and prepare a scoped list of technical changes.
Set up an online store consultation and see what is worth improving before 19 June 2026.
Frequently asked questions
Is a link to a return form enough?
Not always. The new rules require an easily accessible withdrawal function in the shop interface and confirmation of the application. In practice, it is worth checking the whole process: the visibility of the button, form, confirmation, order status and service of the application on the administration side.
Does a WooCommerce store need the withdrawal function?
If the WooCommerce shop sells products or services covered by the right of withdrawal to consumers in the EU, it is worth preparing to implement the return function. The scope of work depends on the current process: customer panel, order status, forms, e-mail messages and possible integration.
Can Hypercon add the withdrawal function to an existing store?
Yes, we can analyse the existing store and prepare the technical implementation of the withdrawal function. We are checking the current return process, customer panel, forms, automatic messages, statuses and possible integrations with the order handling system.
