WooCommerce Subscription Renewals Stopped After a Domain Change?

In this guide

Check whether WooCommerce Subscriptions has placed your migrated production store in staging mode. A change in the site’s URL can trigger its duplicate-site protection, which disables automatic subscription payments and subscription-related emails. Restore live behavior only after confirming which copy is authorized to charge customers.

The official staging and migration documentation explains that Subscriptions compares the current site URL with a recorded live URL. This protection is valuable on a genuine clone. After an intentional domain change, it can also explain why the real shop shows manual renewal behavior.

First decide which copy is production

Write down the new live domain, the old domain, any temporary hosting address and every staging copy. For each, identify whether background jobs can run and whether it has real gateway credentials. DNS pointing customers to the new server does not necessarily stop scheduled work on an old server.

This is especially important when both servers keep the same site URL during a hosting migration. The documented URL comparison may not distinguish those copies. Have the developer or host decommission or isolate the old installation deliberately, including payment processing and outgoing messages.

The owner should confirm the intended live site and business cutover time. The technical team should confirm where that site actually runs. Our staging and production isolation guide covers the broader boundaries that need to remain in place.

Read the mode and recorded URL

In the administration area, inspect the Subscriptions menu for its staging indication. Also open WooCommerce > Status and review Subscriptions Mode and Subscriptions Live URL where available in your installed version. Save the findings before changing anything.

If the current production address differs from the recorded live address and staging mode is shown, the URL-detection explanation fits. If the store already reports live mode, investigate scheduling, gateway and subscription-specific evidence instead. Changing a URL option again is not a useful first response to every missed renewal.

• Production reports staging after a domain change: verify old copies are isolated, then use the supported live-mode workflow.
• A genuine test copy reports staging: leave automatic charging disabled there.
• Production reports live but no renewal attempt exists: inspect scheduled actions and next-payment dates.
• A renewal attempt exists but fails: inspect the associated order notes and gateway result.

Manual-renewal labels observed during staging mode should be interpreted in that context. Avoid bulk-editing every subscription’s payment method before the mode and migration history are understood.

Restore the supported live behavior

After backing up and establishing a single charging site, an authorized administrator can use the staging notice’s supported option to enable automatic payments on the intended production installation. If that notice was dismissed, follow the vendor’s documented method to display it again.

Database options and migration constants are developer tasks. Have the maintainer explain what changed and why, rather than trying several snippets until the warning disappears. Clearing a notice is not equivalent to proving only one copy can process renewals.

Keep genuine test environments isolated after the repair. The vendor notes that staging mode suppresses subscription-related messages, but other WordPress or plugin emails can still be sent. Confirm the broader mail and integration isolation independently.

Reconcile the renewals missed during the move

Before processing anything manually, make a list of subscriptions due during the affected interval. Match each with its renewal orders, notes and payment-provider record. A missing or stale WooCommerce status does not prove that a processor charge failed.

The Subscriptions scheduled-action troubleshooting guide distinguishes failures before and after payment. Use that distinction to decide whether an order needs a payment attempt, a record repair or no further charge. Work from individual evidence before considering a supported batch process.

If money was captured but the order remains unresolved, our paid-but-pending order guide covers reconciliation. Repeatedly clicking a renewal action while the previous result is unknown can make the account history harder to resolve.

Verify a scheduled renewal from end to end

Use a controlled test subscription and supported test gateway environment to confirm the complete process. For production verification, agree the specific legitimate renewal and timing with the merchant rather than creating an unexplained charge.

1. Confirm production reports the intended live URL and live mode.
2. Confirm the selected subscription has the intended payment method and next-payment date.
3. Check that its scheduled action exists and is processed as expected.
4. Match the resulting renewal order to one gateway transaction or the expected non-charge outcome.
5. Verify subscription status, next date and intended messages.
6. Confirm no corresponding processing occurred on the retired or test copy.

Record the outstanding subscription list and assign its review. Restoring normal future renewals does not automatically reconcile every renewal missed during the migration.

FAQs

Why did automatic payments stop when the website still loads?

The URL-based safety check is separate from page availability. A working migrated website can still be treated as a duplicate site for subscription processing.

Should I enable automatic payments on my staging site?

Only the intended production copy should process real renewals. Use isolated test credentials and the vendor’s supported testing workflow for a genuine staging site.

Will changing to live mode charge every missed renewal immediately?

Do not assume that outcome. Review the installed behavior, scheduled work and individual subscription history, then reconcile missed renewals through a supported process.

Can the old server still charge customers after DNS changes?

It may still run scheduled processes if left operational with live credentials. Have the host confirm its shutdown or isolation rather than relying on DNS alone.

Sources

• WooCommerce: Subscriptions staging sites and migrations
• WooCommerce: scheduled-action errors and payment reconciliation

Prepared for website owners by Nithu / Suthakaran Nithursan. Dated advisory facts link to primary sources. Examples are illustrative and are not client results or guarantees.