Executive summary
- What: Every theme submitted to the Shopify Theme Store, new or updated, must now include the shopify-account component in its header, visible on both desktop and mobile.
- Why: The component standardizes sign-in across storefronts and supports passwordless login, automatic Sign in with Shop recognition, and social providers, which lifts authenticated sessions and personalization coverage.
- Who: Theme developers, agencies maintaining forked or bespoke themes, and any merchant still running legacy customer account templates.
What changed
Shopify introduced the shopify-account web component in February 2026 as an optional way to put account access directly in the storefront header. It is now a Theme Store requirement. Any theme you submit, and any update to a theme already listed, must include the component in the header and render it on both breakpoints.
The component renders an avatar. Signed-out customers get a default icon that opens a sheet with sign-in options and a preview of what sits behind the login, typically Orders and Profile. Signed-in customers see their initial or Shop profile picture. Shopify controls the component and updates it independently of your theme release cycle, so you get styling hooks through CSS parts, CSS variables and a signed-out-avatar slot, but not full markup control over the signed-in state.
The second half of the announcement matters more for existing stores: legacy customer accounts are deprecated. Themes are no longer required to carry legacy customer account Liquid templates, and a store still on legacy accounts that upgrades to a theme without those files is migrated to the current version automatically.
Why it matters
For Shopify Plus merchants the practical gain is session depth. Account access that lives in the header, with passwordless and Shop recognition paths, removes the redirect to a separate login page that has historically leaked intent. More signed-in sessions means more reliable identity for segmentation, faster checkout, and personalization that works on the first pageview instead of the second.
The deprecation carries the risk. If your theme still ships legacy account templates, a routine theme update can trigger an account system migration you did not plan for. Anything bolted onto those Liquid pages, custom loyalty blocks, wholesale gating, referral widgets, needs to be re-platformed onto customer account UI extensions before that happens. We covered the tradeoffs in more depth in our guide to new versus classic customer accounts.
Role-specific impact
- Marketers: Expect a higher share of identified sessions. Revisit email capture flows, because the component offers marketing opt-in at sign-in, and audit any campaign that deep links to legacy account URLs.
- Developers: Add the component behind a shop.customer_accounts_enabled check, wire the menu attribute to your customer account menu, and confirm rendering on mobile. Then inventory every legacy account template in the theme and map each customization to a customer account UI extension.
- Store admins: Confirm which customer account version the store runs before approving a theme deploy. Check that staff runbooks, help articles and order status links still resolve after the switch.
Use-case example
Real-world scenario
A Plus apparel merchant on a heavily forked theme runs roughly 900,000 sessions a month with about 11 percent signed in. Account access sits behind a text link in a collapsed mobile menu. Adding the component to the header on both breakpoints, alongside passwordless and Shop sign-in, typically moves identified sessions into the high teens within a few weeks. The same project surfaces four legacy account templates carrying a custom returns form, which the team rebuilds as a customer account UI extension before the migration rather than after it breaks.
Implementation checklist
- Confirm whether the store runs legacy or current customer accounts, and record the answer before any theme work starts.
- Add shopify-account to the header, guarded by shop.customer_accounts_enabled, and verify it renders on desktop and mobile.
- Style through CSS parts, CSS variables and the signed-out-avatar slot only. Do not fork the signed-in sheet.
- Inventory legacy customer account Liquid templates and list every customization attached to them.
- Rebuild those customizations as customer account UI extensions, then test order history, profile and any gated content.
- Update analytics and consent tagging so sign-in events from the component are captured.
- Ship to a preview theme, QA the full signed-in and signed-out journey, then publish.
FAQ
Q: Does this affect a custom theme that is not listed in the Theme Store?
A: The requirement applies to Theme Store submissions and updates. A bespoke theme is not blocked, but the legacy customer account deprecation applies to every store, so the migration work lands either way.
Q: Will adding the component migrate our customer accounts automatically?
A: The component redirects to the current customer accounts. The automatic upgrade is triggered by moving to a theme without legacy account templates, so treat template removal as the decision point and schedule it deliberately.
Resources
shopify-account component documentation
Need guidance? Talk to Makro.