Before your WooCommerce store is launched for real customers, you should complete at least one full test order.
This is not just about whether the „Place order“ button can be clicked. An order connects many areas of your shop: product, shopping cart, coupon, customer address, tax, shipping, payment, order status, and email notifications.
Therefore, a shop can look finished at first glance and still reveal an error only during the first complete checkout process.
Important: A test order should replicate the actual process of a future customer as closely as possible. Therefore, do not test your shop only in the WordPress backend, but also from the public shop page to the completed order.
Where should you place a test order? #
For extensive technical testing, a separate test or staging website is the safest environment. There, you can check settings, payment processes, and extensions without affecting real customers or ongoing orders.
WooCommerce generally treats a normal test order just like any other order. It can, for example:
- Trigger WooCommerce emails,
- appear in your orders,
- be included in WooCommerce Analytics,
- be processed by connected plugins or external services.
WooCommerce Core does not have a general special order status „test order“ by which every extension could automatically recognize that it should not do anything with this order.
Therefore: Before placing a test order, check which additional systems are connected to your shop. These may include payment providers, inventory management systems, shipping solutions, accounting, or other automations.
After completing tests, you should remove test orders that are no longer needed so that they are not accidentally processed further or included in your later evaluations.
Before the test: Check the most important basic settings #
Before placing an order, briefly check the most important shop settings. This is not about every single detail yet, but rather about ruling out obvious configuration errors before the actual test.
| Area | What you should check |
|---|---|
| Products | Price, stock status, tax status, and variants if applicable are correct. |
| Cart & Checkout | The correct WooCommerce pages are assigned and the checkout can be accessed. |
| Taxes | The tax technical rules intended for your shop have been set up. |
| Shipping | The required shipping zones and shipping methods are active. |
| Payments | At least one suitable payment method is set up and functional. |
| Emails | The required WooCommerce notifications and recipients are set up. |
If you haven't set up these areas yet, the relevant articles will help you WooCommerce basic settings, Taxes, Shipping, Payment methods and Email notifications.
Perform the test order from a customer's perspective #
It is best to open your shop in a private or incognito browser window. This prevents you from being logged in as a WordPress administrator at the same time and lets you see the shop more like a normal visitor experiences it.
Then select at least one typical product from your range and go through the entire ordering process.
- Open a product page.
- Check price, description, images, and availability.
- Select a variation for a variable product.
- Add the product to the shopping cart.
- Change the quantity if necessary.
- Test a coupon if you use coupons.
- Go to checkout.
- Enter a realistic test address.
- Check shipping, tax, and total.
- Select a payment method.
- Complete the order using the designated test procedure.
Pay attention to the small things as well: Are error messages understandable? Do selection fields work? Are mandatory fields correctly required? Can you operate everything on a mobile device?
We explain how shopping cart and checkout basically work in the article Understanding Cart and Checkout in WooCommerce.
Intentionally test products and variants #
If your shop uses different product types, you should not exclusively test the simplest product.
For a variable product, for example, you should check whether the available variants can be selected correctly and whether the price, image, stock status, or other variant-specific details change correctly.
When managing inventory, check after ordering whether the inventory has changed as you expect.
For products with different tax classes, shipping classes, or special shipping conditions, you should execute at least one corresponding test case.
You can find the basics in the articles Create variable products and Manage inventory, SKU, and delivery status.
Do not only test vouchers positively #
When using coupons, don't just test whether a valid coupon code works.
Also check at least one case where WooCommerce must reject the coupon.
Assuming your voucher is only valid from CHF 100.00. Then, for example, you test a shopping cart with CHF 90.00 and then one over the required limit.
The same applies to product or category restrictions, expiration dates, and usage limits.
This is how you can tell not only that the coupon works, but also that your restrictions are actually taking effect.
You can find more about this in the article Creating coupons and discount codes in WooCommerce.
Check taxes, shipping and total #
In checkout, you shouldn't just look at the calculation superficially. Check the individual components of the order.
| Exam | Question |
|---|---|
| Products | Do product prices and quantities match? |
| Discounts | Is a voucher correctly applied? |
| Shipping | Does the correct shipping method with the designated costs appear for the test address? |
| Taxes | Does WooCommerce calculate the expected tax amounts based on your saved rules? |
| Total amount | Does the combination of products, discount, shipping, and taxes result in the expected final amount? |
For multiple shipping zones, test at least one address from each important zone.
For example, if you have set up different shipping conditions for Switzerland and Germany, a single Swiss test address is not enough.
The same applies to free shipping: if the threshold is CHF 100.00, for example, you should test one shopping cart just below and one at or above this threshold.
For taxes: The test order checks whether WooCommerce applies your stored rules correctly from a technical standpoint. It cannot confirm whether these rules are legally correct under tax law.
Test payment methods using the designated test mode #
Many online payment providers offer a test or sandbox mode. This allows you to simulate a payment without triggering a regular real payment.
How this test mode is activated and used depends on the respective payment service provider and its WooCommerce extension.
Therefore, always use the current test instructions of the payment provider actually being used for online payments. Do not use real credit card data in test mode, and do not use test payment data in live mode.
Important: Do not simply carry out real payments and then refund them afterwards if your payment provider has a dedicated test mode. Real transactions can, for example, incur fees that do not necessarily disappear through a refund.
After a successful test payment, you should check whether WooCommerce has created the order and set the expected order status.
Test, if possible, also a canceled or provider-declined payment attempt. Your shop must not only handle successful payments properly.
We explain the basics in the article Setting up and managing payment methods in WooCommerce.
Check the order completely in the backend afterwards #
After completing the test order, you open:
WooCommerce → Orders
Find the order just created and check it completely.
Check in particular customer data, products, quantities, discounts, shipping method, tax amounts, payment method, total amount, and order status.
Order notes are important, too. Payment providers and WooCommerce can use them to store information regarding payments and status changes.
Compare the backend amount with the amount you saw in checkout. Both must match the order actually placed.
You can find more about order management in the article Managing WooCommerce orders: status, payment, and shipping.
Check order status and payment separately #
A created order does not automatically mean that an online payment was successful.
Therefore, also check the test or transaction view of a payment service provider. The simulated payment process there should match the WooCommerce order.
Also check whether WooCommerce has updated the order status accordingly.
For example, in a normal, successfully paid order for physical goods, it is often In progress to be expected. Other payment methods and product types may have a different status flow.
What the statuses mean, we explain in the article WooCommerce Order Status Simply Explained.
The emails are also part of the test order #
A complete test order does not end on the order confirmation page.
Then check the expected WooCommerce emails.
The customer should receive the message appropriate to the order process. At the same time, the shop owner should receive the designated administrative notifications.
Check this while doing so:
- Recipient address
- Sender name and sender address
- Subject
- Order number
- Products and quantities
- Prices and total sum
- Billing or delivery address
- existing links
- Display on desktop and smartphone
Check the spam folder too.
If an expected message is missing, you should not simply assume that WooCommerce doesn't send emails at all. Use the diagnostics from WooCommerce is not sending emails: Systematically checking causes.
Test guest order and customer account #
If your shop allows both guest checkouts and customer accounts, you should try out both options.
During a guest checkout, you verify whether the customer can complete the purchase without an account.
For an order with a customer account, you should also check whether the order is in the area My account appears and whether the intended account functions are available.
If customers can create an account during or after checkout, you should also test this entire process completely.
You can find more about this at Setting up customer accounts and guest checkout in WooCommerce.
Test your shop on a smartphone too #
A checkout that works on your large screen doesn't automatically have to be easy to use on a smartphone.
Therefore, perform at least one test on a mobile device or in a realistic mobile view.
Pay special attention to whether:
- Product variants can be selected,
- form fields are completely visible,
- Error messages are displayed in a comprehensible way,
- shipping and payment methods can be selected,
- buttons are not covered,
- the order button is clearly accessible.
Especially the checkout should not only work technically, but also be intuitive to use.
Intentionally provoke error cases #
A good mystery shopping test does not consist only of a successful sample order.
Test some typical error cases as well. For example:
| Test | What was supposed to happen? |
|---|---|
| Leave mandatory field blank | WooCommerce clearly points out the missing field. |
| Enter invalid voucher | The discount is not applied, and the customer receives a clear message. |
| Address outside your delivery areas | No unauthorized shipping method is offered. |
| Select unavailable variant | The product cannot be incorrectly ordered without being noticed. |
| Cancel payment or have it declined | WooCommerce processes the order according to the payment flow. |
This allows you to control not only the ideal scenario, but also situations that inevitably occur during actual shop operations.
Test orders can trigger external systems #
This point is easily forgotten during tests.
If your shop is connected to other systems, a test order can also trigger actions there.
Depending on the extensions used, for example, order data could be transmitted to an external service or shipping and administration processes could be initiated.
WooCommerce explicitly points out that other plugins and services may not be able to distinguish a test order from a real order.
Therefore, check the documentation of the integrations you are actually using before the test, and only deactivate automated processing if this is intended for the test and can be done safely.
What you should clean up after the test #
If the test order is no longer needed, you shouldn't just leave it sitting among the real orders.
WooCommerce recommends deleting completed test orders after testing so that they are not accidentally processed, shipped, or permanently included in your analytics.
Additionally, check whether your payment provider manages its own test transactions and if any further cleanup work is necessary there.
Following that, the verification of the payment method is particularly important:
Before activating the shop: Make sure that all payment providers that are supposed to accept real payments are actually operating in the designated live mode. An accidentally active test mode can prevent real customer payments from being processed.
The final check before launching the shop #
If your test order was successful, go through the shop one last time from a customer's perspective.
| Area | Control |
|---|---|
| Product | Price, inventory, variants and images are correct. |
| Cart | Quantities, removal, and vouchers work. |
| Checkout | Mandatory fields and customer addresses are working. |
| Shipping | The correct zone, method, and costs are used. |
| Taxes | The stored tax rules are applied technically as intended. |
| Payment | The payment method processes the test correctly. |
| Order | Order data and status are correct in the backend. |
| Emails | Customer and shop receive the expected messages. |
| Customer account | Guest and account expiration work according to your configuration. |
| Mobile | The entire ordering process can also be operated on a smartphone. |
| Live mode | The payment providers required for real payments are correctly activated for production. |
If all these points are correct, you haven't just checked individual WooCommerce settings, but rather tested the actual ordering process from start to finish.
Summary #
A complete test order is one of the most important checks before launching a WooCommerce store.
Test the shop as much as possible from the perspective of a normal customer: select a product, use the shopping cart, fill out the checkout, check shipping and taxes, make the payment, and then check the order and emails.
Do not test only the successful ideal case. Invalid vouchers, unavailable shipping areas, cancelled payments, and other typical error cases should also be handled sensibly.
Note that WooCommerce does not fundamentally distinguish a regular test order from a real order. Test orders can therefore affect emails, analytics, and connected systems. For extensive testing, a staging environment is the safest solution.
After the test, you should remove any test orders that are no longer needed and, before going live, check in particular that your real payment providers are operating in the correct live mode.
