Tag Archives: Subscriptions

WooCommerce Subscription Renewals Going Wrong? Failed, Missing and Duplicate Renewals Explained

Subscriptions are the best revenue a store can have: predictable, recurring, and earned once. They’re also unforgiving when something goes wrong, because a renewal happens without the customer at the keyboard. Nobody sees an error message. Nobody clicks “try again”. If the renewal fails silently, you lose a month’s revenue. If it runs twice, a loyal customer finds two charges on their statement.

The forums show both sides. Threads on WordPress.org and elsewhere describe duplicate payments for subscription renewals, double charging on renewal, multiple payment intents on renewal even after payment succeeded, and renewals that simply never happened after an update or a change of payment plugin. WooCommerce maintains a whole troubleshooting page for common renewal issues.

This guide explains how renewals actually work, the three ways they go wrong, how to diagnose each, and how to catch them before your subscribers do.

This guide is about renewals in the official WooCommerce Subscriptions extension and similar plugins. Details vary by plugin and gateway, so check your plugin’s documentation for specifics.

How a renewal actually happens

Subscription renewal pipeline: a scheduled action fires, a renewal order is created, the saved token is charged, the result is recorded and emails are sent. Three ways it fails: it never happens because cron or the queue stalled, it fails because of tokens, keys or webhooks, or it runs twice because of overlapping actions or retries.

A renewal is a chain of background events:

  1. A scheduled action fires at the next payment date. WooCommerce Subscriptions uses Action Scheduler for this (look for actions like woocommerce_scheduled_subscription_payment in WooCommerce → Status → Scheduled Actions).
  2. A renewal order is created, a normal WooCommerce order linked to the subscription.
  3. The gateway charges the saved payment method (a stored token) without the customer present.
  4. The result is recorded. The renewal order moves to Processing or Completed on success, or Failed on failure, and the subscription’s next payment date moves forward.
  5. Emails go out, and on failure, any retry rules are scheduled.

Every link in that chain can break, and because it all happens in the background, nothing alerts you by default.

Problem 1: Renewals that don’t happen at all

Symptoms: subscriptions show a next payment date in the past; no renewal order was created; revenue quietly drops; subscribers don’t notice (until they do).

Why: WooCommerce’s documentation is direct about it: renewals depend on scheduled actions, and if cron jobs aren’t running or the Action Scheduler queue fails, renewals aren’t created when expected. Common culprits:

  • WP-Cron disabled without a server cron, or loopback requests failing (guide)
  • A huge past-due backlog in Action Scheduler
  • PHP memory or time limits killing the renewal action
  • A site running in a staging / duplicate site mode, where renewal payments are deliberately not processed automatically

Diagnose: in Scheduled Actions, search for the subscription ID. Is the payment action pending and past due? Failed? Open it and read the log.

Fix: fix the scheduler, then let past-due renewals run. For individual subscriptions, WooCommerce documents creating a pending renewal order manually and processing it as a stopgap.

Problem 2: Renewals that fail

Symptoms: renewal orders in Failed status; subscriptions moved to On hold.

Why: most are ordinary: expired or declined cards, insufficient funds. But some are store-side:

  • Missing or invalid payment tokens, for example after switching payment plugins, migrating gateways, or when a staging site processed renewals against the same customer records
  • Gateway authentication errors: expired API keys, a disconnected account (guide)
  • Webhook problems leaving a successful charge recorded as failed (Failed orders guide)

Diagnose: read the renewal order’s notes and the gateway logs. Does the subscription have a saved payment token? Did the gateway actually decline, or did the store fail to ask?

Fix: genuine declines → customer updates their payment method, and a retry system recovers many. Store-side failures → fix the token, keys or webhook, then process the renewal again. Before retrying, check the gateway to make sure the “failed” renewal didn’t actually succeed. Otherwise you create the next problem.

Problem 3: Duplicate renewals (charged twice)

Symptoms: two renewal orders for the same subscription and period; two charges on the customer’s card; angry email or a “duplicate processing” chargeback.

Why: WooCommerce’s troubleshooting guide lists the usual causes:

  • Overlapping scheduled actions: more than one payment action for the same subscription and timestamp
  • Manual actions (clicking Process renewal or Create pending renewal order) on a renewal that was already in progress
  • Conflicting plugins or custom code triggering renewals
  • Retrying a “failed” renewal that had actually succeeded at the gateway
  • Gateway retries after timeouts where the first attempt went through

Diagnose: in Scheduled Actions, look for multiple payment actions with the same subscription ID and timestamp. In the gateway, count the charges for that customer and period.

Fix: refund the duplicate from the duplicate renewal order (so WooCommerce and the gateway agree), cancel duplicate actions, check the subscription’s next payment date, and remove the cause.

A worked example: the overnight double renewal

