You clicked "Update" and now your store is gone.
White screen. A cryptic error message. Maybe nothing loads at all. Your checkout is dead. Your products are invisible. Customers are seeing an error page instead of your store.
I have fixed this exact situation on more than a hundred WordPress and WooCommerce sites since 2011. I worked at WooThemes (the company that built WooCommerce) in 2014. I have seen every version of this crash.
Here is what is actually happening, and what you can do about it right now.
Why Plugin Updates Crash WooCommerce Stores
Your WooCommerce store runs on layers of software. WordPress at the bottom. WooCommerce on top of that. Then your theme. Then every plugin you have installed. Each one depends on the others behaving a certain way.
When a plugin updates, it changes its code. Sometimes that new code conflicts with your version of WordPress. Sometimes it conflicts with WooCommerce. Sometimes it conflicts with another plugin that was working fine yesterday.
The most common crash causes:
PHP version conflicts. The updated plugin requires a newer version of PHP than your server is running. The site hits a fatal error and goes white.
Plugin-to-plugin conflicts. Two plugins try to do the same thing, or one plugin changes something the other depends on. After the update, they collide.
Database migration failures. Some plugin updates change the database structure. If that migration fails halfway through (server timeout, memory limit), the plugin's data is in a broken state and the site cannot load.
Memory exhaustion. The update process itself eats more memory than your hosting plan allows. WordPress runs out of memory mid-update and the site crashes.
Theme incompatibility. Your theme expects the old version of the plugin. The new version changes how it outputs data. The theme breaks trying to display it.
None of these are your fault. They are the reality of running an open-source system with dozens of independently developed components.
What to Do Right Now
Do not panic. Your data is almost certainly still there. The database is intact. The site just cannot render because one piece of code is throwing an error.
Here is the process, step by step.
Step 1: Check if Your Hosting Has Automatic Backups
Before you touch anything, find out if you have a backup. Most decent hosting providers (Afrihost, Hetzner, SiteGround, Kinsta, Cloudways) keep daily or weekly backups.
Log into your hosting control panel. Look for "Backups" or "Restore." If you have a backup from before the update, restoring it is the fastest path back to a working store.
If you do not have a backup, keep reading. There are still options.
Step 2: Access Your Site Files via FTP or File Manager
You cannot use the WordPress admin because the site is crashing before it loads. You need another way in.
Use an FTP client (FileZilla is free) or the File Manager in your hosting panel (cPanel, Plesk, or similar). Connect to your site and navigate to /wp-content/plugins/.
Step 3: Rename the Plugin That Was Just Updated
If you know which plugin you updated last, find its folder in /wp-content/plugins/. Rename it. Add "-disabled" to the end of the folder name.
For example: rename woocommerce-subscriptions to woocommerce-subscriptions-disabled.
WordPress will see that the plugin folder name does not match what it expects and will deactivate it. Reload your site.
If the site comes back, you found the problem.
Step 4: If You Updated Multiple Plugins at Once
This is trickier. You do not know which one caused the crash.
Rename the entire /wp-content/plugins/ folder to /wp-content/plugins-disabled/. Then create a new empty folder called /wp-content/plugins/.
Your site should load now (with no plugins active). It will look broken because WooCommerce and everything else is off. That is fine. You just confirmed the problem is plugin-related.
Now move plugins back one at a time from /plugins-disabled/ to /plugins/. Reload the site after each one. When the site crashes again, you found the conflicting plugin.
Step 5: Check the PHP Error Log
Your server keeps a log of PHP errors. This tells you exactly which file and which line of code caused the crash.
In cPanel, look for "Error Log" or check the file at /home/yourusername/public_html/error_log. In the log, look for the most recent "Fatal error" entry. It will name the plugin and the specific problem.
This is the single most useful piece of information for diagnosing the crash. If you are going to contact a developer for help, send them this log.
Step 6: Check Your PHP Version
Some plugin updates require PHP 8.0 or higher. If your server is still on PHP 7.4, the update could cause a fatal error.
You can check your PHP version in cPanel under "PHP Version" or "MultiPHP Manager." If you are behind, upgrading PHP may fix the crash. But be careful. Upgrading PHP can break other plugins too. Test on a staging site first if you can.
Step 7: Increase WordPress Memory Limit
If the crash is caused by memory exhaustion, you can try increasing the limit.
Add this line to your wp-config.php file (you can edit it via FTP or File Manager):
define('WP_MEMORY_LIMIT', '256M');
This does not fix the underlying problem, but it may give WordPress enough room to finish loading.
What if You Do Not Have a Backup?
This is more common than people admit. And it is not the end of the world.
Your database is still there. Your files are still there. The site is not destroyed. It just cannot render because of a code error.
Follow Steps 2 through 5 above. In most cases, disabling the problem plugin and rolling it back to the previous version (you can download older versions from the WordPress plugin directory) will get you back online.
If the database was corrupted by a failed migration, that is harder. You need someone who can read the database tables and repair or rebuild the affected data. This is where DIY usually stops and professional help starts.
When to Stop Trying and Call a Professional
Be honest with yourself about the line between "I can handle this" and "I am making it worse."
Call a professional when:
- You cannot identify which plugin caused the crash
- The PHP error log shows database errors, not just plugin errors
- You have made changes and the site is now in a worse state than when you started
- The site is an active store processing orders, and every hour of downtime costs real money
- Your hosting provider's support team cannot help (they usually can not, beyond restoring a backup)
- You do not have a backup and the database may be corrupted
There is no shame in this. Plugin conflicts and crash recovery are specialist work. A developer who has done this before can usually diagnose the problem in under an hour and have you back online the same day.
I have recovered WordPress and WooCommerce sites that were crashed, hacked, corrupted, and abandoned mid-migration. One example: a WordPress site recovery and security project where the site had been compromised and needed both recovery and hardening.
How to Prevent This From Happening Again
Once your store is back online, put these safeguards in place.
Set up automated backups. Daily backups minimum. Weekly database backups are not enough for an active store. UpdraftPlus, BlogVault, or your hosting provider's backup tool all work. The important thing is that the backup exists and you know how to restore it.
Use a staging site. A staging site is a copy of your live store where you test updates before they go live. Most managed WordPress hosts offer one-click staging. Update plugins on staging first. If staging breaks, your live store is still safe.
Update plugins one at a time. Never click "Update All." Update one plugin. Check the site. Update the next. If something breaks, you know exactly which update caused it.
Keep WordPress, WooCommerce, and PHP reasonably current. Falling two or three major versions behind is when update crashes get ugly. Small, regular updates are safer than big jumps.
Remove plugins you are not using. Every inactive plugin is still code sitting on your server. It can still conflict. If you deactivated it six months ago and never reactivated it, delete it.
The Short Version
Your WooCommerce store crashed after a plugin update. Your data is almost certainly fine. Disable the plugin that was updated (via FTP, not the admin). Check the PHP error log to see exactly what went wrong. Restore a backup if you have one. If you do not have a backup or the problem is in the database, that is when it is time to call someone who has done this before.
If your store is down right now and you need someone who has fixed this exact problem more than a hundred times, get in touch.