WooCommerce emergency: what to do first
Your store is down, checkout is failing, or the orders have stopped. Take a breath: most store emergencies come from one recent change, and you can usually find it in fifteen minutes. Work through these steps in order. Each one narrows down where the problem is.
Is it the whole site, or just checkout?
This one answer tells you where to look next. It takes a minute.
- Open your store in a private browser window, so you see what a customer sees, not a version you’re logged in to.
- Try the home page, a product page, and the cart. Then go to checkout and get as far as the payment step. You don’t need to pay.
- Try to log in to your WordPress dashboard (wp-admin).
- Nothing loads, or you get a blank white page or “There has been a critical error”: something is crashing the whole site. Check your email: WordPress often sends the site’s admin a message naming the plugin or theme that caused it, with a link to log in safely. Then go to step 02.
- The site loads, but checkout fails or payments are declined: the problem is in checkout or the payment plugin. Go to step 04, after a quick look at step 02.
- Everything looks fine, but no orders are coming in: checkout might be failing only for some customers, or orders might be getting stuck before they’re saved. Try a real order with a cheap product, then go to step 04.
- Very slow, or errors that come and go: the server may be overloaded or out of memory. Your host can tell you, so skip ahead to step 06.
What changed?
On the stores we watch, the most common cause by far is something that changed shortly before it broke.
Think back over the last day or two. Did anyone:
- update a plugin, a theme, WooCommerce or WordPress itself? Updates that run automatically count too.
- install or switch on a new plugin?
- change a payment setting, a shipping rule or a caching setting?
- move the site to a new host, or does your host say they changed something?
If you find a likely change, undo it: switch the new plugin off, or go back to the previous version of the one that updated. If the store works again, you’ve found the problem. Leave it switched off and tell the plugin’s makers what happened.
If you can’t get into wp-admin, you can still switch a plugin off. Use your host’s file manager to rename its folder inside wp-content/plugins, for example by adding -off to the end. WordPress turns off a plugin when it can’t find its folder. Change the name back later to bring it back.
Before you undo anything big, check that your host has a recent backup. Most do, and many can restore yesterday’s copy of the site for you.
Read the error
When something crashes, the server usually writes down why. That note often names the plugin responsible.
- The error log. Most hosting control panels have a “logs” or “error log” page. Download it and paste it into our free PHP error log reader. It puts the serious errors first and tells you which plugin or theme each one came from. Nothing you paste leaves your browser.
- WooCommerce’s own logs. If wp-admin works, go to WooCommerce → Status → Logs. Look for files with “fatal-errors” in the name, or named after your payment plugin, dated today.
- The status report. On the same Status page, copy the system status report and paste it into our free status report checker. It points out memory limits that are too low, background tasks that have stopped running, and out-of-date plugin files.
Check the payments
If the site works but money isn't coming in, look at it from the payment company's side.
- Log in to Stripe, PayPal or your payment provider and look at today’s payments. If you see failed or declined payments, the error shown there usually says why: an expired key, a blocked card type, or a setting that changed.
- If the provider shows no attempts at all, customers aren’t reaching the payment step. The problem is on your site, so go back to steps 02 and 03.
- If payments succeed but orders stay “pending” in WooCommerce, the payment company’s confirmation isn’t getting back to your store. PayPal confirmations that stopped arriving shows what that looks like.
- If checkout breaks after a payment plugin update, work through what to check when WooCommerce payments are failing.
- Empty carts, someone else’s cart, or “session expired” at checkout usually mean your checkout pages are being cached. Our checkout cache checker tells you in a few seconds.
Let your AI assistant look at the real data
If your WordPress dashboard still loads, you can install Operanse now and let Claude, ChatGPT or Cursor look at your store for you.
Describing a broken store to an AI assistant only gets you general advice. If you give the assistant your store’s actual information, it can point you to the most likely cause and tell you where to look first.
Operanse is a WordPress plugin that reads what’s happening on your store and makes it available to your AI assistant. Here’s how to set it up:
- Create a free account. It comes with 14 days of Insight, and you don’t need a card.
- Install the Operanse plugin from Plugins → Add New, then connect it with the code your dashboard gives you.
- Add Operanse to your AI assistant. The setup guide covers Claude, ChatGPT and Cursor.
- Ask it in plain words: “Checkout stopped working this morning. What’s wrong with my store?”
What it can see straight away. WordPress and WooCommerce already keep a record of this, so your assistant can check it the moment the plugin is connected:
- when orders stopped, and whether failed or unpaid orders are piling up
- background tasks that have failed or got stuck, like subscription renewals and order emails
- messages your store sends to other apps (webhooks) that keep failing
- every plugin and theme on the store and its version, plus the server’s memory and time limits
What it picks up in the next few minutes. If the store is still crashing, Operanse records the next crash and names the plugin or theme that caused it. For a checkout that fails every time, that’s often the whole answer.
What it can’t tell you. Operanse only sees what happens after you install it. It can’t say what changed before then, and it hasn’t learned yet what a normal day looks like for your store. Even so, it gives your assistant the facts it needs to tell you where to start looking.
The plugin only reads. Neither it nor your AI assistant can change anything on your store, so it can’t make the problem worse.
If you can’t get into wp-admin, skip this step for now. The plugin can’t be installed until the dashboard loads again.
When to call for help
Some problems aren't yours to fix. Knowing who to call saves an hour.
Call your host when
- the whole site is down and the error log is empty, or you can’t reach the control panel
- the site is very slow, or errors come and go, especially during busy times
- you see “database”, “memory” or “502/503/504” errors
- you need yesterday’s backup restored
Call a developer when
- the error log points to a plugin you can’t switch off without breaking something else
- the problem came back after you switched the plugin off
- it’s custom code your store was built with
- payments go through but orders don’t update, and the payment company says everything is fine on their end
We’re planning emergency support, where a professional developer fixes the problem for you. It isn’t available yet, but you can register your interest.
Whoever you call, send them: what you saw and when it started, what changed shortly before, the errors from step 03, and what you’ve already tried. It saves them half an hour, and saves you paying for it.
Questions
Should I restore a backup straight away?
Only if you can’t find the cause quickly and the store is losing sales. A restore puts back yesterday’s site, so any orders, customers and changes since then are lost unless your host can keep them. Undoing the one change that caused the problem is usually safer.
Will switching a plugin off lose its settings?
Almost never. Switching a plugin off (or renaming its folder) keeps its settings. Deleting it from the Plugins page can remove them, so switch it off instead.
How do I stop this happening again?
Turn off automatic updates for your payment and checkout plugins, and update them yourself at a quiet time so you can check checkout afterwards. Keep daily backups. And use a monitoring tool that tells you when orders stop or payments start failing, so you hear about it before your customers do. Operanse does this, and a single store is free on the Watch plan.
How much is the outage costing me?
Our outage cost calculator works it out from your own numbers, and you can send the result to a client or manager.