Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Update WooCommerce Safely

Short answer

To update WooCommerce safely, back up your database and files, test the update on a staging copy, then update WooCommerce on the live store and run any database update it asks for. Check the cart, checkout, payments, shipping and order emails before you reopen the store. If a check fails, restore the backup and fix the problem on staging first.

Key takeaways

  • Back up both the database and the wp-content folder before every WooCommerce update, and keep the backup off the live server.
  • Test WooCommerce, WordPress, extensions, payment gateways and the theme together on staging before you touch the live store.
  • WooCommerce 11.2.2, released on 4 November 2026, was a security release that also required a database update.
  • For WooCommerce 10.8 and later, the recommended stack as of November 2026 is WordPress 6.9 or newer, PHP 8.3 or newer and MySQL 8.0 or newer.
  • Run the database update only after a current backup exists, and watch it finish in Scheduled Actions before you test checkout.
  • After an update, place a test order and check shipping, tax, payment and order emails before you reopen checkout to customers.

What is the safest way to update WooCommerce?

The safest way is to back up the store, test the full update set on staging, then apply the same updates to the live store and check checkout before reopening it.

WooCommerce is not a single file change. Its update guide says keeping WooCommerce, WordPress, extensions, themes and payment gateways up to date keeps a store secure, compatible and working.

A safe update treats those parts as one set. Update one part on live while another part stays old, and the parts may not work together.

What do you need before you update WooCommerce?

You need a current backup, a staging copy, the release notes for the new version, and a note of the versions you run now.

Start with versions. Open “WooCommerce > Status” and write down the WooCommerce version, the WordPress version and the PHP version.

Then read the release notes for the version you plan to install. The WooCommerce 11.2.2 release notes show the pattern to look for: released on 4 November 2026, security update marked Yes, and database update marked Yes.

Also list every extension and payment gateway that touches money. That list includes payment gateways, shipping, tax and subscription tools, plus your theme.

You also need a quiet window. Pick a time with few orders, and tell anyone who edits the store that no product or order changes should happen during the update.

How often should you update WooCommerce?

Update WooCommerce about once a month, and update sooner when a release fixes a security issue or a fault your store depends on.

WooCommerce's update guide says a monthly cadence works well for most stores. Check for WooCommerce, WordPress, extension and theme updates around the same time each month.

Security releases break that routine on purpose. The 11.2.2 notes call that release a security release with multiple security updates, and they recommend updating as soon as possible.

Waiting for the next monthly slot after a security release leaves the known fault open. A monthly plan is a floor, not a reason to delay a security fix.

How do you check versions and compatibility before updating?

Check the server requirements, the WordPress and PHP versions on your site, and the tested-up-to version of each extension before you update.

ItemRecommended as of November 2026Where to check it
WordPress6.9 or newerWooCommerce > Status
PHP8.3 or newer, tested up to 8.4WooCommerce > Status, Server environment
MySQL or MariaDBMySQL 8.0 or newer, or MariaDB 10.6 or newerWooCommerce > Status
WordPress memory limit256 MB or moreWooCommerce > Status
WooCommerceLatest stable release, 11.2.2 as of November 2026WooCommerce > Status

WooCommerce's server recommendations list those values for WooCommerce 10.8 and later. The same page says the store still runs on PHP 7.4 and MySQL 5.6, but those versions are old and past their best support.

WooCommerce 10.8 needs WordPress 6.9 or newer as a minimum, and its minimum PHP is 7.4, according to WooCommerce's PHP and WordPress guide. The minimum is not the same as the recommended version, so aim for the recommended values above.

PHP 7.4 reached its end of life in November 2022, so a store still on 7.4 should plan a PHP move with its host before the next big update. PHP's supported versions page lists which branches still get fixes.

For help choosing a version, read which PHP version to use for WordPress.

Next, check each extension. In “WooCommerce > Extensions > My subscriptions”, look at the tested-up-to WooCommerce version for each item.

If that value is older than the WooCommerce version you plan to run, look for an extension update and read its release notes first. Contact the extension developer if no update states support for the new version.

How do you back up WooCommerce before an update?

Back up both the database and the wp-content folder, then store at least one copy away from the live server.

