For a WooCommerce store, the most important page isn’t the homepage — it’s the one where someone pays. After an update, “the shop loads” is nowhere near enough. The question is whether a customer can still get from a product to a completed order.
Testing that properly has one obvious problem: you don’t want to charge real cards, send real confirmation emails or reduce real stock. Here is how to check the journey safely.
Why checkout deserves its own check
A checkout depends on WooCommerce, the theme, the payment gateway, shipping and tax rules, and often a handful of extensions. Any of them can change in an update. Some failures are loud, like an error on the checkout page. Others are quiet: a shipping method disappears for one country, a coupon stops applying, or the order confirmation email never sends.
Start with a staging copy
The safest place to test is a staging copy of the store — a private duplicate where orders, emails and stock changes don’t affect real customers. Before using it for tests, it needs a little preparation:
- Outgoing email captured or disabled, so customers never receive test messages.
- Connections to live services — fulfilment, accounting, CRM — paused or pointed at test accounts.
- Payment gateways switched to test mode.
Use the gateway’s test mode
Most payment providers offer a test mode with test keys and published test card numbers. Stripe, for example, documents test cards such as 4242 4242 4242 4242 that behave like real payments without moving money. PayPal offers a sandbox environment for the same purpose.
What to walk through
- Find a product and add it to the basket, including a variation if the store uses them.
- Change the quantity and apply a coupon.
- Check shipping options and tax for the main countries you sell to.
- Pay with a test card and reach the order confirmation page.
- Confirm the order appears in the admin with the right status, and the emails were generated.
After a WooCommerce update it is also worth opening WooCommerce → Status, which lists theme template files that are out of date compared with the new version — a common source of subtle checkout issues. We explain how to handle them in WooCommerce outdated templates.
# List active plugins and whether updates are waiting
$ wp plugin list --status=active --fields=name,version,updateWhen there is no staging
Not every store has a staging environment. In that case we don’t create recurring real-money orders by default. Instead we agree a safer alternative with the store owner — typically a regular manual walk-through that stops before payment, plus a staging setup as a recommended next step.
For the full update process around these checks, see how to update WooCommerce without breaking checkout.
How often, and how deep
A weekly automated purchase-flow check is possible once a safe test environment exists. The exact scope and frequency depend on the store: how many payment methods it uses, how complex shipping is, and which integrations sit behind the order. We agree that during the store review, before care begins — and we are clear that live payments, fraud checks and third-party services remain outside what any test can guarantee.
Frequently asked questions
How do I place a test order in WooCommerce?
Use a staging copy or switch your payment gateway to test mode, then pay with the provider’s published test card numbers. No real money moves.
Can I test checkout on a live store?
You can walk through the flow up to payment, but avoid real transactions. If a live test is ever agreed, refund and mark it clearly so it doesn’t distort stock or reports.
What should I check after a WooCommerce update?
Basket, shipping, coupons, tax, payment, the confirmation page, the order in admin and the order emails — plus WooCommerce → Status for outdated templates.
Do test orders reduce stock?
They can, like real orders. That’s another reason to test on staging, or to reset stock after testing.
