Blog

If WooCommerce subscriptions stop renewing, treat it like a checkout outage, because recurring revenue can quietly leak away for days before anyone notices.

The tricky part is that “not renewing” can mean a few different things. Sometimes WooCommerce never creates the renewal order. Sometimes the renewal order is created but payment fails. Sometimes payment succeeds at the gateway, but WooCommerce never receives the confirmation. Each one has a different fix.

This guide walks through the most common causes, how to diagnose them, and what to avoid when money, customer accounts, and recurring billing are involved.

First, figure out what is actually failing

Before updating plugins or changing settings, look at the subscription timeline. You want to know where the process stops.

• No renewal order was created: this usually points to scheduling, WP-Cron, Action Scheduler, or subscription status issues.
• A renewal order was created but payment failed: this usually points to expired cards, missing payment tokens, gateway settings, or customer authentication requirements.
• Payment was taken but WooCommerce still shows unpaid: this usually points to webhook, IPN, API, SSL, firewall, or callback problems.
• The subscription is on hold or cancelled unexpectedly: check failed payment rules, admin changes, stock settings, and plugin conflicts.

Tip: Do not start by manually changing order statuses to “completed” unless you know payment was actually captured. It can create accounting messes, access problems, and angry customers.

How WooCommerce Subscriptions renewals normally work

WooCommerce Subscriptions uses scheduled actions to know when a subscription is due for renewal. When the renewal time arrives, WooCommerce creates a renewal order and then tries to charge the customer automatically if the subscription has a valid saved payment method and the gateway supports automatic recurring payments.

If the subscription uses manual renewal, WooCommerce creates the renewal order but does not automatically charge the customer. The customer needs to pay the invoice themselves.

That distinction matters. A store owner may think renewals are broken when the subscription product was actually configured for manual renewals, or when the customer chose a payment method that cannot be reused automatically.

Common cause 1: The customer’s payment method cannot be charged

This is the most common and least exciting cause. Cards expire, banks decline transactions, customers replace cards, fraud systems block charges, and some payment methods simply do not support automatic renewals.

Check the renewal order notes first. WooCommerce and the payment gateway usually add a plain-language reason, such as a declined payment, missing payment token, expired card, authentication problem, or gateway error.

What to check

• Does the subscription have a saved payment method attached?
• Does the gateway support automatic recurring payments for that payment type?
• Was the card declined or expired?
• Did the customer remove their saved payment method?
• Was the payment method created while the gateway was in test mode?

How to fix it

If the customer’s payment method is the issue, the cleanest fix is usually to ask the customer to update their payment method from their account area. Avoid entering card details on behalf of a customer unless your payment processor and compliance setup explicitly allow that.

For Canadian stores, common gateways include Stripe, PayPal, and Moneris. If you use Moneris, this related guide may help: How to Set Up Moneris Payment Processing on Your Canadian WooCommerce Store.

Common cause 2: The payment gateway is not configured for automatic renewals

A payment gateway can work perfectly for one-time checkout and still fail for subscriptions. Recurring payments need saved payment methods, tokenization, and gateway callbacks that tell WooCommerce what happened after the charge attempt.

If renewals broke after switching gateways, changing API credentials, moving the site, or enabling a new payment method, start here.

What to check

• Is the gateway’s subscription or tokenization feature enabled?
• Are the live credentials installed, not test credentials?
• Are webhook or callback settings active in the gateway account?
• Does the gateway plugin officially support WooCommerce Subscriptions?
• Are old subscriptions still tied to a previous gateway?

Do not guess at API setup screens, because payment gateway dashboards change. Check the current official documentation for your gateway and WooCommerce Subscriptions compatibility before changing credentials.

For a broader payment troubleshooting process, read WooCommerce Payment Gateway Troubleshooting.

Common cause 3: WP-Cron or Action Scheduler is not running properly

WooCommerce relies on scheduled actions to process subscription renewals. If scheduled tasks are stuck, disabled, or delayed, renewal orders may not be created on time.

This often happens on low-traffic sites, sites with broken cron configuration, overloaded hosting, or stores where a plugin conflict is blocking scheduled actions.

Signs this is the problem

