Moving from checkout.liquid to Checkout Extensibility: A Phased Plan
Short answer: Older Shopify Plus stores customised checkout by editing a file called checkout.liquid. Shopify replaced that approach with Checkout Extensibility, where branding comes from checkout settings, extra fields and blocks come from checkout UI extensions, and custom discount, shipping or payment rules run as Shopify Functions. The safest migration is phased: list every customisation, decide which ones still matter, rebuild them one at a time in a development store, test, then publish. Deadlines and eligibility have changed more than once, so as of November 2026 read Shopify's current upgrade notices before you set dates.
Why a phased plan beats a switch-over weekend
checkout.liquid was a single place where anyone could drop in a script, a banner, a gift note field and a tracking pixel. Over years it accumulates items nobody remembers adding. Moving in one go means you rebuild half-understood features under time pressure and may lose conversion tracking in the process.
A phased plan gives you a record of what exists, a ranking of what matters and a rollback at each step.
Phase 1: inventory what the old checkout does
Open the checkout.liquid file and the Additional scripts box in checkout settings. Then build a table with one row per customisation.
| Customisation | What it does | Who depends on it | Replacement route |
|---|---|---|---|
| Logo and colours | Branding | Marketing | Checkout branding settings |
| Order note or gift field | Collects extra data | Fulfilment team | Checkout UI extension or app |
| Tracking pixel | Reports purchases | Ads manager | Customer events or pixel settings |
| Hidden shipping method for some postcodes | Rule logic | Operations | Delivery customisation function |
| Payment method hidden for some carts | Rule logic | Finance | Payment customisation function |
| Trust badges | Visual | Marketing | Checkout UI extension |
Ask each owner whether they would notice if it disappeared. Anything nobody defends can be retired, which makes the project smaller.
Phase 2: sort into three routes
Settings only. Fonts, colours, logo, corner radius, buttons and background can be set in the checkout branding area, with no code.
App or ready-made extension. Many common needs, such as upsells, delivery date pickers or gift messages, already exist as apps built on the extension platform. Compare cost against a custom build.
Custom build. If the requirement is specific to your business, a developer builds a checkout UI extension (for the interface) or a Function (for back-end rules). Extensions run in a sandbox, so they cannot do everything a free-form script could. Check what is possible before promising a stakeholder.
Phase 3: rebuild in a development environment
- Create a development store or use a duplicate of your theme and checkout setup if your plan allows previews.
- Build or install each replacement individually.
- Put each change behind a short review with the person who owns that function, for example the warehouse lead for the gift note field.
- Keep a changelog with the date, what was installed and who approved it.
Avoid batching. If conversion drops after launch, you want to know which change did it.
Phase 4: test the whole checkout like a customer
- [ ] Guest checkout on mobile and desktop.
- [ ] Logged-in customer with saved address.
- [ ] Discount code and automatic discount together.
- [ ] Shipping rate change after address entry.
- [ ] Each payment method, including wallets.
- [ ] Order notes, gift fields and any custom data landing in the order record.
- [ ] Confirmation page, thank-you page and email.
- [ ] Analytics events firing once, not twice.
- [ ] Accessibility checks such as keyboard use and field labels.
Record screenshots against each item. This turns a feeling of it seems fine into evidence.
Phase 5: publish and watch
Publish during a quiet period rather than before a sale. For the first fortnight, compare checkout completion rate, payment errors and support tickets against the previous fortnight, remembering that seasonality will blur it. Keep the change log open and be ready to disable an extension if it misbehaves.
Things that commonly go wrong
Tracking breaks silently. Old scripts that sent purchase events from the confirmation page no longer run in the same way. Replace them with the supported pixel route and verify in your analytics tool with a real test order.
Fields lose their destination. A custom note used to be stored in an order attribute that a printing tool reads. Confirm the new extension saves to the same place or update the tool.
Rules duplicated. A theme script hid a payment option and a Function now does too. The result can be conflicting behaviour. Delete the old logic after the new one works.
Overbuilding. Not every nice-to-have deserves a rebuild. If a feature did not help conversions or operations, retire it.
When to bring in a developer
Branding and standard apps are within reach of a store owner. Functions, extensions with data back to your own systems and anything affecting how orders are priced warrant a developer, plus a staging process. If you are Canadian and have bilingual checkout needs, remember to test both languages, since extension text must be translated too.
A realistic timeline
For a store with a handful of customisations, expect inventory and sorting to take a few days, builds to take a few weeks depending on developer availability, and testing and a monitored launch to take another week. Stores with many scripts take longer. Work backwards from any deadline Shopify has announced for your plan, leave a buffer of a couple of weeks, and avoid scheduling go-live in your busiest trading period. A short written sign-off from marketing, operations and finance at the end of phase 4 keeps responsibility clear if something unexpected turns up later.
FAQ
Do I lose my current customisations at once?
Shopify sets the rules and dates for ending support for the older approach. Read the admin notices and the upgrade guide for your own store rather than relying on a blog summary.
Can non-Plus stores use extensions?
Some checkout features are available more widely and others are Plus only. Check the documentation for what your plan includes.
Will page speed change?
Extensions are hosted by Shopify's platform and load differently from custom scripts. Measure before and after with a real test.
Do we need to rebuild everything?
No. Many stores find they can retire a third of what they had.
If your checkout has accumulated years of tweaks and you want a calm, tested migration, talk to us about an audit.