WooCommerce maintenance plan: what to monitor so checkout never breaks

How store maintenance differs from website maintenance

On a company website, the main risks after an update are a broken layout or a contact form that stops sending. On a store, the stakes are higher and the moving parts are more numerous. Orders, stock, customers and payments live in the database and change every hour.

That changes how maintenance has to be done. You cannot simply restore yesterday's backup when something goes wrong, because you would lose today's orders. Updates need to be tested before they reach the live store, and a rollback has to be planned so that it does not overwrite new data.

• Checkout is the most important journey. Every check starts and ends with the question: can a customer still buy?
• Several external services are involved. Payment gateways such as Stripe or PayPal, shipping integrations, tax or VAT plugins and invoicing tools all depend on each other.
• Emails are part of the product. Order confirmations, shipping notices and password resets are what customers rely on after paying.
• Data changes constantly. Backups and rollbacks must account for orders placed since the last copy.

A typical example from practice: in one of the stores I look after, a routine plugin update changed how the checkout handled an optional field. The store looked fine, product pages loaded and the uptime monitor stayed green. Only a test order showed that one payment method no longer completed. Without that check, the first signal would have been a quiet drop in sales.

That is the logic behind the routine below. It is not about doing more work, but about checking the things that cost money when they fail, in the order customers experience them.

Every week: the core of a WooCommerce maintenance plan

These are the checks I do every week. None of them takes long, but skipping them is how small problems become lost sales.

• Test order. Place a real order on the live store, ideally with a low-value or hidden test product, and go through the whole journey: cart, checkout, payment, confirmation page. Then cancel or refund it. Automated monitoring tells you the site is up; only a test order tells you people can buy.
• Payment gateways. Check that each payment method offered at checkout still appears and completes. Look at the gateway's own dashboard for failed payments, webhook errors or account notices. Gateways change their requirements from time to time, and the warnings often go to an inbox nobody reads.
• Transactional emails. Confirm that the test order generated the customer confirmation and the store notification, and that they arrived in the inbox, not spam. If the store sends emails through the hosting server, consider a dedicated email sending service.
• Updates on staging. Apply plugin, theme and WooCommerce updates on a staging copy first. Test the cart, checkout and account pages there, then repeat on the live store with a fresh backup taken right before.

Two quick extras belong in the weekly round as well. First, look at the order list for orders stuck in “pending payment” or “failed”. A sudden cluster of them is often the first trace of a gateway problem. Second, open the WooCommerce status page and the logs, and look for fatal errors and failed scheduled actions. Scheduled actions handle things such as subscription renewals and follow-up emails, and when they fail they fail silently.

Keep a short log of each week: what was updated, the result of the test order and anything unusual. When something breaks later, that log is the fastest way to find the cause.

Every month

Monthly checks look at the store's health rather than at individual updates.

• Performance. Check how fast product, cart and checkout pages load, not only the homepage. Slow checkout pages are often caused by scripts added for marketing or by a plugin doing too much on every request.
• Backups. Confirm that backups run on schedule, are stored off the server and that a restore works. A backup you have never restored is an assumption, not a safety net.
• Plugin review. List the plugins installed and ask whether each is still needed, still maintained and still compatible with the current WooCommerce. Remove what is no longer used.
• Customer journeys beyond checkout. Once a month, also test account registration, password reset, applying a discount code and, if you sell subscriptions, a renewal on staging. These paths are used less often, so problems there go unreported for longer.
• Licences. Paid extensions for payments, shipping, subscriptions or tax need active licences to keep receiving updates. Check renewal dates and make sure licences are on the store owner's account.
• Tax and shipping settings. If tax rules, shipping zones or rates changed in your business, confirm that the store reflects them.
• Accounts and roles. Review who has administrator or shop manager access. Staff who have left and old agency accounts should be removed, because these accounts can see customer data.

If you are not sure where your store stands today, a free website review is a good starting point. You get a report within 3 business days, with no obligation.

The most common failures after WooCommerce updates

Most WooCommerce updates go smoothly. When they don't, the failures tend to fall into the same few categories.

• Outdated template overrides. Themes often override WooCommerce templates. After a major update, those overrides can be out of date, which breaks the layout or hides fields at checkout.
• Payment plugin conflicts. A gateway plugin may lag behind a WooCommerce release, or two plugins may both modify the checkout. The payment step then fails silently or shows a generic error.
• Checkout changes. WooCommerce has been moving towards block-based cart and checkout pages. Extensions built for the older checkout may not work with the new one, so check compatibility before switching.
• Database updates. Some releases need a database update after installation. On a large store this takes time and should not be started in the middle of a busy period.
• Changed prices or totals. A tax, currency or discount extension that falls out of step with WooCommerce can calculate totals differently, for example applying VAT twice or skipping a shipping fee. Compare the test order's total with what you expect, line by line, not only whether it went through.
• Emails stop sending. A change in an email plugin or SMTP configuration means customers pay but receive nothing.
• Caching the wrong pages. A caching or performance plugin that starts caching the cart, checkout or account pages shows customers someone else's basket or an outdated total. These pages must always be excluded from page cache.

The answer to all of these is the same: test on staging, update the live store at a quiet time, take a backup right before, and have a rollback plan that keeps new orders. Updating the store yourself? Avoid the Friday evening slot.

How I maintain stores at Esumo: the Partner plan

For online stores I recommend the Partner plan. It costs €690 a month net and includes 15 hours of work, with further hours at €42/h. It covers weekly updates tested on staging with rollback, monitoring of the checkout journey, a response within 4 hours on business days, a monthly report and a monthly call.

Smaller stores with few changes can start on Growth, at €390 a month including 4 hours, with updates tested on staging and a 1 business day response. If a store has a long update backlog, I first run a takeover and clean-up: 2 weeks, €690 one-off. All plans run on a monthly contract with 1 month's notice, and prices exclude VAT.

When checkout breaks despite all the checks, the order of work is fixed: first restore the ability to buy, even with a temporary workaround such as switching off the failing payment method, then find the cause, then fix it properly on staging. You get a short note on what happened and what I changed so it does not repeat.

Details of each plan are on the WordPress care page, and the article on scope of work explains how I divide responsibilities with your team and other providers.