• Renewal orders are not being created at all.
• Many scheduled actions are overdue.
• Other scheduled tasks are also failing, such as emails, imports, stock syncs, or backups.
• Renewals run only when someone visits the site.
• The issue started after a hosting move or caching change.

How to fix it

In WooCommerce, check the scheduled actions area under WooCommerce status tools. You are looking for overdue, failed, or repeatedly retried actions connected to subscriptions and payments.

If actions are stuck, do not bulk-delete them blindly. Some may represent real renewal attempts, failed payments, or customer notifications. Deleting the wrong ones can make the subscription history harder to reconstruct.

A more reliable fix is to make sure your site has a working server-side cron process, enough hosting resources, and no plugin fatal errors blocking the queue. On busy stores, this is often a hosting and maintenance issue, not just a plugin setting.

Common cause 4: Webhooks or callbacks are blocked

Payment gateways need to talk back to your WooCommerce store. If the gateway cannot reach your site, WooCommerce may never learn that a payment succeeded, failed, was refunded, or needs attention.

This can cause confusing situations where the payment dashboard shows a charge, but WooCommerce still shows the renewal order as pending or failed.

Common blockers

• Security plugins blocking gateway requests.
• Firewall rules blocking foreign IP addresses or automated requests.
• Maintenance mode plugins hiding the site.
• Basic authentication on staging or recently launched sites.
• SSL problems or redirects that break callback URLs.
• Caching rules applied to checkout, account, cart, or payment callback pages.

Payment callback URLs should not be cached. Cart, checkout, account pages, and gateway return endpoints need to stay dynamic.

If you recently added a CDN, firewall, or caching plugin, review those settings carefully. A speed improvement is not worth much if renewal payments stop syncing.

Common cause 5: The site was copied from staging to live incorrectly

Staging sites are extremely useful, but WooCommerce subscriptions need extra care. A staging copy contains real-looking orders, subscriptions, scheduled actions, and sometimes payment tokens. If staging is pushed over the live site without care, renewal schedules can be overwritten or duplicated.

That can lead to missing renewals, duplicate renewal attempts, wrong payment mode, or customer account confusion.

Safe staging habits for subscription stores

• Never let a public staging site process real renewals.
• Disable outgoing customer emails on staging.
• Use gateway test mode only on staging.
• Do not overwrite live orders, subscriptions, users, or scheduled actions when pushing design changes.
• Take a fresh backup before moving anything between staging and live.

If your store has active subscriptions, a staging workflow should be planned, not improvised. This article explains the general idea: WooCommerce Staging: Why You Need a Test Site.

Common cause 6: A plugin update introduced a conflict

WooCommerce, WooCommerce Subscriptions, payment gateway plugins, tax plugins, membership plugins, and email plugins all touch the renewal process in some way. One incompatible update can break renewals even if the storefront still looks normal.

Common conflict points include payment token handling, subscription status changes, scheduled action processing, checkout validation, tax recalculation, and email notifications.

What to do after an update

• Check WooCommerce status for fatal errors and outdated templates.
• Review recent plugin updates against the date renewals stopped.
• Check payment gateway logs and subscription order notes.
• Test a subscription renewal in a safe environment where possible.
• Roll back only if you have a clean backup and understand what data changed after the update.

Be careful with rollbacks on live WooCommerce stores. Orders, subscriptions, users, and payments may have changed since the update. Restoring an old backup can erase legitimate orders if you are not selective.

Common cause 7: Subscription settings are not what you think they are

Sometimes nothing is technically broken. The subscription settings simply do not match the business expectation.

For example, a product may be set to manual renewals, synchronized renewals may shift the next payment date, a free trial may delay the first payment, or a subscription may be on hold because of a previous failed payment.

Check these settings

• Is automatic renewal enabled for the subscription?
• Is the subscription status active?
• Is the next payment date in the future?
• Was the next payment date manually changed?
• Are renewal orders set to reduce stock, and could stock be blocking the order?
• Do failed payment rules pause, cancel, or retry subscriptions?

If only one customer is affected, compare that subscription to a working one. If every subscription is affected, look at gateway, scheduled actions, hosting, or a recent plugin change.

