Description
From June 19, 2026, EU Directive 2023/2673 obliges every online retailer in the European Union to offer a digital withdrawal function that is at least as easy to use as the purchase flow itself. Most plugins in the directory stop at “a button”. This one ships the complete toolkit every EU store needs to comply — and a few things competitors don’t offer at any price.
Only this plugin in the directory ships, all of it, for free
- Two-step confirmation function (Art. 11a(3)) — the EU-wide baseline of the online withdrawal right. The public form leads to a review screen with a read-only summary and a dedicated “Confirm withdrawal” button; the request is registered only when that button is pressed, preventing the unintended exercise of the right. Held server-side between the two steps in a single-use token, so it works even without JavaScript.
- Complete durable-medium acknowledgement of receipt (Art. 11a(4)): the confirmation email reproduces the full content of the declaration (name, order, order date, scope, affected products) and the exact date and time of submission, carrying a verifiable SHA-256 receipt hash as tamper-evident proof — recomputable from the stored fields if a dispute arises.
- Annex I.B model withdrawal form (Directive 2011/83/EU) generated dynamically from your shop data, rendered as a collapsible block below the public form, with a printable view on the same URL. Meets the pre-contractual information obligation of Art. 6(1)(h).
- Double-consent checkboxes at the WooCommerce checkout for the two consents the directive expects to apply specific exceptions:
- Mandatory consent for digital content (Art. 16(m)) — blocks the place-order step until accepted.
- Optional consent for services started within the 14-day window (Art. 14(4)(a)) — enables pro-rated billing if the customer later withdraws.
Every consent is persisted on the order with the exact text shown, accepted/declined state, timestamp, IP and user agent — durable proof in case of dispute.
- Single “Withdrawal status” dropdown per product and per category with four explicit options (Standard, Digital content, Service started early, Other Article 16 exception). Drives both the Article 16 exclusion flag and the matching checkout consent in one place, with full subcategory inheritance.
- Configurable public notice on excluded products, rendered between price and add-to-cart, with separate title+body for digital content and other Article 16 exceptions.
- Article 16 exclusions with category inheritance — competing plugins gate this behind a paid Pro tier; here it’s free.
- Native GDPR integration: suggested Privacy Policy snippet + personal-data exporter + eraser, all keyed on the customer email — no second GDPR plugin to install.
- Standalone mode: the form, shortcode, request log, email notifications, SHA-256 receipt hash, Annex I.B model and GDPR integration all run without WooCommerce. The plugin always lives in its own top-level Withdrawals menu (with a Settings submenu), with or without WooCommerce — same path on every install.
Public-facing pieces
- Public withdrawal page automatically created on activation with a neutral, translation-ready template and the form embedded via shortcode (with a “review with a legal advisor” disclaimer).
[ayudawp_withdrawal_form]shortcode for embedding the form anywhere on the site.[ayudawp_withdrawal_link]shortcode for a permanent link to the withdrawal page from any widget area, footer or template part — helps meet the “clearly identifiable” requirement of Article 11a of Directive 2023/2673 without forcing a specific footer layout.- HTML5-semantic form with HTML5 validation, honeypot anti-spam, escaped output, sanitized input and CSRF nonces.
- Privacy-policy acceptance checkbox before submit, linked to the WordPress-configured Privacy Policy page.
- Frontend and backend links generated by the plugin carry
rel="noopener nofollow"to keep the site’s link equity contained.
WooCommerce-specific pieces (auto-activated when WooCommerce is detected)
- My Account Right of withdrawal endpoint with a per-order “Withdraw” button shown while the order is in an eligible status, deep-linked to the form with the order pre-filled.
- Withdrawal notice injected into transactional emails (processing, completed, customer invoice) with a direct link to the form pre-filled with the order number. Eligible order statuses configurable; admin emails never receive the notice.
- Automatic verification of the order/email pair when WooCommerce is active: the request is matched to a real order and gated by the configured eligible statuses. The 14-day deadline is surfaced as an advisory flag for the admin, not an automatic rejection (the period legally runs from delivery, which the shop verifies).
- Configurable advisory deadline: choose order date vs. WooCommerce completion date as the basis, plus optional grace days, for the deadline flag surfaced to the admin — all from the settings UI, no code.
- Order-number compatibility with Sequential Order Numbers (free and Pro), Custom Order Numbers for WooCommerce (WPFactory) and YITH numbering schemes out of the box; a filter covers any other resolver.
- “Withdrawal” column on the WooCommerce orders screen (legacy and HPOS) showing the status of any linked request, toggleable from Screen Options.
- Private order notes added at every lifecycle step (request received, accepted, rejected, completed) including any admin comment.
- HPOS-compatible from day one, declared via
FeaturesUtil::declare_compatibility().
Admin tooling
- Full request log as a private custom post type with status lifecycle (pending accepted rejected completed), customer details, scope (full / partial), IP, user agent and UTC submission timestamp for legal traceability.
- CSV export of the request log for accounting and consumer-protection audits: an “Export to CSV” bulk action on the listing plus a filtered export by status and date range under Withdrawals Export withdrawals. Columns include submission and resolution timestamps, scope, status, acknowledgement-delivery flag, receipt hash and excluded items, with cells escaped against CSV/formula injection.
- Audit trail per request: resolution timestamp recorded on every status change and a flag for whether the acknowledgement email was accepted for delivery (with its timestamp), both shown in the request detail and the CSV as burden-of-proof evidence.
- Bulk actions to mark several requests as accepted, rejected or completed at once, with email notification on transition.
- Status metabox with required comment when rejecting, optional comment when completing — comment forwarded to the customer email.
- Acknowledgement email to the customer on confirmation: the Art. 11a(4) durable-medium receipt with the full declaration content, the date and time of submission and the SHA-256 hash as proof, plus a follow-up email on every status transition.
- Notification email to the shop admin with reply-to set to the customer, sanitized against header injection.
- Captured checkout consents surfaced in the request detail metabox: exact text, accepted/declined state, timestamp, IP, user agent — durable proof on file.
- Consistent admin menu: always a top-level Withdrawals menu with a Settings submenu, regardless of whether WooCommerce is active. Same path on every install.
- Legal disclaimer block in the settings page making it explicit that the plugin provides optional technical tools and does not guarantee legal compliance.
- Mandatory / Recommended / Optional tags on every setting description so the merchant can scan the form quickly.
Built for production
- Conditional asset loading: CSS only loads on the withdrawal page, single-product pages that actually show the excluded notice, and plugin admin screens.
- Translation-ready, bundled es_ES translation, follows WordPress Coding Standards, fully escaped output and sanitized input, capability checks and nonces on every admin action.
- 7 documented filters and 3 actions for developers and agencies to extend the plugin without forking.
- PHP 7.4+, WordPress 6.0+, WooCommerce 7.0+ (optional).
Why this plugin?
The EU directive becomes enforceable in every member state on June 19, 2026, so the WordPress.org directory is filling up with “withdrawal button” plugins. This one stands out for verifiable reasons:
- Fully free, no paid tier. No premium add-on, no feature locked behind an upsell, no “Pro” version on the horizon. Everything documented on this page is what you get on install.
- Two-step “confirm withdrawal” function built in, the EU-wide baseline of Article 11a(3): the public form shows a read-only review screen and registers the request only after explicit confirmation, fully server-side and working without JavaScript — where many “button-only” plugins register the request on the very first click.
- The only plugin in the directory that issues a SHA-256 receipt hash as durable-medium proof of every withdrawal request, recoverable from the stored fields if a dispute later arises.
- The only plugin in the directory that ships the Annex I.B model withdrawal form dynamically generated from the shop data, with a printable view — meeting the Art. 6(1)(h) information obligation that the new directive does not replace.
- The only plugin in the directory that injects the two consent checkboxes (Art. 16(m) digital content and Art. 14(4)(a) service started early) at the WooCommerce checkout, with durable proof persisted on the order.
- The only plugin in the directory that ships Article 16 product/category exclusions with full subcategory inheritance — competing plugins gate this behind their own paid Pro tier.
- The only plugin in the directory that integrates natively with the WordPress GDPR tools (Privacy Policy snippet + personal-data exporter and eraser) — no second GDPR plugin to install.
- Standalone or with WooCommerce. Works without WooCommerce as a self-contained tool (form, shortcode, log, emails, SHA-256, GDPR, Annex I.B) and lights up store-specific features automatically when WooCommerce is detected.
- Compatible by default with Sequential Order Numbers (free and Pro), Custom Order Numbers for WooCommerce (WPFactory) and YITH numbering schemes.
- Configurable from the settings UI, without writing code: deadline basis (order date vs. completion date), grace days, eligible order statuses, withdrawal page, notification email, consent text per type, excluded-notice text per type, Annex I.B trader phone.
- Developer-friendly: 7 documented filters + 3 actions so agencies can extend it without forking.
- Maintained by a Spanish WordPress trainer with 15+ years on the platform: bundled es_ES translation, prompt replies on the WordPress.org support forum and an active roadmap of free improvements (classic widget, Gutenberg block, dashboard widget, custom WC order status and more — all free).
Roadmap
Planned for upcoming free versions:
- WooCommerce Checkout block support for the Art. 16(m) and Art. 14(4)(a) consent checkboxes, using
woocommerce_register_additional_checkout_field()so the consents work on stores that have already migrated from the classic[woocommerce_checkout]shortcode to the block. - Classic widget to surface the withdrawal link in themes with widget areas.
- Gutenberg block for the withdrawal link, fully supported in block themes (align, color, typography).
- Dashboard widget with counters, pending requests and monthly basic stats.
- Custom WooCommerce order status “Withdrawal requested” with automatic transition on acceptance.
- Urgency indicators in the request list (days remaining, expired).
- PDF download of the request with the SHA-256 receipt hash printed on it, reusing the same standalone-print infrastructure as the Annex I.B view.
- Signed token in the email link so guest customers can check status without logging in.
- Rate limiting on the public form to prevent abuse.
- Optional IBAN field to speed up manual refunds.
- HTML email templates that inherit the WooCommerce email theme.
- Optional modal display mode for the shortcode.
- Visible audit log on each request detail screen (status transitions, admin comments, email-delivery timestamps).
- Optional opt-in auto-injection of the withdrawal link in
wp_footer.
Privacy
This plugin stores the following personal data for each withdrawal request, exclusively to fulfil the legal traceability of consumer rights and to allow the shop to handle the request:
- Customer name and email address (required to contact the consumer about the request).
- Order reference and order date (required to validate the request against the purchase).
- IP address and User-Agent string (required to evidence when and how the request was submitted, in line with the directive’s “durable medium” requirement).
- Submission timestamp (UTC) and SHA-256 receipt hash (required to recompute and verify the integrity of the original submission if disputed).
Data is stored as a private custom post type entry (ayudawp_withdrawal) accessible only to administrators. The plugin does not transmit any data to third-party services; all communication happens between the shop and the customer via standard WordPress emails.
You should add a section to your site’s privacy policy describing this storage. The plugin contributes a suggested Privacy Policy snippet that you can paste from Settings Privacy Policy Guide. Withdrawal data is also exposed to the native WordPress Tools Export Personal Data and Tools Erase Personal Data screens (filtered by customer email).
Support
Need help or have suggestions?
Love the plugin? Please leave us a 5-star review and help spread the word!
About AyudaWP.com
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.
Screenshots
Public withdrawal form with all required fields. 
Withdrawal log inside the WordPress admin. 
Per-request detail screen with status management, including the captured checkout consents (text, accepted/declined, timestamp, IP, user agent). 
WooCommerce My Account integration with per-order Withdraw button. 
EU Withdrawal Settings Page (WooCommerce active), with the Checkout consent, Annex I.B model and Excluded products notice sections. 
EU Withdrawal Settings Page (Standalone). 
Per-product “Withdrawal status” dropdown in the WooCommerce product editor (General tab), with the inheritance notice when the value is pulled from the product’s category. 
Per-category “Withdrawal status” dropdown in Products Categories edit screen. 
Excluded products notice rendered on the public single product page (between price and add-to-cart button). 
Mandatory digital-content consent (Art. 16(m)) shown at the WooCommerce checkout. 
Optional service-start consent (Art. 14(4)(a)) shown at the WooCommerce checkout. 
Annex I.B model withdrawal form rendered as a collapsible block below the public withdrawal form, with a printable view link.
Installation
- Upload the plugin folder to
/wp-content/plugins/. - Activate the plugin from the Plugins screen.
- The plugin creates a “Right of withdrawal” page automatically with a sample legal template. Review and edit it from Pages.
- Go to Withdrawals Settings to configure the notification email address and the page that hosts the form.
- Add the URL of the withdrawal page to your footer or to the legal links section so it is visible from any page on your site.
FAQ
-
Will the form check the 14-day deadline?
-
It does not auto-reject based on it. The 14-day withdrawal period legally runs from the moment the goods are delivered (or, for digital content, from the start of the download) — a date the shop cannot detect automatically — so rejecting a request on the order or completion date would risk turning away customers who are still within their legal window. Instead, the plugin flags requests that look past the approximate window in the admin notification email and lets you verify the real delivery date (for example from the carrier tracking) and decide. Eligibility for the form, the My Account button and the email notice is governed by the configured order statuses. You can still tune the advisory calculation (order date vs. completion date, plus grace days) under Withdrawals Settings, and the
ayudawp_euw_grace_daysfilter keeps working; theayudawp_euw_skip_deadline_checkfilter no longer has any effect, since there is no longer a deadline gate to skip. -
How do I mark products that are excluded from the right of withdrawal (Article 16)?
-
The plugin uses a single Withdrawal status dropdown set per category and per product.
- By category: go to Products Categories, edit the category and pick a “Withdrawal status” — for example Other Article 16 exception for perishable or custom-made goods, or Digital content (Art. 16(m)) for sealed digital content. Every product in that category (and its descendant categories) will inherit the status automatically.
- By product: edit the product, scroll to the General tab and pick the “Withdrawal status” there. By default it is set to — Inherit from category; pick any other option (including Standard) to override the inheritance for that product only.
The four possible statuses are:
- Standard — withdrawal applies normally (default).
- Digital content (Art. 16(m)) — product is excluded from the withdrawal right, and a mandatory consent checkbox is shown at the WooCommerce checkout for any cart containing the product.
- Service started early (Art. 14(4)(a)) — withdrawal still applies, and an optional consent checkbox is shown at checkout so the trader can charge a pro-rated amount if the customer withdraws after the service has started.
- Other Article 16 exception — product is excluded (perishable, custom-made, hygiene-sealed, sealed audio/video/software media unsealed after delivery, etc.), no checkout consent needed.
When a withdrawal request lands on an order containing excluded items, the plugin flags it in the admin notification email and on the request detail screen. The request is never auto-rejected, because a partial withdrawal over the non-excluded items in the same order can still be valid. The admin reviews and decides.
If the Excluded products notice is enabled (default: yes), a configurable notice will also appear on the single product page between price and add-to-cart button so the consumer reads it before purchasing.
Upgrading from earlier versions: any category that was previously listed in the retired “Excluded categories” picker is migrated automatically to the new per-category dropdown (with status Other Article 16 exception) on the next admin request. No configuration is lost.
-
How do the checkout consent checkboxes work (Art. 16(m) and Art. 14(4)(a))?
-
From version 1.5.0 the plugin can inject two consent checkboxes at the WooCommerce checkout when the cart contains products flagged for them:
- Type A (mandatory, Art. 16(m)): digital content. The customer must accept it to complete the order; without acceptance recorded, the customer keeps the 14-day withdrawal right even after accessing the content.
- Type B (optional, Art. 14(4)(a)): services started within the 14-day window. If accepted, the trader may charge a pro-rated amount when the customer withdraws after the service has started. Without it, an early withdrawal forces a full refund.
Each flag is set per product (General tab) or per category (Edit Category screen), with full subcategory inheritance — the same hierarchy used by the Article 16 exclusions module. The exact text shown to the customer, plus accepted/declined state, timestamp, IP and user agent, is persisted on the order so the trader has durable proof if the customer later contests the request. The metabox of each withdrawal request also surfaces these consents for the linked order.
The two checkboxes can be enabled/disabled globally from Withdrawals Settings Checkout consent, and their text is fully editable.
-
Does the plugin include the Annex I.B model withdrawal form required by Directive 2011/83/EU?
-
Yes, from version 1.5.0. The plugin renders the Annex I.B model form dynamically from the shop name, address (from WooCommerce when available) and notification email, with an optional trader phone configurable from settings. It appears as a collapsible block right below the public withdrawal form, with a printable view available from the same page. Providing this model is a pre-contractual information obligation under Art. 6(1)(h) of Directive 2011/83/EU — the online function added by Directive 2023/2673 complements but does not replace it.
-
What is the receipt verification code in the customer email?
-
It is a SHA-256 hash computed from the request data (post ID, customer name, email, order reference, scope, order date and submission timestamp). The customer keeps the email as a tamper-evident proof on a durable medium. If a dispute later arises, you can recompute the hash from the stored fields with the
ayudawp_euw_compute_receipt_hash()helper and confirm the original submission was not altered. -
Where are withdrawal requests stored?
-
Each request is saved as a private custom post type entry called
ayudawp_withdrawal. You can manage them under the top-level Withdrawals menu in your admin area. They are not publicly accessible from the frontend. -
Does it support HPOS (High-Performance Order Storage)?
-
Yes. The plugin declares HPOS compatibility on load.
-
Does the plugin work without WooCommerce?
-
Yes. The form, shortcode, withdrawal request log, email notifications, SHA-256 receipt hash and native GDPR integration all run as a standalone tool, with their own top-level Withdrawals menu in the admin and a Settings submenu. The plugin layers extra features on top automatically when WooCommerce is active: order/email validation gated by eligible order statuses (with an advisory deadline flag for the admin), “My Account” withdrawal endpoint, withdrawal notice injected into transactional emails, “Withdrawal” column in the orders screen, private order notes on every status change, and Article 16 exclusions by product/category. Activating WooCommerce later lights those features up; deactivating it leaves the standalone features intact.
-
Does it work with plugins that change the WooCommerce order number (Sequential Order Numbers, Custom Order Numbers, etc.)?
-
Yes. The form accepts both the internal WooCommerce order ID and the displayed order number. The resolver looks up the customer-facing number in the standard
_order_numberpost meta, which covers WooCommerce Sequential Order Numbers (free and Pro), Custom Order Numbers for WooCommerce (WPFactory) and any plugin that follows the same convention. For plugins that store the number elsewhere or compute it on the fly (e.g. YITH Sequential Order Number, custom integrations), use theayudawp_euw_pre_resolve_wc_orderfilter to provide your own resolver. -
Will the notice appear on every WooCommerce email?
-
No. By default the notice is only added to the customer-facing emails relevant to the withdrawal window: order processing, completed and customer invoice (the manually triggered one). Admin emails never receive the notice. The notice is also gated by the configured list of eligible order statuses (default: Processing and Completed) so the manual invoice email only carries it when the order is in one of those statuses. You can change the email list with the
ayudawp_euw_email_idsfilter and the status list under Withdrawals Settings Eligible order statuses or with theayudawp_euw_allowed_statusesfilter. -
In which languages is the plugin available?
-
All strings are translation-ready. Translations are managed through the official WordPress.org platform at translate.wordpress.org, so any locale with enough translated strings is delivered automatically to your site when the WordPress site language matches. Contributions to existing or new locales are welcome there.
-
Does the plugin pass GDPR requirements?
-
The plugin asks for explicit privacy policy acceptance before submission and stores the visitor IP and user agent only for the purpose of legal traceability of the request. See the Privacy section above for the full list of stored fields. From version 1.4.0 the plugin also integrates natively with the WordPress GDPR tools: a suggested Privacy Policy snippet appears in Settings Privacy Policy Guide, and withdrawal data is exposed to Tools Export Personal Data and Tools Erase Personal Data so admins can fulfil access and erasure requests without leaving the WordPress admin.
-
What happens if the customer deletes their WordPress user account?
-
The withdrawal log is independent of the WordPress user table — it lives as a private custom post type indexed by the customer email. Deleting the user account does not delete the log automatically; the customer must request erasure through Tools Erase Personal Data (where the plugin registers an eraser that removes every withdrawal request matching the customer email) or you can delete the corresponding
ayudawp_withdrawalentries manually if your retention policy requires it. -
Can I customise the email subjects and bodies?
-
Currently the emails are sent in plain text and their copy is translatable through the standard WordPress text-domain. HTML email templates that respect the WooCommerce email theme are planned for a later release. For now, advanced customisation requires hooking into the wp_mail filters.
-
Which hooks does the plugin expose for developers?
-
Filters:
ayudawp_euw_grace_days— extra days added to the 14-day deadline. The default is the value stored in settings; the filter receives that value, so returning$days + Nadds on top of it.ayudawp_euw_skip_deadline_check— retained for back-compat but no longer has any effect: since 1.8.0 the deadline is advisory and never gates a submission, so there is nothing to skip.ayudawp_euw_email_ids— array of WooCommerce email IDs where the withdrawal notice is injected.ayudawp_euw_allowed_statuses— array of order statuses (without thewc-prefix) for which the withdrawal button and email notice are offered. Receives the value stored in settings and the currentWC_Order(when available).ayudawp_euw_allow_unverified_order— returntrueto accept submissions whose order number cannot be matched against a real WooCommerce order. Useful for sites that also handle non-WC purchases.ayudawp_euw_pre_resolve_wc_order— short-circuit the order resolver. Return aWC_Orderinstance to accept,falseto reject, ornull(default) to fall through to the built-in strategies. Useful for plugins that store the displayed order number outside the standard_order_numberpost meta (e.g. YITH Sequential Order Number, custom ERP integrations).ayudawp_euw_resolve_wc_order— late filter that receives the resolvedWC_Order(orfalse) and the raw reference, for auditing or last-chance overrides.
Actions:
ayudawp_euw_after_submission— fires after a withdrawal request has been processed. Arguments: CPT ID, submission data array.ayudawp_euw_after_status_change— fires after a status change (individual or bulk). Arguments: CPT ID, new status, optional admin comment.ayudawp_euw_after_form— fires inside the public form wrapper, right after the</form>tag, so modules can inject content below the form without coupling. No arguments. Used internally by the Annex I.B model form.
-
Is this plugin enough to comply with EU Directive 2023/2673?
-
The plugin covers the functional requirements that Directive 2023/2673 imposes EU-wide from 19 June 2026: a discoverable digital withdrawal function, eligibility by order status with an advisory deadline flag, Article 16 exclusions with subcategory inheritance, durable-medium proof via the SHA-256 receipt hash, the model form from Annex I.B of Directive 2011/83/EU and the double-consent checkboxes at checkout that enable the Art. 16(m) and Art. 14(4)(a) exceptions. On top of that it adds operational tools that the directive does not mandate but that make handling requests practical: per-status email injection, status lifecycle with bulk actions, native GDPR integration, public notice on excluded products and full traceability. Member States can layer extra national requirements on top of the EU baseline — the two-step confirmation flow with an intermediate review page expected by the strictest member states (Germany, for example) ships since version 1.7.0; a future release will adapt to any further requirement in the final Spanish Real Decreto once it is published. Legal compliance ultimately depends on your business model, catalog and jurisdiction; the plugin provides the technical building blocks, not legal advice — consult a consumer-law specialist for your specific case.
Reviews
Contributors & Developers
“EU Withdrawal Compliance” is open source software. The following people have contributed to this plugin.
Contributors
“EU Withdrawal Compliance” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “EU Withdrawal Compliance” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.8.0
- Improved: Withdrawal requests are no longer auto-rejected by the deadline. The 14-day period legally runs from delivery (Art. 9(2)(b) of Directive 2011/83/EU), a date the shop cannot detect automatically, so blocking a request on the order or completion date risked turning away consumers still within their legal window. Eligibility is now governed by the order status, and requests that look past the approximate window are flagged in the admin notification email for manual review instead of being rejected — the same “never auto-reject, a human decides” approach already used for Article 16 excluded items. The My Account button and the transactional-email notice follow the same rule, so an order in an eligible status always offers the withdrawal entry points. The deadline settings (basis, grace days) now tune that advisory flag, and the
ayudawp_euw_skip_deadline_checkfilter is retained for back-compat but no longer has any effect. - Improved: the public form, the confirmation screen, the success message and the acknowledgement email now state clearly that submitting a request does not by itself mean the withdrawal is accepted: it remains subject to the statutory deadlines and conditions (the 14-day period counted from delivery, or from the start of the download for digital content, and the Article 16 exceptions). Keeps expectations honest now that the deadline is no longer a hard gate.
- Improved: the default “Other Article 16 exception” excluded-product notice, the per-product/category status label and the auto-generated withdrawal page now mention sealed audio, video or software media unsealed after delivery (Art. 16(i) of Directive 2011/83/EU), so shops selling CDs, vinyl, films or boxed software recognise the exception without rewriting the text. Existing notices edited from Settings keep their stored value; only fresh installs and untouched defaults see the new wording.
- Fix: on the classic checkout, the digital-content consent checkbox (Art. 16(m)) could be shown twice — once in the customer-details column and once in the order-review panel that WooCommerce refreshes via AJAX, which a per-request guard could not deduplicate across the two render passes. It now renders a single time, in the customer-details column, a spot the AJAX refresh leaves untouched, so the required checkbox also stops losing its checked state when the customer changes address, shipping or payment method.
For older changelog entries, please check the changelog.txt file