What I Keep Finding on Shopify New Customer Accounts

A thread went up on r/shopify at the end of August asking whether anyone who had moved to Shopify's new customer accounts system regretted the decision. The replies reproduced, more or less in order, every argument I have had with a merchant since February. One Shopify Expert said new accounts had improved the setup in every way. One operator called the system basic and awful. A third mentioned losing their main retention program and sounded tired. All three were right, depending on what the merchant had built before Shopify flipped the switch.

I have been through a lot of these migrations now, mostly solo stores at the $5K to $40K monthly range, and I want to write down the pattern I keep seeing. Field notes rather than a how-to.

What I check first on a migrated store

The first thing I look at is whether the merchant knows they migrated. That sounds absurd, but the February 2026 deprecation did not announce itself on every store. A theme swap to Horizon flips the account system silently. A new store spun up this year has only ever known new customer accounts and will not realize the old world existed. The merchant on the call will sometimes insist their account page still renders through their theme. It does not, and the first ten minutes of the call go to proving it.

Second check: whether the login URL is on their custom domain or still on customer.login.shopify.com. If the store has a custom domain configured, Shopify switched them to a branded URL automatically in May 2025. If the store is still on storename.myshopify.com, the Shopify-domain URL is what customers see. I have had merchants on calls who assumed the branded URL applied to everyone and could not understand why their checkout receipts linked to a Shopify-domain login page.

Third check: whether they lost functionality they built on the legacy templates and have not realized yet. Discount-on-registration flows, newsletter opt-in during account creation, subscription portal links added via Liquid, ReCharge or Loop widgets injected into customers/account.liquid. Every one of these is a candidate for "worked yesterday, gone today, nobody told me." I open the storefront on a test customer, click login, click through to the order history page, and watch for the gap between what the merchant expected and what is actually there.

What is gone and what is only moved

Half of the new customer accounts conversations I have are about the difference between these two.

Gone: Liquid access to the account templates. There is no customers/login.liquid to edit. No customers/account.liquid. No code editor path into the hosted login screen. If you built a custom side-by-side login layout in a Wonder theme or a Dawn fork, it is not coming back. One merchant in a February community thread documented their image-plus-form login design being wiped clean by the forced upgrade; the thread's only answer was that this kind of customization is not possible on the new system anymore.

Gone: in-flow newsletter opt-in during account creation. The signup form on customer.login.shopify.com does not expose a marketing consent checkbox. If your account signup was a passive email-list capture, that capture is now zero. The workarounds, which I will come back to, are post-login popups or a separate newsletter section on the storefront. Neither performs as well as the inline checkbox used to.

Gone: the "Continue with Shop" button, functionally. You cannot remove it without disabling Shop Pay, and the conversion math on disabling Shop Pay is bad enough that I have never recommended it to a merchant.

Moved: order history, saved addresses, payment methods, store credit, and subscription-manager links. These still exist, they just render inside the hosted account portal instead of inside your theme. Any app that properly supports Customer Account UI Extensions, the newer app framework released in 2024, can inject its UI as a block in the portal. ReCharge, Loop, Stamped and a handful of others have done the port. Several legacy-era app blocks have not.

Moved: branding. You still have logo, accent color, button style, and (as of July 2025) the sign-in and OTP page text. All of it lives in the checkout and accounts editor rather than in theme code. For most solo merchants, that editor covers the login page. It will not cover anyone who had meaningful theme customization on their old account page beyond color and logo.

Three failure modes that keep catching merchants late

These are the ones that do not surface in the first week.

OTP email deliverability. The new system is passwordless. The one-time code lands in the customer's inbox, or it lands in spam, or it does not arrive at all. The sender email became configurable in November 2024 (Admin > Settings > Notifications > Sender Email), which fixed the branding half of the problem. It did not fix the deliverability half. I have seen stores where repeat customers who had never had a problem logging in suddenly cannot get back into their account. Older customers who do not use their phone for email drop out of the login flow entirely. There is nothing you as a merchant can do about the arriving-in-spam part at the Shopify level; the work is on sender authentication and the warming of your transactional email domain.

