WooCommerce Subscription Renewal Failed Email Template and Follow-Up Schedule

A failed WooCommerce subscription renewal tells you that a payment attempt did not complete. It does not tell you whether a retry is pending, the customer still has access, or a later attempt succeeded. Before you send a payment request, check the current renewal order and subscription. Then choose the email that matches what you can verify.

Check the renewal state before you write

Find the customer’s subscription and the renewal order behind the failure notice. Check the latest payment event, including any later attempts; an old failure notification may still be in your queue after payment completes. If the order and payment gateway disagree, pause the email and investigate. Check your configured retry and access rules separately: neither a failed order nor an updated card proves that service has stopped or payment has cleared.

For other shop messages, use the broader customer service templates for EU online stores. The checks below are specifically for recurring WooCommerce renewals.

Log the subscription and renewal order references, checked status, check time and chosen message internally. Whoever answers a later reply can then tell whether the email describes the current state or an earlier one.

Match each customer email to a verified state

Use the renewal order and payment record to check whether money was collected; use the subscription and entitlement records to check access. If those records conflict, hold the message for a person to review.

State immediately before send	Message or action	Do not say
Latest attempt failed; renewal remains unpaid	Send the first-failure template unless an equivalent notice was already sent.	That the subscription is cancelled or access has ended.
Renewal unpaid; retry pending or customer action still needed	Send the reminder if it gives the customer a useful next step. Mention a retry only if verified.	That a saved card or scheduled retry means payment succeeded.
Renewal payment completed	Stop failure and reminder messages; check access separately if the customer reports a problem.	That the customer still needs to pay because an earlier attempt failed.
Renewal unpaid; access confirmed stopped	Send the interruption template after checking both records.	That changing a payment method will immediately restore access.
Records disagree or charge disputed	Pause follow-ups and assign an investigation.	That another payment is required before the discrepancy is resolved.

Assign the final check to the person who owns the renewal queue. If messages are scheduled elsewhere, specify who reviews exceptions and cancels queued sends. A payment-method update is a reason to recheck the renewal, not proof that it has been paid.

Template: first failed subscription renewal email

Send this only after confirming that the latest renewal still shows as unpaid. Replace every bracketed field; remove the optional access sentence unless you checked the entitlement.

Do not paste a gateway decline explanation into this email without checking that it is accurate and suitable to share. The customer needs a trustworthy route to their account, not a speculative diagnosis or an unverified payment link.

Template: payment-method update reminder

Use this only while the renewal remains unpaid and the customer still has a useful action to take. Check for a later payment and any method update immediately before sending. Select the retry sentence that fits your settings; delete the other one.

Do not suggest that access is about to end unless you have checked the rule that applies to this subscription and the statement is accurate. If access has already stopped, use the interruption template instead.

Template: confirmed service interruption

This email requires two checks: the renewal remains unpaid, and access to a named service has actually stopped under your store’s rules. Do not call the whole customer account closed if only one subscription benefit is unavailable.

Do not promise an immediate return of access. Confirm the payment outcome and the access state before telling the customer what happens next. Add a deadline only if it genuinely applies under the customer’s terms and your configured rules.

Set a follow-up schedule without sending the wrong message

Write the schedule around events and store-configured rules, not an assumed WooCommerce retry interval. Fill in the owner and review point below for your own workflow; a review point is a prompt to check records, not permission to send regardless of status.

Keep the two stop rules visible wherever sends are prepared: no longer unpaid means no failure follow-up; access not confirmed stopped means no interruption notice. Compare your store, gateway and support notifications before adding a separate email. If an existing failure notice already tells the customer what happened and where to review it, follow up only when the case remains unresolved. These are operating rules, not legal deadlines. For a different payment flow, see the separate Shopify failed-payment email guide.

Handle replies that arrive after the status changes

A customer may reply to an accurate failure email after paying. Treat the email as a snapshot: reopen the renewal order and payment record before responding. If the gateway shows a charge that the order does not, or the customer disputes a charge, hold further payment requests while a person investigates.

If you offer chat, askVela’s WooCommerce integration can show order and payment information supplied by your shop through its WordPress plugin. Do not infer subscription access or a successful renewal from a status you have not verified in the relevant records. For replies needing investigation, the team inbox for follow-up questions supports assignment and internal notes.

Close the case with the checked outcome: whether payment completed, remains outstanding or needs investigation, and whether the affected access is currently available. If you cannot establish that yet, tell the customer you are checking and keep the next payment request on hold.