Kiwistic Get a Free Quote

Home / WordPress Guides / Troubleshooting / WooCommerce Support for Common Store Problems

WooCommerce Support for Common Store Problems

Ognjen Velickovic
}

Last updated Nov 4, 2026

TABLE OF CONTENTS

Free WordPress Site Review

Is your WordPress setup ready for what 2026 demands?
Get a Free Site Review

TL;DR

Most common WooCommerce problems involve checkout failures, payment errors, missing order emails, slow performance, plugin conflicts, or outdated software. The right fix depends on identifying the cause rather than changing settings at random.

  • Start with the symptoms: Check when the issue occurs, which part of your store is affected, and whether it started after an update or configuration change.
  • Troubleshoot safely: Review WooCommerce settings and error logs, and use a staging site to test changes that could disrupt your live store.
  • Know when to get help: If checkout or payments are failing, orders are affected, or the problem keeps returning, professional WooCommerce support can help you investigate and resolve the underlying issue.

This guide covers 10 common WooCommerce problems, what may cause them, and practical steps to troubleshoot them.

Running a WooCommerce store means dealing with more than products and orders. Checkout failures, payment errors, missing order emails, and plugin conflicts can interrupt daily operations and, in some cases, prevent customers from completing purchases.
The challenge is finding out what’s actually causing the problem. An issue that appears after a plugin update might involve a compatibility conflict, a server error, or a misconfigured setting. Making changes without checking the cause can create additional problems.
In this guide, we’ll walk through 10 common WooCommerce problems, explain their possible causes, and show you where to start troubleshooting. You’ll also learn which checks are safe to perform yourself and when it’s better to seek professional assistance.

Before troubleshooting: Protect your live WooCommerce store

Before changing plugins, payment settings, or theme files, identify exactly what is failing. A checkout error and a failed payment notification may look similar to a customer, but they require different checks.
Start with these four steps:

1. Check whether orders and payments are still being recorded.

Go to WooCommerce → Orders and inspect recent orders, their statuses, and order notes. If a customer reports a failed payment, check the transaction in your payment provider’s dashboard before asking them to try again. A payment may have succeeded even when the order status wasn’t updated correctly.

2. Review WooCommerce logs and system status.

Open WooCommerce → Status → Logs and look for relevant errors around the time the problem occurred. Depending on the issue and available logging, these may include fatal PHP errors or payment gateway messages.

Under WooCommerce → Status → System Status, review your server environment, active software versions, and outdated template overrides. A warning is useful diagnostic information, but it doesn’t automatically identify the cause.

3. Identify what changed before the issue appeared.

Check whether the problem started after a WooCommerce update, plugin installation, theme change, or payment gateway configuration change. Note the affected page, the error message, and whether the problem occurs for every customer or only under specific conditions.

4. Test potentially disruptive changes away from your live store.

Before disabling plugins, switching themes, or modifying checkout functionality, create a recent backup and use a staging environment where possible. Make sure staging payment gateways cannot process unintended real transactions, and avoid copying outdated staging orders or customer data back to production.

Important: If customers are being charged but their orders remain pending or failed, stop repeated payment testing until you’ve checked the corresponding transactions. Otherwise, you risk creating duplicate charges.

Once you’ve identified the symptoms and collected the relevant information, use the sections below to investigate the specific WooCommerce problem.

10 Common WooCommerce Problems and How to Fix Them

The following WooCommerce issues can affect everything from checkout and payments to store performance. Each section explains what to check and when the problem may require technical support.

1. WooCommerce Checkout Not Working

A broken WooCommerce checkout can prevent customers from completing purchases. You might see an endless loading spinner, missing payment methods, an unresponsive Place Order button, or an error when submitting an order.
The cause isn’t always the payment gateway. Checkout failures can also result from JavaScript errors, plugin conflicts, caching rules, or blocked server requests.

How to troubleshoot:

1. Identify the checkout type. Open the page assigned under WooCommerce → Settings → Advanced. Check whether it uses the Checkout block or the classic woocommerce_checkout shortcode. This determines which requests need investigating.

2. Check for failed requests. Open your browser’s Developer Tools → Network tab and reproduce the issue using a safe test environment. Classic Checkout typically uses wc-ajax requests, while Checkout Block uses WooCommerce Store API endpoints under /wp-json/wc/store/. Failed requests and their responses can help narrow down the cause.

3. Review caching and plugin conflicts. Make sure checkout pages and related dynamic requests aren’t being incorrectly cached. If the problem started after an update, investigate the affected plugin or theme on staging rather than disabling essential functionality on your live store.

