My customers can't log in since I switched themes — what broke?

A theme switch shouldn't touch your customer database, but it can easily break the login page itself. Here's how to find out which part actually broke.

customer accountstheme migrationloginaccount pagetheme change

What's going on

A merchant switches themes and the storefront looks fine everywhere except one place: customers suddenly can't log into their accounts. The homepage loads, products display, checkout works, but the account login page either 404s, shows a broken form, spins without submitting, or dumps the customer back at a login screen after they enter correct credentials.

This is confusing because nothing about a theme change should touch the customer database or authentication itself. Shopify stores customer accounts and passwords separately from theme files. The break is almost always in how the new theme renders or links to the account and login experience, not in the accounts themselves. That distinction matters, because it means the fix lives in theme settings and templates, not in a support ticket asking Shopify to restore customer access.

Why it happens

Shopify has two different customer account systems, a classic theme-rendered version and the newer Shopify-managed version, and themes are typically built assuming one or the other. If a new theme was designed around a different account system than the one enabled in Settings, then Customer accounts, the login flow can render incorrectly or send customers to a dead end.

Separately, theme changes routinely drop or restructure the specific templates and sections that power login and registration, or leave navigation menu links pointing at locations that only worked with the old theme's structure. Account-related apps, such as social login, B2B or wholesale gating, and loyalty programs, often rely on app embeds too, and those embeds don't carry over automatically when you switch themes.

5 ways to fix it

1

Confirm which customer account system your store is actually running

Shopify stores run on one of two customer account systems: classic accounts, rendered inside your theme, or the newer Shopify-managed customer accounts, which hand login off to a separate Shopify domain instead of using theme templates. Check Settings, then Customer accounts, to see which one is active, and compare that against what your new theme was actually built for. A theme built for one system can render a broken or dead-end login experience if the store is set up for the other.

2

Open the login link the new theme actually generates, not the old bookmark

In theme preview, click through the header or footer account link the way a customer would, rather than typing a remembered login URL from memory. Themes sometimes hardcode account links in navigation menus or custom code instead of using the theme's dynamic link options, so a copied menu item can point somewhere that only made sense in the old theme. If the link 404s or loops back to the storefront, that points to the menu or link itself, not the customer database.

3

Check for missing or altered account templates and sections after the switch

Theme changes can drop, rename, or restructure the templates and sections that power login and registration, or move the login form into a block that wasn't carried over. If any of that is missing, Shopify falls back to a generic or broken page instead of a working form. Compare the new theme's templates and sections against the old theme's in the theme code editor to see what changed, and rebuild any missing login or registration markup to match the new theme's structure.

4

Re-check third-party login and account apps for compatibility with the new theme

Social login, wholesale or B2B login, and membership apps often inject their own script or override the native login form through app embeds. If those embeds weren't re-enabled after the theme switch, in the theme editor's app embeds panel, the app's login flow can silently stop working while the rest of the storefront looks unaffected. Re-enable and retest each account-related app embed individually after any theme change.

5

Rule out stale sessions and caching before assuming it's the theme

Ask affected customers to try an incognito window or clear cookies for your domain. Old session cookies, or a cached version of the previous theme's account page held by a browser or an intermediary cache, can make login look broken for existing customers while new customers pass through fine. If the problem disappears in a clean browser session, the fix is communicating a cache clear to customers, not a code change.

Bottom line

This is almost always a theme-migration gap rather than a platform bug: either the new theme assumes the wrong customer account system, the login link or template didn't carry over cleanly, or an account-related app's embed wasn't re-enabled. Work through the checks above in theme preview before opening a support ticket, since most of them are visible without touching any customer data. There isn't a dedicated BesPoP app for this one; it's a theme configuration issue best fixed directly in the theme editor or with a developer familiar with your specific theme.

Still Stuck?

Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.