Prepare a small order matrix
Choose representative products: in stock, a variant, low stock, unavailable and a basket with several items. Add the actual delivery areas and methods. For each scenario, record the expected total and the person who will receive the order.
Check that the product page gives the information needed to decide and that the basket retains the selected variant, quantity and displayed price. Later charges must be understandable. Use test data or a suitable test environment so the exercise does not create false sales.
- Simple product, variant and stock-out covered.
- Expected total and delivery recorded.
- Test mode or environment identified.
Observe payment and failure states
Run an accepted payment, a decline and an abandoned session. Check that a browser return or double click does not produce duplicate orders for one intent. Compare the customer-facing state with the administration record; a confirmation screen is insufficient if fulfilment sees nothing.
Review error messages: a customer should know whether an order was created, whether to retry and whom to contact. Receipts, emails and payment data must follow the actual provider configuration, checked against its current documentation.
- Success, decline and abandonment observed.
- Customer and administration states agree.
- No misleading confirmation after a failure.
Follow the order after the final click
Test the customer email, team notification, fulfilment, delivery updates and support contact. Find out who can correct an address or cancel an order and how the change is recorded. Emails should reflect the terms actually published on the site.
Include a return or refund test according to the selling arrangements that truly apply. Rules can vary with product, place and contract; have the responsible specialists approve commercial and legal copy. The catalogue guide helps prepare the underlying data.
- Notifications received and understood.
- Fulfilment and support owner named.
- Return or refund path tried where relevant.
Make a launch decision
Collect scenarios in a grid: step, expected result, actual result, evidence, severity and fix. Incorrect prices, payments, stock or confirmations normally block opening the affected journey. Minor visual details can be scheduled after the practical obstacles are removed.
Once live, repeat a controlled order on the real site if the payment provider allows it. Review initial orders with the team handling them: success in staging does not prove that production notifications and integrations are identical.
- Acceptance grid approved by an owner.
- Blocking defects fixed before sales open.
- First production check planned.