A WooCommerce update is not complete when the plugin turns green. It's complete when customers can still search for a product, add it to a cart, pay and receive the correct order confirmation. This guide provides a safe maintenance workflow, not a guarantee that every third-party payment plugin will work.
Outcome: a documented staging test, a production update plan and a post-update checkout checklist. Requirements: administrative access, working backups, a separate staging environment and access to payment-provider test credentials. Estimate at least 75 minutes; complex stores take longer.
1. Document what is running
Record WooCommerce, WordPress, theme and payment plugin versions. List critical extensions: shipping, VAT, discounts, subscriptions, checkout-field customizations, analytics and email services. Note whether the store uses classic checkout or the Checkout block, and record current payment methods.
2. Back up the files and live database
Make a restorable backup of both the database and wp-content. Know how to restore it. A staging snapshot is not a future-safe copy of live orders. If orders arrive after the snapshot, restoring its old database over production would discard newer transactions. Have a recovery plan that preserves new orders and reconciles external payment status.
3. Isolate staging before testing
Create a staging copy under controlled access. Prevent search indexing. Set outgoing customer email to a safe test inbox or disable it where appropriate. Turn off live payment credentials and webhook effects; use the provider's official sandbox/test environment. This is especially important for Montonio, Maksekeskus or Stripe integrations. Do not assume a generic test order exercises real gateway behavior.
4. Apply the planned updates on staging
Update WooCommerce, compatible extensions and your theme in an intentionally documented sequence. If a database update is required, run it on staging and watch logs. Compare templates and console/network errors to the earlier state. Do not blindly apply unrelated updates at the same time.
5. Perform an actual checkout journey
Use the staging checklist. Test at least:
- Search and product detail, including variations and available stock.
- Add to cart, update quantity and apply a coupon.
- Guest and logged-in flows when the shop supports both.
- Shipping, VAT and total calculations in representative countries.
- Sandbox payment success, decline and cancellation where the provider allows it.
- Exactly one order with the expected status, matching payment-provider record, confirmation page and test email.
- Mobile checkout and separate-session cart privacy.
Record the transaction identifier of each sandbox test and remove or label test records according to the staging policy.
6. Roll out in a controlled window
Before the live update, take a fresh backup and ensure an operator can stop new checkouts during the maintenance window if needed. Apply the same tested release set to production; do not import the staging database over the live store. Reopen only after smoke checks. Conduct a carefully scoped production verification that does not make an unintended live charge.
7. If something fails
Collect the failed request, sanitized logs, plugin versions and exact checkout steps. Roll back application files only after considering database migration compatibility and newer orders. Reconcile pending payment-provider callbacks before retrying any transaction; do not blindly resubmit an uncertain payment.
Further reading: WooCommerce — How to update · Payment errors.
Downloads and next steps
Download the staging checklist and release checklist. Complete checks with controlled operator access before reopening checkout, then monitor the reopened store. Also see the WordPress performance guide.
For help planning store maintenance, see e-commerce development.
Documentation reviewed on 12 November 2026. This is a maintenance procedure, not a record of a merchant staging test or a production payment.
Planning changes to your website?
If you are planning a business website, online shop or improvements to an existing site, see how I approach page structure, content management and integrations. The scope starts with what your visitors need to do.