Migrating Your Store Theme Without Breaking Try-On

Why a Theme Switch Deserves a Try-On Checklist

A theme migration is one of the few store changes that can quietly remove a working feature without anyone touching that feature's settings. Looksy lives in your storefront as a theme app extension — a block you add through the theme editor rather than code edited into template files — and Shopify keeps that kind of placement with the theme it was set up on. Switch themes, and the new theme starts without the block. That is not a flaw; it is how theme app extensions keep your theme code untouched and make a clean uninstall possible. But it does mean a theme project needs a small try-on chapter: re-add the block on the new theme, test on a preview before publishing, and verify after go-live. This post walks that sequence in order. The stakes are simple. Shoppers who used try-on yesterday should find it in the same place tomorrow, and the features around it — size help, bundles, email capture — should come through the migration configured the way you left them.

How the Theme App Extension Behaves

Understanding the mechanics makes the checklist obvious. Looksy does not edit your theme's code. It ships as a theme app extension, which your theme references as an app block placed through the Shopify theme editor. The placement — which template, which section, where on the page — is part of the theme's own settings. Two consequences follow. First, your old theme is never modified, which is why rollback is safe: republishing the previous theme restores the previous state, block and all. Second, a freshly installed theme — from the theme store or your own development work — has no knowledge of where you placed the block before, so the placement has to be made again on the new theme, deliberately, in its editor. App-level configuration is a separate layer from the theme: your plan, size charts, bundle pairings, and email follow-up setup are not theme settings, so a migration should not touch them. But should is doing work in that sentence, which is exactly why the verification pass at the end of this post exists — to confirm rather than assume.

Re-Adding the Block on the New Theme

Do the re-add before the new theme goes anywhere near publishing. Open the new theme in the Shopify theme editor, go to a product page template, and add the Looksy block where you want shoppers to meet it. This is also the moment to make placement a decision rather than an accident: the new theme's product page layout will differ from the old one, and the spot that worked before may not be the right spot now. If your old theme is still installed, keep both editors open and use the old placement as reference — not to copy it exactly, but to remember what you had decided and why. Placement relative to the add-to-cart area, the image gallery, and the size guidance are the relationships worth preserving or consciously changing. Save the changes in the editor, but hold the publish. The next step is testing the unpublished theme with the block in place, and doing the re-add first is what makes that test meaningful.

Test on the Preview Before You Publish

Shopify lets you preview an unpublished theme, and that preview is where the migration earns its confidence. On the preview, run the entire shopper flow as a shopper would: open a product page, upload a photo, wait the roughly 20 seconds, and look at the result. Exercise the on-page controls — retry, feedback, download, share — and check the page on a phone as well as a desktop, since the new theme's mobile layout is effectively a second migration. Walk the surrounding features too. Confirm size guidance appears where you expect on products that have charts, and that any bundle placements sit where the new layout intends them to. One practical caution: theme previews have their own quirks. A preview link can pin your browser session to the draft theme, and what a preview serves is not always identical to what the published theme will. Treat the preview as the rehearsal, not the verdict, and plan to repeat the important checks on the live theme after publishing.

The Post-Publish Verification Pass

Publish the theme, then verify with the same rigor as the preview run, because the published storefront is the only environment that fully counts. The core check is the shopper flow end to end on a real product page: photo upload, a result in about 20 seconds, retry and share behaving normally. Then confirm the features around the flow survived. Size Help should be drawing on your charts. Bundle pairings should render in the new layout as intended. If you use Email Follow-Up, confirm the connection to Klaviyo or Shopify Flow on a fresh capture rather than assuming it. And look at your analytics after some live traffic — try-ons, add-to-carts, and purchases appearing there is the quiet signal that events are flowing normally after the switch. Finally, check in your storefront's language if you sell in more than one. Looksy lists 47 supported languages, but a new theme is a new context — verify what shoppers actually see rather than carrying assumptions over from the old theme.

If Something Looks Wrong

The migration has a built-in safety net: because Looksy never edits theme code, your previous theme is exactly as you left it. If the new theme misbehaves in a way you cannot quickly diagnose, republishing the old theme restores the storefront that worked, try-on included, while you investigate the new theme as an unpublished draft. Most issues at this stage are placement, not breakage. If the block is not appearing, reopen the new theme's editor and confirm the block was added to the template the affected product actually uses — product page templates can be plural, and a block added to one template does not appear on products assigned to another. If the block is placed and the flow still misbehaves, gather specifics before contacting support: which template, which product, what you saw, and on which device. And if you ever need to remove and reinstall the app while troubleshooting, the clean uninstall means no leftover code accumulates in your theme either way.

Facts in this post come from the public Shopify App Store listing for Looksy. Last checked 29 July 2026.