Why did Shopify start forcing automatic Checkout Extensibility upgrades starting January 2026 instead of leaving it opt-in indefinitely?
Shopify began auto-upgrading checkouts on 6 January 2025, not January 2026. The programme applied to Shopify Plus stores still running checkout.liquid on the information, shipping and payment pages, with 30 days of email notice before each upgrade. Shopify's stated reason is fraud control: unsandboxed checkout code makes risk assessment unreliable, so affected stores lost fraud indicators in the admin.
The date in the question is wrong, and the correction is the point
There was no January 2026 forced-upgrade programme. The auto-upgrade started 6 January 2025, and Shopify's wording is direct: "Starting January 6, 2025, we will begin auto-upgrading checkouts that continue to use checkout.liquid" (per Shopify Help Center, September 2026). Each store got 30 days of email notice, and the outcome was blunt: the information, shipping and payment pages reverted to a default state and all checkout.liquid customizations were lost.
The only automatic upgrade running in 2026 is narrower. Stores on the Pause and Build plan are upgraded automatically, and Shopify states the upgrade persists after reactivation (per Shopify Help Center, September 2026). That is not a forced-migration campaign. It is housekeeping for stores that are not trading.
We checked this against the Shopify changelog and the Help Center this session because a wrong year here changes who should have acted and when. If you are auditing a store's history, the year to look for in the mailbox is 2025.
Why Shopify stopped waiting
The escalation ladder Shopify published is unusually specific about its reasoning, and none of it is about aesthetics or developer preference.
From 14 August 2024, Plus stores that had not upgraded lost, in Shopify's own terms:
- Support for checkout.liquid customizations. "Shopify won't provide customer support for updating or fixing checkout.liquid customizations on the Information, Shipping, and Payment pages."
- Payment gateway management. The ability to deactivate a gateway or switch provider was disabled.
- Fraud signals. "Accurate risk assessment becomes unreliable with unsandboxed code executing in checkout, so fraud indicators and recommendations in the admin will no longer be available for new orders."
- Payout speed. "Since orders will be deemed as higher risk, payouts may be delayed by up to 5 days after a transaction is processed."
(All four per Shopify Help Center, September 2026.)
Read those in order and the motive is legible. Arbitrary Liquid running inside the checkout means Shopify cannot reason about the checkout, and a platform that cannot reason about its own checkout cannot underwrite fraud on it or pay out against it with confidence. The unsandboxed-code sentence is the whole argument compressed into one line. Extensibility is not a nicer API; it is a sandbox, and the sandbox is what makes the risk model work.
What actually happens to a store that is not ready on the date
Nothing dramatic happens to the storefront. The checkout keeps taking orders. What you lose is the customization, silently, in a way that mostly shows up in reporting rather than on the page.
- Custom fields, conditional messaging and layout changes revert to Shopify's defaults.
- Anything downstream that parsed those customizations, including some analytics, loses its input.
- Nobody on the team gets an error. The first signal is usually a metric that flattened.
That is the honest failure mode for every date in this family, and it is why the work is worth doing in advance rather than in response.
The one thing Shopify does not do
Shopify has not auto-upgraded actively trading non-Plus stores to the new thank you and order status pages. The 26 August 2026 date is a deadline after which the legacy customizations stop working, not a date on which Shopify rewrites the store for you. A merchant who waited past it has non-working tags rather than replaced pages, which is a different repair job.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Shopify forced this because its fraud model required it, not because the platform wanted tidier code. Once you read the payout-delay clause you can see the commercial pressure: unsandboxed checkouts were a liability on Shopify's balance sheet, not just a support burden.
- What we’ve seen: The stores that got auto-upgraded in 2025 were almost never stores that decided to ignore the deadline. They were stores where the person who owned the checkout had left and the notification emails went to an address nobody read. Deadline exposure is an ownership problem long before it is a technical one.
- Where we disagree: The common read is that Shopify was heavy-handed. We think the opposite, and the evidence is the schedule: a published deadline, then twelve months of degraded-but-working, then 30 days' individual notice. Platforms rarely give that much runway. The complaint worth making is about the communication channel, not the timeline.
- What this page adds: the forced-upgrade year is 2025 rather than 2026, the escalation ladder from 14 August 2024 that preceded it, and Shopify's published reason, which is fraud scoring and payout risk rather than developer experience.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.
Where we worked this out
Our decision records