Checkout scripts audit
Find out what breaks in your checkout on 26 August 2026
Shopify switches off Additional scripts on the Thank you and Order status pages for Basic, Shopify and Advanced plans. Paste what sits in that field and get a per-script replacement plan.
The code is parsed in your browser. Nothing is uploaded or stored.
What actually changes
The Additional scripts field goes away, the tracking has to move
Who is affected and when
On 26 August 2026 Shopify removes the Additional scripts field and the script boxes on the Thank you and Order status pages for the Basic, Shopify and Advanced plans. Plus stores passed the same milestone on 28 August 2025. Stores that have not migrated by the date are upgraded automatically and the legacy customisations are removed with the upgrade, so doing nothing is itself a decision.
What breaks in practice
Anything sitting in that field stops firing: Google Ads conversion tags, Meta purchase events, Tag Manager containers, affiliate postbacks, review invitations, survey and chat widgets. Purchases keep happening, but the platforms that used to hear about them go quiet. Ad platforms then optimise against incomplete data, which is the expensive part.
Why copying the code into a pixel is not enough
Additional scripts run Liquid on the server, so variables like checkout.total_price are printed into the page before it loads. A web pixel receives a checkout_completed event instead, where the same values live under different names and in different units: the total arrives as a decimal amount rather than cents. Code carried across unchanged usually keeps running without errors and reports the wrong numbers, which is far harder to notice than a crash.
Customer fields are restricted now
Email, phone, customer id and addresses are protected customer data. Since 10 December 2025 they are nulled for pixels that do not have approved access, so a script expecting an email address silently receives an empty value. If your tracking identified customers, the migration is not a copy-paste job: it needs either approved access or a different approach.
How to know the migration worked
The only reliable check is a real test order followed by confirmation in the destination system: the conversion in Google Ads, the single non-duplicated Purchase in Meta Events Manager, the sale in the affiliate network dashboard. Checkout runs in a sandbox, so browser-side debugging tools that used to work on the Thank you page cannot attach to it any more.
FAQ
Questions about the 26 August cutoff
Shopify removes Additional scripts, and the script boxes on the Thank you and Order status pages, for every non-Plus plan. Any JavaScript in those fields stops firing that day, and stores that have not migrated are upgraded automatically with the legacy customisations removed.
Partly. Settings > Checkout shows a warning banner and a review screen that lists your scripts and sometimes suggests a matching app. It does not tell you which replacement fits each individual tag, nor how to confirm the replacement actually reports orders.
The Additional scripts field is not exposed by the Shopify API, and the Thank you page is only visible after a real order. Pasting the code is the only way to analyse it, and it keeps the analysis in your browser.
Two usual causes. Liquid variables such as checkout.total_price do not exist in a pixel and have to be read from the event payload instead, where the amount is already a decimal rather than cents. And customer fields such as email or phone are nulled for pixels without approved access to protected customer data, so the code receives empty values instead of an error.
No. It is an informational tool, not legal or technical advice, and it comes with no warranty that your migration is complete. Always confirm each replacement with a test order.