If you woke up one day and found your carefully crafted Shopify login popup was broken, your custom account page was gone, or your clients were calling about a strange new login flow — you are not alone.
In February 2026, Shopify officially deprecated legacy customer accounts. For new stores, the old system is no longer available. For existing stores that had not opted in, it is no longer receiving updates or technical support.
We hit this at Ogresto while building a client store. The popup login we had built — seamlessly branded, smooth UX, no page redirect — broke overnight. Here is everything we learned.
What Shopify Actually Changed
The new system is called New Customer Accounts and it uses OAuth 2.0 with PKCE — the same authentication standard used by Google and Apple. It supports:
- Email OTP (one-time password) — no passwords needed
- Social login (Google, Facebook)
- Proper session management across storefront and checkout
- A hosted login and account page
On paper it is better. In practice it removed a lot of things developers relied on.
What You Actually Lose
No More Popup Login
This is the one that frustrated most developers. Legacy accounts let you build a fully custom login modal — a popup that appeared over the page, kept the customer in context, and felt seamless.
With new customer accounts, Shopify redirects customers to a hosted login page. You cannot intercept this with a popup. You cannot style it beyond basic branding. The customer leaves your storefront, logs in on Shopify's hosted page, and comes back.
It works. But it breaks the seamless experience many stores had built.
No Full Account Page Customisation
Legacy accounts let you build a completely custom account dashboard inside your Liquid theme — order history, saved addresses, loyalty points, all on a page you designed.
New customer accounts use Shopify's hosted account pages. You can add UI extensions, but you are working within their framework, not building freely.
Multipass Is Being Phased Out
If you used Multipass — Shopify's system for passing authenticated users from a custom frontend to checkout without re-login — that is going away. The replacement is the Customer Account API with OAuth flow.
Third-Party App Compatibility
Many apps that hooked into legacy accounts — loyalty programmes, subscription managers, wishlists — need updates to work with the new system. Not all have updated yet.
What You Actually Gain
Most frustrated developers skip this part. But the new system is genuinely better in several real ways.
Email OTP and Social Login
Customers no longer need to remember a password. Login with a one-time email code or Google/Facebook. For most ecommerce stores this reduces login friction significantly. Fewer forgotten passwords = fewer abandoned account creation flows.
Proper Session Management
The legacy system had a known problem in headless setups — customers would log in on the custom frontend and then be asked to log in again at Shopify checkout.
The new OAuth flow maintains the session properly across both. For anyone building custom storefronts this is a genuine improvement.
Better Security
OAuth 2.0 with PKCE is the industry standard for secure authentication in 2026. Shopify made the right long-term call here even if the migration pain was real.
UI Extensions for Account Pages
Shopify has opened the new account pages to UI extensions — custom blocks on the order detail page, profile page, and other sections. The extension system is improving with each release.
Should You Fight It or Accept It?
Most developers fall into one of two camps after dealing with this.
Camp 1 — Accept and Adapt
For most Shopify stores, the new system is fine. The hosted login page is clean, the OTP flow is smooth, and customers adapt quickly. If your store does not have highly complex account requirements — accept the change, implement UI extensions for whatever customisation you need, and move on.
Camp 2 — Work Around It
If you genuinely need a seamless in-page login experience — a heavily branded UX, a complex account dashboard, a B2B store with account-specific pricing — the new system is a genuine constraint. Your options:
Customer Account UI Extensions — build inside Shopify's framework, limited but improving.
Custom Next.js storefront — decouple your frontend entirely and build whatever account experience you want via the Storefront API and Customer Account API. More complex and expensive but full control.
Hydrogen — Shopify's own React framework, purpose-built for headless with tight integration to the new Customer Account API.
For most stores — implement the new system. For stores with genuinely complex account requirements — that is when a headless conversation becomes worth having.
How to Implement It Without Destroying Your UX
Step 1 — Enable on a Development Store First
Go to Shopify Admin → Settings → Customer accounts → Switch to New customer accounts.
Do this on a dev store first. Test the complete login and account flow before touching production.
Step 2 — Update Your Theme Navigation
The account icon in your header needs to link to the correct URL for new customer accounts. Update your header Liquid and check that login, logout, and account page links all work correctly after the switch.
Step 3 — Audit Your Apps
Go through every app touching customer accounts, loyalty, subscriptions, or wishlists. Check each app's documentation for new customer accounts compatibility. Replace or temporarily disable anything incompatible before switching.
Step 4 — Add Your Branding
Settings → Branding in Shopify Admin. Add your logo, brand colours, and a custom header image to the hosted account pages. Not full design control but it makes the hosted pages feel less foreign.
Step 5 — Build UI Extensions for Custom Sections
Need custom content on account pages? Build Customer Account UI Extensions — React-based extensions deployed through the Partner Dashboard. Shopify's developer docs have full guides.
Step 6 — Test the Full Customer Journey
Create a test account and walk through every scenario: new account creation, email OTP login, social login, order history, updating address, logging out. Test on mobile — this is where the hosted page experience is most visible.
Our Honest Take
We were frustrated too. When Shopify deprecated legacy accounts we had a client store with a custom popup login and a complex account dashboard — both needed reworking.
But stepping back — Shopify made the right call. OAuth 2.0 is the correct foundation for authentication in 2026. Email OTP genuinely reduces friction. The double-login problem in headless setups is now actually solvable.
The frustration was about the migration, not the destination.
FAQ
Will legacy customer accounts stop working completely?
Not immediately for stores already using them. No hard shutdown date yet. But technical support has ended — migrate proactively.
Can I still have a login popup?
Not natively. Some developers have tried embedding the hosted page in an iframe popup but it is not officially supported and can break with Shopify updates.
Does this affect SEO?
No. Customer account pages are not indexed by Google regardless of which system you use.
Do I need Shopify Plus?
No. New customer accounts work on all plans.
How do I add custom content to account pages?
Customer Account UI Extensions — Shopify's official React-based framework for custom blocks on the new account pages.
Originally published at ogresto.com
We build custom Shopify stores and themes at Ogresto. If you are dealing with this migration and need help — feel free to reach out.