EU Withdrawal Button for WooCommerce

2.1.0

• New pricing model: one free edition + one Pro plan (€79/year) with every paid feature. Existing Basic licenses purchased earlier remain fully valid.
• New: withdrawals overview for everyone — the free edition now shows the full withdrawals list in the admin (read-only; one-click management actions are Pro).
• New: GDPR consent checkbox (Pro) — optional privacy notice + required checkbox on the confirmation step, with a {privacy_policy} placeholder linking to your privacy policy page.
• New: payment-method-aware IBAN field (Pro) — optionally show the refund IBAN field only for offline payments (COD, bank transfer, cheque); card payments are refunded via the gateway.
• New: IBAN protection (all plans) — refund IBANs are now stored encrypted, displayed masked (EE38****5877) with an explicit reveal action, masked in CSV exports and REST responses, and automatically erased 30 days after the withdrawal is completed (with an audit note).
• New: return instructions page — select the page with your return instructions; the customer confirmation email links to it (falls back to your WooCommerce Terms page).
• New: WordPress privacy tools integration — withdrawal records are included in the built-in personal data export and erasure (Tools → Export/Erase Personal Data).
• New translations: Italian and Dutch. Italian contributed by Cristina Gregolin (Artilabio), Dutch contributed by Mark Govaerts (Bepos) — thank you!
• Fix: bundled translations now actually load — the load_plugin_textdomain() call was lost in the 2.0.0 refactor, so Estonian/Finnish/French/Swedish stores saw English.
• Fix: the Export CSV button (Pro) did nothing — its AJAX handler was never registered.
• Fix: the My Account countdown badge replaced the order number link; the linked order number is now always shown with the badge next to it.
• Fix: bulk “Mark as completed/rejected” now performs the complete flow (order status, order note, customer email, previous-status restore) exactly like the row actions; the REST API complete/reject endpoints too (previously the REST reject restored the wrong status and re-sent WooCommerce status emails).
• Fix: products in excluded categories (and Pro product-level exceptions) can no longer be selected in a partial withdrawal — exempt lines are shown unselectable and filtered server-side.
• Fix: the withdrawal form no longer fails on sites with full-page caching (the security nonce baked into cached HTML expired; the public endpoints now rely on rate limiting + order/email verification).
• Fix: the customer confirmation email no longer promises a refund deadline tied to the (possibly extended) withdrawal window, and only mentions the “withdrawal closed” email when that email actually exists and is enabled.
• Fix: fresh installs now show the sticky bar on all page types by default (existing installations keep their settings).
• Fix: plain-text emails no longer contain raw HTML; the merchant email order link is HPOS-safe.
• Fix: the “Require order validation” setting is now labelled accurately (“Require email match”) — the order number was always verified regardless of the toggle.
• Performance: frontend CSS/JS and the modal markup now load only on pages with a withdrawal entry point; the admin orders list and My Account column no longer run one query per row.
• Developer: ra_euwb_confirmation_before_actions action in the form template; ra_euwb_offline_payment_methods filter; shared set_withdrawal_status() service behind admin, bulk and REST status changes.

2.0.2

• Fix: the optional footer “Right of withdrawal” link is now always visible — it previously inherited the theme’s footer text colour and could blend into the background. It now sits on a light strip with a clearly coloured link.
• New: French (fr_FR), Finnish (fi) and Swedish (sv_SE) translations bundled.

2.0.1

• Fix: the withdrawal total on the confirmation step now updates live as the customer checks/unchecks items or changes quantities, instead of always showing the full order total.
• Fix: the withdrawal total now reflects only the selected line items — shipping, fees and other order lines are no longer included.
• Tweak: the confirmation total is now labelled “Withdrawal total” for clarity.
• Compatibility: tested up to WordPress 7.0.

2.0.0

• WordPress.org edition. First release published on the WordPress.org plugin directory. Feature parity with 1.5.x, Lite tier only. Paid upgrades continue to be distributed via riin.eu.
• Code: Full prefix refactor to ra_euwb_ / RA_EUWB_ / ra-euwb- across options, hooks, CSS classes, JS globals, nonces and admin menu slugs, to comply with the WordPress.org guidelines on unique prefixes. Existing WC order status slugs (wc-ewb-withdrawn, wc-ewb-completed), the database table ({prefix}ewb_withdrawals) and the _ra_euwb_deactivated_withdrawal order meta key are preserved so existing installations continue to work without data migration.
• Code: Removed all inline <style> and <script> output. Admin order-status colours and the frontend ra-euwb-hidden utility class are now part of the enqueued stylesheets. Frontend button colours are static (overridable via theme CSS) instead of dynamic option-backed inline styles.
• Code: Custom CSS setting removed from the free build (WordPress.org guideline: plugins must not execute arbitrary user-supplied CSS from options).
• Code: Text domain updated from eu-withdrawal-button to eu-withdrawal-button-for-woocommerce to match the WordPress.org plugin slug.
• Misc: Removed the now-unused class-ewb-i18n.php helper (text domain is loaded directly via load_plugin_textdomain() on init).

