Skip to content
NewsSep 2026·8 min read

How to update WooCommerce safely: the 11.x checklist

How to update WooCommerce without surprises: backups, staging and extension checks, what changed in 11.0 to 11.2, and what to do if the database update stalls.

SmartWP teamThe people who build our plugins
Flat illustration of a block crossing a bridge from an old version to a new one over a safety net

To update WooCommerce safely, back up the files and the database, check that your extensions support the new version, and try the update on a staging copy of the store first. Then update the live store in a quiet hour and place a test order once the database update has finished.

WooCommerce doesn’t treat 11.0 as a bigger step than 11.1. Its version numbers make no distinction between major and minor releases, and a new one arrives about every five weeks. Any release can include a database update or change something an older extension relied on.

Current version

WooCommerce 11.1.2, released on 22 September 2026. Version 11.2 is due in the week of 6 October.

Requirements

WordPress 7.0 or newer and PHP 7.4 or newer. WooCommerce 11.1 raised the WordPress minimum.

Last checked

6 October 2026, against the WooCommerce 11.1.2 code and its release notes.

What changed in WooCommerce 11.0, 11.1 and 11.2

WooCommerce’s release notes mark 11.0 and 11.1 as backwards compatible, and both run a database update.

WooCommerce 11.0 (4 August 2026)

  • Customers who checked out as guests and later made an account can confirm their email address in My Account. WooCommerce then adds their earlier guest orders to the account.
  • The Product Editor beta has been removed. If you still edit products in it, switch back to the classic editor before you update. Your products and their data stay as they are.
  • Action Scheduler, the queue behind WooCommerce’s background jobs, moves to version 4.0.

WooCommerce 11.1 (September 2026)

  • It needs WordPress 7.0 or newer, so update WordPress first if the site is still on 6.9.
  • Variation image galleries are built in. If you use the Additional Variation Images extension, 11.1 switches it off and copies its galleries across in the background.
  • EU stores can switch on a right-of-withdrawal form for My Account under WooCommerce → Settings → Advanced → Features. It’s off by default.

WooCommerce 11.2 (due in the week of 6 October 2026)

  • The experimental abandoned cart recovery is removed, and the 11.2 database update cancels any recovery actions still queued. Line up a replacement if you used it.
  • If you calculate coupon discounts sequentially, coupons with the same priority and item limit apply in the order the customer entered them, which can change cart totals.
  • The Cart and Checkout blocks get a fixed-width order summary and switch to two columns only at a wider size, so check any custom CSS on those pages.

The WooCommerce developer blog has the full notes for 11.0 and 11.1, and the 11.2 pre-release notes.

Action Scheduler 4.0: what changes for your store

Action Scheduler is the queue WooCommerce and many extensions use for background work, including the database update itself. You’ll find it under WooCommerce → Status → Scheduled Actions. Version 4.0 came with WooCommerce 11.0 and changes three things.

  • Failed actions are deleted once they’re three months old. Before 4.0 they were kept forever.
  • Clean-up runs as its own job, once a day at 3 am site time, and keeps going until any backlog is cleared.
  • Actions marked as unique now compare their arguments too, so an extension that relied on the old check may queue more jobs than before. Watch the Pending count for a day or two after you update.

If you keep failed jobs longer for investigations or audits, a developer can change the window:

functions.php
// Keep failed Action Scheduler actions for six months instead of three.
add_filter( 'action_scheduler_retention_period_for_failed', function () {
    return 6 * MONTH_IN_SECONDS;
} );

WooCommerce’s Scheduled Actions screen already counts pending, past-due and failed jobs. To change the window without code, the Scheduled action monitor in Admin Powerups has a “Keep failed actions for” setting of up to 730 days.

A shop and its identical staging copy side by side
Test the update on a staging copy before it touches the live store.

Before you update: the WooCommerce update checklist

Start a few days before you plan to update, so there’s time to wait for an extension developer if one isn’t ready.

How to update WooCommerce step by step

  1. Update the staging copy first, in the order you’ll use on the live store. Place a test order with each payment method, then check the order emails and anything your extensions add.
  2. Switch the live store to Coming soon under WooCommerce → Settings → Site visibility, so nobody checks out while files and the database change. WooCommerce’s own update guide suggests this for every update window.
  3. Update the extensions whose new versions still support the WooCommerce you’re running. Hold back any that need the new WooCommerce.
  4. Go to Plugins → Installed Plugins and click Update now under WooCommerce. Wait for it to finish before you open another page.
  5. Let the database update finish, then update the extensions you held back.
  6. Place an order, refund it, check its emails arrived and look in WooCommerce → Status → Logs for new fatal errors. Then switch Coming soon off.

