How to Uninstall WooCommerce from WordPress Safely (Without Losing Store Data)

The safest default is to deactivate and delete WooCommerce normally. WordPress removes the plugin, while WooCommerce leaves products, orders, coupons, settings and related records in the database. Use the permanent-removal method only after a verified backup and exports, because adding define( 'WC_REMOVE_ALL_DATA', true ); to wp-config.php permanently erases WooCommerce data when the plugin is deleted.

Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.

Choose the removal route before touching WordPress

There are two different operations that are often called “uninstalling WooCommerce.” They have very different consequences. Decide which result you need before opening the Plugins screen.

#	Preview	Product	Price
1		WordPress Multisite Administration	$34.38	Buy on Amazon
2		Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition)	$9.90	Buy on Amazon
3		WordPress 24-Hour Trainer	$3.95	Buy on Amazon
4		Teacher Record Book	$4.89	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

WooCommerce Support describes the full-removal action this way: “As this action is destructive and permanent, the information is provided as is. WooCommerce Support cannot help with this process or anything that happens as a result.” Treat that warning as a decision gate, not as a routine cleanup suggestion.

Normal deletion is not a database purge

Deleting the plugin folder and deleting the store are separate decisions. A normal uninstall removes WooCommerce’s executable plugin files but intentionally keeps the information that makes the store recoverable. That distinction explains why products or orders may still appear in the database after the plugin has been deleted. It also means you can reinstall WooCommerce later without having to recreate the catalog from scratch, provided the surrounding site and extensions still support it.

#1 Best Overall

Sale

WordPress Multisite Administration

$34.38

Buy on Amazon

Full removal is a different lifecycle. It is intended for a confirmed end-of-life store or a clean-slate migration in which the old records have been exported and no longer need to remain on the site. There is no ordinary “undo” button after that cleanup. The practical recovery route is restoring the pre-removal backup or rebuilding from exports.

Prepare the site before uninstalling

Preparation determines whether removal is reversible and whether another plugin can continue working afterward. Complete every applicable item before deactivating WooCommerce.

1. Make and verify a complete backup

Create a full copy of the WordPress files and database, then verify that the backup can actually be restored or downloaded. Keep at least one copy outside the site—an external hard drive or SSD for WordPress backups can provide an offline copy. The official guidance does not require a particular backup product, storage medium or capacity; the important point is that the copy exists and is usable before any destructive step.

• Include the database, because products, orders, coupons, settings, options and scheduled data are stored there.
• Include the WordPress files, especially wp-config.php, themes, uploads and any custom integration code.
• Record when the backup was made and where it is stored.
• For a permanent removal, do not proceed until you can locate the backup and have checked its completeness.

A backup that exists only inside the same hosting account is less useful if the account or database is damaged. Keep the recovery copy separate from the site you are changing, and make sure the person performing the uninstall knows how to retrieve it.

2. Export records that must survive the site

Backups are for recovery; exports are for using the business records after WooCommerce is gone. Export whatever your accountant, tax authority, legal adviser, customer-service team or migration plan requires. Depending on your obligations, that may include order history, customer records, product catalogs, coupons, refunds, invoices or reports. Store those exports outside WordPress and confirm that they open correctly before deleting anything.

Do not assume a later plugin installation will recreate every report or setting exactly as it was. Exports give you a usable copy for accounting, customer questions and migration, while the backup preserves the technical state needed for a full restore.

3. Inventory extensions and integrations

Open the installed-plugin list and identify every extension that connects to WooCommerce. Include payment, shipping, tax, analytics, subscriptions, invoicing, fulfillment and custom integration plugins. Also note payment webhooks, scheduled integrations, theme templates and custom code that call WooCommerce functions or use its shortcodes.

Deactivate and, where appropriate, delete dependent extensions before WooCommerce. WordPress.com support specifically identifies WooPayments, WooCommerce Shipping and WooCommerce Tax as examples. Removing the parent plugin first can leave a dependent extension attempting to load missing code, producing an error or crash.

