Withdrawal Pro Pro

Yes. Pro is an extension (addon) for the free plugin – it requires active “Withdrawal” (buddypilot-withdrawal) version 1.0.1 or newer. The free version can be downloaded for free from WordPress.org. Pro is installed separately from a ZIP file downloaded from buddypilot Hub after purchase.

Three main signals that Free is not enough: (1) Your store sells WooCommerce subscriptions – Free treats subscriptions like regular products and does not cancel renewals upon withdrawal. (2) You sell bundles (Product Bundles) – Free cannot correctly calculate the refund for a partial bundle return. (3) You handle more than 5-10 declarations per month and want refunds created with one click instead of manually clicking through all line items. If none of these apply, Free usually suffices.

No. Refunds are always approved by the operator from the declaration detail page. “Auto-refund” means the plugin builds a WooCommerce refund with the exact items and amounts declared by the customer – the operator sees everything before clicking “Approve”. There is no “automatic refund after X days without verification” mode.

Pro features continue to work – we never disable code at runtime. Only automatic updates are paused, and only after a 14-day grace period from expiration. This is the “GPL soft-expiration” model: you pay for updates and support, not for access to features.

Each license is assigned to one domain. Transfer requires contacting hello@buddypilot.pl with information about the new domain – we do this manually and free of charge. Common reasons: migrating staging to production, changing the store domain, transitioning from .local to hosting.

Currently we fully support WooCommerce Product Bundles (the official Woo addon). YITH Product Bundles and WPC Product Bundles are on the roadmap – follow the changelog. Composite Products (Woo) is also planned. If you use a different bundle plugin and need support, let us know via support – we prioritise the roadmap based on requests.

Upon filing a withdrawal declaration for an order containing a WooCommerce subscription: (1) all associated subscriptions with active and on-hold status are cancelled immediately, (2) the proportional amount for the unused portion of the current billing period is calculated in accordance with Article 9(2)(b)(iii) and recorded in the order meta, (3) a cancellation note is added to the subscription and parent order, (4) the customer sees a confirmation notice in My Account. The operator sees the proration in the refund preview and can accept or modify it before clicking “Approve”.

No. The plugin creates a refund in WooCommerce (with exact line items and amounts) and a PDF withdrawal declaration as a legal document. A credit note is a separate accounting document typically generated by an invoicing plugin (e.g. WooCommerce PDF Invoices, Flexible Invoices, WP-Hermes). We work correctly with these plugins – the WooCommerce refund triggers the issuance of a credit note in their workflow.

19 June 2026. From that date, every online store selling to consumers in the European Union must have a withdrawal function compliant with Article 11a – regardless of the seller’s country of registration. This also applies to stores outside the EU if they sell to EU consumers. Enforcement is handled by national consumer protection authorities (UOKiK in Poland).

Yes. The plugin integrates with native WordPress privacy tools: personal data export (Personal Data Export) includes the consumer’s declarations, anonymization (Personal Data Eraser) removes or anonymizes data in declarations according to the WordPress process. Full minimum: we do not collect more data than is required to handle the withdrawal (email, order number, optional reason provided by the customer).

Very minimally. Most of the code is loaded only in the admin panel and on pages related to withdrawal (form, declaration detail page, Annex page). The order front-end in My Account has minimal overhead: one DB query to check if the customer is eligible for withdrawal, plus rendering the button. All admin operations run on native WP mechanisms.