Shopify launch & migration QA checklist

Define the release surface

Write down the exact market, device, browser and public journeys that changed. A useful test plan is narrower than “check the whole store”.

1. 1List the homepage, priority collections, representative products, cart and every campaign landing page.
2. 2Include edge-case products: multiple variants, sold-out items, subscriptions, bundles, discounts or personalisation where relevant.
3. 3Record the production release time, theme or migration change, primary market and who owns each repair.

Protect URLs, navigation and discovery

Migrations and theme changes often leave shoppers on missing, redirected or disconnected pages even when the homepage looks correct.

1. 1Open old high-value URLs and confirm each resolves to the intended new page—not the homepage or an unrelated collection.
2. 2Follow header, menu, search, collection, breadcrumb, footer and policy links on mobile and desktop.
3. 3Check campaign links without relying on a logged-in session, cached page or merchant-admin access.

Verify product choice and price state

The selected product state must remain consistent from the product page through the cart.

1. 1Choose representative size, colour, selling-plan or personalised options and confirm availability, media, SKU and price update together.
2. 2Add the selection to cart and compare the product, variant, quantity, price, discount and fulfilment message with the product page.
3. 3Repeat with a sold-out or unavailable combination and confirm the store blocks the impossible purchase clearly.

Test cart and checkout handoff

The public buying path should survive quantity changes, removal, discounts and the handoff to Shopify checkout.

1. 1Change quantity, remove an item, return to shopping and reopen the cart; totals and item state should remain correct.
2. 2Test any public discount, free-shipping threshold or cart message against the actual cart total and stated conditions.
3. 3Confirm the checkout button opens the expected secure Shopify checkout. Do not place a real order unless the merchant has authorised a test transaction.

Reconcile trust and fulfilment claims

A store can be technically functional while still presenting conflicting delivery, returns or product information at the decision point.

1. 1Compare delivery, returns, guarantees, subscriptions and product claims across the product page, cart, footer and policy pages.
2. 2Place turnaround time, photo or personalisation requirements, approval steps and exclusions beside the action they affect.
3. 3Verify reviews or proof used near the purchase action support the exact claim being made; do not turn one review into a universal promise.

Run the mobile and regression pass

Retest the same journey on a real mobile viewport, then preserve a compact baseline for the routes that matter after release.

1. 1Check that overlays, cookie notices, menus, selectors and sticky actions do not hide the product, price or add-to-cart control.
2. 2Inspect representative pages for missing accessible names, broken focus order, unreadable contrast and unexpected console or network failures.
3. 3After fixes, rerun the original reproduction steps and retain the URL, environment, observed result and pass condition for regression checks.