Make a short inventory before changing anything: plugin name, whether it is still needed, credentials or webhooks it owns, and whether it shares data with another system. This prevents an apparently successful uninstall from leaving an external service repeatedly calling URLs that no longer exist.

4. Decide whether Action Scheduler is shared

WooCommerce uses Action Scheduler tables, but another active plugin may use the same library. WooCommerce does not remove those tables through WC_REMOVE_ALL_DATA by default for that reason. Do not plan to remove them merely to make the database appear cleaner; first verify that no other active plugin depends on Action Scheduler.

If you cannot establish that the tables belong exclusively to WooCommerce, leave them in place. Shared infrastructure is safer to retain than to delete speculatively, particularly on a site that still runs other commerce, marketing or maintenance extensions.

Rank #2

Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition)

$9.90

Buy on Amazon

Safely remove WooCommerce while retaining its data

This is the recommended path when you may need the catalog or order history later. It follows WordPress’s documented lifecycle: deactivate the plugin, then use Delete.

1. Finish the backup and exports. Confirm that the complete site backup and any required business exports are stored outside the WordPress installation.
2. Handle dependent extensions first. From Plugins → Installed Plugins, deactivate companion plugins and integrations that require WooCommerce. Delete them only if they are no longer needed. Pay particular attention to WooPayments, WooCommerce Shipping and WooCommerce Tax.
3. Deactivate WooCommerce. In Plugins → Installed Plugins, locate WooCommerce and select Deactivate. Deactivation stops the plugin without performing the final uninstall operation.
4. Delete the plugin. Return to the same list, select Delete for WooCommerce and confirm WordPress’s prompt. WordPress defines uninstall as deactivation followed by deletion; the two stages have different cleanup responsibilities.
5. Check the public site. Visit the home page, product URLs, checkout-related URLs and login page. Check the front-end pages that matter to your theme and business, rather than assuming that removal was isolated to the plugin screen.
6. Check the administration area. Open the dashboards and content screens still used by the site. Look for PHP errors, broken blocks, missing widgets or notices from extensions that were not removed.

What this route preserves

WooCommerce’s normal uninstall behavior leaves its store data in place by default. That includes products, orders, coupons, settings and related records. Keeping those records makes this route appropriate when you might reinstall WooCommerce, migrate the store, or need historical information later.

Preservation does not mean the store is immediately usable without WooCommerce. The records remain available, but the product, cart, checkout and account interfaces supplied by WooCommerce may no longer render. That is expected when the runtime plugin has been removed.

What this route does not clean up automatically

Deleting the plugin does not understand every site-specific reference to the store. After the deletion, remove or repoint items that still intentionally or accidentally target WooCommerce:

• Menus and widgets linking to shop, cart, checkout or account pages.
• Shortcodes in posts, pages and reusable content.
• Theme templates, custom functions and blocks that call WooCommerce code.
• Payment or fulfillment webhooks and external scheduled integrations.
• Extension settings and credentials for services you have retired.
• Navigation links, redirects and search-engine settings for URLs that no longer exist.

These follow-up edits are site-specific. Use the documentation for the relevant theme or extension before removing a setting whose purpose is unclear. If another plugin still needs WooCommerce, do not delete that dependent plugin’s settings or credentials until you have confirmed its replacement workflow.

Permanently erase WooCommerce data

Use this route only when the store records are no longer needed, required exports are complete, and the backup has been verified. The constant must be added before deletion; simply deleting WooCommerce without it follows the data-retaining path.

1. Edit wp-config.php

Open the site’s wp-config.php file using the method provided by your host or server administrator. Add this line above the comment /* That's all, stop editing. */:

define( 'WC_REMOVE_ALL_DATA', true );

Keep the spelling, capitalization, quotation marks and semicolon exactly as shown. Save the file, and ensure that the edit did not introduce an extra character or remove an existing configuration line.

2. Remove dependent extensions first

