Renewal Reminder Emails for UK Subscriptions: DMCCA Rules, Timing, and Templates
From Spring 2027, UK subscription businesses will be required to remind customers before taking a renewal payment. Here is what the reminder must say, when to send it for each billing frequency, and how to keep proof — the part most merchants miss.
What the DMCCA actually requires
The Digital Markets, Competition and Consumers Act 2024 introduces a dedicated regime for consumer subscription contracts. One of its central duties: traders must send reminder notices before a subscription renews and payment is taken, so the customer has a genuine opportunity to cancel before being charged.
Two details matter for planning:
- Timing is anchored to the payment date, not the calendar month — the reminder must land in reasonable time before the charge.
- Longer contracts contemplate more than one notice. For annual renewals in particular, a single email the day before is unlikely to satisfy the intent of the regime.
Enforcement of the subscription provisions is expected from Spring 2027, with the CMA able to act directly — including fines of up to 10% of global turnover for consumer-law breaches. The wider picture is covered in our complete DMCCA 2027 guide.
What a compliant reminder must contain
A reminder that does its legal job answers four questions at a glance:
| Element | Why it is there |
|---|---|
| The contract will renew unless the customer acts | No surprise auto-renewal — the core mischief the DMCCA targets |
| The renewal date (when payment is taken) | Gives a real deadline to decide |
| The amount to be charged | Especially important after a trial or a price change |
| How to cancel, with a working route | Pairs with the DMCCA easy-exit duty |
Keep marketing out of it. A renewal reminder is a notice, not a newsletter — mixing in upsells weakens its evidential value and invites the argument that the customer was not clearly informed.
Timing by billing frequency
One schedule does not fit all plans. A sensible default, scaled by billing interval:
| Billing interval | Reminder schedule (days before charge) | Rationale |
|---|---|---|
| Daily | 1 | Anything more would be spam; one clear notice |
| Weekly | 3 · 1 | Short cycle, two touchpoints |
| Monthly | 14 · 7 · 1 | Standard cadence; final notice lands the day before billing |
| Annual | 60 · 30 · 7 · 1 | Long contracts warrant multiple notices — the regime contemplates ≥2 for extended terms |
Practical caveats that break naive implementations:
- UK timezone handling. A "1 day before" reminder computed in UTC can land on the wrong calendar day during British Summer Time. Build in a buffer.
- Dedupe per renewal cycle. If your job runs daily, make sure the same reminder is not sent twice for one billing event — and is not skipped when a renewal date shifts.
- Failed sends need retries. A bounced reminder that nobody notices is a compliance gap and a lost piece of dispute evidence.
A reminder template that works
Subject: Your [Store] subscription renews on [date]
Hi [name],
A quick reminder that your [plan name] subscription with [Store] will renew automatically on [date], and [amount] will be charged to your saved payment method.
No action is needed if you would like to continue. If you would like to cancel or change your plan, you can do so any time before [date] here: [manage subscription link].
[Store] · [support email]
That is the whole email. Renewal fact, date, amount, exit route — nothing that muddies the notice.
The evidence trail — the part merchants miss
Sending reminders is half the duty. Proving you sent them is the other half, and it is the half that pays off immediately:
- Chargebacks today. "Subscription cancelled" and "recurring transaction not authorised" disputes are won with a documented timeline. A timestamped reminder — sent before the charge, not actioned — is direct evidence of informed consent. Details in our chargeback guide.
- The CMA from 2027. If a complaint lands, "we send reminders" is an assertion; a dated send log per customer per renewal is a defence.
Minimum viable record per send: recipient, timestamp, subject/content version, and the renewal event it relates to — exportable, so you can hand a packet to a dispute reviewer without engineering work. Your policy pages need the same treatment: see the UK subscription compliance checklist.
Doesn't my subscription app already do this?
Partly. Recharge, Appstle, Loop, Seal, Skio, and Bold all send transactional notifications, and some include upcoming-order emails. What they are not designed to be is a UK compliance record:
- Content is not held against DMCCA requirements (renewal fact + date + amount + cancel route)
- Timing is not scaled per billing interval with annual multi-notice schedules
- Sends are not logged as dateable, exportable evidence
That is the layer Subnotice adds alongside your existing platform — see how it pairs with Recharge, Appstle, Loop, Seal, Skio, or Bold.
Frequently asked questions
Are renewal reminder emails legally required for UK subscriptions?
They will be. The DMCCA requires reminder notices before a subscription renews and payment is taken, with enforcement expected from Spring 2027. Until then they are best practice — and the strongest single piece of evidence in subscription chargeback disputes.
What must a DMCCA renewal reminder contain?
That the contract will renew unless the customer acts, the renewal payment date, the amount, and clear cancellation instructions — sent in reasonable time before the charge.
When should reminders be sent for different billing frequencies?
Scale with the interval: monthly ~14/7/1 days before billing; annual earlier and more than once (e.g. 60/30/7/1); weekly ~3/1; daily — one notice before the charge.
Do Shopify subscription apps send these reminders automatically?
They send transactional notifications, but not a compliance record: content is not checked against DMCCA requirements and sends are not logged as exportable, dateable evidence. That layer has to be added.
Why keep proof that a reminder was sent?
From 2027 — because the CMA can fine directly and undocumented compliance is hard to defend. Today — because a timestamped reminder log is the core evidence that wins subscription chargebacks.
Automate compliant reminders — with proof
Subnotice sends pre-renewal reminder emails timed to each plan (daily, weekly, monthly, annual), logs every send with a timestamp, and exports a dated audit trail. Free policy scan, no card required.
Install free on Shopify →