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

Troubleshooting · Troubleshooting

How to Fix a Broken WooCommerce Checkout in WordPress

Short answer

A broken WooCommerce checkout is usually caused by a cached checkout page, a plugin or theme conflict, an incompatible payment gateway, or a shipping setup with no matching rate. Find which checkout you use, check the logs, exclude checkout from caching, and run a conflict test. Fix the cause the symptom points to, then place a test order.

Key takeaways

  • Block and classic checkout fail in different ways, so find which one the store uses before fixing anything.
  • A gateway that does not support the Checkout block will not appear as a payment option.
  • A cached checkout page can carry a stale security token, so the order request fails.
  • The fatal-errors log under WooCommerce > Status > Logs names the PHP error behind a blank checkout.
  • Shipping options only appear when a zone and rate match the exact address entered.

What does a broken WooCommerce checkout mean?

It means shoppers can fill in the checkout form but cannot finish the order, because the page, the order request, or the payment step fails.

The symptom matters more than the label. A blank page, a spinning place order button, a missing payment method, and an error after placing the order each point to a different part of the store. Match the symptom first, then fix that part.

WooCommerce's cart and checkout guide says the Checkout block brings together the address forms, shipping, payment and order review in one container, so a failure in any inner part can stop the whole page (Customizing the Cart and Checkout Pages).

Which checkout does your store use?

Check first, because block and classic checkout fail in different ways and need different fixes.

Open the checkout page in the editor. A Checkout block means the store uses block checkout. A Shortcode block holding [woocommerce_checkout] means classic checkout.

Stores started after WooCommerce 8.3, released in November 2023, use the Cart and Checkout blocks by default, while older stores often still use the shortcode version (Customizing the Cart and Checkout Pages). Do not switch types as a first fix, because extensions may support only one of them.

WooCommerce's cart and checkout guide warns that the two work as a pair, so if you revert one to the classic version, revert the other too (Customizing the Cart and Checkout Pages).

SymptomLikely causeFirst check
Place order spins foreverJavaScript error or failed order requestBrowser console and Network tab
No payment methods shownIncompatible gateway or no gateway set upPayment settings and block warnings
“There was an error processing your order”Server error during order creationWooCommerce > Status > Logs
Shipping options missingNo shipping zone or rate matches the addressShipping zones for that country
Checkout page is blankFatal error or cached bad pageLogs, then cache exclusions
Totals do not updateCached checkout or script conflictCache rules, then conflict test

How do you read the browser console and logs?

Open the checkout page, press F12, and look at the Console tab for red errors and the Network tab for failed requests.

A red JavaScript error names the file that failed, which usually names the plugin or theme behind it. In the Network tab, filter by wc-ajax on classic checkout and watch the checkout request when you click Place order. A 500 status means a PHP error on the server.

Then open WooCommerce > Status > Logs and read the most recent fatal-errors log. WooCommerce keeps a fatal-errors log automatically, and it records PHP errors that stop a page from loading. Match the time in the log to the time the checkout failed.

WooCommerce's update guide says to check the store after updates by placing a test order and reviewing shipping, tax, payment and email behavior, which is the same set of checks to run after any checkout fix (How to update WooCommerce).

Why are there no payment methods at checkout?

The store has no payment gateway that WooCommerce can offer for this order, often because the gateway is not compatible with the checkout type.

WooCommerce's cart and checkout guide says an incompatible payment gateway may not appear as a payment option on the block checkout, and the editor shows a warning naming the extension (Customizing the Cart and Checkout Pages).

If only incompatible gateways are active, no payment methods show at all, and a warning appears on the checkout page.

Open WooCommerce > Settings > Payments and confirm at least one gateway is enabled and set up. Then open the checkout page in the editor and read the warning in the Payment Options block, which can name the gateway that does not support blocks.

If the gateway supports only classic checkout, switch the checkout page back to the shortcode version. The guide explains the change in the block toolbar: select the Checkout block, choose Transform, then Classic Shortcode (Customizing the Cart and Checkout Pages).

How do you exclude checkout from caching?

Exclude the Cart, Checkout and My Account pages from page caching in every layer: the caching plugin, the host cache, and the CDN.

WooCommerce's performance guide says dynamic content such as cart and checkout pages must remain uncached, because a stored copy cannot carry one shopper's order data (How to optimize performance for WooCommerce stores). A cached checkout page can also carry a stale security token, so the order request fails.

  1. In the caching plugin, add /cart/, /checkout/ and /my-account/ to the never-cache list.
  2. Turn off JavaScript delay, defer and combine rules for the checkout page, or exclude WooCommerce scripts from them.
  3. Ask the host to apply the same exclusions to server-level caching.
  4. Purge every cache and place a test order.

WooCommerce's performance guide names WP Rocket, W3 Total Cache and WP Super Cache as caching plugins, and notes that some include built-in WooCommerce support (How to optimize performance for WooCommerce stores).

How do you run a conflict test for checkout?

Test on a staging copy with a default theme and only WooCommerce active, then add plugins back one at a time until checkout breaks again.