4. Check orders before retrying payments. If checkout appears to fail after clicking Place Order, inspect WooCommerce → Orders and your payment provider’s transaction records. The payment or order may already exist.

When to seek help: If checkout continues to fail, requests return server errors, or customers are charged without their orders updating correctly, further technical investigation is needed before making additional changes.

2. WooCommerce Payment Gateway Failures

WooCommerce payment failures don’t always mean something is wrong with your store. A customer’s bank may decline a transaction, the payment gateway may reject a request, or WooCommerce may fail to receive confirmation after a successful payment.
The key is identifying whether the payment actually failed or whether the order status simply wasn’t updated.

How to troubleshoot:

1. Check the affected order. Go to WooCommerce → Orders, open the order, and review its status and order notes. Look for decline reasons, transaction IDs, or gateway error messages.

2. Verify the transaction with your payment provider. Check the corresponding payment in Stripe, PayPal, WooPayments, or whichever gateway you use. If the payment succeeded but WooCommerce still shows Pending payment or Failed, investigate the status synchronization before retrying the charge.

3. Review payment gateway logs. Go to WooCommerce → Status → Logs and select the relevant gateway log, if available. Some payment plugins require logging to be enabled in their settings before they record detailed errors.

4. Check gateway configuration and notifications. Verify that the payment method is enabled and correctly configured. If payments succeed but order statuses don’t update, inspect the gateway’s webhook or callback configuration using its official documentation.

When to seek help: If multiple customers experience payment failures, successful transactions aren’t reflected in WooCommerce, or gateway errors continue after basic checks, the integration needs further investigation.

3. WooCommerce Order Emails Not Sending

Customers may complete a purchase without receiving their order confirmation, or store administrators may stop receiving new order notifications. These problems can have different causes, so installing an SMTP plugin isn’t always the right first step.

Start by checking an affected order under WooCommerce → Orders. If payment was completed but the order remains Pending payment, investigate why its status wasn’t updated. WooCommerce may not have triggered the expected confirmation email.

If the order status is correct, check the following:

1. Email settings: Open WooCommerce → Settings → Emails and confirm that the relevant notification is enabled and has the correct recipient.

2. Transactional email logs: In supported WooCommerce versions, go to WooCommerce → Status → Logs and look for the transactional-emails log. It can show whether an email was sent, failed, disabled, or skipped.

WooCommerce transactional email log showing successful send attempts for new order and customer processing order emails.

3. Email delivery: If WooCommerce handed the message to the mail system successfully but the recipient didn’t receive it, check your mail provider’s delivery logs, spam filtering, and SPF, DKIM, and DMARC configuration.

A successful send attempt does not guarantee inbox delivery. If notifications are consistently missing, identify where the process fails before changing plugins or mail settings.

4. WooCommerce Shipping and Tax Issues

Incorrect shipping costs, missing delivery options, or unexpected taxes can cause customers to abandon checkout. These issues often come from how WooCommerce matches customer addresses with shipping zones and tax settings.

When shipping options are missing

Go to WooCommerce → Settings → Shipping → Shipping zones and check whether the customer’s address matches the correct zone. Make sure that zone contains an enabled shipping method.

Zone order matters: WooCommerce uses the first matching zone. A more general zone placed above a specific one may prevent the intended shipping method from appearing.

WooCommerce Shipping Zones settings showing Serbia with Table Rate shipping and no shipping methods for the Rest of the world zone.

When shipping costs or taxes are incorrect

1. Shipping rates: Check the rates, conditions, and restrictions configured for the matching shipping method. Free shipping, for example, may depend on a minimum order amount or coupon.

2. Tax calculations: Under WooCommerce → Settings → Tax, verify which address is used to calculate taxes, whether prices include tax, and which tax rates apply.

3. Location-specific results: Test the checkout using an affected customer’s shipping address and cart contents. Different destinations or product tax classes may produce different totals.

If you use automated tax calculations or third-party shipping extensions, review their settings and logs before changing WooCommerce’s core configuration.
WooCommerce controls how configured taxes are calculated, but it doesn’t determine your legal tax obligations. Confirm the applicable rates and rules with a qualified tax professional.

5. Slow WooCommerce Store Performance

A WooCommerce store might load quickly on the homepage but become noticeably slower on product pages, in the cart, or during checkout. That difference matters because each part of the store handles data differently.
For example, product images and scripts can slow down a product page, while checkout performance may depend more heavily on server processing, payment integrations, and database queries.

Start by identifying where the slowdown happens.

Test a product page and the checkout page separately using Google PageSpeed Insights. Look at server response times, large assets, and the difference between real-user data (when available) and individual test results.
Then investigate the likely cause:

1. Slow product pages: Check oversized images, unnecessary scripts, and resource-heavy product extensions.