Before deleting WooCommerce, deactivate and, when appropriate, delete extensions that depend on it. WooPayments, WooCommerce Shipping and WooCommerce Tax are named examples of plugins that should be handled first. This order prevents a companion plugin from trying to load WooCommerce after its files have disappeared.

3. Deactivate and delete WooCommerce

1. Go to Plugins → Installed Plugins.
2. Deactivate WooCommerce.
3. Use Delete and confirm the action.

With WC_REMOVE_ALL_DATA set to true, WooCommerce removes its data during uninstall. WooCommerce identifies products, order data and coupons among the records removed and warns that the process cannot be undone through normal plugin controls.

4. Remove the constant after the operation

Once the uninstall has completed, edit wp-config.php again and remove the temporary WC_REMOVE_ALL_DATA line. Leaving a destructive constant in configuration creates a risk if WooCommerce is later installed and deleted again.

Rank #3

Sale

WordPress 24-Hour Trainer

$3.95

Buy on Amazon

Action Scheduler tables require a separate decision

WooCommerce deliberately leaves Action Scheduler tables alone during its normal full-data cleanup because another active plugin may share them. Only add the second constant after you have verified that no active plugin uses Action Scheduler:

define( 'WC_REMOVE_ACTION_SCHEDULER', true );

For extra Action Scheduler table removal, both constants are required:

define( 'WC_REMOVE_ALL_DATA', true );
define( 'WC_REMOVE_ACTION_SCHEDULER', true );

Place both lines above /* That's all, stop editing. */, then deactivate and delete WooCommerce. If you cannot establish that Action Scheduler is unused elsewhere, do not add WC_REMOVE_ACTION_SCHEDULER. Keeping shared tables is safer than deleting data another plugin needs.

Scheduled tasks WooCommerce clears during uninstall

WooCommerce’s uninstall code clears its own scheduled hooks. The published code covers:

• Scheduled sales.
• Unpaid-order cancellation.
• Session cleanup.
• Personal-data cleanup.
• Log cleanup.
• GeoIP updates.
• Tracking.
• Rate-limit cleanup.
• WooCommerce Admin daily tasks.
• Category lookup generation.

This cleanup concerns WooCommerce’s registered scheduled hooks. It does not remove every cron event created by an unrelated extension or external service, so review integrations separately. A payment gateway, shipping service or monitoring system can have its own scheduled work even after WooCommerce is gone.

Compare the two routes before you confirm

Choose the first route when reversibility has value. Choose the second only when permanent erasure is the actual business requirement, not simply because the database looks untidy.

Common failure modes and recovery choices

A dependent plugin reports a fatal error

A companion extension may still be active and attempting to load WooCommerce after the parent plugin was deleted. If the admin remains available, deactivate the dependent extension from Plugins → Installed Plugins. If the site is inaccessible, use the recovery method supplied by your host or WordPress administrator to disable the extension, then restore or reinstall the required components from a verified backup.

The store disappeared after deletion

That result is expected if WC_REMOVE_ALL_DATA was enabled. Do not reinstall and delete repeatedly while troubleshooting. Restore the database and files from the verified pre-uninstall backup, or import the exports if you are rebuilding on a different system.

Products remain after normal deletion

Normal deletion is designed to leave WooCommerce data in place. Remaining products, orders or settings are not evidence that WordPress failed to delete the plugin; they are the expected distinction between plugin-file removal and full data removal.

The database still contains Action Scheduler tables

WooCommerce intentionally does not remove those shared tables through WC_REMOVE_ALL_DATA. Unless you have verified that no active plugin uses Action Scheduler, leave them in place. Removing shared tables without that verification can damage another extension.

Menus or pages still point to a store

Review menus, widgets, shortcodes, templates and redirects after either removal route. These references belong to the site’s content and presentation layers, not solely to the WooCommerce plugin, so they may require manual editing.

Rank #4

Teacher Record Book

• Keep track of everything from attendance to test scores
• Spiral bound
• Measures 8-1/2" x 11"

$4.89

Buy on Amazon

The site works, but external services keep sending requests

