WooCommerce checkout broken

Updated 11 October 2026

Short answer

Place a test order using your payment gateway's test mode and watch where it fails: the checkout page loading, the "Place order" button, or payment. A checkout that spins forever or won't submit is usually a JavaScript error from a plugin or theme conflict, or page caching serving a stale checkout. Errors at payment point to the payment gateway's settings.

What's the problem

The checkout page won't load, "Place order" spins forever, fields are missing, customers see errors, or orders aren't coming through.

Why it happens

  • A plugin or theme conflict, often causing a JavaScript error on the checkout page.
  • Page caching applied to checkout, so customers get stale or broken pages.
  • Payment gateway settings: wrong keys, test mode, or a disconnected account. See WooCommerce payment failed.
  • No shipping methods for the customer's address.
  • Outdated templates in your theme overriding the checkout.
  • Security tools (a firewall or bot protection) blocking the checkout's background requests.

How to fix it

  1. Turn on your gateway's test mode and place a test order to see where it fails.
  2. Open the browser console (F12) on the checkout page. A red error naming a plugin or theme file points to the conflict.
  3. Exclude cart, checkout and account pages from caching, including Cloudflare and any caching plugin.
  4. Check WooCommerce → Status → System Status for outdated templates.
  5. Conflict-test: default theme first, then disable plugins one at a time.
  6. Check firewall logs for blocked checkout requests.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows your WordPress version and plugins against the latest releases; whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when; which requests the firewall blocked, by Cloudflare's own rule names. It doesn't place orders or see your payment gateway, so check WooCommerce > Status and your gateway's logs too.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. WooCommerce: WooCommerce self-service guideofficial docsMost issues are caused by: Outdated software on your site Conflict with your theme Conflict with another plugin
  2. WooCommerce: WooPayments: Startup Guideofficial docsTest mode lets you simulate transactions using test card numbers so that you can ensure your checkout process is working as expected.

Related

WooCommerce payment failed Find out whether the payment provider declined it or your site failed to send it. The order notes and the gateway's own dashboard say which. WooCommerce not working WooCommerce says most problems come from outdated software or a conflict with your theme or another plugin. Update, then conflict-test to find which. Checkout broken Place a test order and see where it stops. Failed payments are usually provider keys, test mode or webhooks; a frozen checkout is usually a script error. JavaScript error Open the browser console (F12). The red error names the problem, the file and the line. That's the starting point for every JavaScript error.

Preventionlabs is independent and not affiliated with WooCommerce. Product names are used only to describe the problem.

← All of WooCommerce