How do I update WooCommerce without breaking checkout?

The short version

• A store update isn’t done until a test order goes through. That’s the rule that matters most.
• Back up the database and files first, and test on a staging copy.
• Check every extension’s “tested up to” version, especially payment and shipping.
• Look for outdated template overrides in your theme under WooCommerce, Status.
• Run Update WooCommerce Database when asked, and wait for it to finish.

This page covers what’s different about a store. For updating WordPress and plugins in general, see our answer on whether plugin updates can break your site.

How do I update WooCommerce safely?

These steps follow WooCommerce’s guide on how to update WooCommerce, checked on October 31, 2026.

1. Back up the database and the wp-content folder. WooCommerce recommends an automated backup service. Orders live in the database, so a files-only backup isn’t enough.
2. Make a staging copy. WooCommerce is blunt: “Do not test updates directly on your production site.” Our answer on staging sites explains how they work.
3. Check extension compatibility. Go to WooCommerce, Extensions, My subscriptions, and look at each extension’s Tested up to WooCommerce version. If it’s older than the version you’re moving to, look for an update and read its release notes. For extensions bought elsewhere, check with their makers.
4. Check template overrides. Go to WooCommerce, Status. The system status report has a Templates section listing theme files that override WooCommerce’s own, and flags any that are outdated. An outdated checkout or cart template is a common cause of a checkout that breaks after an update.
5. Update on staging, with the extensions, payment gateways and theme together.
6. Run the database update if prompted. Select Update WooCommerce Database. Use View progress and wait for “WooCommerce database update complete.”
7. Test on staging: product pages, cart, checkout, a test payment, shipping and tax totals, and the order emails.
8. Repeat on the live store. WooCommerce suggests using Coming soon mode during the update, so nobody checks out mid-change. Update from Plugins, Installed Plugins, and don’t leave the page until it finishes.
9. Test the live store. Place a real order, refund it, and check both emails arrive.

Expected result: a completed test order with a confirmation email, a matching payment in your provider’s dashboard, and no new warnings under WooCommerce, Status.

How often should I update?

WooCommerce suggests a regular, for example monthly, cycle, with security releases applied sooner. Its guide points to the WooCommerce advisories page and changelog to see whether a release fixes a security problem.

Why does it matter?

Updates close security holes, fix bugs and keep payment extensions working with the provider’s latest requirements. But a store has more moving parts than a brochure site. One mismatched extension can stop checkout, and unlike a broken blog page, nobody tells you. Customers just leave.

What are the common mistakes and edge cases?

• Updating on a busy afternoon. Pick your quietest hour.
• Skipping the test order because the home page looks fine. The home page isn’t where money changes hands.
• Updating the payment extension on its own without checking it works with the WooCommerce version you’re on.
• A cached checkout. WooCommerce’s caching guide says the cart, checkout and account pages must not be cached. After an update, clear the cache and check those exclusions are still in place.
• Ignoring outdated templates because the shop “looks fine.” They can break quietly in the next update.
• An expired extension licence. Paid extensions often stop updating when the licence lapses. Keep renewals on a calendar.
• Auto-updates on the store’s core plugins without anyone testing. Convenient, until checkout breaks overnight.

What if this didn’t work?

• Checkout breaks after an update. Put the store in Coming soon mode, restore from your backup if needed, and troubleshoot on staging before trying again. Our help article on why checkout isn’t working has the full checklist.
• The database update seems stuck. Check View progress, and look for failed scheduled actions under WooCommerce, Status.
• The site shows a critical error. See critical error or blank white screen.
• You need help from an extension maker. On WooCommerce, Status, select Get system report, then Copy for support or Download for support, and send that. It describes your setup without passwords.

How much does it cost, and how long does it take?

Updates themselves are free unless an extension licence needs renewing. A careful store update, staging test included, takes one to two hours for a small store, more with many extensions or custom templates.

How does E-3 handle this?

On stores in our website care, updates are tested on a staging copy before they reach the live store, backups run daily, and a person checks the result. Monitoring tracks the PHP version, waiting updates, known plugin vulnerabilities, disk and database space, and plugin-license renewals, so an expired licence doesn’t stop updates without anyone noticing. Daily backups mean a bad update can be rolled back. See our help article on how E-3 keeps WordPress updated.

Related questions

• Do I need to be PCI compliant?
• Why am I getting lots of small failed orders?
• Which payment provider should my store use?
• How do I move my store to another platform?
• Back to the complete online store guide

Sources

1. How to update WooCommerce (WooCommerce documentation)
2. Understanding the WooCommerce system status report (WooCommerce documentation)
3. Configuring caching plugins (WooCommerce developer documentation)