Friday afternoon is the worst time for a store to go down. Weekend orders are about to start, the owner wants to leave, and support everywhere is slowing down. That is exactly when a routine plugin update took a client’s store offline. It was back up in about twenty minutes, and the only reason was a habit I’d built years earlier: back up before every plugin update. No exceptions.
What happened
It was a WordPress store. A plugin had an update waiting, nothing dramatic, a normal version bump. I took a backup, ran the update, and loaded the home page to check. Instead of the store, I got an error screen. The front end was down and so was the admin.
When the admin is down too, you can’t just click “deactivate” on the bad plugin. You have to go in through the hosting file manager or FTP, rename the plugin’s folder so WordPress skips it, and hope that’s the only problem. Sometimes it is. Sometimes the update already changed something in the database, and disabling the plugin leaves the site half working.
I didn’t want to guess on a Friday. I restored the backup I’d taken minutes before. The site came back exactly as it was, orders and all, since nothing new had come in during that short window. Then I left the update alone, flagged it, and tested it later on a copy of the site where breaking things costs nothing.
Should you back up before updating WordPress plugins?
Yes. Every time. This is one of the most searched questions around WordPress updates, and the answer is never “it depends.” Most updates go fine. You back up for the one that doesn’t, and you never know which one that will be.
The reason people skip it is time. A full backup on a big store can take a while, and if you’re updating a few plugins a week, it feels like overhead. That’s the wrong math. A backup takes minutes. A broken store with no restore point can take hours or days, and on a store those are hours with no sales.
The habit, step by step
This is what I do on every WordPress or WooCommerce site I manage. It’s cheap, and most of it you can do with tools you already have.
- Know where your backups live. Many hosts take daily backups automatically. Find out if yours does, how long it keeps them, and how to restore one. Do this before you need it.
- Take a fresh backup right before updating. A daily backup from last night is not enough for a store. Orders came in since then. Take an on-demand backup, files and database, just before you touch anything.
- Update one plugin at a time. Bulk updating ten plugins at once means that if something breaks, you don’t know which one did it. One at a time, check, then the next.
- Check the pages that make money. After each update, load the home page, a product page, the cart and the checkout. Add something to the cart. If you can, run a test order.
- Restore fast if it breaks. Don’t spend an hour debugging a live store. Restore, confirm it works, then investigate on a staging copy.
- Keep a copy off the server. If the host itself has a problem, backups stored only on that host go down with it. Download one now and then, or use a backup plugin that sends copies to cloud storage.
How often should you back up a WooCommerce store?
For a store that takes orders, daily at minimum, plus an on-demand backup before any change. WooCommerce stores are different from brochure sites because the database changes constantly. Every order, every customer account, every stock adjustment is a database write. A week old backup of a store means a week of orders you’d have to recreate by hand.
A few things worth knowing:
- When you restore a store backup, any orders placed after that backup are gone from the site. Check your payment processor for orders in that window so you can rebuild them. This is why the backup right before the update matters: it keeps that gap tiny.
- If you have a slow hour, update then. For most local stores that’s early morning.
- Test your restore at least once. A backup you’ve never restored is a hope, not a plan.
Why Friday updates are a bad idea anyway
I broke my own rule that day by updating on a Friday afternoon. The update had a fix the client wanted before the weekend, so I went ahead. It worked out because of the backup. But the lesson stuck: if an update isn’t urgent, do it early in the week. If something goes wrong, plugin developers and hosts are around to help, and you have days to fix it before the weekend rush.
Security updates are the exception. If a plugin has a known hole being exploited, update now, Friday or not. That’s another reason to have the backup habit locked in. When you need to move fast, you don’t want to be figuring out backups for the first time.
The cost of the habit
Here’s what this habit costs: a few minutes before each update and, if your host doesn’t include backups, a backup plugin or service. That’s it. Compare that to a store that’s down for a weekend.
The Friday story ended fine. The client barely noticed. That’s the point. When the habit works, nothing happens, and nobody thanks you for nothing happening.
If you manage a store, do one thing before your next update: log into your host, find the backup section, and take a manual backup. Then find the restore button and read what it does. If you can’t find either in five minutes, sort that out before you click update on anything.