BLOG / PRACTICAL RESOURCE

WooCommerce troubleshooting checklist

A repeatable diagnostic workflow for product filters, slow checkouts and unexpected storefront behavior.

This checklist is intended for website owners and developers who need to identify a problem before changing settings. It is not a promise that every error has the same cause. Different themes, payment gateways and caching layers behave differently, so document your environment and test carefully.

Before you begin: Make a verified backup, use a staging copy when possible, and avoid collecting or sharing customer payment information in troubleshooting logs.

1. Record the problem before changing settings

Write down the affected URL, product SKU, browser, device, currency, customer role and steps needed to reproduce the issue. Capture the actual result and the expected result.

Confirm whether the issue occurs when signed out
Try a private browser window and a second device
Record the exact product or cart where it happens

2. Check product data and filter behavior

A filter can only be as accurate as the product attributes and taxonomies it queries. For dependent filters, verify that the available options change based on the selected category without silently selecting an unrelated value.

Review the product category and visible attributes in WooCommerce
Check whether attributes are global taxonomies or custom product attributes
Test one filter at a time and then in combination
Confirm that clearing filters resets both the UI and the URL

3. Check checkout without risking live orders

Dynamic checkout fields depend on customer sessions, payment-provider scripts, shipping calculations and cart updates. Test payment behavior in the gateway sandbox or a staging store—not with real customer card details.

Confirm checkout and cart routes are excluded from full-page caching
Inspect the browser console for script errors
Look for duplicate payment SDK or gateway scripts
Check shipping and tax recalculations when country or address changes

4. Isolate cache and plugin conflicts safely

When a page works correctly without an optimization feature, identify the specific rule causing the regression. Avoid disabling all security or caching controls permanently.

Create a current backup and use staging
Purge cache after reproducing and document whether it changes the result
Temporarily disable one optimization setting at a time in staging
Keep a change log and revert unsuccessful experiments

5. Verify the fix and monitor

A change is not complete when only one test passes. Check fresh and returning visitors, mobile navigation, product variations, cart totals and any currency or wholesale pricing rules affected.

Retest the original reproduction steps
Test an unrelated product and a different device
Verify the customer can proceed without an unexpected reload
Record what changed, how it was tested and how to roll it back

How to share a useful support report

Include the affected URL and SKU, your steps to reproduce, a short description of the expected and actual results, whether the issue affects logged-out users, recent site changes and a screenshot with personal information removed. Do not share passwords, access tokens or private payment information.

Let's bring your ideas to life.

Thoughtful design for your next chapter.

Start a Project ↗