According to Shopify's documentation, legacy customer accounts were disabled for new stores as of February 26, 2026; Shopify no longer provides feature updates or technical support for this version. In the theme and integration projects we've run at Nodus Works, we've seen this change hit two groups at once: stores that still customize a password-based login page in Liquid, and custom apps that integrate directly into the customer account flow. This guide covers why legacy customer accounts are being phased out, how the new system works technically, and the concrete changes theme and app developers run into during the transition.
Why and When Is Legacy Customer Accounts Shutting Down?
Legacy customer accounts is Shopify's older, password-based customer account system that could be customized through Liquid templates; Shopify closed it off to new stores on February 26, 2026, and stopped shipping updates or support to existing users. According to Shopify's own changelog, the final sunset date will be announced separately within 2026; for now, migration is still optional, but stores that stay on the legacy system don't receive new features or support.
The core reason behind the change is security and infrastructure consolidation. The new customer accounts system runs on the same infrastructure as Shopify's checkout and integrates directly with B2B features and Shop Pay. Password-based login is replaced by a one-time passcode (OTP) sent by email, an architectural choice that eliminates the risk of password leaks and brute-force attacks.
Critical Note: Migration is technically optional today, and you can roll back to the old system within 30 days of upgrading; but according to Shopify's own data, more than 70% of stores have already moved to the new system. Choosing to stay on legacy means staying on infrastructure that no longer receives updates or support.
During migration, existing customer data (order history, address details, account information) is preserved; what changes is the login method and where account pages are hosted. In the legacy system, account pages were part of the theme and edited through Liquid; in the new system, account pages are hosted on Shopify's own separate subdomain.
| Feature | Legacy Customer Accounts | New Customer Accounts |
|---|---|---|
| Login method | Email + password | Email + one-time passcode (OTP) |
| Hosting | Part of the theme (Liquid) | Separate Shopify subdomain |
| Customization | Liquid template editing | shopify-account web component + UI Extensions |
| B2B / Shop Pay integration | B2B not supported at all | Built in, directly integrated |
| Shopify support | Discontinued (as of Feb 26, 2026) | Active development ongoing |
How Does the New Customer Accounts System Work? (OTP, the End of Liquid)
In the new customer accounts system, a customer enters their email address and then signs in using a one-time passcode sent to that address; the step of creating or remembering a password disappears entirely. This flow shares the same underlying infrastructure as Shopify's checkout authentication.
The biggest architectural change is that account pages are no longer part of the theme's Liquid files. In the legacy system, template files like customers/account.liquid and customers/login.liquid were edited inside the theme; in the new system, these pages run in a separate environment hosted by Shopify, and the store owner has no direct access to the Liquid code behind them.
Note: In the new customer accounts, account pages are no longer part of the theme but of a separate surface hosted by Shopify; so customization no longer goes through editing Liquid templates, but through an app-based extension architecture.
The practical result is this: if you want a brand-specific account page experience, say loyalty point display, a custom order status panel, or the kind of per-customer donation tracking we built in the Wear The Peace project, you now have to build it using Shopify's Customer Account UI Extension architecture instead of adding a few lines of Liquid to your theme code. We covered the technical setup of UI extensions step by step in that separate guide; this article focuses less on development steps and more on who the migration affects, when, and how.
According to the Shopify Help Center, styling and branding options in the new system are currently limited; a more advanced visual customization capacity similar to the checkout branding API is planned for a later stage, but for now you shouldn't expect full theme parity beyond basic brand colors and a logo.
Tip: If you've invested in a tightly brand-matched custom design for your account pages, accept that this investment won't carry over one-to-one to the new system, and prioritize accordingly: get the functional migration working first (the login flow itself), then rebuild the visual customization incrementally with UI extensions.
What Changes for Theme Developers? (The shopify-account Web Component)
For theme developers, the most concrete change is that account pages are no longer part of the theme files. According to Shopify's documentation, the old customer account Liquid files (such as customers/login.liquid and customers/account.liquid) should not be included in new themes; they're replaced by a web component called shopify-account.
This web component makes sure the theme's "Log in" or "My account" link correctly routes the customer to the new customer accounts interface. The practical consequence: if you have a custom login form, password reset page, or account panel design built into your theme, those Liquid files won't work in the new system; those sections of the theme need to be removed and handed over to the standard web component.
Critical Note: If you're running a custom theme with customizations on the customer account pages, list out what function each customization serves (for example, a custom "my orders" view) before upgrading the theme. Otherwise, these functions can quietly disappear during migration, and the issue may go unnoticed until a customer flags it.
According to Shopify's official resources, themes that have already completed this migration (including Shopify's current free themes) ship with the shopify-account component by default; on custom themes, adding this component manually and cleaning up the old Liquid files is work the developer needs to do.
What Changes for App Developers? (Customer Account UI Extensions)
For apps that integrate with the customer account flow, the change is more fundamental. According to Shopify's documentation, apps built on the old Liquid pages don't work with the new system; instead, apps need to move to the Customer Account UI Extensions architecture.
Customer Account UI Extensions let developers add modular components to specific areas of the new customer accounts interface, such as the order detail page or the account homepage. These extensions are integrated into the app through Shopify CLI, are optimized for performance with a Preact and remote-dom based architecture, and run inside a sandboxed layer to protect customer data. Extensions can be placed into different target types, block, full-page, and static; static targets can also contain interactive components, they're not limited to purely static content. This means you can choose between adding a small component to an existing page and building an entirely new account experience.
Note: In the old system, an app could inject code directly into a customer account page via Liquid; in the new system, the same function is only possible through a defined extension target, within the boundaries Shopify sets.
According to Shopify's own data, more than 800 apps have already migrated to this architecture. This wide adoption shows that the extension architecture is no longer "experimental", it's now the standard way to build app functionality here.
Critical Note: The new system also drops a few features tied to the old architecture: Multipass (a method for passing passwordless sessions from a custom frontend to checkout) is being phased out, replaced by an OAuth-based Customer Account API flow; some customer triggers and segment definitions in Shopify Flow built around legacy logic need to be reviewed; and custom storefronts that mutate customer data directly through the Storefront API should be prepared for that capability being removed.
| Extension Target | Use Case |
|---|---|
| Block | Adding a small component to an existing account page (such as order details) |
| Full-page | Building an entirely new, brand-specific account page |
| Static | Showing an independent area outside the page's main flow that can still be interactive on its own |
What Should Stores Operating Under Turkish Data Protection Law (KVKK) Consider?
The shift from password login to email OTP is also something stores operating in Turkey need to review under KVKK (Turkey's Personal Data Protection Law). In the OTP flow, the customer's email address is used to send a verification code at every login; this means the purpose and retention period of this data processing need to be accurately reflected in the store's KVKK disclosure text.
Under Turkey's E-Commerce Law (ETK), it's also worth checking whether the consent texts used during membership and account creation (membership agreement, electronic communication consent) are properly carried over into the new account flow. In the legacy system, these consent checkboxes were usually embedded in custom Liquid forms inside the theme; in the new system, where and how this consent is collected is something that needs to be re-evaluated based on the store's existing setup.
Critical Note: This section is a general technical overview, not legal advice. We recommend verifying with your legal counsel, before migrating, whether your KVKK disclosure text and ETK consent flow are compatible with the new customer accounts system.
At Nodus Works, we've observed that stores treating this migration as a purely technical update, skipping the KVKK/ETK side, end up having to fix this detail later during an audit or a user complaint; building this check into the migration project's scope from the start costs less.
If you'd like to plan your store's migration from legacy customer accounts to the new system end-to-end, including theme, app, and KVKK/ETK compliance, we run this work under our Shopify integration solutions and custom app development service; the goal is to keep your existing customer experience and legal compliance uninterrupted while the login flow changes underneath it.
Frequently Asked Questions
When will legacy customer accounts shut down completely?
It was closed off to new stores on February 26, 2026, and stopped receiving updates or support. The final sunset date hasn't been announced by Shopify yet; migration is still optional for now.
Will I lose my existing customer data during migration?
No. Order history, address details, and account information are preserved. What changes is the login method (OTP instead of password) and where account pages are hosted.
My theme has a custom account page design, what happens to it?
Liquid-based custom designs don't work in the new system. Account pages now live on a separate surface hosted by Shopify; you'll need Customer Account UI Extensions for customization.
My app integrates with the customer account page, what should I do?
You need to move your Liquid-based integration to the Customer Account UI Extensions architecture. You can add block, full-page, or static extension targets to your app using Shopify CLI.
Can I customize account pages to match my brand in the new system?
To a limited extent. Basic brand colors are possible, but the kind of comprehensive customization available in the checkout branding API isn't there yet in the new customer accounts; Shopify plans to expand this area later.
Conclusion
The shutdown of legacy customer accounts isn't a theme update store owners can postpone indefinitely, it's an infrastructure shift that Shopify has stopped supporting. Moving to the shopify-account web component on the theme side, moving to Customer Account UI Extensions on the app side, and reviewing KVKK/ETK consent flows against the new system are three separate but connected parts of the migration.
If you'd like to plan this migration around your store's specific theme and app setup, and work out which customizations can move to the extension architecture and which need to be rebuilt, get in touch with Nodus Works; let's plan the migration together without disrupting your existing customer experience.
