Hey Erik! I hear this a lot, but the data tells a different story. Most buyers on legacy don’t remember their password anyway. They hit forgot password, land in their inbox, spend a few minutes resetting, then finally get in. The one-time code skips all of that. Inbox once, copy the code, done. In addition, Sign in with Shop gives 200M+ buyers a single tap login. Google and Facebook sign-in are supported too.
1 Like
Can you tell me more about your use case? What does Multipass solve for you?
Hey Anton! This is a great question. Transparently, I don’t have a good solution for you right now. I’d love to learn more about this use case so we can look what a good path here looks like together. Mind DM’ing me with what you’re trying to do, why and how often?
Thanks!
@Ryan_Snape I’d be happy to share my use case, but it seems I can’t DM you. Could you please DM me first? I don’t appear to have the option to message you from my account.
I have a question of my own: In B2B, there are often multiple people responsible for placing orders.
With new customer accounts, since email and password credentials cannot be shared within the company, each person in charge must register their own email address. This results in separate order histories, and setting prices using wholesale apps becomes very time-consuming.
This might be a problem that “Shopify Plus” could solve, but I suspect many merchants don’t feel it’s worth paying the Plus fee.
Is there a workaround available for this situation?
Please don’t force this update, there literally no meaning forcing this. There are trillion of custom logics and design that is running currently through liquid. Changing colors and fonts won’t make the accounts custom designable. This is really bad please allow merchants to be able to use legacy aswell
From our experience with enterprise brands, the new customer accounts setup still feels limiting. Account areas are usually heavily customized (both on the UI and logic side) and so far, that’s only been realistically possible with the legacy liquid approach.
Because of that, making this transition effectively mandatory could be a problem for enterprise use cases. These teams often need full control, and the current model doesn’t seem to offer the same level of flexibility yet.
It would probably make more sense not to force the switch until the new system can cover these deeper customization needs.
Curious how you’re thinking about this on the enterprise side.
forcing this transition doesn’t make any sense for enterprise level merchants since 2.0 still doesn’t support complex customizations, making it impossible to replace existing setups for enterprises needs
For many enterprise-level projects, implementing custom order status logic, advanced data handling, and tailored account experiences is essential. These features go well beyond standard use cases; they are core business requirements that drive a brand’s specific operations.
The new customer accounts model abstracts these areas behind extensions, creating a highly constrained environment. Because of this, the ecosystem is losing the flexibility needed to build custom behaviors, specifically regarding:
-Handling custom order flows and unique status updates
-Executing complex logic during customer data modifications
-Building entirely bespoke account portals driven by brand requirements
UI extensions serve a purpose, but they simply do not provide the foundational control that developers had with Liquid and custom implementations.
Moving to a locked-down model creates a major bottleneck for bespoke development, and brands that require full control over their customer portals will likely find these new limitations unacceptable.
2 Likes
Hey! Want to DM me with some examples of heavily customized legacy accounts so I can see from your perspective, and any notes on what’s not possible with new?
Hey Ryan,
Thanks for the info above, this is helpful to understand the options available.
For some background: I run a Shopify Plus store that operates as an invite-only wholesale store. Customers must have an approved wholesale account to access the site, and classic accounts made this straightforward since we had full control over account creation. We have two clients running off this store, a headless Hydrogen site and a React Native mobile app.
With the new Customer Accounts, the unified sign-up/sign-in flow means anyone can create an account, so I’ll need to enforce access post-authentication, whether that’s via a customer metafield, tag, or potentially a third-party IdP, which I’m also considering.
Beyond the access control question, I’ve hit another issue while exploring the Customer Account API: it doesn’t seem to expose the same depth of order data as the Storefront API. For my account / orders page, I rely on product and variant data from line items, along with product-level and variant-level metafields. I haven’t been able to find equivalents for those fields in the Customer Account API’s order queries.
In the meantime, I noticed that context.customerAccount.getAccessToken() in Hydrogen returns a token that appears to work with my existing Storefront API requests, including the customer and order queries I was already using. My current implementation is actually functioning as expected with this token.
That said, the Shopify docs seem to suggest that using a Customer Account API-issued token to access customer data via the Storefront API isn’t a supported pattern. So I’m not sure if this is a gap in the docs, intentional interoperability, or something that will be blocked down the line.
Is this expected behavior? And if the Storefront API customer queries are eventually deprecated, is there a roadmap for the Customer Account API to support richer line item data (product/variant fields and metafields) on orders?
This is a major concern for enterprise brands and custom builds. Forcing the switch while the new accounts still lack the deep customization power of Liquid creates a huge bottleneck for high-volume merchants. We need the functional freedom that legacy accounts provide to maintain complex business logic.
This update is honestly a bit worrying for us.
We’ve built quite a lot on top of legacy customer accounts — not just design, but actual functionality like custom order pages and fully custom account dashboards.
The new system feels pretty limited for setups like this. App blocks and extensions don’t really give the same level of control.
Right now it’s not clear how we’re supposed to migrate without basically rebuilding everything outside of Shopify.
Are we expected to move all advanced account features to external apps or custom dashboards from now on? Or is there going to be a way to support deeper customization in the new system?
Also, if possible, it would really help if the forced migration — especially for Plus stores — could be reconsidered or at least delayed for more complex setups.
Forcing this update doesn’t make sense. Merchants have countless custom workflows and designs running on Liquid right now. Simply changing colors and fonts won’t make accounts truly customizable. Removing legacy support risks alienating larger brands, who rely on deep customizations. This approach would effectively target only smaller merchants. Please allow merchants to continue using the legacy version.
We are currently witnessing a major shift with the transition to Account 2.0, which is now becoming mandatory for newly created development stores.
While innovation is always welcome, forcing such a transition without flexibility creates serious challenges especially for companies operating at scale.
At Holly Palm, we work with large enterprise brands and have built highly complex systems and integrations over the years. Significant investments both in time and capital have gone into creating advanced workflows, data structures, and operational logic.
With the current direction of Account 2.0, many of these systems are at risk of becoming unusable or heavily compromised.
This impacts critical areas such as:
Customer data & consent management
Custom integrations (especially logistics & ERP)
Brand-specific design and user experience flows
Additionally, in markets with strict local regulations, such transitions can introduce compliance risks that are not easy to mitigate.
What makes this more concerning is the broader ecosystem impact:
Enterprise brands are starting to question platform decisions
New potential clients are becoming hesitant
Long-term investments are being put at risk
We strongly believe that:
Transitions of this scale should not be forced without backward compatibility or flexible alternatives
Ecosystem partners and enterprise users should be part of the decision making process
Stability should be prioritized alongside innovation
Shopify has built an incredible ecosystem and that success is deeply tied to its partners and merchants.
We hope to see a more flexible and collaborative approach moving forward.
Let’s build the future together not at the cost of what has already been built.
Hey Anton as discussed over DM. You should be able authenticate to the Customer Account API via PKCE to obtain an access token that can be used with Storefront API. This tutorial would be a good starting point for how to do that: