How to downgrade WooCommerce plugin files takes about a minute, and your products and orders stay in place. The real risk is the database, because a downgrade swaps the code but leaves the newer database schema behind.
I tested every method in October 2026 on a WordPress 7.1.3 test store running WooCommerce 11.2.0 with 12 products and 3 orders. I rolled it back to 11.1.2 three ways: by uploading the older ZIP, with the WP Rollback plugin and with WP-CLI.
This guide shows each method with screenshots from that test. It also covers what to check before you start and how to stop WordPress from updating the plugin again the next night.
When Should You Downgrade WooCommerce?
Downgrade WooCommerce only when a new release breaks something you cannot fix quickly. Typical cases are a checkout error, a broken theme template or an extension that stops working. Treat it as a short term fix and update again once the extension or theme author ships a fix.
Good reasons to roll back include:
- Broken checkout: Orders fail or the payment step throws an error after the update.
- Extension conflict: A payment, shipping or subscription extension is not yet compatible with the new version.
- Theme overrides: Your theme’s WooCommerce templates are out of date and the shop layout breaks.
- Fatal errors: The site shows a critical error and you need the store back online now.
Poor reasons include a changed admin screen or a new setting you do not like. Those are better solved by learning the new screen, because staying on an old version means missing security fixes.
What to Check Before You Downgrade a WordPress Plugin
Before you downgrade a WordPress plugin like WooCommerce, take a full backup, note the current version and check whether the update already changed the database. These three checks decide whether a rollback is safe. Skipping them is how a quick fix turns into missing orders.
Work through this list first:
- Full backup: Back up the files and the database together, and test that you can restore them.
- Current version: Note the exact version you are leaving, so you can return to it later.
- Target version: Pick the last version that worked for you, usually the previous minor release.
- Database version: Check the
woocommerce_db_versionoption, covered in the next section. - Staging copy: Try the downgrade on a staging site first if your host offers one.
A WordPress care plan usually includes daily backups and a staging site, which makes this step a lot less stressful.
Does Downgrading WooCommerce Delete Orders or Products?
No. Downgrading WooCommerce replaces the plugin folder only, so products, orders and customers stay in the database where they always live on the server. My test store kept all 12 products and all 3 test orders after each of the three rollbacks.
What does not roll back is the database schema, and that is the part to plan around.
WooCommerce stores its data in the WordPress database. The plugin folder holds only code, and every method in this guide deletes the old folder and puts the older code in its place.
The WooCommerce guide to installing and uninstalling WooCommerce walks through activating a previous version. Its support FAQ adds that WooCommerce.com supports the latest release and the one before it. That is a good reason to roll back one version and no further.
What the Test Showed About the Database Version
After the downgrade to 11.1.2, the plugin list showed 11.1.2. The woocommerce_db_version option still read 11.2.0-1, the schema version from the newer release. WooCommerce showed no warning about it on the Plugins screen or the Status screen.
On my small test store that caused no visible problem. On a busy store, a schema change such as a new table or column can trip up the older code.
That is why the backup has to include the database. A short hop back to the last minor release is also safer than a jump across several majors.
How to Downgrade WooCommerce Plugin From the Dashboard
How to downgrade WooCommerce plugin from the dashboard is simple: download the older ZIP from WordPress.org and upload it under Plugins, then Add Plugin. WordPress sees the version is older and asks you to confirm. This method needs no extra plugin, so it is the cleanest way to revert plugin update WordPress changes.
Older versions live on the WooCommerce Advanced View page, under Previous Versions. Pick a version from the dropdown and click Download.
Then follow these steps:
- Go to Plugins, then Add Plugin, and click Upload Plugin.
- Choose the older
woocommerce.x.y.z.zipfile and click Install Now. - Check the comparison table, then click Replace current with uploaded.
- Wait for the message that says the plugin was downgraded successfully.
- Open the shop, cart and checkout pages and place a test order.
The comparison table is a useful safety check. It lists the current and uploaded versions side by side with the required WordPress and PHP versions. That lets you spot a mismatch before you confirm.
One snag from my test: the WooCommerce ZIP is about 18 MB. On my first try the upload failed with “The link you followed has expired”.
That message means the file is bigger than the server’s PHP upload limit. Ask your host to raise upload_max_filesize and post_max_size, or use one of the methods below.
How to Rollback Plugin Update WordPress Style With WP Rollback
WP Rollback is a free plugin that lists every version on WordPress.org and installs the one you pick. It adds a Rollback link under each plugin on the Plugins screen. It is the easiest way to rollback plugin update WordPress changes if you are not comfortable handling ZIP files.
I used version 3.2.0 of WP Rollback for this test. Here is the process:
- Install and activate WP Rollback from Plugins, then Add Plugin.
- Go to Plugins, then Installed Plugins, and click Rollback under WooCommerce.
- Select the version you want, then click Rollback.
- Confirm in the popup, then wait for every step to finish.
The whole rollback took under 30 seconds on my test site. The popup shows each step, from downloading the package to cleaning up temporary files.
The list also includes beta and release candidate builds. Skip anything marked beta or rc on a live store. Pick the last stable version that worked for you.
Deactivate WP Rollback when you are done. A plugin you no longer use is one more thing to keep updated.
How to Downgrade Plugin WordPress Sites With WP-CLI
To downgrade plugin WordPress installs from the command line, run wp plugin install woocommerce --version=11.1.2 --force from the site folder. It downloads that version and replaces the current folder in one step. This is the fastest method when your host gives you SSH access.
Here are the commands I used on the test store:
wp plugin list --name=woocommerce --fields=name,version wp plugin install woocommerce --version=11.1.2 --force wp option get woocommerce_db_version
The second command took 11 seconds and printed “Plugin updated successfully”. The wording is confusing, but the version check afterwards showed 11.1.2. The WP-CLI plugin install reference documents the --version and --force options.
The same command works for any plugin hosted on WordPress.org. Swap the slug and the version number, and you have a general WordPress downgrade plugin method that needs no dashboard at all.
How to Stop WooCommerce Updating Again
After a rollback, WordPress shows the newer version as an update straight away. If auto-updates are on, it will install that version again within a day. Turn off auto-updates for WooCommerce and wait for a fixed release before you update again.
On my test store the Plugins screen showed “There is a new version of WooCommerce available” right after the rollback. The Automatic Updates column had the Enable auto-updates link, which means auto-updates were off for that plugin.
If yours says Disable auto-updates, click it. You can also block updates for one plugin with a filter in a small custom plugin:
add_filter( 'auto_update_plugin', function ( $update, $item ) {
if ( isset( $item->slug ) && 'woocommerce' === $item->slug ) {
return false;
}
return $update;
}, 10, 2 );
This stops the automatic update only. You can still update by hand from the Plugins screen once the fix is out.
Then check the WooCommerce changelog until a release mentions your bug. When the release notes mention your bug, or your extension author confirms support, update on staging first.
On my test store the Status screen under WooCommerce showed 11.1.2 right after the rollback. Copy that report into any support ticket so the extension author sees the exact setup.
Does WordPress Roll Back Failed Plugin Updates on Its Own?
Yes, in two cases. Since WordPress 6.3, a manual plugin update that fails to install or activate restores the previous version. Since WordPress 6.6, an automatic update that causes a fatal error on the homepage is rolled back too, with the error written to the log.
A bug that leaves the site running is not caught.
The WordPress 6.3 rollback note covers failed manual updates. The Rollback Auto-Update merge proposal explains how WordPress checks the homepage for a fatal error after an automatic update.
So a white screen after an auto-update often fixes itself. A broken checkout, a missing payment option or a wrong tax total does not, and those are the cases where you need the methods above.
How to Choose the Right Method
Pick the method that fits your access and comfort level. All three gave the same result on my test store, which was version 11.1.2 with every order and product in place. Each one also left the newer database version behind, so the backup rule applies to all three.
- Upload the ZIP: Best when you have no SSH access and do not want another plugin.
- WP Rollback: Best for picking from a list without downloading files yourself.
- WP-CLI: Best for developers and for sites where the upload limit blocks large ZIP files.
If none of them fixes the problem, the cause may not be WooCommerce at all. Switch to a default theme on staging and disable other plugins one by one. If you build custom features, our guide on how to create a WooCommerce plugin explains the version checks that help code survive core updates.
Content that relies on WooCommerce shortcodes is worth testing after any version change, because older shortcodes are slowly being replaced by blocks.
What to Do After the Downgrade
After the downgrade, test the full buying journey from the product page to the order email. Then send the plugin or theme author the exact versions and the error you saw. Set a date to update again, because a rollback leaves you without the newest security fixes.
A rollback only pauses the problem. The goal is to update again within a few weeks, once the conflict is solved.
Use this checklist:
- Test checkout: Place a real or sandbox order and check that the email arrives.
- Check extensions: Open each extension’s settings page and look for errors.
- Review logs: Check WooCommerce, then Status, then Logs for new fatal errors.
- Report the bug: Send the extension author your system status report and the version numbers.
- Plan the update: Set a date to update again on staging.
Loyalty and rewards plugins touch the cart and checkout too. If you run one, test points and redemption after any WooCommerce version change. Our list of the best WooCommerce points and rewards plugins notes which ones keep up with new releases.
Conclusion
How to downgrade WooCommerce plugin safely comes down to one rule: back up the database first. Every method in this guide kept products and orders. None of them reversed the newer database schema.
Use the dashboard upload when you have no SSH access and WP Rollback for a point and click list. Use WP-CLI when the ZIP is too big to upload. Then turn off auto-updates for WooCommerce so the old version stays in place.
Treat the rollback as temporary. Update again on staging as soon as the extension or theme that broke has a fix.
Frequently Asked Questions (FAQs)
Q1. Will I lose my orders if I downgrade WooCommerce?
No. Orders, products and customers live in the database, and a downgrade only replaces the plugin files. My test store kept all 3 orders and 12 products, but back up first because newer database changes are not reversed.
Q2. Where can I download an old WooCommerce version?
Open the WooCommerce plugin page on WordPress.org and click Advanced View. Under Previous Versions, pick a version from the dropdown and click Download to get its ZIP file.
Q3. How do I revert a plugin update in WordPress?
Upload the older ZIP under Plugins, then Add Plugin, and click Replace current with uploaded. You can also use the free WP Rollback plugin or run wp plugin install slug --version=x.y.z --force with WP-CLI.
Q4. Why does WordPress say “The link you followed has expired” when I upload the ZIP?
The file is larger than the server’s PHP upload limit. The WooCommerce ZIP is about 18 MB. Ask your host to raise upload_max_filesize and post_max_size, or use WP Rollback or WP-CLI instead.
Q5. Can I downgrade WooCommerce after the database update ran?
Yes, the files will roll back, but the database stays on the newer version. On a small hop such as 11.2 to 11.1 this is often fine. For bigger jumps, restore a full backup taken before the update.
Q6. How do I stop WooCommerce from updating again?
Click Disable auto-updates next to WooCommerce on the Plugins screen. You can also add the auto_update_plugin filter shown above to block automatic updates for that plugin only.
