WooCommerce Maintenance Checklist: Weekly, Monthly and Quarterly Tasks

On this page

1. Why a store needs extra care
2. Weekly checks
3. Monthly checks
4. Quarterly checks
5. Backups work differently for stores
6. Before festival sales and big campaigns
7. Keep a simple maintenance log

An online store has more moving parts than a normal business website: payments, shipping rates, stock, order emails and customer accounts. Any of them can quietly break after an update, and you often find out only when a customer complains or orders stop coming in. This checklist covers the store-specific tasks to add on top of regular WordPress maintenance.

Why a store needs extra care

On a brochure website, a broken contact form costs you enquiries. On a WooCommerce store, a broken checkout costs you sales every hour it goes unnoticed. Stores also change constantly: orders, stock movements and customer details are written to the database all day, which affects how you update, back up and restore.

• WooCommerce, payment gateway and shipping plugins update often and depend on each other
• Your theme may contain customised WooCommerce templates that go out of date
• Payment gateways and courier services change their settings, APIs and requirements over time

Weekly checks

• Place a test order. Use a low-priced, hidden test product, pay with UPI or a card, then refund it. This confirms the whole flow works: cart, checkout, payment, order status and emails.
• Look for stuck orders. Filter orders by "Pending payment" and "Failed". If your gateway dashboard shows a successful payment but the order is still pending, the gateway's webhook or callback is probably not reaching your site.
• Confirm order emails arrive. Check both the new-order alert to you and the confirmation to the customer, and make sure they aren't landing in spam.
• Check low-stock and out-of-stock products so bestsellers aren't showing as unavailable, or being oversold.
• Confirm backups ran and are stored off-site, not only on the same server.
• Glance at the logs under WooCommerce > Status > Logs for new fatal errors or payment gateway errors.

Monthly checks

• Apply updates on staging first. Update WooCommerce, extensions, the gateway plugin and the theme on a staging site, test the checkout, then repeat on the live store. If WooCommerce asks to run a database update afterwards, make sure you have a fresh backup first.
• Check for outdated template files. The System Status report under WooCommerce > Status flags theme templates that are older than your WooCommerce version. Outdated overrides can break product pages, the cart or checkout.
• Test every payment method on a phone: UPI, cards, net banking, wallets and Cash on Delivery if you offer it.
• Test shipping. Try addresses in different zones or pincodes, check free-shipping thresholds, and compare your rates with what your courier actually charges.
• Review scheduled actions. WooCommerce and many extensions run background tasks, listed under WooCommerce > Status > Scheduled Actions. A growing pile of failed or past-due actions points to a problem worth investigating.
• Reconcile payments. Compare gateway settlements with completed orders so missing or duplicate orders are caught early.
• Tidy coupons and sales. Remove expired coupons and check that scheduled sale prices start and end as planned.

Quarterly checks

• Test a restore of a recent backup on a staging site. An untested backup may fail when you need it most.
• Audit plugins and extensions. Remove ones you no longer use, and check that premium extension licences are active so you keep receiving updates.
• Review staff accounts. Remove people who have left, and make sure staff who only process orders have the Shop Manager role rather than Administrator.
• Clean the database. Clear expired transients and old sessions, and review which tables are growing; see database optimisation.
• Check the PHP version and hosting resources. A busy store needs more server capacity than a brochure site, especially as the catalogue and order history grow.
• Review tax, invoice and policy settings. Confirm GST settings with your CA if anything has changed, and check that your shipping, returns and privacy policies still match how you actually work.
• Check renewals: domain, hosting, SSL and any paid gateway, shipping or invoicing services.

Backups work differently for stores

A daily backup is usually fine for a brochure site. For a store, restoring yesterday's database would wipe out every order, customer account and stock change made since then. So:

• Back up more often, or use a backup service that saves database changes in near real time
• Never restore the full live database just to fix a design problem; restore only the affected files, or fix it on staging
• Be careful when pushing a staging site to live: copying the staging database over the live one overwrites new orders
• If you must restore after a disaster, export recent orders first so nothing is lost

More detail in the WordPress backup and restore guide.

Before festival sales and big campaigns

Diwali, Raksha Bandhan, end-of-season sales or a big Instagram campaign can bring far more traffic than a normal day. A couple of weeks before:

1. Finish all updates, then freeze non-essential changes until the sale is over
2. Test coupons, sale prices and free-shipping offers exactly as customers will use them
3. Update stock levels and confirm your courier can handle extra pickups
4. Ask your host whether your plan can cope with a traffic spike
5. Take a fresh backup and make sure someone can respond quickly if checkout breaks

Keep a simple maintenance log

Write down what you updated, when, and what you tested. When something breaks, the log tells you what changed last, which makes the fix much faster. A shared spreadsheet is enough: date, task, plugin versions and any issues found. It also helps if you ever hand the store over to a new developer.

Don't want to handle this yourself? I look after WooCommerce stores on monthly plans, including updates, test orders and backups. See WooCommerce development and WordPress maintenance.