Check a shop launch with an end-to-end test order

Before launching a shop, check a selected ordering journey through to the connected systems. A confirmation page shows only part of the process. Acceptance needs to establish which test order was paid, transferred, shipped and, where applicable, partially refunded.

Separate the test from real transactions

Shopify describes simulated payments for test orders. WooCommerce also notes test orders’ effects on connected services. A test mode in the payment form does not establish that the whole chain is running in test mode.

Use a suitable separate test environment with test accounts and the providers’ intended sandbox access, meaning their test access. Messages go to controlled test inboxes. For inventory, shipping and other connections, establish that no real customer order or shipment will be triggered. If a service lacks a suitable test option, simulate that step separately and document the limit.

Prepare a worked acceptance case

All identifiers, amounts and expectations are fictional. The simplified card-payment case uses 2 units of P-14 at 25 EUR each, totalling 50 EUR; taxes and shipping charges are not calculated here. The example demonstrates data and state reconciliation, not a test already performed.

The business management system is called ERP here. The references are our own example data, not mandatory field names for the platforms mentioned.

Inspect the evidence at every boundary

Check quantity, item and reference in the shop and the respective test destination. Successful receipt of a transfer request does not prove that the order has been fully created. This case therefore requires a confirmed destination reference.

For a return, treat goods status and payment separately. In the example, 1 unit becomes available again only after the agreed test inspection. A simulated refund alone does not prove an inventory change. Equally, a shipping status does not prove receipt of payment.

Add a failure path and record the limit

Include a declined test payment and an interrupted response during order transfer. The display must not report unconfirmed success. Before retrying, it must be possible to establish whether the transaction already exists, preventing an additional order.

For each step, record the actual observed result and the shop and integration versions used. The completed expectation case provides the template. If a simulation covers an external step only partly, that limitation remains part of acceptance. Add other required payment methods, countries and special cases as separate checks.

Sources

• Shopify Help Center: Placing a test order

• WooCommerce documentation: Testing orders