Your customers add products to the cart, click Checkout, and nothing happens. Or the page loads, but the button does not respond, the payment methods are missing, or an error appears.
A broken checkout is the most costly problem that an online store can have, because every minute without orders is lost income. The first reaction is often to switch plugins: a new payment plugin, a new checkout plugin, even a new theme. This is rarely the fastest way to a fix, and it can add new problems.
Most checkout failures come from a short list of causes: a mismatch between the checkout block and the shortcode, an old cache, an incompatible extension, a payment gateway setting, or a script error. You can check each one in minutes, and fix the real cause without replacing anything.
In this guide, we’ll go through 10 things to check before you change any plugin. We’ll follow a safe order, from the quick checks to the deeper ones, and explain what each result means.
Before You Start
A store is a live system with real orders, so take care.
- Take a full backup of your files and database. Orders are saved in the database, so a restore can remove recent ones. If you plan to restore, export recent orders first.
- Work on a staging site if you can, and copy the live settings.
- Do not turn off plugins on a busy live store without a plan. Choose a quiet hour, and consider maintenance mode.
- Test with a real product, and with a payment method in test mode if your gateway offers one.
- Note the exact problem: what you click, what you see, and any message.
Use a backup tool that includes your database, and test that you can restore it.
Find the Symptom First
| Symptom | Likely area | Check first |
|---|---|---|
| Checkout page is blank or shows a shortcode as text | Page setup or editor | Check 1 and 2 |
| Place order button does nothing | JavaScript or a conflict | Check 5 and 6 |
| No payment methods shown | Gateway or block compatibility | Check 3 and 4 |
| Error on submit | Gateway, server, or security rule | Check 4, 7, and 8 |
| Checkout page shows old content or the wrong cart | Caching | Check 5 |
| Page not found on checkout | Permalinks or page settings | Check 1 |
| Order is placed but no email arrives | Email delivery | Check 9 |
| Checkout is slow | Server, scripts, or extensions | Check 10 |
Check 1: Are the Cart and Checkout Pages Set Up Correctly?
WooCommerce needs pages for the cart, the checkout, and the account. The official documentation on pages not displaying lists the common causes: a missing or unassigned page, outdated permalinks, a cache, and conflicts.
- Go to WooCommerce, then Settings, then Advanced, and open the Page setup section.
- Check that the Cart, Checkout, and My Account pages are assigned, and that each exists.
- Open each page in the editor. It should contain the Cart or Checkout block, or the matching shortcode.
- If a page is missing, create a new one, add the block or shortcode, publish it, and assign it in the settings.
- Go to Settings, then Permalinks, and click Save Changes, without changing anything. This refreshes the rules and fixes many 404 errors.
Check 2: Blocks or Shortcodes: Do You Have a Mismatch?
WooCommerce has two ways to build the cart and checkout. According to its documentation on customizing the cart and checkout pages, blocks are the modern experience, and shortcodes are the classic experience. Stores started after WooCommerce 8.3 use blocks by default, and older stores may still use shortcodes.
A problem arises when your pages, your theme, your extensions, and your settings do not agree.
- A page may have the classic shortcode while a plugin expects the block.
- An extension that adds fields through hooks may not work with the checkout block.
- A theme or page builder may not support the block version.
How to switch to the classic shortcode
The documentation gives these steps.
- Open the Cart or Checkout page for editing.
- Open the List View, and select the Cart or Checkout block.
- Use the Transform button in the block toolbar, and choose Classic Shortcode.
- Save the page.
- Repeat for the other page, since the two work together.
To go back to blocks, use the same Transform option on the classic placeholder.
If the classic checkout works and the block does not, you have found the cause, and the next step is to find the extension that does not support blocks.
Check 3: Is an Extension Incompatible With the Checkout Block?
The documentation says that most extensions work, but that an incompatible extension can cause unexpected behavior. If an active extension has declared itself incompatible, the editor shows a warning and an option to switch to the classic checkout.
- An incompatible payment gateway may not appear as a payment option.
- If only incompatible gateways are active, customers see a message that no payment methods are available.
- Extensions that add custom fields through hooks often need an update to support blocks.
What to do
- Open the checkout page in the editor, and look for a compatibility warning.
- Check each checkout-related extension’s changelog and description for block support.
- Update the extension, or contact its developer.
- If there is no fix, switch to the classic checkout, or replace that one extension.
Check 4: Are Your Payment Gateways Enabled and Configured?
If customers see no payment options, or get errors when they pay, check the gateway.
- Go to WooCommerce, then Settings, then Payments.
- Check that each gateway is enabled, and that its settings are complete.
- Check that the keys are correct, and that they match the mode: test keys in test mode, live keys in live mode.
- Check that the store country, currency, and the gateway’s supported countries and currencies match.
- Check the gateway’s own dashboard for errors, blocked payments, or a suspended account.
- Check the order notes on a failed order. They often hold the gateway’s error message.
- Check that your site uses HTTPS, since many gateways require it.
A gateway can also be hidden by shipping or product rules, such as a minimum order amount or a restriction by country.
Check 5: Clear Caches and Exclude Checkout Pages
Cart and checkout pages contain data that belongs to one customer. They must never be cached for everyone.
- Clear your caching plugin’s cache.
- Clear your host’s cache and your CDN cache.
- Check that the cart, checkout, and account pages are excluded from page caching.
- Check that the cookies that WooCommerce uses for the cart are not stripped by the cache.
- Turn off script optimization, such as minify, combine, and delay, and test the checkout. Turn the options back on one at a time.
- Test in a private window.
The official guidance also tells you to make sure that cart and checkout pages are excluded from caching, since they hold session data. If you are choosing or tuning a cache, our comparison of LiteSpeed Cache vs WP Rocket explains how to set exclusions.
Check 6: Look for JavaScript Errors
When the place order button does nothing, a script error is a likely cause.
- Open the checkout page, and open your browser’s developer tools.
- Go to the Console tab, and reload.
- Look for red errors. A path with /wp-content/plugins/ names the plugin.
- Click the button, and watch for new errors.
- Open the Network tab, and look for requests that fail with codes such as 403, 404, or 500.
A script error often points to a plugin conflict, or to an optimization setting that broke a script. If you see an error from a plugin, move to Check 7.
Check 7: Test for a Plugin or Theme Conflict
If the cause is still unknown, test for a conflict. The documentation suggests switching to a default theme, then deactivating all plugins except WooCommerce and reactivating them one at a time.
On a live store, this is risky, so use a staging site, or a troubleshooting tool that changes the site only for you. Our guide on how to find which plugin is breaking your site shows each method, including safer ways to test on a live site.
Test in this order:
- Switch to a default theme, and test the checkout.
- Turn off plugins that touch the checkout: custom field plugins, coupon plugins, shipping and tax plugins, security plugins, and optimization plugins.
- Turn them back on one at a time, and test after each.
Check 8: Security Rules and Server Limits
A firewall or a server rule can block checkout requests.
- Check your security plugin’s log for blocked requests at the time of your test.
- Check that your firewall allows the payment gateway’s callback addresses.
- Check that the PHP memory limit is high enough. Many stores need 256 MB or more.
- Check the execution time limit, since a slow payment request can time out.
- Check the PHP error log or turn on the debug log, as described in the WordPress debugging documentation.
- Ask your host if a server rule blocks requests.
Check 9: Emails and Order Status
Sometimes the checkout works, but the customer sees no confirmation, or you do not receive the order email. This is an email problem and not a checkout problem.
- Check that the order appears in WooCommerce, then Orders.
- Check the email settings under WooCommerce, then Settings, then Emails.
- Set up SMTP so that messages leave your server reliably. Our review of WP Mail SMTP explains how.
- Send a test order, and check the inbox and the spam folder.
Check 10: Speed and Session Problems
A slow checkout can look like a broken one.
- Check how long the page takes to load, and how long the order takes to process.
- Remove extensions that run heavy checks on every checkout.
- Check for failing remote calls, such as a tax or shipping service that times out.
- Make sure that the server has enough resources for peak traffic.
- Check that customers have cookies enabled, since the cart depends on them.
When Changing a Plugin Makes Sense
Replacing a plugin is the right step when the evidence points to it.
- The extension is no longer maintained, and has no block support.
- The developer confirms a known bug with no fix.
- A test shows that the problem goes away only when that plugin is off, and no setting fixes it.
- A better-maintained alternative exists, and you have tested it on staging.
When you replace a plugin, do it on staging, test a full order from start to end, take a backup, and then change the live store at a quiet hour.
A Safe Testing Routine for a Live Store
When you cannot use staging, follow a careful routine.
- Pick the quietest hour in your sales data.
- Take a backup, and export recent orders.
- Turn on a maintenance message, if you expect the test to take a while.
- Test one change at a time, and write down each change.
- Use a test product at a low price, or a coupon for a full discount, to run orders through.
- After each change, test the whole path: add to cart, open the cart, open checkout, pick a payment method, and place the order.
- Refund or cancel the test order, and remove the test product.
- Turn the store back on, and check live orders over the next hour.
Do not leave debug mode or test mode on after you finish. A gateway left in test mode accepts no real payments, and debug mode can show errors to customers.
Checkout Fields, Shipping, and Tax Settings
Some checkout failures are not technical. They come from a rule that stops the customer from finishing.
| Setting | What can go wrong | What to check |
|---|---|---|
| Required fields | A field that customers cannot fill, such as a state field for a country without states | Edit the field rules, and test with different countries |
| Shipping zones | No shipping method for the customer’s address | Check zones, methods, and the “locations not covered” setting |
| Tax settings | Tax rates missing, so totals fail or show wrong values | Check tax classes and rates |
| Minimum order or product limits | The cart is below a minimum | Check store and gateway rules |
| Coupons | A coupon rule blocks the order | Test with and without the coupon |
| Account settings | Guest checkout turned off, but account creation fails | Check the account options under Settings |
| Terms checkbox | A terms page is missing, so the box cannot be completed | Check the terms and privacy pages |
| Currency and country | A gateway that does not support the currency | Check gateway rules |
If a customer says that checkout “does nothing”, ask for their country, the products in their cart, and the payment method. These details usually point to a rule.
Custom Templates and Theme Overrides
Many themes override WooCommerce templates to change the look of the cart and checkout. An old override can break a page after a WooCommerce update.
- Go to WooCommerce, then Status, and look at the Templates section. It lists templates that your theme overrides, and whether they are out of date.
- If an override is out of date, update the theme, or remove the override and test with the default template.
- If you use a child theme with custom template files, compare them with the current versions in the plugin.
- A page builder that styles the checkout may also override layouts. Test with the default layout first.
Remember that a block checkout is edited with blocks, not with classic template files. If you use blocks, template overrides for the classic checkout no longer apply.
Reading the WooCommerce Status Report
WooCommerce has a status report that shows your environment, and it helps you and your host to find problems fast.
- Go to WooCommerce, then Status.
- Check the PHP version, memory limit, and time limit.
- Check that the database version and tables are up to date.
- Check the list of active plugins, and the theme, for outdated versions.
- Check the template overrides.
- Check the logs tab for payment errors and fatal errors.
- Copy the report if you need to contact support.
The logs often show the real cause of a payment error, such as a rejected key or a failed callback. Read them before you guess.
Payment Gateway Callbacks and Webhooks
Many gateways confirm payments through a callback, which is a message that the gateway sends to your site. If your site blocks it, the customer pays, but the order stays unpaid.
- Check that your site can receive requests from the gateway. A firewall, a security plugin, or a country block can stop them.
- Check that the webhook address in the gateway’s dashboard matches your site address, including https and the right domain.
- Check the gateway’s webhook log for failed deliveries and read the error.
- If you moved to a new domain or changed to HTTPS, update the webhook address.
- Make sure that a maintenance page does not block the callback.
An order that stays in a pending state after payment is a strong sign of a callback problem, not a checkout problem.
Mobile and Browser Problems
If checkout works for you but not for some customers, test other setups.
- Test on a phone, on mobile data.
- Test in different browsers, such as Chrome, Safari, Firefox, and Edge.
- Test in a private window with no extensions, since ad blockers and privacy tools can block scripts.
- Test as a guest, and as a logged-in customer.
- Check for autofill problems, where a browser fills a field with the wrong value.
- Check that wallet buttons, such as those from payment providers, load correctly.
Ask the customer which browser and device they use. A problem that affects one browser often points to a script or a style problem.
What to Do If the Problem Started After an Update
A checkout that broke after an update has a clear suspect.
- Note which plugin, theme, or WooCommerce update came just before the problem.
- Check the change log for that update.
- Test on staging with the update rolled back.
- If the rollback fixes it, keep the old version until the developer provides a fix, and turn off automatic updates for that plugin.
- Report the problem with your versions and the steps that cause it.
For stores, many owners update on staging first, and then on the live site at a quiet hour. Keep a backup before each update, and test a full order afterward.
Protecting Your Store in the Future
- Keep WooCommerce, your theme, and your extensions updated, after a test on staging.
- Choose payment and checkout extensions that are maintained, and support the block checkout.
- Keep the number of checkout-related plugins low.
- Exclude the cart, checkout, and account pages from caching.
- Set up SMTP, so that order emails are reliable.
- Test a full order each week, and after each change.
- Set up an uptime monitor, and an alert for failed orders if your tools offer it.
- Keep daily backups, and test a restore.
- Write a short note of your checkout settings and your payment gateway keys’ location, so that you can repair quickly.
A Short Checklist
- Back up, and export recent orders.
- Check page setup and permalinks.
- Check for a block and shortcode mismatch.
- Check extension compatibility.
- Check gateway settings, keys, and logs.
- Clear caches, and exclude checkout pages.
- Check the browser console and network requests.
- Test for a conflict on staging.
- Check security rules, server limits, and logs.
- Check email, speed, and sessions.
How to Report a Checkout Problem to Support
If you need help from your host, a plugin developer, or a gateway, a clear report speeds up the answer.
- Say what you expected, and what happened instead.
- Give the exact steps, from the product page to the failure.
- Include the time of the last failed test, and the order number if one exists.
- Include your WordPress, WooCommerce, PHP, theme, and key extension versions.
- Copy any error message, and add a screenshot of the browser console.
- List what you already tried, such as clearing caches or switching to the shortcode.
- Include the gateway’s log entry or webhook error, if you have it.
- Say whether the problem affects all customers, or only some browsers, countries, or payment methods.
A complete report often gets a useful answer on the first reply, and it saves you hours of back and forth.
What Not to Do During a Checkout Emergency
- Do not delete the checkout page and rebuild it without a copy.
- Do not turn off all security with no plan to turn it back on.
- Do not change several settings at once.
- Do not switch payment plugins mid-day, with orders coming in.
- Do not restore an old backup before exporting new orders.
- Do not share live payment keys in public posts or screenshots.
- Do not ignore the problem while you wait. If the fix takes time, post a notice on the store, or offer another way to order.
Stay calm, work in order, and write down each step. That record is worth a great deal if you need to ask for help.
Frequently Asked Questions (FAQs)
Why is my WooCommerce checkout not working?
Common causes are a cached page, a block and shortcode mismatch, an incompatible extension, a payment gateway setting, or a script error. Check them in order.
Should I use the checkout block or the shortcode?
The block is the modern default for new stores, and the shortcode is the classic option. If the block causes problems with an extension, you can switch to the shortcode as a fix.
Why are no payment methods showing?
Usually the gateways are disabled, misconfigured, or incompatible with the checkout block. Check settings, keys, and compatibility warnings.
Should I cache the checkout page?
No. Cart, checkout, and account pages hold customer-specific data and should be excluded from caching.
Why does the place order button do nothing?
Often a JavaScript error from a conflict or a script optimization setting. Check the browser console.
Will I lose orders if I restore a backup?
You can. A restore removes data added after the backup date, so export recent orders first.
How do I test checkout without losing sales?
Use a staging site and your gateway’s test mode. If you must test live, do it at a quiet hour.
Can someone fix my checkout for me?
Yes. If you want an experienced person to diagnose and fix it, you can get WordPress management help through this Fiverr gig.
Final Thoughts
A broken checkout feels urgent, and urgency tempts you to swap plugins. Resist that. Most checkout problems come from a short list: page setup, a block and shortcode mismatch, an incompatible extension, a gateway setting, a cache, a script error, or a security rule.
Work through the checks in order, change one thing at a time, and test a real order after each. Keep a backup, protect your orders, and replace a plugin only when the evidence says that it is the cause. With that method, most checkout problems are fixed in an afternoon.

