Directive 2011\/83\/EU grants consumers a 14-day right of withdrawal, and the new Article 11a, effective June 19, 2026, requires every online store selling to consumers in the EU to offer an electronic cancellation feature. The legal framework, deadlines, and penalties are described in detail in the article on the new contract withdrawal requirements<\/a>, while here the focus is on exactly what WooCommerce has released, how to enable it, and where you\u2019ll need to make some customizations. <\/p>\n\n By default, “Order Withdrawal” is disabled, and the documentation itself specifies that the feature can help ensure compliance but does not guarantee it.<\/p>\n\n Go to WooCommerce > Settings > Advanced > Features<\/strong>, and look for ” Order withdrawal<\/strong> ” in the main list. It\u2019s not listed under experimental features, so no feature flag or definition in wp-config.php is required. Enable the option and save your changes. The description in the interface states that this activates a public feature for customer order cancellation requests. <\/p>\n\n After activation in WooCommerce ( >, Settings, >, Advanced, >, Page setup<\/strong> ), a new field called \u201cOrder withdrawal\u201d<\/strong> appears in the \u201cAccount endpoints\u201d<\/strong> group. The default value is \u201cwithdraw-order,\u201d which makes the form accessible at \/my-account\/withdraw-order. If you prefer a Bulgarian slug, such as otkaz-ot-poruchka, enter it there, and the form will work at \/my-account\/otkaz-ot-poruchka without having to regenerate permalinks. <\/p>\n\n The \/my-account\/ part comes from the page set as the “My account” page, and if you’ve renamed it, the endpoint will follow the new address.<\/p>\n\n The field in Page Setup exists only as long as the feature is enabled. If you disable it, the field disappears along with the URL rules. <\/p>\n\n The form requires a first and last name, an email address (entered twice for confirmation), and an order number. The customer chooses whether to cancel the entire order or only certain items; in the case of a partial cancellation, the \u201cAdditional details\u201d field becomes required, and the customer must specify which items are being returned. There is no field for a reason, and there is no registration requirement, which complies with the prohibition on additional mandatory fields in Article 11a. <\/p>\n\n Before submitting, the customer sees a screen to review the information entered. The request is sent only after confirmation, so the two-step process required by the directive is in place. This is followed by a confirmation screen and an email containing a copy of the submitted data. Check whether this email includes the date and time of receipt, because Article 11a explicitly requires them to be provided on a durable medium, and it is not clear from the text of the documentation whether they are included. <\/p>\n\n If they are missing, adding them is a necessary correction, not just a cosmetic change.<\/p>\n\n Notifications about new orders are sent to the Administration Email Address<\/strong> specified in the “Settings” > ” > ” > “General” section<\/strong> in WordPress, not to the email address specified in the WooCommerce settings. The “Reply-to” address is the customer’s email address, so a reply sent directly from your email inbox will reach them. <\/p>\n\n These emails do not appear in WooCommerce > Settings > Emails<\/strong>. They have no recipient field, no toggle to enable them, and no template that you can edit from there. If the requests need to be sent to a separate email address, the only built-in way to do this is to change the administrator email address. The text comes from the WooCommerce language pack, so if the Bulgarian translation is incomplete, you can correct it via Loco Translate or a gettext filter. <\/p>\n\n An inbox notification also appears on the WooCommerce home screen. When the order number and billing email address match those of an actual order, the request is automatically linked to it, and an order note is added to the order. This note is your internal record with the date and time. <\/p>\n\n An error in the order number or an order placed with a different email address does not stop the request. It is accepted, the customer receives the same confirmation, and you receive an email stating that WooCommerce was unable to link it to an order. In this case, there is no order note and no inbox notification, so the email is the only trace. You\u2019ll need to search for the order manually by name, email address, and the entered number. <\/p>\n\n The spam filter for incoming email here poses a real risk, because a single missed email means an unprocessed rejection, which, by law, can still be considered valid.<\/p>\n\n WooCommerce calculates the 14-day window from the order date, not the delivery date. The right of withdrawal in the EU begins upon receipt of the goods, but the system cannot reliably determine when the goods were delivered, so it uses the order date as a substitute. This approach is safe: the warning can only appear after the actual deadline, never before it. <\/p>\n\n For orders older than 14 days, a line is added to the email and the inbox notification stating that the order is past the deadline. This is for informational purposes only, and the order is processed as usual. <\/p>\n\n The same applies to the order status. A request can be linked to an order in any status, including “canceled,” “refunded,” or “failed.” Before taking any action, check the current status, because the form does not validate it. A duplicate request for a single order is rejected right in the form, and the customer sees a message asking them to contact you, without you receiving a notification about the second attempt. <\/p>\n\n There is also a limit of one request every 30 seconds per email address and per IP address.<\/p>\n\n Submitting a request does not change the order status, cancel the order, or generate a refund. The decision on how to proceed\u2014whether to issue a refund, request a return, or seek clarification\u2014is made entirely on a case-by-case basis. <\/p>\n\n The feature does not distinguish between items under Article 16 of the directive. An engraved mug and a standard T-shirt in the same order are treated the same, even though the former is excluded from the right of withdrawal. There is also no automatically generated link in the footer. WooCommerce creates an endpoint, but the visible link labeled \u201cWithdraw from the Contract Here<\/strong>,\u201d accessible from every page, must be added by you via the menu or using code. If your store was built before these requirements were introduced, now is the time to include this in your general review of the site\u2019s terms and conditions<\/a>. <\/p>\n\n Replace “footer” with the actual `theme_location` of your theme, and replace “withdraw-order” with the slug you selected, if you changed it in Page Setup. The snippet goes in the child theme’s `functions.php` file or in a code snippets plugin\u2014not directly in the theme. <\/p>\n\n Now that the feature is built into the core, the question is whether to stick with the plugin you\u2019re already using. The built-in version is no longer a dependency and receives updates along with WooCommerce. For now, plugins offer more control over the email template and text. If you already have a working plugin, keep only one of the two; otherwise, the customer will encounter two different forms for the same action. <\/p>\n\n For a new WooCommerce online store<\/a>, the built-in Order Withdrawal feature is a sensible starting point, and you should only add a plugin when a specific feature is missing.<\/p>\n\n Stores on other platforms receive the form ready-to-use after migration, which is another reason to migrate your online store to WooCommerce<\/a>. Pre-launch test: Place a guest order from an incognito window, submit a cancellation through the form, and check the customer\u2019s email and the order note. Only then should you publish the link in the footer. <\/p>\n\nHow to Activate Order Withdrawal<\/h2>\n\n
What the customer sees<\/h2>\n\n
![\"-\"](\"https:\/\/pixadoro.com\/wp-content\/uploads\/2026\/09\/Withdraw-from-contract-740x1024.webp\" "\\"-\\"")
<\/figure>\n\nWhat Does the Merchant Get?<\/h2>\n\n
![\"-\"](\"https:\/\/pixadoro.com\/wp-content\/uploads\/2026\/09\/Order-withdrawal-request-for-order-1024x670.webp\" "\\"-\\"")
<\/figure>\n\nWhen there is no match<\/h3>\n\n
The 14 days are counted from the wrong date<\/h2>\n\n
What the function does not do<\/h2>\n\n
add_filter( 'wp_nav_menu_items', function ( $items, $args ) {\n if ( 'footer' !== $args->theme_location ) {\n return $items;\n }\n $url = wc_get_endpoint_url( 'withdraw-order', '', wc_get_page_permalink( 'myaccount' ) );\n return $items . '<li class=\"menu-item\"><a href=\"' . esc_url( $url ) . '\">\u041e\u0442\u043a\u0430\u0437 \u043e\u0442 \u0434\u043e\u0433\u043e\u0432\u043e\u0440\u0430 \u0442\u0443\u043a<\/a><\/li>';\n}, 10, 2 );<\/code><\/pre>\n\nPlugin or built-in feature<\/h2>\n\n