- What Changes for Shopify Apps on 1 March 2027
- The Three Routes Onto a Shopify Product Page
- What Your Catalogue Needs Before the First Render
- Performance Budget and a Two-Week Rollout
- Frequently Asked Questions
- Conclusion
Most try-on vendors still describe their setup as one line of JavaScript. On Shopify that line is now on a countdown: the direct answer on virtual try-on Shopify integration is that the widget has to arrive as a theme app extension, because Shopify stops injecting script tags into storefronts on 1 March 2027. This post covers the three routes onto a product page, what your catalogue needs before the first render, and how to keep the page fast.
What Changes for Shopify Apps on 1 March 2027
Shopify has set two dates for the script tag API, and the first one has already passed. Since 1 October 2026, the scriptTagCreate and scriptTagUpdate mutations return a user error, so no app can add or change a script tag on a store.
On 1 March 2027, Shopify stops injecting existing script tags into storefronts altogether, according to the Shopify developer changelog. The deprecation applies across all API versions, so pinning an older one buys nothing.
The read side survives. The scriptTags query and the scriptTagDelete mutation still work, which is exactly what an audit needs: list what is injected on your theme today, then decide what to replace.
The question to put to every vendor
Ask each app on your store, in writing, whether its storefront code ships as a theme app extension. A vendor still relying on a script tag cannot install on a new store at all today, and goes dark on your existing one in March. That answer belongs in the integration-cost line of any virtual try-on vendor evaluation.
The Three Routes Onto a Shopify Product Page
Three integration paths matter for a try-on widget, and they are not equivalent.
- App embed block. Shipped inside a theme app extension and switched on by the merchant in the theme editor, under Customise then App embeds. It loads the widget across the storefront without anyone editing theme code. This is how the Klooset try-on widget installs on Shopify.
- App block. Also a theme app extension, but placed inline in a section of the product template. Use it when the entry point has to sit next to the add-to-cart button rather than float above the page.
- Theme code edit. Pasting a snippet into theme.liquid still works and takes the theme off its upgrade path. Shopify lists the Asset Admin API as not recommended, reserved for vintage themes that have no other option.
Shopify's own guidance is explicit: an app submitted to the App Store needs to use theme app extensions to integrate with online store themes, per the Shopify app documentation. Theme app extensions rely on Online Store 2.0 features, so a vintage theme is the one case worth checking before signing anything.
Headless storefronts sit outside this entirely. On Hydrogen or a custom front end built on the Storefront API, you import the widget yourself, the deprecation does not apply, and the integration question becomes where in your own component tree the try-on entry point lives.
What Your Catalogue Needs Before the First Render
Enabling the app embed is the fast part. What actually sets the launch date is catalogue readiness, and it is worth auditing before the contract rather than after.
- Product imagery. A clean garment shot, consistent background, one per colourway. Lifestyle photography shot at an angle renders worse than a flat product image, and that is a merchandising fix, not a vendor fix.
- Variant mapping. The widget has to report which Shopify variant it rendered, or you cannot tie a try-on session to the order and the return that follows it. Without that link, attribution collapses and the pilot proves nothing.
- A size grid per product. A recommendation built on your own measurements beats a generic scale, because your M is not the market's M. The mechanics are in AI Size Recommendation: Fixing Fashion's Biggest Return Driver, and the capability itself in smart sizing.
The third line carries the money. A render answers how a garment looks, not whether to take the M or the L, and fit is where the expensive volume sits.
20% of clothing and 30% of footwear bought online in the EU is returned. Source: European Environment Agency, 2024.
Performance Budget and a Two-Week Rollout
A try-on widget runs on the product page, which is the page your paid traffic lands on. Google treats a Largest Contentful Paint above 2.5 seconds as the line between good and needs improvement, per web.dev, so the widget has no business loading before the hero image.
Two rules keep it honest. Load the try-on bundle on interaction, not on page load, and give the entry point a fixed placeholder so enabling the app does not shift the layout under the add-to-cart button.
Week one, then week two
Week 1 is a preview theme: enable the embed, place the entry point, check the render on the five product types that carry the most GMV, and confirm the variant and analytics events fire. Week 2 is the live run on the top 20% of the catalogue by GMV, with the rest of the catalogue as a holdout.
Instrument three numbers before launch, not after: add-to-cart rate on covered products, size-related returns isolated from other reason codes, and average order value. The payback maths on those three is laid out in Virtual Try-On ROI: The Business Case for Fashion Brands, and the per try-on pricing makes the cost side of that calculation easy to fill in.
If you are checking whether your current try-on app survives March, book a 30-minute demo: we go through your theme, your catalogue and the migration path on your own store.
Frequently Asked Questions
Will a virtual try-on app still work on Shopify after 1 March 2027?
Only if it ships as a theme app extension. Shopify stops injecting script tags into storefronts on that date, so any widget still delivered through the script tag API stops rendering on the product page, with no action from the merchant.
Does a virtual try-on app embed require Online Store 2.0?
Theme app extensions rely on Online Store 2.0 features, so a store on a vintage theme should confirm compatibility before buying. On a current theme, the merchant enables the app embed in the theme editor and no code is touched.
How long does a virtual try-on Shopify integration take?
Two weeks is realistic when the catalogue is ready: one week on a preview theme for placement and event checks, one week live on the top products with a holdout. Catalogue work, mainly imagery and size grids, is what stretches that timeline, not the install.
Conclusion
Virtual try-on Shopify integration stopped being a question of where to paste a snippet. The route is a theme app extension, the deadline is 1 March 2027, and the real work is catalogue readiness and a measurement plan that can tell a return-rate change from a quiet month. To see the migration and the first render on your own products, request a pilot.