Common cause 8: Hosting resources are too tight

Subscriptions add background work. Renewals, emails, payment calls, stock updates, tax calculations, and membership access changes may all happen at once. On underpowered hosting, scheduled actions can time out or pile up.

This is especially noticeable on stores with many renewals due at the same time, large order histories, heavy plugins, or slow database queries.

Better hosting will not fix a misconfigured gateway, but it can prevent renewal processing from choking under normal load. Ambrite’s Canadian cloud hosting uses LiteSpeed, NVMe SSD storage, Redis object caching, free SSL, and Canadian data centres, which can be a better fit for busy WooCommerce sites than bargain shared hosting.

Common cause 9: Customer emails are not being delivered

Email delivery problems do not usually stop the renewal itself, but they can make subscription issues worse. If failed payment emails, renewal reminders, password reset emails, or invoice emails do not arrive, customers cannot fix payment problems quickly.

For Canadian stores, remember that renewal notices, receipts, failed payment emails, and account emails are transactional. Do not mix them with marketing content unless you have considered consent requirements under Canadian anti-spam rules.

At minimum, make sure your store sends transactional email through a reliable authenticated mail setup, and that SPF, DKIM, and DMARC are configured correctly for your domain.

A practical troubleshooting checklist

Use this order when diagnosing renewal failures. It keeps you from making risky changes too early.

1. Pick one failed subscription and open its related renewal order.
2. Read the order notes for gateway messages, failed payment details, or status changes.
3. Check whether payment was captured in your gateway dashboard before changing WooCommerce order status.
4. Check scheduled actions for overdue or failed subscription tasks.
5. Review gateway logs in WooCommerce if logging is enabled.
6. Confirm live mode credentials are active and webhooks are configured.
7. Review recent changes, including plugin updates, hosting moves, caching changes, security rules, and staging pushes.
8. Test safely on staging or with gateway test tools where supported.
9. Back up before changing anything, especially before updates, rollbacks, or database repairs.

When not to fix it yourself

Some WooCommerce issues are safe to investigate as a store owner. Others are not worth the risk.

Get professional help if payments were captured but WooCommerce shows unpaid, many subscriptions failed at once, scheduled actions are stuck in bulk, a staging site may have touched live payment data, or you are considering database edits.

Also pause before making major updates on a live subscription store. A broken brochure site is annoying. A broken subscription store can affect payments, customer access, invoices, taxes, and support requests all at the same time.

How to prevent renewal problems

The best prevention is boring maintenance done consistently. WooCommerce stores need updates, backups, uptime monitoring, checkout testing, payment gateway checks, and a proper staging workflow.

For subscription stores, add these habits:

• Check failed and pending renewal orders weekly.
• Monitor scheduled actions for overdue tasks.
• Test checkout and account payment-method updates after major plugin changes.
• Keep payment gateway plugins current, but avoid updating blindly on busy sales days.
• Keep daily backups, and know how to restore without wiping new orders.
• Document which gateway, tax, membership, and fulfilment plugins affect subscriptions.

Ambrite offers WooCommerce maintenance for stores that need regular checks instead of emergency fixes. Growth includes a WooCommerce health check covering plugin compatibility and payment gateways such as Stripe and PayPal, while Complete adds cart and checkout testing after major updates.

Final checks before you mark the issue fixed

Once you believe renewals are working again, do not stop at one successful test. Confirm the full loop.

• A renewal order is created at the expected time.
• The payment gateway attempts or captures payment correctly.
• WooCommerce receives the gateway response.
• The order status updates correctly.
• The subscription next payment date advances.
• Customer emails are delivered.
• Any membership, download, shipping, or fulfilment access updates properly.

If all of those pieces work, the renewal system is probably healthy again. If one piece still fails, focus there instead of changing unrelated settings.

Subscription problems are rarely fixed by a single magic checkbox. They are usually a chain issue: scheduling, gateway, callbacks, hosting, plugins, email, or staging. Work through the chain calmly, keep backups close, and avoid manual payment-status edits unless you have verified the money trail first.

This article was written with the help of AI and reviewed by Ambrite. Pricing, features, and technical details may change, so always verify with official sources before making decisions.