On staging, turn on WordPress’s debug log before you update and read wp-content/debug.log afterwards. Deprecation notices there point to code that a later release may stop supporting.

wp-config.php · staging only
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

WooCommerce database update required: what it means

Most recent WooCommerce releases change something in the database, such as removing an old setting or moving data somewhere new. Since WooCommerce 9.9, that update starts by itself in the background once the new version is installed, and a “WooCommerce database update” notice shows while it runs.

The older “WooCommerce database update required” notice, with its Update WooCommerce Database button, appears only if a developer has switched automatic updates off with the woocommerce_enable_auto_update_db filter, or if the update jobs are missing from the queue. Take a backup, then click the button. The 11.0 and 11.1 updates are small: they change a few settings and clear out caches and old data. The 11.2 update has more steps, among them a fix to how Analytics stores order taxes and the removal of the abandoned cart experiment.

What to do if the WooCommerce database update is stuck

The update runs as a set of jobs in Action Scheduler, so it stalls when that queue isn’t running. If the notice won’t go away, check these in order.

  1. Click View progress in the notice (with WP-Cron switched off, the link reads “You can manually run queued updates here”). It opens Scheduled Actions filtered to the pending update jobs, and a job whose scheduled date has passed means the queue isn’t running. Failed jobs are listed under Failed, with the error in the Log column.
  2. Hover over a pending job and click Run to process it straight away.
  3. Open Tools → Site Health, which tests the scheduled events and loopback requests the queue needs.
  4. If DISABLE_WP_CRON is set in wp-config.php, ask your host to run a real cron job for the site. WooCommerce’s notice mentions it when that constant is set.
  5. In WooCommerce → Status → Logs, the wc-updater source lists each update job WooCommerce scheduled and any scheduling errors.

With SSH and WP-CLI you can skip the queue and run the updates directly:

Terminal · WP-CLI
# Run every pending WooCommerce database update now
wp wc update

# Or process only the queued database update jobs
wp action-scheduler run --group=woocommerce-db-updates

If the same job fails every time, stop re-running it. Copy the error from its log and post it on the WooCommerce support forum, or ask your host whether PHP is hitting a memory or time limit.

A stack of version cards with the top one being returned to the stack
A rollback works only if you kept the backup and the old version.

How to roll back a WooCommerce update

WordPress has no downgrade button, and WooCommerce’s database update doesn’t undo itself. The clean way back is the backup you took before you started: restore the files and the database together. Orders placed after that backup won’t be in it, so note them before you restore (another reason to update in a quiet hour).

An older zip from WordPress.org (Advanced View, then Previous Versions) brings back the old code but not the old database, and WordPress.org advises against older versions on production sites, so keep that route for staging.

Should you update WooCommerce right away?

Security releases, yes, after a quick check on staging. Their release notes say “Security update: Yes”, as they did for 11.0.1, 11.1.1 and 11.1.2. For the regular releases, WooCommerce’s guide suggests a monthly routine.

Leave updates alone in the run-up to a sale. Our Black Friday and sale-day checklist pauses updates the day before, so test a new version well ahead of it.

Free ebook, 42 pagesThe Ultimate Checklist to WooCommerce OptimizationGet the checklist

Questions about updating WooCommerce

Do I update plugins or WooCommerce first?

Follow the order that worked on staging. WooCommerce’s warning on the Plugins screen asks you to update untested extensions, or confirm they work, before you update WooCommerce. Its update guide has you update WooCommerce first and the other plugins straight after, in the same window. Anything that needs the new version has to wait until it’s installed.

Can I skip versions, say from 10.8 to 11.1?

Yes. WooCommerce runs every database update you missed, in order. Extensions and custom code are the risk, so test the jump on staging first.

How do I check which version I’m on?

Plugins → Installed Plugins shows it under WooCommerce, and WooCommerce → Status lists it next to your WordPress and PHP versions.

Found a mistake? Tell us. More news

Keep reading