1.5.0

• Compliance Update — EU Directive 2023/2673. All compliance-critical features are available in the free version.
• Guest-friendly direct link in order emails: The WooCommerce customer “processing” and “completed” order emails now include a “Withdraw from this order” button. The link opens the withdrawal form pre-verified against the order — no login required. Solves the guest-checkout compliance gap (the directive explicitly requires that withdrawal must not depend on having a customer account).
• Dismissible sticky bar: Visitors can close the sticky bar with an X button. Dismissal is remembered for a configurable number of days (default 7, configurable 0–30) via localStorage. My Account pages ignore the dismissal and always show the bar (EU compliance — customer must be able to request a withdrawal there).
• Partial withdrawal support: Customers can now select specific items and quantities to withdraw instead of the whole order. The confirmation step shows per-item checkboxes and quantity inputs, pre-filled with the full order.
• Optional IBAN field: Customers can provide a bank account for the refund (useful when they paid by card or want the refund sent to a different account). Leaving it empty tells the merchant to refund to the original payment method. The IBAN is shown prominently in the merchant notification email and in the admin withdrawals list.
• Configurable sticky bar display: New “Show sticky bar on” multiselect under Withdrawal Button → General lets merchants pick which page types show the sticky bar (Homepage, Shop & product pages, Cart & checkout, Other). The My Account pages always show the sticky bar (EU compliance — customer must be able to request a withdrawal there). Existing installations default to My Account pages only after the upgrade, so update your settings if you want the sticky bar elsewhere.
• Discreet footer link: Optional small “Right of withdrawal” link can be shown in the footer (useful when the sticky bar is disabled on most pages).
• Admin: Withdrawals list now shows a Full / Partial badge and a hoverable list of the selected items per request, plus a dedicated IBAN column.
• Emails: Customer confirmation and merchant notification emails now list only the selected withdrawn items (with a partial-withdrawal notice when applicable) and show the IBAN. Legacy rows from pre-1.5.0 fall back to the full-order view.
• Database: New withdrawn_items (JSON) and iban columns on {prefix}ewb_withdrawals. The upgrade runs automatically on plugin load via dbDelta() — no manual action required.
• Security: Submitted item selections are re-validated server-side against the actual order (quantities clamped, unknown items rejected) to prevent tampering.
• Security hardening (CIA audit pass): (a) CSV export now escapes spreadsheet formula injection (leading =, +, -, @, tab, CR) and includes the Withdrawn Items + IBAN columns that were previously silently misaligned. (b) Client IP detection no longer trusts HTTP_X_FORWARDED_FOR / HTTP_CLIENT_IP by default — sites behind a trusted reverse proxy (e.g. Cloudflare) can opt in via the ewb_trust_forwarded_ip filter. (c) Submission now holds a MySQL advisory lock per order around the duplicate check + insert, closing the race window that allowed two simultaneous clicks to create duplicate withdrawal rows. (d) The public ewb_validate_order and ewb_lookup_by_key endpoints are now rate-limited (30 requests per 5 minutes per IP). (e) “Order not found” and “email does not match the order” are collapsed into a single generic verification error to prevent order enumeration. (f) Support form Reply-To header explicitly strips CR/LF defending against header injection.

1.4.0

• IMPORTANT: Clarified “Withdrawal Completed” semantics. Renamed the user-facing label to “Withdrawal Closed” everywhere it appeared (order status, emails, order notes, My Account box, admin). The status no longer implies that an automatic refund has been issued — merchants must refund manually via WooCommerce → Orders. Automatic wc_create_refund() integration is planned for a future Pro release. Internal status slug (wc-ewb-completed) is unchanged so existing orders continue to work.
• IMPORTANT FIX: The sticky bar, withdrawal form, confirmation email, “closed” email and admin information guide previously hardcoded “14 days” even when merchants configured a different ewb_withdrawal_days value. All texts now reflect the configured value dynamically with proper single/plural handling. Merchants can also use the {days} placeholder in the custom Bar text field.
• Updated customer closed-request email to clearly state that the merchant will issue the refund manually, instead of claiming the refund has already been processed.
• Added a “Heads up” admin notice on every plugin settings tab explaining the manual refund workflow.
• Performance & reliability: Order number lookup fallback (step 3) now filters by the configured withdrawal window (days + 2 buffer) instead of the arbitrary “last 500 orders” limit, and is capped at 1000 orders scanned. Both bounds are adjustable via the ewb_order_lookup_cutoff_date and ewb_order_lookup_max_scan filters. A warning is logged if the fallback triggers — this helps merchants spot custom order number plugins that don’t use the standard _order_number meta key.
• Code quality: Custom CSS (Basic+) now uses wp_add_inline_style() attached to the main ewb-frontend stylesheet handle instead of printing a raw <style> tag on wp_head. This integrates with minify/cache plugins and follows WordPress standards.