10 WooCommerce problems and how to diagnose them

WooCommerce problems can originate in the server, theme, an extension, configuration or an external connection. Solving them requires reproducing the fault and isolating its cause. Random setting changes or disabling plugins on the live store may add a second incident to the first.

Before intervening, save a recoverable backup and prepare a test environment where changes could affect orders or payments. Record the time, product, account and steps causing the error. The official conflict-testing guide is a useful reference for organising diagnosis.

1. Checkout does not complete or keeps loading

Check whether the browser reports a JavaScript error or an unfinished request. Repeat the journey using the same product, address and payment method because these may trigger different rules. Compare behaviour signed in and signed out.

In testing, investigate conflicts between the theme, checkout extensions, optimisation and gateway. A captured payment that fails to update the order differs from a form that never sends its request. Do not repeat real charges as a test.

2. Payment is captured but the order remains pending

Find the transaction with the payment provider and compare it with the order identifier and notes. Review gateway logs and notifications. Failed communication can leave different statuses in the provider and WooCommerce.

Do not mark all orders paid or charge them again as a general rule. Document the case and define reconciliation between transaction and order. Event records should explain what each system received.

3. The store breaks after an update

Connect the timing of the fault with published changes: WooCommerce, WordPress, PHP, theme and extension versions. Check requirements and compatibility on a store copy. If a rollback plan exists, apply it carefully to avoid losing recent orders.

Restoring an old database on a store that continues selling can erase new transactions. Test backup and recovery before a major update, with a process to reconcile data arriving afterwards.

4. A 500 error or blank screen

A 500 error is a server response, not a diagnosis. Request logs for the relevant interval and inspect the specific error: memory, PHP compatibility, files, permissions or code. Do not increase limits indefinitely without locating the operation exhausting them.

Avoid displaying traces, paths and sensitive data to visitors while investigating. Share logs privately with the provider responsible for the incident.

5. Pages or products return 404

Check whether the URL changed, the product remains published and permalinks and endpoints are configured correctly. WooCommerce documents specific checks for pages that do not display.

If a path has been removed, decide whether an equivalent destination exists. Do not turn every 404 into a homepage redirect. After correcting the issue, update internal links to the old destination.

6. The website loads slowly

Separate server response time, asset downloading and browser work. An oversized image and a slow query need different remedies. Measure home, category, product and checkout pages, including mobile and sessions with a cart.

Plugin count does not explain performance by itself: what plugins execute, where and with which data matters. One extension may generate expensive requests. Test changes separately and retain previous measurements for comparison.

7. Incorrect stock or sales of sold-out products

Identify which system owns stock: WooCommerce, an ERP, a warehouse or another channel. Check SKUs, variations, reservations and synchronisation timing. Two tools writing the same data can undo one another's updates.

Test an order, cancellation and return. Verify when stock is deducted or restored and how the same event is prevented from being processed twice. Increasing connector frequency does not correct an incorrect mapping.

8. Taxes or shipping differ from expectations

Reproduce the case with its country, province, postcode, customer type and product. Check whether prices are entered including tax and which address determines the calculation. For shipping, review zones, classes, weights and extension rules.

Use expected test cases validated by whoever handles tax or logistics. Technical diagnosis should check those rules rather than improvise tax criteria.

9. Emails do not arrive

First check whether the event generating the email occurred and its task was processed. Then review the sending service, domain authentication and destination. An order's existence does not prove its notification was sent or reached the inbox.

Use a controlled test address and consult delivery logs. Avoid testing with the customer database or resending notifications in bulk to check configuration.

10. Blurred images or a broken layout

Compare the original file with the served size and onscreen space. Review crops, thumbnails and theme changes. If the problem appeared after combining or minifying assets, disable that optimisation in testing to isolate it.

Uploading huge files is not the only answer to poor sharpness. You need a sufficient source for the displayed size and responsive versions, without downloading more pixels than visitors can see.

When to fix WooCommerce and when to consider migration

If the fault has a limited cause and the rest of operations works, fixing it usually makes sense. If dependencies recur that the team can no longer maintain and critical functions demonstrably fit another platform, investigate that alternative with a complete scope.

A WooCommerce to Shopify migration should evaluate data, integrations, design and SEO. Shopify changes some technical responsibilities, but does not eliminate a poorly structured catalogue or uncontrolled integration.

Further reading for your store

• Investigating slow WordPress performance
• Real differences between WordPress and Shopify
• Migrating WooCommerce data and SEO to Shopify

Sources and review

• WooCommerce: conflict testing
• WooCommerce: pages not displaying
• WooCommerce: troubleshooting orders
• Migrating from WooCommerce: data and limitations

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.