Compare real order flows with the scenarios you tested before launch. Business-critical website changes deserve a repeatable test. Use realistic products, page URLs and enquiries so the check reflects what customers can actually do.

Make the decision

Look for repeat customer questions and drop-off at important steps.

Check the result

Record a small number of fixes and retest each after deployment. Write down the expected result before testing. Keep a short record of the device, page or product tested, the outcome and the person responsible for any follow-up.

Test it on a practical example

As a working exercise, choose one live example you can check from start to finish. Write down the intended result before comparing versions, or it will be difficult to tell whether a later change improved anything.

  1. Look for repeat customer questions and drop-off at important steps.
  2. Record a small number of fixes and retest each after deployment.
  3. Compare the final result with the intended use, and record who will confirm that it is ready.

Test a straightforward purchase or edit alongside a case with an exception. Choose a real combination of device, product and customer action. Check both sides of the workflow: what the visitor sees and what appears in the administration area, inbox or order record. Compare each result with the expected outcome before deciding what to change.

What to record before sign-off

Keep a short handover with the test data, expected result and person responsible for follow-up. For changes to a live shop, identify how to restore the earlier behaviour if an important task stops working.

For help with this work, explore our e-commerce website design in East Kilbride and Glasgow or tell us about your project.

Related reading