A WooCommerce store keeps data in two places. The database holds products, orders, posts, pages and settings, while the wp-content folder holds themes, extensions and uploads.

Backing up only one half leaves the other half unprotected. A file copy does not include the database, and a database export does not include your theme or media files.

WordPress's backup guide says to back up the database regularly and always before an upgrade, and to keep at least 3 to 5 recent backups in different places. Read the full advice in the WordPress backups guide.

For a full backup routine, see how to back up WordPress.

A manual backup has 2 steps:

  1. Back up the database with your host panel, phpMyAdmin or a backup plugin.
  2. Use SFTP to download the wp-content folder to your computer.

An automated backup service is the simpler route for most stores. WooCommerce's update guide calls an automated backup service the most efficient and reliable approach.

Check that the backup finished and that its files have a size above zero. A backup with no size, or a backup job that reports an error, is not a backup you can rely on.

How do you test a WooCommerce update on staging?

Copy the live store to a staging site, apply the same updates there, then run the full buying journey before you touch production.

A staging site is a private copy of your site where you test changes. Create it through your host, or restore a backup to a separate WordPress install.

On staging, update WooCommerce, extensions, payment gateways and your theme together. WooCommerce's update guide warns against testing updates directly on the production site.

Then test the flows that matter most to your store:

  • Open the shop page and several product pages.
  • Add a product to the cart and open the cart page.
  • Go through checkout with a test payment method.
  • Check shipping costs, tax amounts and the order email.
  • Open an old order in the admin and check that its details load.

Watch the admin for new notices while you test. A notice about a failed scheduled action, a missing table or an outdated template is a sign to stop and fix the cause on staging.

Do not push the staging database back to live after testing. Orders placed on live while you tested would be lost if the older staging database replaced the live one.

How do you update WooCommerce on your live store?

Set the live site to Coming soon mode, update WooCommerce from the Plugins screen, wait for it to finish, then update the rest of the set.

Follow these steps in order:

  1. Set the live site to Coming soon mode so customers do not check out while files and database changes are running.
  2. Go to “Plugins > Installed Plugins” in the WordPress admin.
  3. Find WooCommerce and click “Update now” if an update is shown.
  4. Wait for WordPress to finish before you refresh the page, open another page or start a second update.
  5. Update your extensions, themes and payment gateways in the same window.
  6. Complete any database update notice before you test the store.

You can also update from “Dashboard > Updates”. Pick the path that fits your routine, but do not run several major store updates at the same time unless you tested that exact set on staging.

For Marketplace extensions, open “WooCommerce > Extensions > My subscriptions” and check that the store is connected to your WooCommerce.com account. That screen shows installed extensions, themes and payment gateways, plus their updates and compatibility.

The whole live update often takes only a few minutes on a small store. Larger stores with many orders can take longer, mainly because the database update has more rows to change.

What happens during the WooCommerce database update?

The database update changes WooCommerce tables so they match the new plugin version, and it runs in the background until it reports that it is complete.

Some WooCommerce updates need a database update after the plugin files change. When one is needed, a database update notice appears in the WordPress admin.

Do not click “Update WooCommerce Database” until a current backup exists. WooCommerce's update guide repeats that warning, and the button starts work that changes order data.

After you click the button, click “View progress” to open Scheduled Actions and watch the pending actions. The update runs there in the background.

When it finishes, a dismissible message says “WooCommerce database update complete”. Do not start checkout tests until you see that message or the notice has gone.

If the WooCommerce version and the WooCommerce database version differ on “WooCommerce > Status”, the database update has not finished or has not run. The WooCommerce system tools guide says the two values should match, and its Tools screen offers an update button for that case.

How do you check your store after updating WooCommerce?

Place a test order on the live store, check shipping, tax, payment and email behaviour, then review the admin for notices before you reopen checkout.

Work through this list before you turn off Coming soon mode:

  • Open the storefront and several product pages, including a variable product if you sell one.
  • Add a product to the cart and confirm the cart page works.
  • Place a test order with a test payment method or a low-risk workflow for your store.
  • Check that shipping and tax are charged as expected.
  • Confirm the order email arrives and shows the right items and totals.
  • Open “WooCommerce > Status” and check that the WooCommerce version and database version match.
  • Look for failed scheduled actions or extension alerts in the admin.

