Edge Commerce JournalInfrastructure for the storefront era

November 11, 2026 - Edge Commerce Journal

Shopify New Customer Accounts: What Breaks When Classic Accounts Go Away

New customer accounts replace passwords with a six-digit code sent to the customer's email, and they run on a different set of pages than classic accounts. Anything you customized on the classic account pages, from login and registration to order history, does not carry over, and apps that injected code into those pages stop working there. Audit your account pages now, rebuild the custom pieces as customer account UI extensions, and test the login flow before your customers find the breakage.

Shopify has been moving stores from classic customer accounts to new customer accounts for two years, and the migration is the kind of change that looks cosmetic until it breaks something a customer actually uses. The login page looks similar. The order history looks similar. Underneath, the whole surface is different, and every customization built for the old one stops working.

The core difference is the login itself. New customer accounts are passwordless: the customer enters an email address and gets a six-digit code, no password to create, forget, or reset. That kills password-reset tickets and credential-stuffing attacks in one move. It also kills every password-based flow your store relied on, including any app that assumed a customer had a password to check against.

What actually changes on the page

Classic accounts lived on your storefront theme: customers/login.liquid, customers/account.liquid, and the rest, all editable in Liquid. New customer accounts live on a Shopify-hosted surface at shopify.com, outside your theme. Your theme files for those pages simply stop being used. Any tracking, upsell, or loyalty widget you pasted into the account pages goes dark, and there is no Liquid file to paste it into anymore.

The replacement is customer account UI extensions, small blocks built from Shopify's components that render inside the new account pages. They are the only way to add content to those pages now. If your loyalty program, subscription portal, or returns widget does not ship an extension, it does not appear in the new account area, and your customers will write in asking where it went.

The pieces that break quietly

The quiet breaks are the ones that cost money. B2B buyers who shared one login across a team now each need their own email code. Wholesale pricing apps that keyed off customer tags still work, but only if the tag logic moved with them. Any flow that linked a customer to an external system by password, including some older CRM and email integrations, needs a new key, usually the customer email or the Shopify customer ID.

Order history is the most visible change. Customers see the same orders, but the page is Shopify's, not yours, so your branding, your returns link, and your reorder button all disappear unless rebuilt as extensions. Test the full path yourself: create an account, log in with the code, open an order, and try to start a return. The gaps show up fast when you walk the path a customer walks.

The migration order that works

Start with an inventory, not a switch. List every customization on your classic account pages, every app that touches them, and every integration that keys off a customer password. Then check each vendor: does it ship a customer account UI extension, and does it work on the new surface today? Vendors that have not shipped one are a deadline, not a detail.

Switch in a quiet week and watch the support inbox for a month. The most common tickets are customers who cannot find the login, customers who never receive the code because it lands in spam, and B2B buyers who shared one account. Put the code-login explanation on your login help page before you switch, and tell your support team the answer is in the email, not in a password reset.

Related reading

For the background behind “Shopify New Customer Accounts: What Breaks When Classic Accounts Go Away”, these earlier guides help: How Edge Personalization Works Without Slowing the Storefront Down, Edge Observability: Seeing Storefront Errors Where They Actually Happen, and Image and Font Delivery at the Edge: The Quiet Speed Win.

Frequently asked questions

What is the difference between classic and new customer accounts?

Classic accounts use passwords and live in your theme as Liquid templates you can edit. New customer accounts are passwordless, using a six-digit code emailed to the customer, and they run on a Shopify-hosted surface outside your theme, so theme customizations do not carry over.

Do I need Shopify Plus for new customer accounts?

No. New customer accounts are available on every Shopify plan. The extensions that customize them, customer account UI extensions, are also available across plans, though some apps that build on them may charge separately.

What happens to my loyalty program when I switch?

Anything your loyalty app injected into the classic account pages stops appearing. Check whether the app ships a customer account UI extension for the new surface. If it does not, your customers lose access to their points and rewards inside their account until the vendor ships one.

Can customers still share one account across a team?

Not the way they used to. Each login is tied to one email address and one code, so a shared password no longer works. B2B buyers who shared a login need separate accounts, and any wholesale pricing that keyed off that shared account needs to be re-tested per user.