Check payment webhooks, fulfillment callbacks and scheduled integrations recorded during your inventory. Disable or repoint them through the relevant service. Removing WooCommerce does not automatically revoke every setting held by an outside provider.

Final verification checklist

• Backup is complete, readable and stored outside the site.
• Required accounting, tax, legal and customer-service exports are stored separately.
• Dependent extensions were handled before WooCommerce.
• The chosen route—data-retaining or permanent—matches the actual business decision.
• If permanent removal was chosen, WC_REMOVE_ALL_DATA was added above the stop-editing comment and removed afterward.
• WC_REMOVE_ACTION_SCHEDULER was used only after confirming that no other active plugin depends on Action Scheduler.
• Public pages, checkout-related URLs, login and essential admin screens were checked.
• Menus, widgets, shortcodes, templates, webhooks and scheduled integrations were removed or repointed where necessary.
• No remaining extension or theme code expects WooCommerce to be active.

Which method should you use?

If there is any chance you will need products, orders, coupons or settings later, use normal deactivation and deletion. It removes WooCommerce’s plugin files while preserving the database records. Choose full removal only for a confirmed end-of-life or clean-slate migration, and only after the backup and export checks are complete. The two workflows are not interchangeable: one is reversible in practice, while the other is designed to erase the store permanently.

Frequently Asked Questions

How do I uninstall WooCommerce without losing my products?

Use the normal WordPress lifecycle: back up the site, handle dependent extensions, deactivate WooCommerce, then click Delete. Do not add WC_REMOVE_ALL_DATA. WooCommerce leaves products and other store records in place by default.

Does deleting WooCommerce delete orders?

Not during a normal deactivation and deletion. Orders, products, coupons, settings and related records are retained by default. Orders are removed only when you deliberately enable WC_REMOVE_ALL_DATA before deleting the plugin.

How do I completely remove WooCommerce and its database data?

Verify a complete backup and required exports first. Add define( 'WC_REMOVE_ALL_DATA', true ); above /* That's all, stop editing. */ in wp-config.php, then deactivate and delete WooCommerce. The action is destructive and permanent.

Where should the WooCommerce removal constant go?

Place define( 'WC_REMOVE_ALL_DATA', true ); in wp-config.php, above the comment /* That's all, stop editing. */. Remove the temporary line after the uninstall has finished.

Should I delete WooPayments before WooCommerce?

Yes. Deactivate and, where appropriate, delete dependent extensions first. WordPress.com specifically names WooPayments, WooCommerce Shipping and WooCommerce Tax because leaving them active can cause errors or crashes after the parent plugin is removed.

Why are Action Scheduler tables still in the database?

WooCommerce leaves them because another active plugin may share Action Scheduler. Add WC_REMOVE_ACTION_SCHEDULER only after verifying that no active plugin depends on it; both removal constants are required for that extra cleanup.

Will uninstalling WooCommerce remove menus, shortcodes and theme code?

No. Menus, widgets, shortcodes, templates, redirects, webhooks and custom code are site-specific references. Review and remove or repoint them separately after either uninstall route.

What should I do if I deleted WooCommerce with the removal constant by mistake?

Stop making further uninstall attempts. Restore the files and database from the verified pre-uninstall backup, or use the business exports when rebuilding on another system. Full removal is not reversible through normal WordPress controls.

The Bottom Line

Back up and export first, then choose deliberately. Normal deactivation and deletion removes WooCommerce while preserving store data. Permanent cleanup requires WC_REMOVE_ALL_DATA, careful dependency ordering and a verified recovery plan; Action Scheduler needs a separate shared-use check.

Quick Recap

SaleBestseller No. 1

WordPress Multisite Administration

$34.38

Bestseller No. 2

Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition)

$9.90

SaleBestseller No. 3

WordPress 24-Hour Trainer

$3.95

Bestseller No. 4

Teacher Record Book

Keep track of everything from attendance to test scores; Spiral bound; Measures 8-1/2" x 11"

$4.89

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.