Theme development
A Shopify theme prelaunch checklist
Build a repeatable Shopify theme QA record with catalog edge cases, accessibility, performance, app testing and a clear distinction between preview and live.
By Happy Themes · · Prepared with AI assistance and checked against the sources below.
A prelaunch checklist should identify what was checked and where. “The build passed” does not establish that an app works in a hosted preview, and a successful preview does not establish that the same release is live. Keep the evidence attached to an exact version and environment.
Define the release before testing
Record the theme version, preview URL, relevant store settings and the person responsible for the decision. Keep a recoverable copy of the current theme. If your work is an update, identify what changed and which shopping paths those changes could affect.
For example, a change to a finish selector needs product, variant-link and cart checks. A navigation change needs direct entry, mobile menu and keyboard checks. Targeted checks help you investigate the actual change while retaining a basic shopping walkthrough.
Use a catalog with edge cases
Include a product with several options, a sold-out variant, a long title, missing optional content and images with different proportions. Test a collection with useful filters and a search that returns no results. Preview essential app integrations using their intended configuration.
Shopify’s theme testing checklist contains a broader set of functional cases, including work in both the theme editor and storefront. It is a starting point for Theme Store preparation, not a substitute for all current requirements or a promise of approval.
Keep four kinds of evidence
- Code checks. Run the checks appropriate to the implementation. For Liquid themes, Shopify’s Theme Check can find issues in source. It cannot prove every customer interaction works.
- Hosted behavior. Test navigation, option selection, cart edits and the configured apps in the actual preview. Record the URL and date.
- Accessibility. Check keyboard access, visible focus, useful labels and meaningful image descriptions. Shopify’s accessibility guidance also makes clear that following a short set of practices does not guarantee full accessibility.
- Performance. Record the page, device conditions and measurement method. Distinguish a laboratory result from real-user data; neither should be invented when unavailable.
Review content and measurement
Check product claims, image rights, policies, contact routes and availability wording. Confirm that titles, descriptions and navigation describe the actual content. Test analytics with the intended consent settings, keeping controlled QA visits separate from claims about customer demand.
Before publishing AI-assisted work, use the AI design review to catch unsupported claims and unclear responsibilities. Do not let a confident draft replace a source check.
Close the loop after release
Once publication is authorized, verify the deployed version, repeat the essential shopping route and retain a rollback target. Assign unresolved issues an owner and a next action. Mark a check “blocked” or “not checked” when access is missing.
For a Theme Store submission, keep submission, approval and public availability as separate states. Hearthline is currently submitted to Shopify; awaiting review/decision. The existence of a demo, a test result or this checklist does not establish Shopify approval.