ARTICLE

Wishlist in Shopify customer accounts

If you are comparing wishlist apps while rolling out Shopify’s new customer accounts, you are really asking one UX question: can shoppers **see and manage saved products inside the account portal, next to orders and addresses, not only as a heart icon in the theme? SaveLayer is built for that: one save engine for the Online Store and Customer Account experiences, with favorites stored as Shopify metaobjects in your admin.

Why new customer accounts change the bar

Shopify’s new customer accounts put a modern, app-like portal in front of logged-in buyers. Once they are used to that layout, a wishlist that only exists in theme code feels out of place. They look for a Saved, Favorites, or Wishlist area inside the account, especially for gift lists, big-ticket consideration, and repeat buyers.

Community threads about favorites in customer account and registry data in account keep saying the same thing: saved products should feel like account data, not a separate gadget.

What to ask when you shop for a solution

Use this as a shortlist while you read app listings and talk to sales:

  • Does it support Customer Account UI extensions (or only the storefront theme)? Theme-only wishlists often never appear where new-account shoppers expect them.
  • Do saves live in Shopify or on the app vendor’s servers? Merchant-owned data in Shopify is easier to trust, export, and automate later.
  • Is it the same list on the storefront and in account? Split systems mean two experiences and two places for support to debug.
  • Does it fit how you sell (B2B, registry, multiple lists)? If you need named lists or contexts, ask whether the product can grow with you (see Choosing a Shopify wishlist app).

How SaveLayer answers for customer accounts

SaveLayer treats wishlists and save lists as first-class Shopify data (metaobjects), not a shadow database on someone else’s infrastructure. On the storefront, shoppers save through the app proxy and theme integration. For new customer accounts, your Customer Account UI extension (built by your team or agency) calls SaveLayer’s customer-account APIs so the same saved items can appear inside the portal: view, remove, and organize flows you design.

That means you can aim for a coherent story: one product powers theme saves and account saves, with data visible in Admin like the rest of your stack (more on ownership in Native wishlist on Shopify).

Sharing (letting friends shop a list without logging in as the registrant) is policy and storefront work you define; SaveLayer holds the saved lines securely per logged-in customer. See Gift registry on Shopify for how we talk about guest-facing pages.

For your developers or agency

SaveLayer uses Shopify’s Customer Account authentication for extensions (session-token exchange, then short-lived SaveLayer access for list and save calls). CORS and channel rules are documented under Authorization and API reference. Plan requirements for customer-account access are listed on Pricing.

Where the shopper is What they expect Common gap SaveLayer direction
Storefront theme One-tap save on products No account home for those saves Theme SDK + app proxy
New customer accounts Saved items beside orders Theme-only apps skip the portal Customer Account APIs for your extension
Headless / Hydrogen Same lists as the rest of the stack Data stuck in a vendor silo Headless channel, same save model
Your team in Admin Visibility into what was saved Opaque third-party storage Metaobjects in Shopify

Next: Pricing, Documentation, Contact us.