A broken checkout is the worst kind of WordPress problem, because it costs you money by the hour. Customers fill their cart, reach the last step, and then the button spins forever, an error flashes up, or the payment options simply aren’t there. Most of them won’t email you about it. They’ll just leave.
In most cases the cause is a plugin: an update that went wrong, two plugins that don’t get along, or an optimisation setting that’s a little too clever. Here’s how to find it, in order of what’s quickest to check.
Pin down exactly what goes wrong
“Checkout is broken” can mean a lot of things. Try a test order yourself and note what you see:
- The Place order button spins and never finishes.
- An error message appears, such as “There was an error processing your order”.
- The page loads, but payment methods are missing, or shipping options never appear.
- Fields are missing, or the address fields won’t update the totals.
- The payment goes through, but the customer never reaches the thank-you page, or no order shows up in your admin.
Also try it logged in and logged out (a private window is easiest), and on a phone. If it only breaks for guests, or only on mobile, that’s an important clue. Write down the exact steps, because you’ll repeat them many times.
Use your payment provider’s test or sandbox mode for this, so you’re not charging your own card over and over.
Check these first
Caching
Cart and checkout pages must never be cached. WooCommerce tells most caching plugins this automatically, but host-level caches and CDNs don’t always listen. If customers see someone else’s cart, or the checkout shows old totals, check your caching plugin and ask your host to exclude /cart/, /checkout/ and /my-account/.
Script optimisation
This is the most common cause we see. Performance plugins that combine, defer or delay JavaScript can break the scripts that update totals and submit the order. Turn those options off, clear the cache, and try again. If that fixes it, you don’t have to give up the optimisation. Most of these plugins let you exclude WooCommerce’s scripts, or exclude the checkout page entirely.
The browser console
Press F12, open the Console tab and try to place an order. A red error here often names the culprit. If the error mentions a file in /wp-content/plugins/some-plugin/, that plugin is your first suspect. The Network tab is useful too: look for a request containing wc-ajax=checkout and see whether it returns an error.
WooCommerce’s own logs
Go to WooCommerce → Status → Logs. Look for logs named fatal-errors and for logs from your payment gateway. A PHP error during checkout usually ends up here, with a file path that points straight at the plugin involved.
Recent changes
Did you update WooCommerce, your payment plugin, or anything else in the last few days? Did you add a plugin that touches checkout, like a field editor, a coupon tool or a shipping calculator? Start there.
Checkout block or classic checkout?
Newer shops use the Checkout block, while older ones use the classic [woocommerce_checkout] shortcode. Some extensions, especially older payment gateways and checkout field editors, only work with the classic version. On the block checkout they might show nothing at all.
Open your checkout page in the editor and see which one you have. WooCommerce often shows a notice there when an active extension doesn’t support the block. If one does, either update that extension, or switch the page back to the classic shortcode until it catches up.
Find the plugin by testing
If none of the quick checks found it, test your plugins. Switch them off in halves, keeping WooCommerce and your payment plugin on, and check the checkout after each change. Keep halving whichever group the problem is in. Our guide on finding which plugin is breaking your site explains the method step by step.
The trouble is doing this on a live shop. Every plugin you switch off from the Plugins screen is off for your customers as well, mid-order.
Culprit Finder runs the same search in your browser only. Customers keep the full shop the whole time. Before you start, tick WooCommerce and your payment gateway under keep plugins on, so they stay on in every step and the problem doesn’t disappear for the wrong reason. Then place a test order at each step and answer whether the problem is still there. If two plugins only break the checkout together, it keeps going until it names both.
One limit to know about: troubleshooting plugins only change things for the logged-in admin running the test. If your checkout only breaks for guests, you won’t be able to reproduce it while logged in. In that case, test on a staging copy of your shop, where switching plugins off for everyone is harmless.
When you’ve found it
- Update it. Check whether a newer version is out, and read its changelog for checkout fixes.
- Contact the author. Include your WooCommerce version, whether you use the block or classic checkout, the console or log error, and the other plugin involved if it’s a conflict. WooCommerce’s Status → Get system report gives them everything else in one paste.
- Keep selling in the meantime. If the culprit isn’t essential, switch it off until there’s a fix. If it’s your payment gateway, consider enabling a second payment method temporarily so customers can still pay.
Stop it happening again
- Update plugins on a staging site first, and place a test order before updating the live shop.
- Don’t update everything at once on a Friday evening.
- Place a quick test order yourself after every round of updates. It takes two minutes, and it’s the cheapest insurance a shop can have.