WooCommerce's conflict guide gives the order: update all plugins and themes first, switch to a default theme such as Twenty Twenty-Five or Storefront, then deactivate all plugins except WooCommerce (How to test for plugin and theme conflicts).

If checkout works in that clean state, reactivate plugins one at a time and place a test order after each one.

Use the Health Check & Troubleshooting plugin when there is no staging copy. It limits the changes to your own session, so shoppers keep seeing the normal store. The plugin is free on WordPress.org (Health Check & Troubleshooting).

The full isolation method is covered in How to Fix Plugin Conflicts in WordPress.

Why do shipping options not appear at checkout?

No shipping zone or rate matches the address the shopper entered, so WooCommerce has nothing to offer.

Open WooCommerce > Settings > Shipping and check the zones. A zone only applies to the countries and regions listed in it, and a rate only applies inside its own zone. Test with the exact country, state and postcode the shopper used.

The settings screen itself is explained in How Do WooCommerce Settings Work?. If the address is outside every zone, add a zone for it or add a rate to the zone that covers it.

WooCommerce's update guide lists shipping, tax, payment and email as the behaviors to check after any update, because a missed zone or rate often appears right after a change (How to update WooCommerce).

What if checkout broke right after an update?

An update changed WooCommerce, a plugin, the theme, or the PHP version, and one of those changes no longer fits the rest of the store.

Write down what changed and when. WooCommerce's update guide says to test updates on staging first and to set the live site to Coming soon mode during the update window, so a store that skipped staging has no safe copy to compare against (How to update WooCommerce).

Check the System Status report for outdated template warnings. The report is explained in How Do You Read the WooCommerce Status Report?. Then read the fatal-errors log for the first error after the update time.

The safe way to update next time is covered in How to Update WooCommerce Safely. WooCommerce 11.3.1 was released on 19 November 2026, and its changelog lists checkout fixes, so check whether a newer release already addresses the fault (WooCommerce).

How do you confirm checkout works again?

Place a full test order as a logged-out shopper, from the product page through to the order confirmation screen.

  • The cart keeps its items all the way to checkout.
  • Shipping and tax update when the address changes.
  • A payment method appears and the place order button completes.
  • The order appears in WooCommerce > Orders with the right status.
  • The order email arrives, or the email log shows it was sent.

Use a gateway test mode on staging, or a low-value real product you can refund. Never leave a live store in test mode, because real customers would be told their order went through when no money moved.

If orders pile up with past-due background jobs after the fix, the steps in How to Fix Past-Due Actions in the WooCommerce Action Scheduler clear the backlog.

What mistakes should you avoid?

Do not test fixes on the live checkout during busy hours, do not switch checkout types to dodge a warning, and do not leave the store in gateway test mode.

  • Testing on live checkout risks real orders failing while you work.
  • Switching from blocks to classic checkout, or back, can break extensions that support only one type.
  • Leaving test mode on means orders that look paid never take money.
  • Clearing caches once and never retesting leaves a stale checkout page in place.

WooCommerce's server recommendations ask for WordPress 6.9 or newer and PHP 8.3 or newer, tested up to PHP 8.4, so a store on old PHP can fail checkout in ways no plugin fix will cure (WooCommerce Server Recommendations).

The PHP project lists security fixes for PHP 8.3 until 31 December 2027 and for PHP 8.4 until 31 December 2028 (Supported Versions).

Frequently asked questions

Why does the place order button spin forever?

A spinning place order button usually means the order request failed in the background. Open the browser Network tab, filter by wc-ajax on classic checkout, and read the status of the checkout request. A 500 status points to a PHP error, which the fatal-errors log under WooCommerce > Status > Logs should name.

Can a payment gateway be incompatible with block checkout?

No. A gateway that does not support the Checkout block will not appear as a payment option, and if it is the only gateway active, checkout shows no payment methods at all. Either use a gateway that supports blocks, or switch the checkout page back to the classic shortcode version.

Why are there no shipping options at my WooCommerce checkout?

Open WooCommerce > Settings > Shipping and test with the exact address the shopper entered. A zone only covers the countries and regions listed in it, so an address outside every zone gets no rates. Add a zone for that address or add a rate to the zone that covers it.

Can caching break WooCommerce checkout?

It can, because a cached checkout page can carry a stale security token and old totals. Exclude the cart, checkout and account pages from every cache layer, including the host cache and the CDN, then purge all caches and place a test order to confirm the fix.

Why is my WooCommerce checkout page blank?

A blank checkout page usually means a fatal PHP error. Open WooCommerce > Status > Logs and read the latest fatal-errors log, which names the file and line. Then switch to a default theme and deactivate other plugins to find whether the theme or a plugin causes it.

Sources

  1. Customizing the Cart and Checkout Pages WooCommerce
  2. How to test for plugin and theme conflicts WooCommerce
  3. How to optimize performance for WooCommerce stores WooCommerce Developer Docs
  4. How to update WooCommerce WooCommerce
  5. WooCommerce Server Recommendations WooCommerce
  6. Health Check & Troubleshooting WordPress.org
  7. Supported Versions PHP

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

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test