A store switches to New Customer Accounts, and the loyalty tag that used to fire on the old register page simply stops writing.
Orders keep arriving, so nobody notices for a week. Membership and CRM reports show the drop first, and then someone blames the traffic mix. That pattern comes up again and again across Shopify merchant and developer threads, usually after a social-login app that relied on classic Liquid or a custom OIDC connection went quiet.
Before a locksmith changes the front door lock, a careful household gathers every key that opens it: the spare under the mat, the one the neighbour holds, the copy the cleaner keeps on her own ring. Anyone left off that list is locked out on Monday morning.
I call this the key ring count. Every route a shopper uses to create or resume an account is a key, and the switch to New Customer Accounts changes the lock on all of them at once.
The count comes first. The choice of path comes second, and the rebuild list comes third.
Introduction
This article teaches you to map each live Shopify login path against New Customer Accounts, choose native Google or Facebook, Shop, a Plus identity provider, or stay on classic, and list theme or app surfaces to rebuild before sunset. Whether Plus is the right plan for checkout, B2B, and fees belongs in Choosing the Right Shopify Plan.
Hosted account pages you cannot theme sit next to hosted checkout in How to Fix Shopify Accessibility Bugs That Block WCAG AA. Another 2026 platform sunset, the Additional Scripts cutoff, is covered in Shopify Additional Scripts Cutoff on 26 August 2026.
The useful move is a path-by-path map. A blanket revert or a Plus upgrade bought for two buttons skips the keys that still write tags, wallets, and mobile sessions.
Where are all the keys?
Walk the store twice, once as a first-time buyer and once as a returning customer. Include the paths marketing still promotes in email and ads, because those are the keys people forget they handed out.
- Header or drawer Sign in or Account link
- Cart or checkout Sign in chip
- Theme pages that still point at
/account/loginor/account/register - Third-party social buttons (Google, Facebook, Apple, SMS) injected by an app
- Membership, loyalty, or wholesale portals that host their own login
- Mobile app deep links that used Multipass or a shared token
- Popups and landing pages that promised "create an account" and wrote tags or metafields
For each key, write down the URL or app, whether it still works after the switch, which profile fields it writes, and what enrolment side effect it owned, such as newsletter, loyalty, or a B2B company.
Shopify's help centre treats a customer profile in admin as an account already, so anyone with that email can request a one-time code. A broken button can still leave an order behind, which is why new member registrations and first-time checkout completion need measuring apart from paid-order count.
This reflects patterns we see regularly across the Shopify merchant and developer community: the drop shows up in membership and CRM reports first, then someone blames traffic mix.
Why the lock is changing in 2026
From February 2026, Shopify deprecated classic accounts for new stores and for stores that were not already using them. Feature updates and technical support for the legacy version have stopped as well.
A sunset date is due later in 2026. After it, the legacy Liquid files will be locked and then removed, and a brand-new store already has no classic toggle to find.
Shopify now ships two account products under the same admin label, which is half the confusion.
Classic customer accounts (legacy) render login, register, and account pages from theme Liquid, with email and password on your own domain. Apps and custom CSS can attach to those templates, and Multipass on Plus can mint a session from an external system.
New Customer Accounts host sign-in and the account area on Shopify's domain, where the default method is a six-digit email code and sessions can last up to 365 days. Optional methods are Sign in with Shop when Shop Pay is on, and native Google or Facebook social sign-in, while Shopify Plus can replace the whole experience with your own identity provider.
Which lock does your store need?
Every key on the ring ends up in one of four places.
- Stay on classic if the store still has that option, with a rebuild date on the calendar before sunset.
- Switch to New Customer Accounts and turn on native Google or Facebook plus email codes, and Shop if you already run Shop Pay.
- Switch and accept email codes or Shop only, then rebuild the enrolment that used to live on the register page.
- Connect a Plus identity provider when you need Apple, SMS from an app, Multipass-style mobile SSO, or any OIDC source Shopify does not list.
Customer accounts key ring
Five facts decide which place each key goes, and nostalgia for the old password box is the one to leave out of the meeting.
Five facts that place each key
Which sign-in methods buyers already use. Native social on New Customer Accounts covers Google and Facebook only. Apple, SMS OTP from a login app, and a corporate IdP sit behind Plus, while Shop sign-in is available when Shop Pay is active and can prefill checkout.
What the old register page wrote besides a password. Native social syncs the email onto the customer profile, and that is where its job ends. An app hook that tagged VIPs, opted the shopper into a list, or created a loyalty wallet will not replay, so if that hook paid for itself, budget a replacement before you switch.
Whether you still own the HTML. New account pages are hosted, and you change branding in Settings and add Customer Account UI extensions. Once you leave classic, customers/login.liquid is gone, and brands that used the login page as a campaign landing page lose that space.
Headless, Hydrogen, and Storefront API tokens. Shopify is moving customer-scoped data and authenticated actions to the Customer Account API, and Storefront API customer mutations are on a deprecation path. A Hydrogen password form that called customerAccessTokenCreate needs a new OAuth plan.
Plan economics against identity scope. Plus for a custom IdP is the same gate Multipass always had. If you already need Plus for checkout UI extensions or B2B, fold identity into that contract, and if the only gap is Google and Facebook, native social on a lower plan closes it. The fee and checkout half of that call lives in the plan framework, not here.
Checkout that stalls before payment is a different map: start with How to Fix Shopify Checkout Abandonment When Your Funnel Looks Healthy. Plus checkout display versus logic is covered in When to Use Checkout UI Extensions vs Shopify Functions.
Turning native social on takes a few clicks. Open Settings > Customer accounts > Authentication, connect Google or Facebook with credentials from Google Cloud Console or Meta for Developers, and complete a sign-up on a phone from the old button's URL.
Old /account/register links often land on a plain sign-in screen. New Customer Accounts have no separate register page, because the first successful code creates the profile.
Score each key against the four locks
Score each inventoried path against the four options. A path that fails more than one "must have" on native social is a rebuild or a Plus row, rather than a hope that the app vendor will catch up.
| Need | Stay on classic | New accounts: native social + email + Shop | New accounts: email or Shop only | Plus identity provider |
|---|---|---|---|---|
| Available on a brand-new store (from Feb 2026) | No | Yes | Yes | Yes, on Plus |
| Email and password on your domain | Yes | No (email one-time code) | No | Only if your IdP offers it |
| Google or Facebook one-click | Via a third-party app | Native, all plans | Off unless you connect them | Your IdP, or native plus IdP |
| Apple, SMS, or custom OIDC | App-dependent | No | No | Yes |
| Theme Liquid login and register files | Yes, until sunset | No | No | No |
| Loyalty or list enrolment at signup | Often via app on register | Email only unless you rebuild | Must rebuild | Depends on IdP claims and extensions |
| Mobile app shared login (old Multipass) | Plus Multipass | No | No | Plus IdP |
| Shopify support and feature updates | Stopped Feb 2026 | Current product | Current product | Current product |
What has to be rebuilt before you flip it?
Write the rebuild list before the toggle. The admin switch takes minutes, while recovering enrolment and SSO after a quiet week takes a whole sprint.
On the theme, replace hardcoded /account/login and /account/register links with the shopify-account web component, or the current theme account link that already uses it. Remove CSS and scripts that targeted classic customer templates, since Theme Store submissions are moving to that component as a requirement and a Dawn or custom theme that still ships the old files will force an upgrade when you change themes.
On apps, list every integration that injects a login button, a register form, or a customer Access Token. Third-party social login that needed custom OIDC on classic will stay broken on New Customer Accounts unless you are on Plus and the vendor has rebuilt against the Customer Account API. Loyalty and form apps that only listened on customers/register.liquid need a Customer Account UI extension or a form you own, and any app subscription that no longer fires is a cost with no job left. Treat those seats like the unused ones in The Hidden Cost of Running a Shopify Store When 12 Apps Quietly Eat Your Margins.
On headless and custom storefronts, plan the Customer Account API OAuth flow before you promise a date. Embedded apps that used Storefront API @inContext with a classic customerAccessToken need a documented client for the new API, and it is worth confirming the current Partner path for your app type instead of assuming the Headless or Hydrogen channel is the only way to get credentials.
On analytics, annotate the switch date and compare 14 days before against 14 days after. Watch new customer registrations, first-time checkout completion, and loyalty enrolments, because paid-order volume can stay flat while membership acquisition falls, and that is the pattern that sends teams back to classic too early.
On staff comms, password reset emails and "create your account" flows in your ESP still describe the old page. Update those templates the same week you switch, or support tickets will recreate the old URL for you.
What should my store do?
A non-Plus store where Google and Facebook cover the audience can stay on its current plan. Connect native Google and Facebook, keep email codes, turn on Shop sign-in if Shop Pay is already live, and rebuild any register-page enrolment as a Customer Account UI extension or a post-login form. Classic only delays the job here, since sunset will still arrive.
A non-Plus store whose social app also enrolled loyalty or SMS login should hold off on buying Plus at the first meeting. Measure whether native Google and Facebook recover registrations over two weeks first. If the missing piece is Apple, SMS, or a wallet created at the old button, either rebuild that wallet on a page you own or put a Plus IdP on the same roadmap as other Plus work, and revert to classic only while the admin still offers the toggle, with a written sunset date on the ticket.
A Plus store with a mobile app or an enterprise IdP should treat New Customer Accounts as the default and book the identity-provider project as the Multipass replacement. Shared login between iOS, Android, and the storefront belongs to the IdP. Customer Account UI extensions cover order history, profile blocks, and branded account pages that classic Liquid used to fake, but checkout branding still does not paint the account header automatically, so budget account branding apart from checkout UI extensions.
A new store, or one that never used classic, has no classic path at all. Count the keys the same way, then choose native social plus Shop or a Plus IdP, and spend the week on the rebuild list instead of hunting for a hidden legacy toggle.
Conclusion
You can now map each live Shopify login path against New Customer Accounts, choose native Google or Facebook, Shop, a Plus identity provider, or stay on classic, and list the theme or app surfaces to rebuild before sunset. Classic remains a holding pattern for stores that still have the toggle. New Customer Accounts are the product Shopify will keep, and the work is the inventory plus the enrolment rebuild.
Change the lock once you know who holds every key. If the count turns up a social-login app, a Hydrogen token, and a Plus IdP question in the same stack, a Shopify stack assessment will turn the ring into a sequenced rebuild. For a discovery call that starts from the login inventory, use contact.
