Changing themes is not the same as uninstalling apps. Store-level tools can remain installed while their blocks, embed settings or legacy theme code differ in the replacement theme. Test the behaviour on a real product and in the target theme, not just the app list or a screenshot.
The CSV contains example checks, not test results. Replace the examples with your own products, markets and owners. Keep customer data and credentials out of the file.
1. Identify where each feature lives
- App block: test the templates that actually use it. A review block working on a default product does not prove it is present on a custom product template.
- App embed: open App embeds in the target theme editor. Verify the relevant store default and market settings before testing the browser.
- Theme code: look for vendor snippets or scripts added to the old theme. Do not copy them blindly: confirm whether the vendor now uses an embed or block, and check for duplicate initialization.
- Store-level workflow: identify apps or integrations that also act in checkout, inventory, email or fulfilment. Assign their tests separately; republishing the old theme will not revert those settings.
Shopify's guide to theme apps distinguishes blocks, embeds and code. A public scan can record a baseline on the live site but cannot inspect a private preview or prove a workflow is working.
2. Test representative journeys in the draft
- Product: choose a product with a real review widget or subscription option. Change variants, then add to cart. Confirm the intended variant and selling plan, where relevant, reach the cart.
- Collection: apply a filter and follow a result on mobile. Check that a sold-out variant or an empty result has a usable fallback. Repeat in a representative market if availability differs.
- Cart: update quantity, remove a line and open checkout. If a bundle or discount changes the purchase, verify price and quantities at checkout, not only in the cart drawer.
- Discovery and measurement: compare titles, canonicals and intended structured data on representative URLs. Check the GA4 purchase workflow separately with approved test data.
Use Shopify's theme preview and record the theme, template, product, market and device. Do not assume a change made in a connected app's dashboard is isolated to that draft.
3. Decide whether to configure, build or redesign
Use a block or theme setting for an isolated placement issue. If the feature needs to work across multiple templates and remain editable by merchants, define its states and maintenance before commissioning custom Shopify development. If your team is deciding between a partial redesign, a theme rebuild or a change of platform, see Migraciones.io's Shopify consulting scope. Both service pages are in Spanish.
Give each release-blocking test an owner. Keep the previous theme available and write down which changes, such as a pixel change, would need their own rollback. After publishing, repeat a small smoke test on the public URL.
Editorial note: Detectify features Migraciones.io as a service provider. These references do not affect app matches or confidence labels.