What to test on WooCommerce staging before an update
A WooCommerce store can look unchanged after an update while one shipping zone or payment method has stopped working. The homepage is a useful first check. It is not a checkout test.
Build the test around the ways this store actually takes orders. Start with the store’s most common order, then choose cases that change shipping, discounts or payment behavior. Those differences are where a casual check tends to miss trouble.
Make staging safe before making it realistic
Confirm the staging hostname, then isolate outgoing email, payments, fulfilment services and webhooks. Use the gateway’s documented sandbox mode and test credentials. Do not assume a cloned installation automatically knows it is a test environment.
Protect the copy from public access, particularly if it includes real customer information. Keep only the data necessary for the exercise under your retention policy. Ask the service owner how subscription renewals, stock synchronization and other scheduled activity should be disabled on the copy.
WooCommerce’s update guidance recommends a current backup and staging tests before production changes. It also calls for checking the store’s main workflows after updating. Treat that as the baseline, then add the scenarios specific to your extensions and customers.
Choose orders that expose different behavior
- A guest order for a simple product with the most common payment method.
- A logged-in order with a saved address, where the store supports it.
- A variable product with a non-default option and an actual stock constraint.
- A shipping address in a different supported zone.
- A discount that should apply, and one that should be rejected.
- A failed or cancelled payment that must not look like a successful order.
Add a subscription, booking, downloadable product or tax scenario only when the store uses it. Record the expected outcome before running the test. Otherwise an unexpected result can be waved through as “probably how it always worked.”
For example, write the expected shipping service and total for a known test basket. You do not need a huge spreadsheet. You need enough detail to notice that the free-shipping threshold changed or that a variation lost its price.
Follow the order beyond the thank-you page
Inspect the order in the admin area. Check the status, line items and customer details. Confirm the controlled inbox received the expected message. If fulfilment is part of the scope, verify the sandbox event or integration log instead of assuming a successful checkout means the warehouse would receive the order.
Check that a cancelled payment leaves the right state. A store can have a healthy happy path and a broken failure path that confuses customers or reserves stock indefinitely. Write down which integration checks were simulated because no sandbox was available.
Move the tested changes, not stale customer data
Before production work, confirm which changes belong to plugin files, templates or configuration. New live orders may have arrived since the staging copy was created. Replacing the entire production database with that old copy can lose them.
Use a deployment procedure appropriate to the store and agree a maintenance window if required. Run a controlled production verification afterward using a payment workflow the owner has approved. A sandbox success cannot prove that live credentials are valid.
Save the tested versions, scenarios, results and any remaining exceptions. Those notes become the starting point for the next update rather than a task someone has to reinvent. Pair this checklist with the plugin update workflow and keep the restore procedure close enough to use if a production check fails.
Have a correction or a workflow we should cover? Tell the IrmaWP team.