2. Slow cart or checkout: Review server performance, payment integrations, and caching configuration. These pages contain customer-specific information and shouldn’t be treated like ordinary static pages.

3. Slow WooCommerce admin: Check WooCommerce → Status → Scheduled Actions for repeatedly failing or backlogged tasks. If the issue persists, investigate database activity and server resources.

Caching, image optimization, and better hosting can improve performance, but they address different bottlenecks. Measure the problem before making changes, then test whether the adjustment actually improved the affected page.

6. WooCommerce Plugin and Theme Conflicts

A WooCommerce feature that suddenly stops working after an update may indicate a plugin or theme conflict. Common symptoms include broken product variations, missing checkout fields, JavaScript errors, or features that work in the WordPress admin but fail on the storefront.
However, the most recently updated plugin isn’t necessarily responsible. The issue may involve another extension, theme customization, or an incompatibility between multiple components.

How to identify the conflict

On a staging copy of your store, reproduce the issue and temporarily disable non-essential plugins while keeping WooCommerce and the affected functionality active. If the problem disappears, reactivate plugins individually and repeat the same test until it returns.
If disabling plugins doesn’t resolve the issue, test with a default WooCommerce-compatible theme, such as Storefront. This can help determine whether your active theme or its customizations are involved.
Once you’ve identified the conflicting component, check for a compatible update or contact its developer. Avoid permanently removing an essential extension or editing its files without understanding how that change affects your store.
A successful conflict test identifies where the problem originates. It doesn’t necessarily mean the underlying compatibility issue has been fixed.

7. Outdated WooCommerce Templates

After updating WooCommerce, you may see a warning that your theme contains outdated copies of WooCommerce template files. This happens when a theme or child theme overrides default templates that have since changed in WooCommerce.
An outdated template doesn’t necessarily mean something is broken, but it can cause compatibility issues with product pages, cart functionality, or checkout.

What should you check?

Open WooCommerce → Status → System Status and scroll to the Templates section. You’ll see which template files your theme overrides and whether WooCommerce reports them as outdated.

WooCommerce System Status showing outdated meta.php and tabs.php template overrides in the Total theme.
If an update is available for your theme, review its changelog to see whether it addresses the affected templates.
For customized templates, updating is more involved. A developer may need to compare the existing override with the current WooCommerce template, incorporate relevant changes, and preserve any custom functionality.

Don’t simply replace customized template files with new ones. Doing so can remove modifications your store depends on. Test the updated templates before deploying them to your live store.

8. Blurry or Incorrect WooCommerce Product Images

Product images may look sharp in the WordPress Media Library but appear blurry, stretched, or incorrectly cropped on your WooCommerce storefront.
This usually happens when the image displayed by your theme doesn’t match the available image dimensions or cropping settings.
To identify the issue, check three things:

1. Original image quality: Open the image in Media Library and inspect its dimensions. WooCommerce recommends images of at least 800 × 800 pixels for most product displays, although larger layouts may require higher resolution.

2. Theme image settings: Check Appearance → Customize → WooCommerce → Product Images, if your theme provides these controls. Make sure the image width and cropping settings match your product layout.

3. Generated thumbnails: If you’ve changed themes or image sizes, go to WooCommerce → Status → Tools and use Regenerate shop thumbnails to recreate the required image sizes.

If the images remain blurry, inspect whether the theme is stretching a smaller image beyond its natural resolution. Regenerating thumbnails cannot restore detail that was missing from the original upload.

9. WooCommerce White Screen of Death (WSOD)

The White Screen of Death (WSOD) occurs when your WordPress or WooCommerce site displays a blank page instead of loading normally. It can result from a PHP fatal error, an incompatible plugin or theme, or exhausted server resources.
Rather than immediately disabling plugins or increasing memory limits, start by finding the error.

Where to look first:

1. WordPress recovery email: Check the site’s administrator inbox for a technical issue notification. If WordPress detected a fatal error, the email may identify the affected plugin or theme and provide a recovery link.

2. WooCommerce fatal-error logs: If you can access your dashboard, open WooCommerce → Status → Logs and look for a fatal-errors log. Check the timestamp, error message, and referenced file.

3. Hosting error logs: If the WordPress dashboard is inaccessible, use your hosting control panel to inspect PHP error logs or ask your hosting provider to retrieve the relevant entries.

A memory-related error may require adjusting server resources, while a fatal error referencing a plugin or theme calls for a different investigation.
Avoid disabling essential WooCommerce components on your live store without understanding the impact. If the error prevents access to your dashboard, recovery may require hosting-level or file-level intervention.

10. WooCommerce 500 Internal Server Error