If your store uses the new order storage, read what HPOS is in WooCommerce to know where order data now lives. That helps when an old order looks wrong after an update.

If a payment gateway was part of the update, check its own settings page too. A gateway update can change which payment methods show at checkout, so confirm the methods you offer are still listed.

How do you roll back WooCommerce if the update breaks your store?

Keep checkout closed, restore the backup you made before the update, then fix the cause on staging before you try the update again.

First, keep the site in Coming soon mode so no new orders arrive while the store is in a broken state. New orders taken after a restore point would be lost by a restore.

Next, restore both parts of the backup: the database and the wp-content folder. Restoring only the plugin files leaves the database at the new version, which may not match the old plugin.

After the restore, open “WooCommerce > Status” and confirm the WooCommerce version and database version match the pre-update values. Then test the shop, cart and checkout again.

If the store works after the restore, go back to staging and find the cause. Common causes are an extension that does not support the new WooCommerce version, a theme template that needs an update, or a PHP version below the recommended level.

Do not try the same update on live a second time without a change on staging. The same set will fail in the same way unless something in it has changed.

If you cannot find the cause, ask your host or the extension developer for help, and give them the WooCommerce version, the WordPress version, the PHP version and the exact error message. That list is what support needs to start.

What mistakes should you avoid?

Updating on the live store without a backup or a staging test is the most common mistake, and it turns a small fault into lost orders.

Other mistakes to avoid:

  • Updating WooCommerce alone and leaving payment gateways, extensions and the theme on old versions.
  • Clicking the database update before a backup exists.
  • Refreshing the page or starting a second update while the first one is still running.
  • Pushing a staging database back to live and wiping orders placed since the staging copy was made.
  • Updating during a busy sales period without a quiet window or a plan to close checkout.
  • Ignoring a tested-up-to version that is older than the WooCommerce version you plan to run.
  • Skipping the test order and reopening checkout on the hope that the update worked.

A store also needs enough server headroom for the update. WooCommerce hosting resources explains the memory and database load a store places on its host.

For payment setup after an update, see what WooPayments is if that gateway is part of your store.

Frequently asked questions

Can I update WooCommerce without a staging site?

You can, but it is a risk. Without staging, the first time you see a fault is on the live store, in front of customers. If you have no staging option, at least take a full backup first, update during a quiet period, set the site to Coming soon mode, and test checkout right after. A host staging tool is worth asking your host about before the next update.

How long does a WooCommerce update take?

The plugin file update often takes only a few minutes on a small store. The database update can take longer on a store with many orders, because it has to change more rows. Plan a window of at least 30 minutes, and longer for a large store, so you are not rushed if the database step runs slowly or a check fails.

Should I update WordPress before WooCommerce, or WooCommerce first?

Check the requirements first. WooCommerce 10.8 needs WordPress 6.9 or newer, so if your WordPress version is below that minimum, update WordPress first. In general, update the parts in the order you tested them on staging, and do not change the order on live. Test the same set on staging, then apply the same set on live.

What if the database update notice does not go away?

Open WooCommerce, Status and check whether the WooCommerce version and the database version match. If they differ, open Scheduled Actions from the notice and look for pending or failed actions. Do not click the update button again and again. Keep a backup ready, note any error message, and ask your host or the extension developer for help with that message.

Is it safe to leave automatic updates on for WooCommerce?

Automatic updates can install a security fix fast, which is useful, but they can also install a major version before you have tested it on staging. Many store owners turn on automatic updates only for minor security releases, and handle major versions by hand with a backup and a staging test. Check your setting under Plugins, Installed Plugins, and pick the option that fits your store.

Do I need to update WooCommerce extensions at the same time?

Yes, in most cases. Extensions, payment gateways and themes are written for specific WooCommerce versions, so an old extension may not work with a new WooCommerce version. Update them in the same window you tested on staging, and check the tested-up-to version for each one before you start.

Sources

  1. How to update WooCommerce WooCommerce Documentation
  2. WooCommerce Server Recommendations WooCommerce Documentation
  3. Update PHP and WordPress WooCommerce Documentation
  4. WooCommerce 11.2.2: Release notes WooCommerce Developer Blog
  5. WordPress Backups WordPress Documentation
  6. PHP: Supported Versions PHP

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test