An update broke your WooCommerce checkout. Here is how to get selling again.

A broken checkout is the most expensive failure a WordPress site can have, because it is silent. The site looks fine. Traffic arrives. Nothing sells, and you often find out from a customer rather than from your own monitoring.

If you are in this right now, work top to bottom.

Get selling again first, diagnose second

Roll back. If you know which update ran, reverse it. Most decent hosts keep a restore point from the last 24 hours, and plugins like WP Rollback will revert a single plugin to its previous version. Restoring the whole site risks losing orders placed since the backup, so prefer reversing the one plugin.

If you cannot roll back, deactivate. Turn off the plugin that updated most recently and test checkout. On a live shop this is not elegant, but a shop missing a feature sells more than a shop that cannot take payment.

Then tell people. A banner saying "checkout is briefly unavailable, we will be back within the hour" loses far fewer customers than a checkout that silently fails.

Find what actually broke

Checkout failures cluster into a handful of causes.

A payment gateway conflict. The most common. Gateway plugins hook deeply into the checkout flow and break when WooCommerce changes it. Check whether your gateway has an update of its own waiting — usually it does, released days after the WooCommerce one.

A JavaScript error. Open checkout, open the browser console, and look for red. A single JS error stops the place order button doing anything at all, with no server-side error to find in the logs.

A PHP fatal error. Turn on WP_DEBUG_LOG (logging to file, not displayed on screen) and try checkout again. The log will name the file and line, which usually names the plugin.

A theme template override. If your theme has customised WooCommerce templates, a WooCommerce update can leave them outdated. WooCommerce → Status flags these — look for templates marked as out of date.

Caching. Checkout, cart and account pages must never be cached. A caching plugin that updated and reset its exclusions will break checkout in ways that look random, and often only for logged-out visitors.

Test it properly before declaring victory

Do not just load the checkout page. Place a real order, end to end:

• Add to cart, apply a coupon, change quantity
• Complete checkout with each payment method you offer
• Confirm the order appears in WooCommerce with the right status
• Confirm the customer email and the admin notification both arrive
• Repeat on a phone — mobile checkout breaks separately and more often
• Check with a logged-out browser as well as a logged-in one

Use your gateway's test mode, or place a small real order and refund it. A real order is the only test that proves the whole chain.

Stop it happening again

WooCommerce updates break things more often than WordPress core does, because there are more moving parts and more third-party code sitting in the checkout path. Three habits prevent nearly all of it.

Update on staging first. Never update a shop directly on live. Copy to staging, update, place a test order, then push. This one habit prevents most of these incidents outright.

Update the gateway at the same time. When WooCommerce releases a significant update, payment gateway updates usually follow within days. Do them together, not weeks apart.

Freeze during peak. Do not update anything in the week before Black Friday, or during your own busy season. The risk is asymmetric — a small improvement against a lost trading day.

If this keeps happening

A shop that breaks after updates usually has an underlying cause: an outdated theme with template overrides, a gateway plugin that is no longer maintained, or too many plugins touching the checkout.

Our WooCommerce care add-on covers exactly this — staging-first updates, checkout and payment tested after every one, and freeze windows during your busy season. It is $59 a month on top of a care plan, which is less than one lost trading afternoon.