Carticy Widerrufsbutton & EU Withdrawal Form for WooCommerce

The button is the visible part. The value is the record behind it: a durable receipt the customer keeps, a tamper-evident fingerprint stored with each request, the model form, your exclusions, and recorded consent for digital goods. That is what lets you show what happened, later, if anyone asks.

Yes, completely. There is no paid version, no locked features, and no upsell prompts, and it does not collect or send your data to us.

No. It provides the tooling and the records; it is not legal advice. Confirm your wording, exclusions, retention and refunds with qualified counsel.

Yes. The flow follows the withdrawal-button model (Art. 11a Directive 2011/83/EU; § 356a BGB) with two separately labelled controls and a durable-medium acknowledgement, and it ships the German Muster-Widerrufsformular wording.

Each request is signed with a keyed HMAC-SHA256 over its contents, using a secret generated once and kept private on your site. Because the secret never leaves the server, a stored request cannot be silently changed or forged and still produce the same fingerprint, and the customer holds an independent copy in their emailed receipt.

Yes. HPOS and cart/checkout blocks are declared compatible, and the digital-content consent is captured on both the classic and block checkout.

By default, no: refunds stay a deliberate decision. But you can opt in. Under Order handling you can have the order status change (On hold or Cancelled) when a request is confirmed or completed, and issue the refund automatically when you mark a request complete. The default leaves the order untouched.

Yes, and that is the default. After you confirm a withdrawal the customer gets a return code and your return address, the request waits at a "Received" step until the parcel arrives, and the refund settles when you mark it complete. You can turn the wait off if you prefer to refund straight away. A full withdrawal refunds the items and the original outbound shipping, and you can deduct for value lost to handling beyond normal inspection.

Yes. Choose Store credit when completing a withdrawal (or set it as your default) and the plugin issues the refund as a single-use, email-locked WooCommerce coupon and sends the customer the code. This covers most exchange requests without any third-party service.

From when the order reaches the status you treat as delivered (Completed by default), because the right of withdrawal runs from when the customer receives the goods, not from the order date. It also works with shipment-tracking plugins that record an exact delivery date.

Not directly, because reliable label generation depends on each store's carrier account and country. You can record a return tracking number on each return, and a carrier integration can supply a prepaid label.

Yes. Every customer and admin notification is sent through WooCommerce's own email template, so it uses your store's email header, colors, logo and from-address, exactly like the rest of your WooCommerce emails.

Yes. Turn on the webhook under Settings and point it at a URL from Zapier, Make, n8n, or your own service; every event (created, confirmed, completed, rejected) is posted there as JSON. Add a signing secret and each request is signed so you can verify it came from your store.

The WooCommerce Orders list gains a "Withdrawal" column showing each order's withdrawal state, and the order screen has an "EU Withdrawal" panel with the same badge and a link into the queue. The order's own status is never overwritten unless you turn on order automation.