Post a "my WooCommerce checkout is broken" question anywhere and the first reply is almost always the same: "Deactivate all plugins, switch to a default theme, then turn them back on one by one."

On a brochure site that's fine. If the site goes weird for ten minutes, nobody loses money.

On a live store, it's a different story. The plugins you turn off are the store: the payment gateway, shipping rates, tax, subscriptions, the emails. This post goes through what actually happens when you deactivate everything on a store, and how to find the broken plugin without doing it.

What breaks while everything is off

Checkout stops taking money. With the gateway plugin off, customers either see no payment method or can't finish an order. Some leave and don't come back.

Webhooks fail. Payment providers send events (payment succeeded, refund, dispute) to an endpoint that the gateway plugin registers. With the plugin off, that endpoint is gone. Most providers retry failed webhooks for a while, but not forever. An order paid during your test window may never be marked as paid.

Scheduled jobs pile up or vanish. WooCommerce and many extensions run background work through Action Scheduler and WP-Cron: subscription renewals, follow-up emails, stock syncs, feed exports. While a plugin is inactive, its jobs either don't run or fail. Many plugins also clear their own cron events in their deactivation hook, so turning them back on doesn't always bring the schedule back the way it was.

Deactivation code runs. "Deactivate" is not the same as "pause." Each plugin's deactivation hook runs, and you don't control what it does. Usually it's harmless cleanup. Sometimes it's flushing rewrite rules, clearing caches, or removing scheduled tasks.

Your page cache keeps the broken version. If a page gets cached while half the plugins are off, visitors may keep seeing that version after you're done.

It can point at the wrong plugin. One-by-one reactivation finds the plugin that makes the bug come back. If the real cause is two plugins that only break together, you'll blame whichever of the two you turned on last.

Safer options, from best to good enough

1. Reproduce it on a staging copy

A staging copy with the same PHP version, the same plugin versions and a recent copy of the database is still the best place to test. Turn off whatever you like there. Watch out for two things:

  • Make sure staging can't email real customers or charge real cards (use the gateway's test mode, and block outgoing mail or send it to a log).
  • If the bug doesn't show on staging, the copy isn't the same as production. Compare PHP version, plugin versions, and server caching before you go further.

2. Turn plugins off for your own browser only

Some tools can switch plugins off for one logged-in session while everyone else sees the normal store:

  • Health Check & Troubleshooting: its troubleshooting mode disables all plugins for your session. You choose which ones to turn back on.
  • Culprit Finder: a free, open-source plugin I built (disclosure: I'm the author). It switches plugins off only for your own logged-in browser and never changes the active plugin list, so customers, search engines and other admins keep the full store. You answer "is the problem still there?" and it halves the suspects each time, so 30 plugins take about 7 answers. It also finds two-plugin conflicts, and gives you a plain-text report to paste into the plugin author's support forum.

Because nothing is really deactivated, no deactivation hooks run and no webhook endpoints disappear for real traffic.

One honest limit: these tools test as you, a logged-in admin. If a bug only shows for guest customers, or only for a certain country or shipping zone, check whether you can reproduce it as a logged-in user first. If you can't, go back to option 1.

3. If you really must deactivate on production

Sometimes there's no staging and no plugin you can install. Then reduce the damage:

  • Take a full backup (files and database) right before you start.
  • Pick the quietest hour of the day for your store.
  • Don't deactivate everything at once. Halve the list instead: turn off half, test, keep the half that contains the problem, repeat. With 30 plugins that's about 5 rounds instead of up to 30.
  • Keep the payment gateway and WooCommerce itself on unless you have a real reason to suspect them.
  • Purge the page cache when you're done.
  • Afterwards, check WooCommerce → Status → Scheduled Actions for failed or past-due actions, and look for orders that stayed "Pending payment" during your window.

What to check before you blame a plugin at all

A lot of "checkout is broken" reports aren't plugin bugs:

  • Read the logs first. WooCommerce → Status → Logs often names the failing gateway or the PHP error directly. So does wp-content/debug.log with WP_DEBUG_LOG on.
  • Check the browser console on the checkout page. A JavaScript error from one plugin can stop the whole checkout form.
  • Check what changed. If it broke right after an update, the update is your first suspect. Roll back that one plugin before you test anything else.

Summary

  • On a store, deactivating plugins means turning off payments, webhooks and scheduled jobs for real customers.
  • Use staging first. If you can't, turn plugins off for your own browser only.
  • If you have to touch production, halve the list instead of turning everything off, and check scheduled actions and pending orders afterwards.
  • If the bug only appears when two plugins are both active, report it to both authors as a pair.

What's the worst thing that happened to a store you've worked on during a "deactivate all plugins" test? I'd like to collect real cases.