Building & managing a store
Test the order journey before launching a store
A practical acceptance checklist for the moments between finding a product, paying and receiving a useful confirmation.
2 minute read · Practical guide
The key decision: Test the exceptions as carefully as the successful purchase.
More on Building & managing a storeChoose representative journeys
Test a simple product, a variant, an unavailable item and a basket with more than one product. Use mobile as well as desktop. Start from a category page or search result, not only a direct product link, so navigation and product discovery are part of the check.
Check the buying decision
Confirm that images, price, selected variant and availability agree. Read the delivery and returns information as a first-time customer would. Check the total before payment, including any configured shipping or other charges. The buyer should not have to contact support to understand what the order contains.
Use the provider’s test process
Use supported test or sandbox methods for payments. Check success, failure and cancellation without using real customer details. Confirm that retrying a failed payment does not create a second fulfilment instruction. A developer and the operations owner should agree what evidence closes each test.
Follow the order into operations
Check the order record, customer message, stock change and dispatch information. Test a cancellation and refund through the supported process. If the store connects to another system, verify the record there too; seeing a confirmation screen does not prove every handoff worked.
Make launch acceptance explicit
Maintain a short issue list with severity, owner and retest result. Separate launch blockers from improvements that can wait. Record the release version, recovery contact and the person approving launch. Keep a few critical journeys as a reusable checklist for theme, payment or extension updates.