Shopify Customer Accounts on a Framer Storefront in 2026
Shopify customer accounts work with a Framer storefront, but not the way a Liquid theme uses them. Customer accounts are hosted by Shopify on a shopify.com URL with passwordless sign-in, so your Framer site links customers into them rather than rendering them. Order history, saved addresses and returns live on Shopify's side; the entry point, and the design around it, is the part you own.
That split matters more this year than last. Shopify's older email-and-password system is now called legacy customer accounts and is deprecated, while the newer system is on by default for every store created since mid-2024. If your storefront is a Framer site talking to Shopify, the decision is no longer "which account type do I enable" — it is "where does my design end and Shopify's begin."
Customer accounts vs legacy customer accounts
A customer account is the signed-in area where a shopper sees their orders, addresses and payment methods. Shopify now ships two versions of it, and only one has a future.
The newer version is simply called customer accounts. Shoppers enter an email and receive a one-time 6-digit verification code, with no password required. The pages are managed separately from your theme, branded from the checkout and accounts editor, and served from a shopify.com base domain — the default format is https://shopify.com/{your-store-ID}/account, and you can point a subdomain such as account.yourbrand.com at it instead.
Legacy customer accounts are the original email-and-password pages rendered by your Liquid theme. Shopify renamed "classic customer accounts" to "legacy customer accounts" on December 9, 2024, and in the same note was blunt about where this ends:
"Although we have not yet announced a timeline, classic customer accounts will eventually be retired." — Shopify Changelog, December 9, 2024
No sunset date has been published since. Treat legacy accounts as a short-term fallback, not a plan.
Do Shopify customer accounts work with a Framer storefront?
Yes — and a Framer build actually sidesteps the hardest part of the old setup. Because customer accounts are hosted and maintained by Shopify, there is no theme code to port and nothing that breaks when your Framer site changes.
Two facts make the architecture obvious. First, newly created shops have had the newer customer accounts enabled by default since July 31, 2024, so most stores pairing Shopify with Framer in 2026 are already on them. Second, the account pages never needed your frontend in the first place. A Framer site's job is to place the sign-in link, send the shopper to the hosted account URL, and bring them back to a page you designed.
The alternative is building the account UI yourself against Shopify's Customer Account API. That API has been generally available since January 2024 and is the recommended cross-platform way to manage customer data. It is a real option for a Hydrogen or Next.js storefront. It is a poor fit for Framer, because it is an OAuth 2.0 flow that expects a storefront registered as a customer account client — plus somewhere to hold tokens and refresh them. Framer gives you a published site, not a backend.
Which account features are Shopify-hosted and which you must build
Almost everything a shopper expects is already Shopify-hosted; the only common gap is wishlists. "Shopify-hosted" means it already works once accounts are on; "Customer Account API" means it exists but you build the interface; "Build in Framer" means Shopify will not do it for you at all.
| Account feature | Legacy accounts | Customer accounts (hosted) | Available via Customer Account API | Where it lands for a Framer store |
|---|---|---|---|---|
| Login | Email + password, theme-rendered | Email + 6-digit code, no password | Yes (OAuth 2.0) | Shopify-hosted — link out |
| Order history & status | Yes | Yes | Yes | Shopify-hosted |
| Saved addresses | Yes | Yes | Yes | Shopify-hosted |
| Reorder ("Buy again") | No | Yes | Yes | Shopify-hosted |
| Self-serve returns | No | Yes | — | Shopify-hosted |
| Store credit | No | Yes | — | Shopify-hosted |
| Saved payment methods | No | Yes | — | Shopify-hosted |
| Subscriptions portal | App-dependent | Yes — skip, pause, cancel, update payment | App-dependent | Shopify-hosted or app block |
| B2B company profile | No | Yes (works with B2B) | Partial | Shopify-hosted |
| Wishlists | App or custom Liquid | App blocks only | No | App block, or build in Framer |
| Account page branding | Theme settings | Checkout & accounts editor | Full control | Shopify's editor, matched by hand |
Two rows deserve a note. Wishlists are the one genuinely missing piece — Shopify's own comparison treats them as app-block territory rather than a built-in feature, so a Framer store that wants a designed wishlist is building it. And profile editing flipped: in the newer accounts customers change their own name and email, where legacy accounts made them email you.
What does the sign-in link actually look like in Framer?
One link, two decisions. The link itself points at your account URL — the shopify.com/{store-ID}/account default, or your account.yourbrand.com subdomain if you set one up, which is the version worth having on a brand-led site.
The decisions are placement and return path. Put the sign-in entry in the same place on every page, usually the header, and treat "Account" as a nav item rather than a modal, because the shopper is leaving your domain and coming back. Shopify redirects to your store homepage after sign-in, so if you want them to land somewhere more useful, design that landing page deliberately.
Worth knowing: upgrading from legacy accounts redirects old URLs such as /account/login automatically, and the upgrade is reversible within 30 days. That window is your test budget.
Where this leaves checkout and guest buyers
Accounts and checkout are separate problems, and conflating them costs conversions. Most storefronts should keep buying possible without an account at all — the mechanics of that are in our guide to Shopify guest checkout from a Framer site, and what you can and cannot restyle after the cart is covered in what a Framer store can control on Shopify checkout pages.
If you are building against the APIs directly, the account layer is deliberately narrow: Shopify's docs state the Customer Account API "authenticates buyers, not apps," and cap it at 3,000 requests per minute per customer across all apps. Pair that with the product and cart surface described in our notes on the 2026-07 Storefront API changes.
For most Framer and Shopify builds, the honest answer is the boring one. Let Shopify host the account, point a subdomain at it, brand it in the accounts editor, and spend your design effort on the pages that actually sell. Tools like FramerLink exist to keep the product and catalog side of that pairing in sync, which is the half where custom work pays off.
Frequently asked questions
Do Shopify customer accounts work with a Framer storefront?
Yes. Shopify hosts the account pages on a shopify.com URL with passwordless login, so a Framer site links customers into them instead of rendering them. Order history, saved addresses, returns and store credit all live on Shopify's side. Only the sign-in entry point and the surrounding design are yours.
What is the difference between customer accounts and legacy customer accounts?
Customer accounts are Shopify-hosted, use a one-time 6-digit email code instead of a password, and add returns, store credit, saved payment methods and reorder. Legacy customer accounts are the older email-and-password pages rendered by a Liquid theme. Shopify renamed them in December 2024 and has deprecated them.
What is the Shopify customer account URL?
The default format is https://shopify.com/{your-store-ID}/account. You can instead point a subdomain of your own domain at it, such as account.yourbrand.com, which is the better option for a brand-led Framer storefront. Upgrading from legacy accounts redirects old paths like /account/login automatically.
Can I build my own account pages with the Shopify Customer Account API?
Technically yes, but not from Framer alone. The Customer Account API has been generally available since January 2024 and uses an OAuth 2.0 flow that expects a registered storefront client plus somewhere to store and refresh tokens. Framer publishes a site, not a backend, so linking out is the practical path.
Are wishlists included in Shopify customer accounts?
No. Wishlists are not a built-in feature of Shopify customer accounts. Shopify's own feature comparison treats them as app-block territory, so you either install an app that adds a wishlist block to the account page or build the wishlist yourself on the Framer side of the storefront.
Sources
- Customer accounts — Shopify Help Center
- Customer accounts and legacy customer accounts — Shopify Help Center
- New Customer Accounts is now Customer Accounts — Shopify Changelog
- Newly created shops will have New Customer Accounts enabled — Shopify Changelog
- GraphQL Customer Account API — Shopify Dev Docs