Our apps are affected by the ScriptTag deprecation. We’ve already published Checkout and Customer Account Extensions that allow merchants to migrate away from ScriptTags.
I just have a question about the warning banner shown to new merchants.
The migration documentation for partners it sounds like new merchants will still see the warning banner only if you disable script tags for all merchants using your app:
It seems like the only way to remove this warning for new merchants is to break functionality for existing merchants:
If you believe your app no longer requires a display_scope of order_status or all, you can submit the following form and we will update your ScriptTag display_scope to online_store for existing merchants.
This will prevent the banner from being shown for new app installs and will remove your app from the customizations report
Am I reading this right?
Just want to make sure, because at this time it’s not possible to tell if a merchant has set up your app blocks in their theme. We cannot even tell if all of our existing merchants have finished their Customer Account Extension migrations.
So it sounds like, if you want to opt out of this deterring warning banner, you have to break order status script tags for your existing merchants as well by filling out that form - even though there’s no deadline for non-Plus stores to migrate to Customer Extensions at this time, (and Plus is not till August 2025).
Just seems like an unfair punishment for partners that used the ScriptTag system, took the time to migrate to Extensions, only to have a warning on their apps to new merchants and hurt their install rate.
Can we opt out of this banner for new merchants if we no longer provide new merchants with the ScriptTag functionality? That way new merchants are only shown the Extensions option, and this deterring banner isn’t shown to them?
Hi Dylan, I have exactly the same issue . I would like to know some official recommendation from Shopify. We see merchants migrating to new checkout but it needs time and I don’t feel comfortable to break our app for ~40% of our merchants
Thanks for joining Martin, I was mostly worried I was the only one seeing this issue.
We want to make sure merchants have a seamless transition as possible from ScriptTags to Extensions.
And I totally agree with Shopify that starting February, no new merchants should be able to use the ScriptTags functionality. We’re happy to disable that legacy functionality in our apps for new installs.
However, applying this warning banner policy to partners when Shopify itself doesn’t give itself their own deadline for existing non-Plus merchants using ScriptTags seems to be a double standard.
100% agree that if you’ve done everything you need to, your app shouldn’t be penalized, and you shouldn’t be breaking functionality for existing merchants by removing your Script Tags from their shops.
If you’ve implemented Thank you/Order status page UI extensions and/or Web Pixels, merchants won’t see the “Unsupported features” banner on the app install page. This is the behaviour you can expect:
If you have UI extensions: merchants will see a notice letting them know that your app uses new features that are only supported on the new Thank you and Order status page, with a prompt for them to migrate to the new version of these pages so they can leverage your app’s features on these pages
If you only have web pixels: no banner or notice will appear on the app install page, since web pixels are supported on both the legacy and new Thank you and Order status pages
This is what the UI extensions notice will look like:
Thank you for clarifying, that version of the compatibility report screenshot is missing from the documentation about the ScriptTag migration.
So it sounds like the warning banner I shared from the documentation is only for partners that haven’t published any Customer Account Extensions at all:
I see the intent of these banners and I appreciate the differentiation.
Just a small piece of design feedback - they look so similar with the same color and styling, and I had to reread myself several times before I understood that the 2nd message was a good thing.
To play devils advocate, can’t merchant’s be shown a simple message that conveys the same idea?
One example:
Order status & Thank you page app blocks supported
Merchants will be aware of what Customer Account Extension App Blocks are, they just need to know if the app they are installing will provide them.
I just don’t think there’s a need to share a large wordy warning-esque banner if the Partner has published extensions to prepare the merchant for the migration.
I completely agree with @Dylan. I use both script tags and checkout extensions to support merchants using both legacy and new checkouts. In this case, I don’t believe an installation banner is necessary, as we aren’t introducing any disruptive changes for the merchants.
Hey @Dylan and @Axel. For context, the reason this banner is needed is because a merchant needs to be made aware that them being on the legacy version of the TYP/OSP is preventing them from using an app’s features on these pages. With Script Tags no longer being created upon net new installs starting February, the only way for merchants to leverage an app’s features on these pages is for them to upgrade.
Agree the wording/UX needs make it clearer that the issue is on the merchant’s side, not the app’s side. We’ll iterate on this.
Thanks for being open to suggestions @Kenza_Iraki , I really appreciate it. The messaging details seem so small, but they make a huge impact for us and merchants.
That makes total sense, and I agree, some in-dashboard prompts is going to be the best way for merchants to see and understand that they will need to upgrade their TYP/OSP pages.
There will probably be a general banner shown to un-upgraded merchants outside of the App Store/app install context to explain this I assume.
Thank you for this discussion, it helped me better understand the situation with the Script Tag deprecation.
If we’ve published a Customer Account Extension covering functionality previously supported by script tags but ideally would also like merchants still using script tags to keep that functionality for as long as possible, is there any guidance on whether we should complete this google form?
I guess my question is ultimately still the one posed at the beginning, do we have to make a choice between breaking functionality for existing users and having new installs see the banner?
That’s right, we’ll be progressively adding more and more urgency around the migration via banners, notifications etc. in the admin.
The form is only meant to be filled out by apps that:
never meant to have their script tag functionality extend to the order status page (only wanted to target the Online Store but didn’t specify a display_scope, or accidentally used a display_scope of all, or
have completely removed support for their order status page script tags, even for their existing merchants
If existing merchants do rely on your script tags for features on the thank you and order status pages, please do not fill out the form, because that will indeed break functionality for these merchants. If you’ve published a Thank you or Order status extension, you’re good to go, merchants have everything they need from your app to upgrade. The email was only sent out to you to let you know that starting February, no merchants that don’t already have your app installed will be able to use your Script Tags, so if they are still on the legacy Thank you and Order status pages, they will need to upgrade first before being able to use your app’s functionality on these pages, via UI extensions.
We’ve pro-actively placed a banner over functionality in our app for merchants that is using OSP ScriptTags with a link to documentation and a short screencast on how to use TYP/OSP app blocks instead.
But unfortunately we’re still seeing a increase in merchants adopting the OSP ScriptTag functionality. We of course will be disabling this option by Feb 1st for new merchants of course.
But it just shows how difficult it will be to migrate these grandfathered merchants away from this no-extra-steps option.
Once there’s a hard deadline from Shopify about non-Plus stores dropping support for the pre-existing both|order_status tags, then we can communicate more effectively. Right now I don’t believe there’s a deadline set.
. I would like to know some official recommendation from Shopify. We see merchants migrating to new checkout but it needs time and I don’t feel comfortable to break our app for ~40% of our merchants 
Order status & Thank you page app blocks supported