Shopify's legacy checkout customisations are gone. Check what stopped working
With the last legacy Thank you and Order status page scripts switched off, some stores have lost tracking, upsells and post-purchase integrations without noticing. Here's what to check.
Shopify's move to Checkout Extensibility is now complete across all plans. The old ways of customising checkout and the post-purchase pages are retired: checkout.liquid, Additional Scripts, and script tags on the Thank you and Order status pages. In their place are checkout UI extensions, web pixels and Shopify Functions.
Most stores migrated on time. Some didn't, and the problem with this change is that nothing visibly breaks. The checkout still works and orders still arrive. What disappears is everything that relied on those scripts.
What tends to fail without anyone noticing
- Conversion tracking pasted into Additional Scripts for ad platforms and affiliate networks
- Post-purchase surveys and "how did you hear about us" widgets
- Upsell or referral offers shown on the Thank you page
- Custom fulfilment or CRM integrations triggered from Order status page scripts
How to check your store
Compare your ad platform conversion counts against Shopify order counts week by week, going back a few months. A sudden drop with no change in sales usually means tracking was lost when the legacy scripts were switched off. Then place a test order and go through the Thank you and Order status pages, checking that everything you expect to see is there.
The fix
Tracking moves to web pixels, configured through the Customer events section of the admin. Visible customisations move to checkout UI extensions, either from the App Store or as custom app extensions. Most rebuilds are small and bounded once you know exactly what was lost.
We audit Shopify checkouts for anything lost in the move to Checkout Extensibility and rebuild it with web pixels and UI extensions.
See Shopify support →Related articles
PHP 8.2 reaches end of life in December. Is your Drupal or WordPress site ready?
PHP 8.2 stops receiving security fixes on 31 December 2026. Here's what that means for Drupal and WordPress sites, and how to plan an upgrade that doesn't break custom code.
20 Oct 2026 · 4 min readPlatform updatesStill on Strapi v4? Planning the move to v5
Strapi v5 changes the content API response format, the Document Service and the plugin system. Here's how to scope the upgrade without breaking your front end.
29 Sep 2026 · 5 min readPlatform updatesDrupal's Experience Builder goes stable — what changes for content teams
Drupal 11.2 ships Experience Builder as a stable, default-on visual page-building layer. Here's what it actually changes for editors, and what site builders need to configure first.
14 Aug 2026 · 5 min readStay ahead of the next release
Security alerts, platform updates and industry analysis — straight to your inbox.