WooCommerce
How to update WooCommerce without losing a day of sales
29 July 2026 · 6 min read
On this page
Updating a shop is not the same job as updating a website. The consequences are financial, immediate, and usually silent. This is the procedure that avoids them.
Never update a live shop directly
If you take one thing from this: copy to staging, update there, place a test order, then push.
Most decent hosts include one-click staging free. It converts a risky change into a rehearsal, and it is the single largest difference between how a shop should be maintained and how most are.
If you genuinely have no staging option, then at minimum take a backup immediately before — not last night's — and update during your quietest hour with time to fix things.
The order
1. Back up first. Files and database. Minutes old, not hours.
2. WooCommerce core before its extensions. Extensions are written against the current WooCommerce; updating them first can fail in ways that updating core first avoids.
3. Your payment gateway, at the same session. This is the important one. WooCommerce releases are very often followed by gateway updates within days, because the gateway has to adapt. Updating WooCommerce in November and the gateway in January is how checkout breaks.
4. Shipping and tax extensions.
5. Theme last, and check whether it overrides WooCommerce templates — see below.
Check for outdated templates
WooCommerce → Status, and scroll to the templates section. If your theme carries customised WooCommerce templates, a WooCommerce update can leave them out of date, which breaks checkout in subtle ways.
WooCommerce flags these explicitly. Anything listed as outdated needs updating by whoever built the theme before you go live.
What to test, every time
Not the checkout page — a complete order.
- Add to cart, change quantity, apply a coupon
- Complete checkout with each payment method you offer, in test mode or with a real small order you refund
- Confirm the order appears in WooCommerce with the correct status, total and tax
- Confirm both emails arrive — the customer's and yours. These fail silently.
- Repeat on a phone. Mobile checkout breaks separately and more often.
- Test logged out as well as logged in. Caching problems usually affect only one.
- Check a product page, a category page and the cart for layout damage.
Fifteen minutes. It is the difference between "we updated" and "we know customers can still pay".
When not to update
- The week before your busy season. Freeze. Full peak checklist here.
- During a promotion.
- Friday afternoon, unless you plan to be available.
- When you cannot test properly. A rushed update is worse than a delayed one — unless it is a security fix, in which case update and test anyway.
If it breaks
Roll back the single plugin rather than restoring the whole site. Restoring a shop backup deletes every order placed since it was taken, which can cost more than the outage.
The full recovery sequence is here, but the first move is almost always: deactivate or roll back the plugin you just updated, and confirm checkout works again.
Keep a note of exactly what you updated and when. If something surfaces two days later — a tax rule, a shipping calculation — that note is how you find the cause instead of guessing.
The cadence that works
Security updates within 72 hours regardless. Everything else batched, on staging, once a week or once a fortnight, outside your busy periods.
That is what our WooCommerce care does — staging-first updates, a real test order after each one, gateway updated alongside WooCommerce, and freeze windows when you ask for them.