Shopify just turned the storefront login into platform-owned territory. As of July 30, 2026, the shopify-account web component is a hard Theme Store requirement, so any theme you submit or update now has to render Shopify's own sign-in surface in the header. For a studio shipping premium Shopify Plus storefronts, that deletes a build task teams have owned for years, and it forces a decision most merchants have been dodging: move to new customer accounts or keep running a login flow Shopify already deprecated.
What changed on July 30
Shopify made its shopify-account web component a mandatory Theme Store requirement effective July 30, 2026, so every theme submitted or updated after that date has to include it. The component is Shopify's own drop-in sign-in surface, and it ships passwordless sign-in, automatic Sign in with Shop recognition, and social sign-in providers out of the box, per the Shopify changelog entry. The rule is specific about placement. The component has to sit in the theme header and stay visible on both desktop and mobile, so a login link buried in a footer or hidden inside a mobile menu no longer passes review. Legacy account templates are no longer required in a theme, because the account model they targeted has been retired underneath them.
shopify-account component vs hand-built login templates
The component is a managed replacement for the account UI theme developers used to build and maintain by hand. A classic Liquid theme carried its own login, register, and account templates, and every studio wired its own markup, validation, and password reset around them. The shopify-account component collapses all of that into one element Shopify owns and updates. The upside is real. Passwordless email codes, Sign in with Shop, and social providers arrive without a single line of auth code in the theme, and Shopify carries the security burden for the highest-risk surface on the store. The cost is control. You style around a component whose internals you no longer own, so heavy custom account flows, bespoke field layouts, and unusual registration steps get harder, not easier. For most premium brands that is the right trade, because the login and account area is rarely where design budget earns its return, and a self-maintained auth surface is a standing liability. When a brand genuinely needs a custom account experience, that work now moves to the Customer Account API and a headless surface rather than the Liquid theme.
New customer accounts vs classic accounts
New customer accounts sign shoppers in with a one-time email code and Sign in with Shop, while classic accounts used a stored password and were deprecated on February 26, 2026. Shopify's note is blunt: classic customer accounts are no longer available to new stores or to existing stores not already using them, feature updates and technical support have stopped, and a final sunset date will be announced later in 2026, per the deprecation changelog. New customer accounts are more than a login change. They bring native store credit, self-serve returns, and B2B support, and they let merchants customize the account area through apps rather than theme code. The shopify-account requirement is the front-of-store half of that shift. Shopify deprecated the old account model in February, and it is now making the new one unavoidable at the theme layer, so a merchant still on classic accounts is running deprecated infrastructure behind a login surface the Theme Store will refuse to certify.
What we would change this quarter
Audit every Shopify theme you maintain for the shopify-account component now, and put any store still on classic accounts on a migration plan before the sunset date lands. Three concrete moves follow. First, add the component to the header on any theme you expect to update or resubmit, and test it on mobile, because header placement and mobile visibility are explicit review criteria. Second, confirm which account model each store runs, since a store still on classic accounts will not get the passwordless flow or Sign in with Shop and is on borrowed time. Third, move any genuinely custom account requirement off the Liquid theme and onto the Customer Account API, which is where bespoke account work belongs once the standard surface is a managed component. We fold this into our Shopify Plus storefront work, and it rhymes with a pattern we flagged when the Customer Account API dropped checkout: Shopify keeps pulling account and identity out of merchant-owned code and into platform-owned components. Plan for the surface you own to shrink, and put your craft where it still moves revenue.