Complete the buying journey on a phone
Find a product through categories and search, choose a variant, change quantity, enter an address and complete a test order. Repeat without registration if guest checkout is supported. Check unavailable items, unsupported delivery and basket preservation when returning. Use realistic screen sizes and keyboard navigation rather than only the designer’s full-screen layout.
Check what happens after checkout
The responsible team should receive the correct order total and items while the customer receives a clear confirmation. Test payment notifications, stock reservations, cancellation and refunds in the agreed sandbox. Internal failures should not expose credentials or stack traces. Staff permissions should match actual responsibilities.
Prepare ongoing operation
Assign owners for payments, catalogue data and support enquiries. Verify backups and restoration, domain and certificate expiry, access and error monitoring. Remove publicly visible test products. Remove staging indexing restrictions only after checking production settings.
- The mobile buying journey is complete.
- Amounts and statuses agree across systems.
- Staff permissions follow their responsibilities.
- Recovery and support are prepared.
Project questions
Is one paid test order enough to validate a store?
No. Also test refusals, cancellations, refunds, delivery errors and stock limits. Exception paths often reveal the gaps between systems.