Bitron Right of Withdrawal vs WordWave – Text to Speech AI Narration

From 19 June 2026, EU member states require every consumer-facing online shop to provide an online withdrawal function — not just static information, but a continuously available electronic interface where the consumer can declare intent to withdraw, and from which the shop sends an automatic confirmation on a durable medium. In Hungary the same rule applies through the amendment of Government Decree 45/2014. Bitron Right of Withdrawal delivers exactly that, accessibly. What the plugin does A continuously available, accessible withdrawal form — embeddable via the [bitrow_form] shortcode or the Withdrawal Form Gutenberg block, so it drops into any classic-editor page, a block-built layout, or a page builder that handles either. Tight WooCommerce integration: the form is surfaced to logged-in customers as a Withdrawal item in their My Account menu, but only while they have at least one order still inside the window — so a customer with nothing eligible doesn’t see a dead link. A withdrawal link is automatically attached to WooCommerce’s customer order emails (processing, completed, invoice) while the window is open — a discreet text link (not a prominent button) to avoid accidental clicks. Its position in the email (top, after the order details, or bottom — bottom by default) and both the surrounding message text and the link label are configurable under Settings → Email. HTML and plain-text variants, with a filter to extend the list of carrier emails. Guest and logged-in customer paths. A logged-in customer sees a select of their own in-window orders. For guests, optional email verification: with the free OneCode Login plugin active, the guest proves they own their email with a one-time code, and the form then loads that email’s orders just like for a logged-in customer — closing the gap where anyone who knew an order number and the billing email could file on someone else’s behalf. When email verification is not in force, an unverified guest is never shown any order data: instead of looking up an order, they file a free-text withdrawal declaration (no order is matched server-side, no line items or totals are disclosed), which is recorded flagged as unverified for the shop to match by hand. Order data is therefore only ever shown to logged-in or email-verified customers. Item-level partial withdrawal. After the customer picks an order, they tick exactly which line items (and quantities) they want to withdraw from — the form is not all-or-nothing. Bank-account capture for non-card payments. When the original gateway can’t refund automatically (e.g. cash on delivery, bank transfer), the customer enters a Hungarian IBAN or domestic GIRO account number — validated client- and server-side with MOD-97 / CDV checks — so the shop has everything to wire the refund manually. Customizable form copy and brand colors. An optional intro paragraph above the form and the submit-button colors (background + text) are configurable from Settings → Form, with a live WCAG contrast meter that announces the ratio as you type so a custom brand color cannot quietly drop below AA. An “advanced” panel additionally exposes the form body text, wrapper background, and input/fieldset border colors for themes that need the form to blend in — these three are not contrast-checked and carry an explicit “you own the contrast” warning. The same values can be overridden per-instance through [bitrow_form] shortcode attributes or the block’s Inspector panel. Automatic confirmation email to the customer (durable medium) and notification to the shop admin, with editable subject and body templates for both — empty fields fall back to safe i18n defaults so the plugin is functional out of the box. The admin notification recipient is a configurable email address (defaults to the site administration email); leave it empty to switch admin notifications off. Optional business-customer exclusion: because the right of withdrawal is a consumer right, shops that also sell to VAT-registered businesses can switch the online form off for orders carrying a business marker (e.g. a VAT-number checkout field). Business buyers are shown a contact pointer instead; consumer orders are unaffected. It’s a technical filter, not legal advice. Per-product and per-category withdrawal exemptions for the CRD §16 / 45-2014 §29 carve-outs (perishables, custom-made, sealed digital downloads, etc.). The withdrawal form still shows exempted items inside an eligible order so the customer sees what they bought, but the quantity input is locked at zero with a visible “Not eligible for withdrawal” badge; orders that consist entirely of exempt items are blocked at step 1 with a contact pointer. A separate Settings → Exclusions tab manages the lists with searchable autocompletes. Exclusion type split — excluded by law vs waivable. The exclusion settings separate two legally distinct cases: “excluded by law” items (perishables, custom-made, opened sealed goods) where the right never applies and no customer action is involved, and “waivable” items where the right exists but the customer can expressly give it up. Each case has its own product and category pickers; existing exclusions keep behaving as “by law”. Checkout withdrawal waiver. For waivable goods (typically digital content), the shop can show a consent checkbox at checkout through which the customer expressly waives the right of withdrawal for the affected items. It appears only when the cart actually contains a waivable item, works on both the classic shortcode checkout and the block-based (Store API) checkout, can be optional or mandatory, and records the consent on the order as evidence (timestamp, IP, a fingerprint of the statement text, the covered products and the mode). Off by default; enable and word it under Settings → Exclusions. “Withdrawals” hub in the customer’s My Account area — a single durable, log-in-gated landing page for everything withdrawal-related: a one-click button to start a new declaration (when the form page is configured), plus the full list of past declarations submitted from the account (reference number, date, order link, items, refund preference, status). The menu item appears only when the customer has at least one past record OR an order still inside the withdrawal window; the list itself is privacy-scoped to the customer’s own account email and never reveals records filed under a different email. Minimal record-keeping with unique BITROW-XXXXXX references for evidentiary value, plus a per-record detail page in the admin. Admin can mark a record as closed (and reopen it) once the case is resolved, with timestamp and the closing user recorded — keeps the working list focused on what’s still pending. Withdrawal status on the order screen. When an order has an associated withdrawal, the WooCommerce order-edit screen shows a “Right of withdrawal” panel with the withdrawal’s status and a direct link to its record. Optional withdrawal column on the orders list. A Settings → General switch (off by default) adds a column to the WooCommerce orders list flagging which orders have a withdrawal and its status (a dash when none). HPOS- and legacy-orders compatible. WCAG 2.1 AA accessibility throughout — programmatic labels, focus management, live regions, sufficient contrast. GDPR integration with WordPress’ personal data export and erase tools, plus a suggested paragraph for the Privacy Policy Guide. Compatibility The plugin integrates with WooCommerce orders. It declares HPOS (High-Performance Order Storage) compatibility and uses the WooCommerce CRUD API throughout. WooCommerce is referenced for compatibility only — the trademark is not used in the plugin name or slug. Important — what this plugin does NOT do This is a technical tool, not legal advice, and does not by itself guarantee legal compliance. The plugin does not generate Terms of Service text, privacy-policy text, or other legal content — those must be prepared by your own lawyer. The confirmation email contains only a factual acknowledgement (received, when, with which ID, what content); any “what happens next” wording is the shop operator’s own policy and must come from you. The plugin records each withdrawal and notifies you, but it does not issue refunds automatically. Refunds remain a deliberate admin action through WooCommerce’s standard refund interface. Privacy The plugin stores only what is necessary to acknowledge and document the withdrawal: name, email, order reference, optional note, timestamps and a unique identifier. No IP address is stored in plain text. On plugin removal the stored records are kept by default (so an accidental deactivation cannot destroy evidence); a setting lets you opt in to deletion at uninstall. Pro version The free plugin covers the full legal compliance core on its own. Bitron Right of Withdrawal Pro adds a convenience and automation layer on top, for shops that process withdrawals regularly: One-click WooCommerce refund — issue the refund straight from the withdrawal record, instead of re-entering it by hand in WooCommerce. Status management and history — a richer status workflow (received, in progress, goods returned, refunded, rejected) with a full audit trail of who changed what and when. Automation rules — define rules that act on incoming withdrawals automatically (status transitions, notifications), so routine cases handle themselves. Custom form fields — add your own fields to the withdrawal form and store them on the record. Searchable admin + CSV export — find any declaration fast and export the list for accounting or reporting. Webhooks — push withdrawal events to your CRM, ERP or any external system in real time. REST API — read and manage withdrawal records programmatically from your own integrations. The Pro plugin is standalone: it contains the full compliance core plus the convenience layer, so you install it instead of the free plugin, not alongside it. Pro adds convenience, not extra compliance — the free plugin already makes you compliant. Learn more and see pricing

