Customer accounts changed twice this year. Check yours still works
Customer accounts got two quiet but breaking changes this year. Since June 16, 2026, metafields need a definition before the Customer Account API will read them. Since July 30, 2026, the shopify-account component has been a Theme Store requirement. Neither one throws an error. Things just stop showing up.
That's exactly why they're worth checking on purpose. A broken account page is obvious. A field that silently comes back empty isn't.
What happened on June 16?
Metafields stored on the app resource now need two things before you can access them through the Customer Account API: a metafield definition and customer accounts permissions. Before this, they could be read without either.
If a metafield doesn't have a definition, it stops returning a value. You don't get an error or a warning, just an empty response, and most front-end code shows that as nothing at all.
This affects you if you use customer account UI extensions, run Hydrogen or any other headless storefront, or have an app writing customer data that the account area reads back. The usual casualties are loyalty balances, subscription details, wholesale tiers, saved preferences and B2B account information, because those are exactly the things people keep in metafields.
How do I check?
Log into a real customer account on the live store (your own is fine) and see whether everything that should be there is there. It sounds crude, but it's the fastest reliable test, because you can't see the failure from the admin side. The data is still sitting in the metafield. It just isn't being served.
Pick an account with the most going on, like a subscriber, a loyalty member or a wholesale customer. Accounts with barely anything in them hide the problem.
Then, in the admin, check that every metafield the account area relies on has a definition, rather than just existing as an ad hoc value. If an app owns the metafield, that's a question for the app's developer.
What happened on July 30?
The shopify-account component became mandatory for the Theme Store. Every new theme, and every update to an existing one, now has to include it in the header, visible on both desktop and mobile.
The component itself came out in February 2026 and handles sign-in on the storefront, including passwordless login, automatic Sign in with Shop recognition and social providers.
Does that affect my store or only theme developers?
Strictly speaking, it's a Theme Store submission rule. But it'll affect you the next time you update your theme, because your theme vendor has to comply before they can ship updates.
Keep an eye on this if your theme is customized. If your developers changed the header (and on most established stores, they have), a theme update that adds the component can clash with those changes. Usually that means a duplicate account link, or the component turning up somewhere odd on mobile.
The other thing to check is consistency. The requirement says visible on desktop and mobile, which is a pretty good hint about where themes were getting it wrong before. If your account link disappears below a certain screen width, you're now out of step with where the platform is heading.
What is the ten-minute version of this check?
- Sign in to your storefront as a real customer, on a phone. Make sure the account link is there and works.
- Open the account area and check that every field that should have something in it does, especially anything that comes from an app.
- Do it again with your most complex type of customer: a subscriber, a loyalty member or a B2B account.
- In the admin, check that the metafields behind those fields have definitions.
- Ask any app whose data shows up in the account area whether it's been updated for the June 16 change.
If everything shows up, you're fine and it only cost you ten minutes. If something's blank, it's probably been missing since June.
Why do these matter more than they look?
Customer accounts are where your repeat buyers spend their time, and they're the customers you spent the most to win. A subscriber who can't see their next delivery date doesn't file a bug report. They cancel or email support, and neither of those shows up on a dashboard as "account metafield returned null".
Both are cheap to fix and expensive to ignore. Adding a metafield definition takes a few minutes. Finding out three months later that your loyalty balances have been blank the whole time costs a lot more. The next platform change worth checking the same way is market-driven shipping, which starts rolling out on October 1.
We audit Shopify storefronts, including the account area. It's the part most audits skip, because you have to be logged in as a real customer to see it.