checkout.liquid snippet line for line. Shopify no longer supports that layout for the Information, Shipping, and Payment steps; its Thank you and Order status use was sunset August 28, 2025. Identify the business behavior, then choose a supported checkout UI extension, Shopify Function, web pixel, or native checkout setting.On this page
Why the old tutorial looks convincing
Older checkout customization guides show jQuery page:load handlers, selectors against the checkout form, Shopify.Checkout.step, injected inputs, and CSS overrides. Even Shopify’s historical documentation preserves examples of these techniques with deprecation notices. They describe a previous checkout architecture, not a current deployment recipe. DOM-based checkout modifications were fragile even before Checkout Extensibility because Shopify could change the rendered markup.
Map the requirement to the right layer
| Legacy goal | Modern direction |
|---|---|
| Show explanatory content in checkout | Checkout UI extension at an eligible target; availability depends on plan and target |
| Reject an invalid checkout or cart condition | Cart and Checkout Validation Function where supported |
| Hide, rename, or reorder eligible payment options | Payment Customization Function where supported |
| Change eligible shipping option presentation | Delivery Customization Function where supported |
| Record purchase analytics | Web pixel and customer privacy-aware event handling |
| Change branding | Native checkout editor or supported checkout and accounts configuration APIs |
Some old behavior has no supported one-to-one replacement. For example, arbitrary DOM access and rewriting Shopify-owned checkout fields are not general extension capabilities. Confirm plan requirements, API targets, and checkout settings before committing to a solution.
A practical migration inventory
Search old code for checkout.liquid, Shopify.Checkout, page:load, checkout[attributes], and checkout form selectors. For each occurrence, write down the actual requirement, current data source, checkout step, required persistence, and failure behavior. Build one small proof of concept per capability rather than migrating the entire file at once. If a customization changes price, shipping, or payment eligibility, verify the server-side mechanism instead of trusting UI-only hiding.
How to test this
- Archive the old checkout customization and list each visible or behavioral change.
- Confirm the store’s plan, checkout upgrade status, and extension target availability.
- Build the smallest supported replacement for one behavior.
- Test guest and logged-in checkout, mobile and desktop, accelerated checkout, and relevant markets.
- For validation, test both accepted and rejected carts; for Functions, verify the final checkout outcome.
- Verify order attributes, discounts, shipping and analytics in the created order or downstream system.
- Run a rollback rehearsal and remove obsolete scripts only after replacement verification.

