Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WooCommerce Not Working Properly? 7 Steps to Find and Fix the Cause

WooCommerce Not Working Properly? 7 Steps to Find and Fix the Cause

Short answer

WooCommerce usually stops working properly because of a theme or plugin conflict, outdated software, page caching on cart and checkout, or low server limits. Check WooCommerce > Status, update everything, run a conflict test with Health Check & Troubleshooting, and read the logs to find the exact cause.

Key takeaways

  • Most WooCommerce problems come from theme or plugin conflicts.
  • WooCommerce > Status flags outdated templates, versions and limits.
  • Health Check troubleshooting mode tests conflicts without affecting visitors.
  • Cart, Checkout and My Account pages must never be cached.
  • Debug and WooCommerce logs usually name the faulty plugin or file.

Why is WooCommerce not working properly?

When WooCommerce misbehaves, the cause is usually outside WooCommerce itself. A theme or plugin conflict, an outdated component, aggressive caching or a server limit accounts for most problems.

WooCommerce's own self-service guide notes that a large share of support requests come down to conflicts with third-party themes and plugins. That is why conflict testing sits at the centre of the steps below.

The symptoms vary. You might see a blank shop page, an add to cart button that does nothing, a checkout that spins forever, missing emails or orders stuck in pending payment.

Work through the checks in order. Each one rules out a common cause and takes only a few minutes, and most stores are fixed before the end of the list.

Back up the site before you change anything. If the store takes live orders, do the heavier tests on a staging copy so customers are not affected.

Step 1: Write down exactly what is broken

Before changing anything, describe the problem precisely. Note which page fails, what you clicked, what you expected and what happened instead.

Check whether it happens for everyone or only for you. Try a private browser window, a different browser and a phone on mobile data.

If the problem only shows when logged in, or only in one browser, the cause is often a browser extension, a cached file or a session cookie rather than the store.

Take a screenshot of any error message. Error text often names the plugin or file that caused it, which can save a lot of guesswork.

Step 2: Check the WooCommerce System Status report

Go to WooCommerce > Status. The System Status report lists your WordPress, PHP and database versions, active plugins, theme and template overrides.

Items shown in red need attention. Common ones are outdated template overrides in the theme, a low PHP memory limit and missing WooCommerce pages such as Cart or Checkout.

Look at the “Templates” section near the bottom. If your theme overrides WooCommerce templates with old versions, layout and checkout problems are likely until the theme is updated.

Also check the “Database” section. If it shows a pending update, our guide to the WooCommerce database update required notice explains how to run it safely.

Step 3: Update WooCommerce, the theme and plugins

Outdated software is one of the most common causes of odd store behaviour. A plugin built for an older WooCommerce version may call functions that no longer exist.

Go to Dashboard > Updates and update WordPress core, WooCommerce, your theme and WooCommerce extensions. Update WooCommerce extensions together with WooCommerce when possible.

Check the PHP version too. WooCommerce and WordPress need a supported PHP release, and the PHP supported versions page shows which branches still get security fixes.

After updating, clear all caches and test the store again before moving on.

Step 4: Run a plugin and theme conflict test

A conflict test switches off everything except WooCommerce, then turns things back on one by one until the problem returns. WooCommerce describes the process in its guide on how to test for plugin and theme conflicts.

The safest tool is the Health Check & Troubleshooting plugin. Its troubleshooting mode disables plugins and switches the theme only for your logged-in session, so visitors still see the normal site.

Install it, go to Tools > Site Health > Troubleshooting and enable troubleshooting mode. Then enable WooCommerce from the plugins list and try to reproduce the problem.

If the problem disappears, re-enable plugins one at a time, testing after each, until it comes back. The last plugin you enabled is the likely cause.

If the problem only returns when you switch back to your normal theme, the theme is the cause. Our broader guide to fixing plugin conflicts covers what to do once you find the culprit.

Step 5: Exclude store pages from caching

Page caching is great for blog posts but harmful for carts. A cached cart or checkout page can show another visitor's items, stale prices or broken nonces.

Make sure your caching plugin, host cache and CDN exclude the Cart, Checkout and My Account pages. Most WooCommerce-aware caching tools do this automatically, but custom rules and CDN settings can override them.

