Your store is live, orders come in most days, and nobody has a written list of what should be looked at, or when. The developer who built it has moved on to other work. You log in, glance at the dashboard, see some orders and assume all is well. Then one morning a customer phones to ask why her payment went through but no confirmation ever arrived.
This is a WooCommerce store maintenance checklist built around that problem. It is sorted by how often each job needs doing, from a two-minute daily glance to a quarterly review, so you can hand parts of it to a staff member and keep the rest for yourself or whoever looks after the site.
Why a store needs its own list
A brochure site can sit untouched for a few weeks and the worst outcome is usually a stale page. A shop has moving parts that change every day: stock counts, order statuses, payment gateway connections, emails sent to customers, background jobs that run on a schedule. Each of those can stop working quietly while the home page looks exactly as it did yesterday. Online store upkeep is mostly about watching those parts, not the design.
The general website maintenance checklist on this site covers the jobs every WordPress site needs, such as backups, updates and security. Everything below is the extra layer a WooCommerce shop adds on top. Read the two together rather than treating either as complete on its own.
Every day: the two-minute glance
This is the part most worth giving to a person rather than a plugin, because it relies on knowing what a normal day looks like for your business.
- Compare today’s orders with what you expected. A Tuesday with no orders when Tuesdays normally bring several is the earliest signal you will get that something is wrong.
- Look at the order statuses, not only the count. In WooCommerce > Orders, a run of “Pending payment” or “Failed” orders means customers are reaching the payment step and not getting through it.
- Check that the new order email reached you. If the order is in the dashboard but the email never arrived, customers are probably missing their confirmations too.
- Open the payment gateway’s dashboard and check that the payments listed there roughly match the paid orders in WooCommerce.
Write nothing down on a normal day. Only note the days that look odd, with the date and what you saw.
Every week: the working checks
Place one real order
Once a week, buy something. Use a cheap product, pay with a real method, and follow it all the way: the cart, the checkout, the payment page, the thank-you page, the customer email and the admin email. Refund or cancel it afterwards. Few monitoring tools tell you as much as this does, because it walks the same path your customers walk.
Read the logs
WooCommerce keeps its own logs under WooCommerce > Status > Logs. Look for entries from your payment gateway and for anything marked as a fatal error. You do not need to understand every line. You are looking for new entries that keep repeating, so you can pass them to someone who does.
Check the scheduled actions
WooCommerce and many extensions queue jobs to run in the background, such as delivering webhooks, sending some emails and syncing with other services. They are listed under WooCommerce > Status > Scheduled Actions. A growing pile of “Past-due” or “Failed” actions usually means the site’s scheduled tasks are not running properly, and that tends to show up later as odd order behaviour.
Glance at stock
Pick three or four best-selling products and compare the stock shown in WooCommerce with what is physically on the shelf. If the numbers drift, read our guide on why WooCommerce inventory stops matching your orders before the drift turns into overselling.
Confirm the backup ran
Check that last night’s backup exists, that it includes the database and not only the files, and that it is stored somewhere other than the server the shop runs on.
Every month: the WooCommerce store maintenance checklist proper
This is the bulk of the work, and the part that is often handed to someone else. Taken in order, it looks like this.
- Updates. WordPress core, WooCommerce, the payment gateway plugin, the theme and every other plugin. On a store this is not a one-click job; the process is set out in our post on updating WooCommerce without breaking checkout.
- Template overrides. Under WooCommerce > Status > System Status, scroll to the templates section. If your theme contains outdated copies of WooCommerce templates, it says so there. Outdated overrides are a common reason a product page or the cart looks wrong after an update.
- Coupons and promotions. Delete or expire codes from past campaigns. Old codes leak onto coupon-sharing sites and keep getting used long after you meant them to stop.
- User accounts. Review everyone with Administrator or Shop Manager access. Remove former staff and old developers. Shop Manager is enough for someone who processes orders.
- Speed of the heavy pages. Test a category page and a product page with many variations, not only the home page. These are the pages shoppers browse and the ones that slow down first as the catalogue grows.
- Plugins nobody uses. Deactivate and delete them. Every inactive extension is still code on your server that needs updating.
- Customer-facing emails. Send yourself a test of the order emails from WooCommerce > Settings > Emails, and check they still show your current address, phone number and returns details.
Every quarter: the slower risks
These are jobs that do not break anything when skipped for a month, but cause real trouble when skipped for a year.
- Restore a backup to a staging copy. A backup you have never restored is a hope, not a plan. Restore it somewhere safe and check that products, orders and customer accounts are all there.
- Check who controls the payment gateway account. Make sure the login belongs to the business, not to a former developer, and that the API keys in WooCommerce are the live ones, not test keys left over from the build.
- Review shipping zones and tax settings against what you actually charge now. Couriers change rates and businesses add new regions without anyone updating the store.
- Read your policy pages. Returns, refunds, shipping and privacy pages should describe how you actually work today.
- Note renewal dates for the domain, hosting, SSL certificate if it is not automatic, and every paid extension licence.
Before and after a busy period
A sale or a festival season changes the risk. The week before, finish all updates, then stop. Do not update anything during the busiest days unless something is actually broken. The week after, catch up on the updates you held back and check stock counts against reality, because busy periods are when stock problems surface.
What to write down
A store log does not need special software. A shared document or spreadsheet with these columns covers it:
| Column | What goes in it |
|---|---|
| Date | When the check or change happened |
| Who | The person who did it |
| What changed | Plugin names and the version moved from and to, setting changed, product edited |
| Test order | Order number of the test order placed afterwards, and whether it completed |
| Anything odd | Errors, slow pages, emails that did not arrive |
When something breaks, this log is the first thing a developer will ask for. “It stopped working sometime last week” is hard to work with. “It stopped after the gateway plugin update on the 12th, and the test order after it failed” usually points straight at the cause.
Common ways a store checklist goes wrong
Watching the site, not the money
Uptime monitoring tells you the home page loads. It does not tell you the payment step works. A shop can be “up” for days while every checkout fails. That is why the weekly real order matters more than any alert.
Restoring an old backup over a live shop
Restoring a full backup brings back the database as it was when the backup was taken. Any orders placed since then disappear from WooCommerce. Before you restore anything on a live store, export recent orders or note their numbers, and ask whether a files-only restore would fix the problem instead.
Updating at the busiest hour
If your orders peak in the evening, that is the worst time to run updates. Choose the quietest hour your order history shows.
Checking everything once, then never again
The first pass through a list like this always finds something. The value comes from repeating it, so the second and third passes find very little and you notice at once when that changes.
Splitting the list between people
For most small shops a sensible split is: the person who packs orders does the daily glance and the stock spot-check, the owner reads the monthly summary, and someone technical handles the updates, logs, scheduled actions and backup restores. That technical part is the kind of work covered by ecommerce website maintenance services, whether you use us, a freelancer or a developer on staff. What matters is that each line has a name next to it.
If you only have time for one thing from this whole page, make it the weekly real order. It catches the failure that costs the most, a checkout that quietly stopped working, sooner than almost anything else here.
If you would like someone to work through the technical half of this list with you, or to look at a store where something already feels off, our WooCommerce support page explains what a support session covers.
Next in this series: Prepare a WooCommerce Store for a Sale: Festival Countdown