App store review for iOS and Android apps. If you are building a mobile app on top of Shopify's Customer Account API, Apple's App Review and Google Play reviewers cannot log in. OTP goes to a real email address they have no access to. Shopify has not shipped a test mode or a static OTP option. The confirmed workaround, from a community thread last September, is to spin up a dedicated Gmail or Outlook mailbox for the reviewers and tell them in your submission notes how to retrieve the code themselves. It depends on the reviewer actually reading submission notes and doing the extra step. One developer I compare notes with hit an Apple 2.1(a) rejection on exactly this and spent a week getting the resubmission accepted.

PayPal email mismatch. When a customer's PayPal email differs from their Shopify account email, new customer accounts can associate the order to the wrong account, or fail to associate it at all. One merchant in a community thread last June disabled PayPal entirely to stop their support inbox filling up with "I cannot see my order" complaints. There is no setting on the Shopify side for this. The practical mitigation is a short line at checkout telling PayPal customers to use their PayPal email address when creating an account, which merchants with any PayPal volume should seriously consider.

What I rebuild first, and what I let go

For a solo merchant who has just completed the move to new customer accounts, this is the order I actually work in.

1. Rebuild the discount-on-registration program using Shopify Flow. "Customer account created" is a trigger. "Send discount code email" is a standard action. A one-page Flow replaces the old Liquid version in about twenty minutes if you are already comfortable in Flow. The customer gets the code in email instead of on the thank-you page. That is a worse funnel, but it is a workable one.
2. Rebuild the newsletter capture as a Klaviyo or Shopify Email post-login popup. The in-flow checkbox is unrecoverable, so stop trying to recover it. The next-best capture point is a one-screen popup the first time a logged-in customer lands on their account page, with a benefits-first message rather than another discount hook.
3. Audit which account-page apps have shipped Customer Account UI Extensions. Install the compatible version of your subscription or loyalty app and remove the legacy integration. For apps that have not shipped CAE blocks after this long, assume they are not going to, and plan around their absence.
4. If a custom domain is not already configured, configure one. The branded login URL is the one piece of merchant-visible branding that comes for free once a custom domain exists.
5. Let go of the hosted-login page look. You will not get back the pixel-level control you had. Match the logo and accent color to your theme, write a sign-in page title that sounds like you, and move on. I used to spend audit calls trying to find clever CSS workarounds. I stopped. There are none, and the hour is better spent on the four items above.

If you want a second pair of eyes on which legacy flows you still need to rebuild on a specific store, a free 15 minutes with a help1 expert is the version of this call I usually have. Bring your legacy template list and the apps you had attached to the old account page.

What I still do not have a clean answer for

Customer Account UI Extensions remain the only self-serve way to get real content onto the account page, and they require either an app that already implements them or a developer who can build one. A June 2026 developer thread confirmed that CAE blocks ignore the Theme Editor's visibility settings; extensions keep rendering on the live page even after being hidden in the editor preview. I have not personally reproduced this on a store I run, so I am taking that developer's word for it, but it is enough reason to test any CAE-based app with a hide-this-block setting before paying for a year of it.

I also do not know whether the OTP email spam issue is improving over time or holding steady. The merchants I talk to who struggled with it last summer are still struggling with it now, but my sample is small and self-selected. If you have measured your login-start to login-complete conversion before and after a sender-domain change, I would be curious to see the numbers; the community threads argue both ways and I have no data of my own worth citing.

And for anything beyond branding - custom profile fields, custom account layouts, a loyalty UI that lives inside the account portal - the honest answer is still: find an app that already does it, hire a developer to build a CAE extension, or move to a headless frontend using the Storefront API and the Customer Account API. I have walked a merchant through the first two paths more than once. The headless route, for a solo store at this revenue size, has never once been worth the rebuild. Related reading: our earlier postmortem on a theme swap that silently flipped a store to new customer accounts covers the "I did not mean to migrate" version of this situation.

The hosted-surface wall is not a bug Shopify is going to patch in the next changelog. It is a direction, and the solo merchants who make peace with it earliest lose the least of their old store on the way through.