

Compliance check: each item with its status, what we found and what to do.
The UK Digital Markets, Competition and Consumers Act 2024 brings in new rules for subscriptions: customers must be able to leave online as easily as they joined, get a written confirmation when they cancel, and see the key terms before they subscribe. The UK government announced in August 2026 that the rules come into force in January 2027. The draft regulations that fill in the details — The Consumer Subscription Contracts (Cancellation and Information) Regulations 2026 — were laid before Parliament in October 2026 and are due to apply from 1 January 2027; they are not yet made, so the wording may still change.
Renew Forge helps a WooCommerce Subscriptions store get ready now, and keeps a record of what happened when a customer cancels. Wording and behaviour are configurable, so you can match them to the final regulations and to your own terms. It is a tool, not legal advice, and it does not guarantee compliance on its own.
Renewal reminders, cooling-off refunds and a pre-contract acknowledgement at checkout are part of Renew Forge Pro, a separate plugin.
The customer presses Cancel subscription. The subscription moves to “Pending cancellation” at once: the customer keeps access until the end of the period already paid for and no further payment is taken. The page confirms it and shows the date access ends, and the confirmation email goes out. A second press changes nothing.
Cancellations made another way — with the WooCommerce Subscriptions Cancel link, by a shop manager in wp-admin, by a payment gateway or through the REST API — are confirmed and journaled too, once per cancellation. By default the WooCommerce Subscriptions Cancel link is replaced by the Renew Forge button, so customers have a single way to cancel; you can keep it in the settings.
If WooCommerce Subscriptions refuses a cancellation, or the confirmation email cannot be sent, the shop is told straight away: an email to the shop, a note on the subscription and a notice on the Dashboard and the Renew Forge screens until someone marks it handled. A confirmation email that failed is tried again three more times within 24 hours. A fault in the journal never stops a cancellation.
Records are only ever added. The plugin never edits a record, and the only deletion it makes is of the whole journal, when you delete the plugin with “Delete the journal and the Renew Forge settings when the plugin is deleted” switched on. The CSV export writes each record as it was stored. A recorded compliance check shows what your store looked like on a given day.
The plugin makes no external requests and loads nothing from third-party servers. It schedules nothing on activation; its only background task is the retry of a confirmation email that failed to send. It adds suggested wording about the journal to the privacy policy guide under Settings Privacy. When you delete the plugin, the journal and settings stay unless you tick the delete-data checkbox in Renew Forge Settings first.
Documentation: https://renewforgewp.com/docs/
Guide to the UK subscription rules: https://renewforgewp.com/uk-subscription-rules/
Fires after a customer cancels with the Renew Forge button.
do_action( 'rnwf_subscription_cancelled', $subscription_id, $outcome, $email_sent )
Filters the list of compliance check items (objects implementing RenewForge\Compliance\Check).
Lets a plugin that sends renewal reminders describe them in one line; the compliance check then shows the reminders item as passed.
This plugin does not connect to any external service. It makes no HTTP requests and sends no data anywhere.