The WordWave text-to-speech for WordPress transforms written posts into listenable audio using AI narration. It allows visitors to listen instead of read, improving accessibility, engagement, and time on page without changing your publishing workflow. With WordWave, you can convert blog posts to audio automatically or manually and display a lightweight audio player directly inside your content. The plugin generates high-quality MP3 audio and only displays the player where audio exists, ensuring a clean and fast experience. View and listen to our product video to hear actual generated AI audio narration you can easily add to your own site: or use this YouTube Link Text to Speech for WordPress Turn written WordPress content into audio using AI-powered text-to-speech technology (via OpenAI or ElevenLabs). Offer an audio version of your posts so users can listen while multitasking, commuting, or browsing hands-free. Turn Blog Posts Into Audio With Custom Intro Message Convert WordPress posts into audio automatically when published, or generate narration manually when needed. The built-in player embeds directly into your content, and features customizable introduction text. AI Narration Made Easy Generate natural-sounding AI voice narration without recording, editing, or hiring voice talent. Audio is saved as standardized 24kHz MP3 files compatible with all modern browsers. Built-In Audio Player WordWave includes a fast, lightweight audio player optimized for performance. It does not block page rendering and will only appear when audio is available. Accessibility Benefits Text-to-speech improves accessibility for visitors with visual impairments and provides an alternative way to consume content. Adding audio can increase user engagement and time on page. LISTEN TO DEMOS Listen to customizable AI audio narrations on these featured live sites: Blog Post Player Embed Example AI Audio Voiceover Example Video Vanguard Culture Audio Content Archive Page Press Wizards Blog Post ✅ Free Standard Features Text-to-speech for WordPress blogs AI narration with natural voice output Uses your OpenAI or ElevenLabs API key 5,000 word limit per narration Convert blog posts to audio automatically on publish or manually Built-in audio player Google Analytics tag on player Automatically add player to new posts Exclude specific posts using tags Ignore images and captions during narration Add intro message before narration Standardized 24kHz MP3 audio output Plugin updates ✨ Premium Upgrade (Optional) For content creators, podcasters, and professionals, a Premium version is available with expanded features and tech support. Check out our free trial for these features: Unlimited word count Multiple voice selections and language support Narrate pages, custom post types, and WooCommerce products Automatically generate audio for new content Player positioning controls Add intro and outro Downloadable MP3 files Podcast audio feed and archive page Voice styles (pace, tone) Built-in play stats dashboard Technical support AI Provider Voice Samples OpenAI currently offers 13 built‑in voices to control how speech is rendered from text. Listen to an overview of the voices here. ElevenLabs voice samples are available in the plugin’s Settings page, when ElevenLabs is selected as the AI provider, and retrieves then displays their current voices and sample links. External services OpenAI: This plugin connects to OpenAI’s Text-to-Speech API to generate audio narrations, it is needed to create MP3 files from post content. It sends post text segments, selected voice/model, and narration settings when narration is generated (manually or on publish). This service is provided by OpenAI: terms of use, privacy policy. ElevenLabs: This plugin can connect to the ElevenLabs Text-to-Speech API to generate audio narrations and voice previews when ElevenLabs is selected as the provider. It sends post text segments, selected voice/model, and generation settings when narration is generated (manually or on publish). It also sends short preview text and selected voice ID when an admin clicks a voice preview in settings. This service is provided by ElevenLabs: terms of service, privacy policy. WordWave Stats API (5starplugins.com): This plugin can send aggregate plugin usage and environment statistics to improve compatibility and product quality. It sends site URL, WordPress version, PHP version, plugin version, enabled provider, active feature flags, and aggregate player event totals. It does not send post content or visitor personal data. Data is sent only when Share Plugin Statistics is enabled by an admin, on settings save and on a scheduled interval. This service is provided by 5 Star Plugins: terms of use, privacy policy. WordWave Remote Sidebar Messages (5starplugins.com): This plugin fetches a JSON file from 5starplugins.com to display rotating sidebar notices on the plugin admin pages (for example, feature announcements and upgrade messaging). It sends a standard HTTP GET request to a 5starplugins.com JSON endpoint (for example, /wordwave-premium-messages.json) and includes a WordWave user-agent string that contains plugin version and site URL. Requests are made when the admin settings page loads and then cached in a transient for up to 24 hours. This service is provided by 5 Star Plugins: terms of use, privacy policy. Knowledgebase Widget (via support.5starplugins.com): This plugin loads a Knowledge Base and Support widget only on the WordWave admin pages only after clicking the Yes opt-in link for support resources when first activated. It is used to provide access to our own knowledgebase and support resources, and retrieves the KB articles only when clicked on. This service is provided by 5 Star Plugins: terms of use, privacy policy. This plugin includes the Freemius SDK, if you opt-in, it is used for optional analytics and licensing features. It loads only if you opt-in on plugin activation, or if you click on a Trial or Upgrade link. This service is provided by Freemius: terms of use, privacy policy.