A store with 600 monthly subscribers moves to a new host. During the migration, the old and new servers both run for a few hours, and both have WP-Cron active, pointing at the same database.

  • At 02:00, the old server’s scheduler picks up 40 due renewals and starts charging them.
  • At 02:01, the new server’s scheduler picks up the same actions before they’re marked complete.
  • 31 subscribers are charged twice. The second set of renewal orders sit next to the first, with different transaction IDs and identical totals, a minute apart.
  • The first complaint arrives at 08:30. By 10:00 there are nine, and one chargeback.

The fix: refund every duplicate from the duplicate renewal order, check each subscription’s next payment date, and switch off the scheduler on the old server. The lesson is never run two copies of a store against the same database with background processing switched on, and for subscription stores, put staging and migration copies into a mode that doesn’t process renewals.

Preparing before a change that could affect renewals

Before you migrate hosts, change payment plugins, update the subscriptions extension or edit renewal-related code:

  1. Note when renewals usually run and how many are due in the next few days.
  2. Pause or schedule the change away from big renewal batches.
  3. Make sure only one environment can process renewals.
  4. Afterwards, check Scheduled Actions for past-due and duplicate payment actions.
  5. Compare the next day’s renewal orders and gateway charges.

Why renewal problems hide so well

  • They happen in the background, often overnight.
  • They’re spread out: a few subscriptions a day, not a dramatic outage.
  • Failed renewals look normal, because cards do expire.
  • Missing renewals leave no order at all. There’s nothing to look at.
  • Duplicates are noticed by customers first, on their statement.

So the realistic goal is: notice within a day that the renewal machinery has stalled, that a renewal was charged twice, or that a “failed” renewal was actually paid.

How Ordafide helps with renewals

Table of renewal problems: renewal never ran (check past-due actions; Ordafide queue health), renewal failed (order notes and gateway; stuck payment check), charged twice (duplicate actions; duplicate charge check), duplicate not refunded (refund mismatch check), no receipt (email log; customer never emailed check).

Renewal orders are ordinary WooCommerce orders, so Ordafide’s checks apply to them like any other order, and its store health checks watch the scheduler that renewals depend on.

Ordafide Order Integrity for WooCommerce (free):

  • Background job queue health: how far behind Action Scheduler is, how many jobs have failed, and the most likely cause in plain language, plus WP-Cron status and a loopback test. When this goes red, renewals are at risk.
  • Duplicate charge: one gateway payment reference on two orders, or the same customer charged twice for an identical basket within minutes. That covers the classic double renewal from overlapping actions, which usually fire close together. The duplicate window is configurable if your duplicates arrive further apart.
  • Stuck payment and paid but cancelled: renewal orders left Pending or Failed even though a payment reference or confirmed payment date shows money moved.
  • Refund mismatch: for the clean-up afterwards, to make sure duplicate renewals were actually refunded and recorded.
  • Customer never emailed: paid renewals where the receipt never went out.

Ordafide Pro adds:

  • Gateway reconciliation (Stripe, PayPal, Square, Mollie, Razorpay; read-only): catches renewal charges with no matching order, orders marked paid with no payment, and amount disagreements.
  • Order volume anomaly detection: a sudden drop in orders at the hour renewals usually run is a signal that the scheduler has stalled.
  • Alerts to Slack, SMS, email or webhook, so a queue backlog or a run of duplicates reaches you the same day.

Ordafide doesn’t manage subscriptions, retry payments or change renewal dates. Those stay with your subscriptions plugin. It tells you when the orders and the money stop agreeing, and when the machinery behind renewals has stopped.

Renewal health checklist

  • Real server cron running WP-Cron; loopback test passing
  • No large past-due backlog in Scheduled Actions
  • No duplicate payment actions for the same subscription and date
  • Staging sites never process live renewals (test keys, staging mode)
  • Gateway API keys valid; webhooks delivering
  • Failed renewals checked against the gateway before retrying
  • Duplicate renewals refunded from the duplicate order
  • Monitoring and alerts on queue health and duplicate charges

Communicating with affected subscribers

Subscribers are your most loyal customers, so renewal problems deserve a personal touch:

  • Charged twice: refund immediately, email before they notice if you can, and say clearly that it was your error and the duplicate has been refunded.
  • Renewal missed: decide whether to charge now (and tell them first) or skip the period. Surprising someone with a late charge invites disputes.
  • Renewal failed because of your setup (not their card): don’t send them a “please update your card” email. Fix your side, retry, and only contact them if needed.

A weekly renewal check (10 minutes)

  1. Scheduled Actions: search for pending subscription payment actions that are past due. Any?
  2. Failed tab: any failed renewal actions this week? Read the error.
  3. Renewal orders: filter recent orders to renewals. Any Failed? Any duplicates for the same subscription and date?
  4. Gateway: do renewal charges in the gateway match renewal orders?
  5. Subscriptions: any active subscriptions with a next payment date in the past?
  6. Integrity scan: check Ordafide’s findings for duplicate charges and stuck payments.

Most weeks it’s empty. The week it isn’t, you’ll catch the problem days before subscribers do.