Start with a specific acceptance list
Describe the customer task the change should improve. For a product-page update, that might be choosing a size, understanding a detail and adding the intended variant to the cart. For navigation, it might be finding a collection from a phone. Keep the intended behaviour concrete enough for someone else to check.
Write down what is included and what should stay consistent. Identify the affected templates, the example products and any market or language differences. This prevents a review from becoming a list of unrelated wishes just before release. Separate a new request from a defect in the agreed change.
Keep a clear reference before editing
Shopify recommends making a backup copy before customising a theme. A duplicate provides a theme reference you can retain while working on the proposed version. Name the copies so the reviewer can distinguish the current reference, the working version and the approved release.
Treat that copy as one part of the release plan. A downloaded theme is not a complete store backup: Shopify says theme downloads exclude store content such as products, collections, menus and pages. Record any accompanying store-data, app or configuration changes separately. A plan to restore an earlier theme should not imply those other changes will be reversed.
Review the journey, including awkward cases
Test the proposed experience with a short list of representative examples. Include a normal product and an unusual one: a long title, multiple options, an unavailable choice or content that occupies more space. Check the route from collection to product to cart, rather than reviewing each component in isolation.
Use both a phone-sized view and a desktop view, and check the relevant interaction on actual devices when possible. Open menus, change options, increase quantities and remove an item. Confirm that labels remain readable and controls remain usable. Screenshots help record appearance; they do not demonstrate that an interaction works.
- Record the page, device and exact steps for each issue.
- State the expected result and what happened instead.
- Attach a screenshot or recording when it explains the problem.
Approve a named version
Give the reviewer one clear version to assess and one acceptance list to follow. Record who approved it and which unresolved items are acceptable to defer. Avoid making unreviewed finishing changes after approval; even a small adjustment can affect wrapping or interaction on another screen.
Before release, confirm the responsible person, a suitable checking window and access to the previous theme. Agree what would justify stopping or reversing the release. This is an operating decision for the store, not a promise that a theme copy can undo every kind of change.
Check the customer-facing version after publishing
Shopify allows one published theme at a time. Publishing another theme moves the previous one into the draft themes area. Confirm that you are publishing the approved version, then open the storefront customers actually visit and repeat the essential journey.
Recheck the changed feature alongside nearby behaviour: navigation, product selection, cart contents and important links. Use a fresh browser session as part of the check so an editor view is not your only evidence. If a material issue appears, follow the agreed recovery decision and record what happened.
Leave a useful release note
A short handoff should say what changed, which version was published, what was checked and what remains open. Keep any follow-up requests separate from the completed scope. Include the date and the person responsible for the next review.
This makes the next maintenance task easier to understand. Instead of relying on a message saying everything is done, the store has a record of the intended behaviour and the checks that supported release. Start your next theme change with that same small acceptance list.