A 500 Internal Server Error means the server couldn’t complete a request. In WooCommerce, it may affect your entire storefront or appear only when customers add products to their cart, update checkout details, or place an order.
Unlike a specific PHP error message, an HTTP 500 response doesn’t tell you what went wrong. The underlying cause could be a server configuration issue, a PHP error, or a problem with a plugin or custom code.

To narrow down the cause:

1. Identify the affected request. Does the error appear across the entire store or only during a specific action? A 500 response during checkout may point to a failed server-side request rather than a problem with the whole website.

2. Check server error logs. Look for entries matching the time and URL of the failed request. Your hosting provider can help retrieve these logs if you don’t have direct access.

3. Review recent server changes. If the error began after changes to PHP settings, server configuration, or .htaccess rules, investigate those changes before modifying anything else.

If the logs identify a specific plugin, PHP function, or server configuration issue, address that cause rather than applying unrelated fixes.
For persistent errors that interrupt checkout or prevent access to your store, contact your hosting provider or a WooCommerce developer with the affected URL, error timestamp, and relevant log entries.

When to Get Professional WooCommerce Support

Not every WooCommerce issue requires a developer. Incorrect shipping settings or image dimensions may be straightforward to fix, especially when the cause is clear.
However, some problems are best handled by someone who can investigate the underlying code, server logs, or payment integrations.
Consider professional WooCommerce support when:
  • Customers cannot complete purchases. Checkout failures or unavailable payment methods are affecting transactions.
  • Payments and orders don’t match. A payment succeeds, but the corresponding WooCommerce order remains pending or failed.
  • An issue keeps returning. A temporary fix works, but the same problem reappears after an update or configuration change.
  • Troubleshooting requires code or server changes. The problem involves PHP errors, custom integrations, or modifications that could disrupt your live store.

If you’ve identified a problem but aren’t confident about making the necessary changes, Kiwistic offers WooCommerce support for investigating and resolving store issues.

You don’t need to know the technical cause before requesting help. A description of the symptoms, affected pages, and when the issue started is a useful starting point.

How to Prevent Recurring WooCommerce Problems

Fixing a WooCommerce issue is only part of keeping an online store reliable. Updates, new extensions, and configuration changes can introduce problems even after everything appears to be working.
A practical maintenance routine should include:
  • Controlled updates: Test significant WooCommerce, theme, and plugin updates on staging before applying them to your live store.
  • Regular backups: Keep recoverable copies of your files and database, and verify that your backup process works.
  • Checkout testing: After updates, confirm that customers can add products to their cart, complete a test purchase, and receive the expected emails.
  • Error monitoring: Review recurring errors and failed scheduled actions before they affect important store operations.

These checks won’t prevent every technical issue, but they can help you identify problems earlier and reduce the risk of unexpected disruptions.

For businesses that need ongoing help with updates, backups, and technical maintenance, explore Kiwistic’s WordPress maintenance plans.

Conclusion

WooCommerce problems are easier to resolve when you understand what’s failing before making changes. Whether you’re dealing with checkout errors, missing order emails, or outdated templates, the right troubleshooting approach starts with identifying the symptoms and checking the relevant settings or logs.
Some issues can be resolved with a simple configuration change. Others require investigating payment integrations, plugin compatibility, or server errors.
If your store is experiencing a persistent technical issue, Kiwistic WooCommerce Support can help you investigate the problem and determine the next steps.

FAQ

How much does professional WooCommerce support cost?

The cost depends on the problem and the type of assistance required. A straightforward configuration issue may be handled as a one-time fix, while recurring errors, custom code, or complex payment integrations may require more extensive support. For ongoing technical assistance, some providers offer monthly maintenance plans with defined services and support hours.

Can I get official support from WooCommerce.com?

WooCommerce provides documentation and support for its products, including eligible extensions purchased through WooCommerce.com. However, support for third-party plugins, custom code, hosting configurations, and theme-specific issues may fall outside its scope. If the problem involves a third-party extension, start with its developer. For issues affecting multiple components of your store, independent WooCommerce technical support may be more appropriate.

What's included in a WooCommerce maintenance plan?

Coverage varies by provider, but maintenance plans commonly include software updates, backups, security checks, and technical monitoring. Before choosing a plan, confirm whether it covers WooCommerce-specific tasks such as checkout testing, payment gateway troubleshooting, and compatibility issues. These services aren’t automatically included in every WordPress maintenance package.

Ognjen Velickovic

WordPress Developer & Product Manager at Kiwistic. I build and maintain WordPress sites for small businesses and troubleshoot everything from login lockouts to security issues. These guides come from real experience, so you don't have to figure it out alone.

You May Also Like…