What should a Shopify pre-launch check cover?
A useful pre-launch check follows the real shopping path from product discovery to checkout handoff. It confirms that the store's content and controls agree, records customer-visible failures and separates automated storefront QA from manual brand, analytics, accessibility and payment review.
Do not wait until the final hour to discover basic data problems. Run focused checks during implementation, then use this list as the controlled release pass after theme changes, products, discounts and required apps are stable.
1. Freeze the test scope
Agree on the storefront domain, launch market, language, currency, devices and products that matter most. Select representative risk groups: one simple product, one product with multiple options, one discounted product and any bundle, subscription or app-driven flow.
Record what is intentionally outside scope. A public storefront QA pass does not prove analytics accuracy, tax configuration, shipping rules, email delivery or payment settlement unless those areas are separately tested with the right access.
2. Review products and merchandising
- Product title, description, media, price and compare-at price are accurate.
- Availability, sold-out, preorder and low-stock messages match the merchant's rules.
- Variant selectors show the right labels and unavailable combinations.
- Changing a variant updates selected state, media, price, SKU or availability when applicable.
- Product recommendations and collection links lead to valid storefront pages.
Test an alternate option, not the option already selected at page load. This avoids a false warning where the theme appears unchanged simply because the test clicked the current variant again.
3. Test the cart as a customer
Add the selected product and compare the cart line item with the product page. Check the chosen variant, unit price and quantity. Increase and decrease quantity, remove the item and inspect the empty-cart state. If both a cart drawer and cart page exist, move between them and confirm state remains consistent.
Apply any launch promotion using a recorded expectation. Compare the observed discount and total with the agreed rule. Treat an uncertain calculation as a warning that needs merchant review, not as a pass.
For a detailed sequence, use the Shopify cart testing checklist.
4. Verify checkout handoff
Use the storefront checkout control and confirm that Shopify checkout begins with the intended items. Stop before payment submission during routine QA. If a completed order is part of the release criteria, use Shopify's approved test-order workflow with the merchant's permission and document it as a separate test.
Review customer-facing links around the purchase path as well: shipping information, returns, contact details, privacy and terms. These pages need human copy and legal review even when functional storefront controls pass.
5. Complete the manual release review
Review narrow mobile and desktop widths. Confirm navigation, sticky controls, drawers, modals and app widgets do not obscure product information or the add-to-cart action. Keyboard focus, readable contrast and tap target size should also be checked manually.
Separately verify analytics events, consent behavior, SEO metadata, redirects, domain configuration, notification emails, tax, shipping and any business-specific acceptance criteria. These checks need project context that a generic storefront audit cannot infer.
6. Make a release decision
Collect each customer-visible issue with expected behavior, observed behavior, evidence and recommended action. Then assign one final outcome:
- Ready for handoff: no unresolved issue blocks the agreed journey.
- Ready with warnings: remaining items are documented and accepted for follow-up.
- Fixes required before handoff: a failure blocks purchase or violates an agreed requirement.
A clear decision prevents a long list of checks from being mistaken for approval. Send that decision with a client-ready Shopify handoff report.
Pre-launch checklist questions
When should the final QA pass run?
Run it after product data, theme changes, promotions and required apps are stable, but before final client approval and domain launch.
How many products should be tested?
Test representative risk groups rather than every identical product. Include a simple product, a multi-variant product, a discounted product and any unusual bundle, subscription or app-driven flow.
What makes a store ready for handoff?
The agreed journey works, blocking failures are resolved, accepted warnings have owners and the client receives a clear record of scope, evidence and limitations.