Ecommerce testing checklist.

Before you start

Choose test products, variants, a customer account and delivery addresses. Write down expected prices and promotion rules. Record the store version, market, browser and device.

Repeat key journeys on desktop and mobile. Mark each check as passed, failed, not tested or not applicable. Copy this list into your release notes or print the page.

Finding products

1. Find a known product.

   Use the menu and search to reach a product you have chosen in advance.

   Expected: The right product opens with the expected price and availability.

2. Repeat on mobile.

   Open the menu, search and use a relevant filter on a narrow screen.

   Expected: Controls work, results match the filter and overlays do not block shopping.

Product details

3. Switch variants.

   Select two sizes or colours, including a differently priced option if available.

   Expected: The selection, price, image and availability match your product data.

4. Try an unavailable item.

   Select an out-of-stock variant with its stock rule recorded in advance.

   Expected: Purchase is blocked or the intended backorder option appears. No silent substitution.

Basket

5. Add and change quantity.

   Add the selected variant, then change from one unit to two.

   Expected: The correct variant reaches the basket and totals recalculate without extra units.

6. Return, then remove.

   Reload the basket, remove one product, then empty it.

   Expected: Items persist as intended. Removed products and their charges disappear.

Promotions

7. Check the saving.

   Apply an eligible offer, include an excluded item, then change quantities.

   Expected: Only eligible products receive the correct saving. Totals update after every change.

8. Check the boundaries.

   Try below and at the minimum spend, an expired code and a disallowed combination.

   Expected: Eligibility and stacking follow your configured rules. Invalid offers do not change the price.

Checkout

9. Check address and delivery.

   Correct an incomplete address, then change the delivery method or destination.

   Expected: Errors are clear. Available methods and charges follow your delivery rules.

10. Compare the final summary.

    Enter checkout as a guest and signed-in customer where supported. Stop before payment or order submission.

    Expected: Items, quantities, discounts, shipping and total match the latest basket and address.

Orders and payments

Agree on the payment environment, fulfilment and cleanup first. Real transactions need explicit authorization.

11. Complete a test order.

    Use the agreed payment method. Compare the confirmation, email and order record.

    Expected: One order has the correct items, total and payment status. Stock changes follow your rules.

12. Check recovery and cleanup.

    Test a supported simulated payment failure and retry. Cancel or refund the completed test order as agreed.

    Expected: Recovery creates no duplicate paid order. Refund status, stock and fulfilment match the cleanup plan.

Testing a Shopify store?

Check the candidate theme in preview, then repeat the critical journey after publishing. Verify your actual discount combination settings.

Follow Shopify's test-order guidance for payment checks. Customers cannot place live orders while the payment provider is in test mode. A theme preview is not a separate payment sandbox.

Make failures easy to fix.

Record the steps, expected result, actual result and a screenshot. Assign an owner and repeat the affected journey after the fix. Keep customer and payment details out of shared evidence.

These are functional starting points. Adapt them to your store; a pass describes only the scenarios tested.