Shopify quietly confirmed last month that its August 28, 2026 deadline for mandatory migration off checkout.liquid — the legacy scripting layer that has powered customized checkout experiences for tens of thousands of Shopify Plus stores since 2013 — will not be extended. The announcement, delivered via a developer changelog update and a follow-up email to Plus accounts, has set off a wave of emergency audits, app migrations, and agency retainer negotiations that insiders say is the largest forced platform upgrade cycle in Shopify’s history.
According to Shopify’s internal partner data, roughly 11,200 active Plus stores were still running at least one checkout.liquid customization as of early June, representing anywhere from simple gift message fields to deeply integrated loyalty redemption flows and B2B pricing logic. For those merchants, the clock is now running at under 80 days.
What exactly is changing — and why does it matter for operators?
Checkout.liquid is being replaced by Checkout Extensibility, a composable architecture built on Checkout UI Extensions, Functions, and the Branding API. Shopify has argued since the 2023 rollout that the new system is more performant, more secure, and better suited to its one-page checkout infrastructure. What it has not argued — and what merchants are now discovering — is that the migration is painless.
The core problem is that checkout.liquid allowed merchants to inject arbitrary JavaScript and Liquid templating directly into the checkout DOM. Checkout Extensibility explicitly does not. That means any customization that relied on DOM manipulation, third-party pixel injection at checkout, or custom form logic built outside Shopify’s app ecosystem needs to be rebuilt using sanctioned extension points — or replaced entirely with a certified app.
- Loyalty integrations: Merchants running Yotpo Loyalty or LoyaltyLion redemption fields directly in checkout need to verify their app versions are Extensibility-certified and reinstall extension blocks via the Checkout Editor.
- Upsell and cross-sell apps: Tools like Zipify OCU and ReConvert have released Extensibility-native versions, but merchants on older installs may be running deprecated code.
- Custom B2B pricing logic: Merchants using Shopify Functions to gate pricing by customer tag are largely fine; those who hardcoded pricing overrides in checkout.liquid are not.
- Address validation and fraud tools: Several address autocomplete and fraud scoring tools used lightweight checkout.liquid injection and have not yet published fully certified replacements.
- Analytics and attribution pixels: Post-purchase and checkout-stage pixels from tools like Northbeam and Triple Whale need to run through the Web Pixels API — a migration that is technically straightforward but operationally easy to miss.
How are Shopify agencies responding to the deadline pressure?
Agency capacity is the immediate bottleneck. Senior Shopify Plus developers who can audit and migrate a complex checkout configuration are billing at $175–$250 per hour, and lead times at top-tier partners like Guidance, Barrel, and Hy-phen have stretched to six weeks for new project starts — meaning merchants who haven’t already engaged a partner are mathematically at risk of missing the deadline without heroic effort.
“We started getting inbound calls in March from merchants who assumed this deadline would get pushed like the last two. It didn’t, and now we’re triaging. Stores with three or four checkout customizations we can move fast. Stores with fifteen? Those are 40-hour projects minimum, and we’re not taking new ones at this point.” — Kara Nishimura, Director of Partnerships, Barrel
Shopify’s own Solutions Engineering team has been running weekly office hours for Plus merchants since May, and the company extended free access to its Checkout Extensibility migration guide — a document it previously gated behind partner credentials — to all Plus accounts in late May. Several agency operators told Ecommerce Times that the guide is thorough but assumes a level of developer familiarity that most in-house ecommerce teams don’t have.
Some agencies have responded by productizing the migration. Austin-based Ethercycle launched a flat-rate checkout audit service at $3,500 that delivers a line-item inventory of every checkout customization and a migration path recommendation within five business days. According to founder Kurt Elster, the offer sold out its first cohort of 12 slots in 48 hours after a single LinkedIn post.
“Merchants don’t actually know what’s living in their checkout.liquid. We’ve seen stores with scripts from agencies they haven’t worked with in four years. The audit alone is valuable regardless of what they do next.” — Kurt Elster, Founder, Ethercycle
Which Shopify apps are certified — and which are still lagging?
Shopify’s App Store now displays a “Works with Checkout Extensibility” badge for certified apps, but the coverage is uneven. As of June 10, the majority of high-volume upsell, subscription, and loyalty apps from established vendors had achieved certification. The gaps tend to cluster in two places: niche B2B tools with smaller engineering teams, and older apps that were built by developers who have since been acquired or gone inactive.
Subscription platforms are a particular watch area. Recharge Payments confirmed Extensibility certification for its standard checkout integration in Q1, but merchants running Recharge’s legacy “Shopify Checkout Integration” path — as opposed to its newer native checkout model — are being urged to migrate within Recharge’s own platform before the Shopify deadline compounds the complexity. Bold Subscriptions, now part of the Bold Commerce suite, published its certification in April.
Gorgias, Klaviyo, and Okendo have all confirmed their post-purchase and checkout-stage integrations are compliant. Attentive’s checkout SMS opt-in widget, which previously ran via a checkout.liquid snippet, has been rebuilt as a certified UI Extension and is available in the current app version — but merchants need to manually remove the old snippet and install the new extension block, a step that Attentive’s customer success team is actively pushing through outreach campaigns.
What happens to merchants who miss the August 28 deadline?
Shopify has been explicit: after August 28, checkout.liquid will no longer render on Plus stores. The file won’t be deleted — merchants will still be able to access it in their theme code — but Shopify’s checkout pipeline will ignore it entirely. That means any functionality dependent on the file simply stops working, silently, on a live checkout.
The risk profile varies dramatically by what a merchant has in checkout.liquid. A store with only a gift message field faces a minor UX regression. A store with custom B2B net-term logic, a loyalty points redemption widget, and an address validation override faces potential checkout abandonment spikes and customer service volume that could disrupt a peak sales period.
“Our biggest concern is the merchants who have no idea this is happening. They’re not reading the developer changelog. They bought a Shopify Plus plan three years ago, had an agency set things up, and assume it’s still running fine. For some of them, August 29th is going to be a very bad morning.” — Marcus Holloway, VP of Merchant Success, Guidance
Shopify has stated it will send additional in-admin notifications to affected stores in the weeks leading up to the deadline, but has not confirmed whether it will implement any grace period or soft-failure mode for stores that miss the cutoff. A Shopify spokesperson declined to comment on whether any exceptions would be made for enterprise accounts.
Is Checkout Extensibility actually better once the migration is done?
Among merchants and agencies that have completed migrations, the technical verdict is largely positive — with caveats. Checkout UI Extensions render inside Shopify’s sandboxed checkout environment, which means they’re subject to the same performance budgets as the checkout itself. In practice, merchants report that extension-based customizations load faster and are less likely to break after Shopify platform updates than their checkout.liquid equivalents were.
The Branding API, which governs fonts, colors, corner radius, and button styling, has matured significantly since its 2023 launch and now gives design teams enough control to satisfy most brand standards without custom code. The main remaining complaint is around layout flexibility — the extension placement system uses defined slots (information banner, shipping method details, order summary, etc.) and does not allow the freeform DOM injection that checkout.liquid permitted.
For DTC brands with complex checkout flows, the functional parity question is real but increasingly manageable. Shopify Functions — which run server-side and are not subject to the same sandbox constraints — handle discount logic, payment method filtering, and shipping customization with more reliability than the JavaScript workarounds many merchants had built in checkout.liquid.
The merchants most likely to feel the loss are those who built genuinely bespoke checkout UX — multi-step flows, custom progress indicators, embedded product configurators — that the current extension slot system can’t replicate. For those use cases, some agencies are pointing clients toward headless checkout architectures built on Shopify’s Storefront API, though that path introduces its own cost and complexity tradeoffs that make it unsuitable as an emergency August solution.
What should Shopify Plus merchants do right now?
The operational checklist that agency leaders are giving their clients breaks down into four immediate steps:
- Audit checkout.liquid today. Pull the file from your theme code and document every customization, snippet, and external script reference. If you don’t have a developer on staff, this is where a flat-rate audit service pays for itself.
- Cross-reference every app against Shopify’s certified list. For any app that touches checkout, confirm in your Shopify admin that the extension block is installed and active — not just that the app is installed.
- Remove deprecated snippets manually. Several app vendors have issued Extensibility-native updates but left old checkout.liquid snippets in place. Those snippets will stop rendering August 28 but may still cause parsing errors or slow checkout load times until removed.
- Test checkout end-to-end in a staging environment after every change, including edge cases like discount code stacking, express checkout paths (Shop Pay, Apple Pay, Google Pay), and any B2B customer tag logic.
For merchants who genuinely cannot complete the migration before August 28, Shopify’s official guidance is to prioritize removing or disabling checkout.liquid customizations rather than leaving them in place — effectively accepting a temporary feature regression in exchange for a stable checkout. That’s a hard sell for revenue-driving features like loyalty redemption, but it’s the safer operational choice compared to a broken checkout on a live store.
The broader lesson that operators and agency leaders are drawing from this deadline cycle is one about platform dependency management: the merchants with the least pain are those who had already adopted a Checkout Extensibility-native stack in 2024 and 2025, when the migration was optional. The ones scrambling now are those who treated a deprecated architecture as a stable foundation. It’s a pattern the industry has seen before, and one that the Hydrogen 3.0 transition is already setting up to repeat.
