WooCommerce / Emergencies
WooCommerce emergencies: when a problem needs urgent intervention
Not every broken store is an emergency, and treating every problem as one leads to rushed changes that make things worse. The question is simple: is the store losing orders, payments or data right now?
Short answer
It is an emergency when the store is losing orders, payments or data right now: no customer can check out, customers are charged without orders, the store shows a critical error, or orders and stock are not being processed. In that case, record what changed and when, take a backup, avoid mass updates and manual data edits, and get an engineer on the root cause.
Severity
Is it an emergency?
Nobody can complete an order
Checkout fails for every customer, on every payment method.
Charged without an order
Money is being taken while orders fail or stay pending.
Critical error on the store
The shop, checkout or admin shows a critical error or a blank page.
Orders not processed
Emails, stock updates or fulfilment syncs stopped; scheduled actions piling up.
Partial checkout failure
One payment method, country or customer group cannot check out.
Annoying, not blocking
Slowness, admin errors or visual problems that do not stop sales.
The first ten minutes
- Confirm the scope: does it affect every customer, or only some — guests, one payment method, one country, mobile?
- Record the timeline: when it started, and every change shortly before: updates, new plugins, PHP version, hosting, DNS, CDN or security rules.
- Capture the evidence: the exact error text, WooCommerce → Status → Logs (
fatal-errorsand the gateway's log), the provider's dashboard for affected payments. - Take a backup before anyone changes anything.
What not to do
- Do not update every plugin, the theme and WooCommerce at once.
- Do not restore an old full backup without checking which orders it would erase.
- Do not delete or manually edit orders, scheduled actions or database tables.
- Do not disable security, caching or CDN rules across the board on production.
Stabilise, then fix the cause
Sometimes the right first step is rolling back the one change that triggered the problem. That stops the damage, but if the change only exposed a deeper incompatibility, the problem returns with the next update. The work is finished when the root cause is understood, fixed and documented.
Frequently asked questions
What should I do first when WooCommerce breaks?
Write down when it started and what changed before it, copy the exact error, check WooCommerce → Status → Logs, and take a backup before anyone changes anything.
Should I put the store in maintenance mode?
Only if customers are being harmed — for example charged without orders. Maintenance mode can also block payment notifications from the gateway, so check that callbacks still reach the store.
Should I update all plugins to fix it?
No. Mass updates multiply the number of changes, can introduce new problems and hide the original cause.
$ describe the problem
Have a WooCommerce problem?Request a diagnosis.
Tell us what is failing, what changed recently and the business impact. We review every request and recommend the appropriate next step.
Never send passwords, API keys or card data through the form.