Also exclude the WooCommerce cookies used for carts and sessions from cache rules, so logged-out shoppers get fresh pages once they add a product.

After changing settings, clear the WordPress cache and any CDN cache, then test again in a private window.

Step 6: Turn on debugging and read the logs

If nothing obvious shows up, turn on WordPress debugging to capture PHP errors. Add the debug constants to wp-config.php as described in the WordPress debugging documentation.

Keep the display of errors off on a live store and write them to the log file instead. Our guide on enabling debug mode in WordPress shows the safe settings.

WooCommerce also keeps its own logs under WooCommerce > Status > Logs. Payment gateways, webhooks and scheduled actions write details here, and fatal errors are logged automatically.

Look for lines that repeat around the time the problem happened. A file path in a fatal error usually points straight to the plugin or theme responsible.

Step 7: Check server limits and scheduled tasks

Some problems come from the server rather than code. A low PHP memory limit or short execution time can cut off checkout, imports or report generation.

The System Status report shows the WordPress memory limit and PHP time limit. If they look low, ask your host to raise them to the levels your extensions recommend.

WooCommerce also relies on scheduled background tasks for emails, subscriptions and stock updates. If many tasks are stuck, see our fix for past-due Action Scheduler actions.

Resaving permalinks under Settings > Permalinks fixes many 404 errors on product, cart and endpoint pages. Just open the page and click Save Changes without editing anything.

Common WooCommerce problems and where to start

Once you know which part of the store fails, go straight to the matching fix. The table maps common symptoms to their usual causes.

SymptomUsual causeWhere to start
Add to cart does nothingJavaScript conflict or cachingConflict test, cache exclusions
Checkout spins or failsGateway, theme or script errorLogs, conflict test
Products missing from shopVisibility, stock or theme settingsProduct and shop settings
No order emailsMail delivery or email settingsSMTP plugin, email settings
“Session expired” errorsCached pages or cookie issuesCache exclusions
Store pages show 404Permalinks not flushedResave permalinks

For checkout issues in particular, follow our guide to fixing WooCommerce checkout not working.

If the cart button is the problem, our guide on WooCommerce add to cart not working covers the JavaScript and caching causes in detail.

When customers never receive confirmations, see WooCommerce emails not sending for mail delivery fixes.

When to contact support or report a bug

If a conflict test points to a third-party plugin or theme, contact its developer with the steps to reproduce the problem and the relevant log lines.

If the problem persists with only WooCommerce active and a default theme, it may be a core bug. Search the WooCommerce support forum, and if nobody has reported it, open an issue in the WooCommerce GitHub repository.

Include your System Status report when you ask for help. It answers most of the first questions a support engineer would ask.

Frequently asked questions

Why did WooCommerce stop working after an update?

An extension or theme may not yet support the new WooCommerce version, or a database update may be pending. Check WooCommerce > Status for warnings, update the other components and run a conflict test.

How do I test WooCommerce without affecting customers?

Use the Health Check & Troubleshooting plugin, whose troubleshooting mode changes plugins and theme only for your session. For bigger tests, use a staging copy of the store so live orders are never at risk.

Can caching break WooCommerce?

Yes. If cart, checkout or account pages are cached, shoppers can see empty carts, stale prices or session errors. Exclude those pages and WooCommerce cookies from every cache layer.

Where are the WooCommerce error logs?

Go to WooCommerce > Status > Logs. Gateways, webhooks and fatal errors write entries there, and WordPress debug logging can add PHP errors to a separate debug log file.

Do I need to reinstall WooCommerce to fix problems?

Rarely. Reinstalling the plugin files does not remove products or orders, but it seldom fixes conflicts. Find the actual cause with the System Status report, a conflict test and the logs first.

Sources

  1. How to test for plugin and theme conflicts WooCommerce Documentation
  2. WooCommerce self-service guide WooCommerce Documentation
  3. Understanding the WooCommerce System Status report WooCommerce Documentation
  4. Health Check & Troubleshooting WordPress.org Plugins
  5. Debugging in WordPress WordPress Developer Resources
  6. Supported versions PHP.net

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.