Sign in with Shop, the buyer-facing component that already powers lead capture and customer accounts, is now a drop-in for any storefront app that needs a known buyer, including wishlists, back-in-stock alerts, loyalty, reviews, and more.
This post covers why we expanded Sign in with Shop, what's shipping, how to integrate it, and the best practices to follow so it actually drives conversion in your app.
TL;DR
- You can now use Sign in with Shop as the authentication layer for any storefront app that benefits from a known buyer, including wishlists, back-in-stock alerts, loyalty, reviews, and more.
- Self-serve setup in the Developer Dashboard, a drop-in SDK, and full developer documentation.
- Available now.
The buyer identity gap in storefront apps
Every storefront app that does something meaningful with a buyer hits the same wall: identity. To write a review, send a back-in-stock alert, or deliver a loyalty perk, you need to know who the buyer is. So you build a form, ask for an email, and hope the buyer types something real. A lot of them don't.
That's the cost of every app reinventing identity on the storefront. Buyers get login fatigue. Apps get unverified data. Merchants get a fragmented customer story stitched together from a half-dozen partner databases.
There's already a sign-in buyers recognize across Shopify storefronts: Sign in with Shop. Until recently, it powered one narrow flow: lead capture. We've rebuilt it as a drop-in component any partner can integrate.
Why we built it this way:
- Recognition compounds. Every integration that captures a Shop session raises the recognition rate for every surface that follows, including checkout. The more partner apps integrate, the more recognized buyers you build for.
- One sign-in per store, not per app. The first partner app on a store to authenticate creates the session; other partner apps on the same store skip the prompt. Scopes are additive, so a second app only triggers consent for the incremental scopes it needs.
- Same Developer Dashboard, same credentials. Shop APIs sit alongside Storefront and Admin APIs. No new console, no separate onboarding.
Add verified Shop sign-in with the SDK
Sign in with Shop ships as a generalized authentication layer with three pieces:
- Self-serve OAuth client setup in the Developer Dashboard. Shop APIs are now available alongside Storefront and Admin APIs using the same credentials. You create and manage OAuth clients yourself, with no manual onboarding required.
- A drop-in Sign in with Shop SDK. Embed it in your storefront app's UI the same way you'd embed any other web component. The component handles the sign-in flow, consent, and session creation. You receive a scoped access token when the buyer authenticates.
- A recognition signal you can route on. Read whether Shop already knows a buyer on a store, and show a “Continue as [name]” button instead of running a full sign-in flow. The bigger lever once you ship: fewer prompts, more conversions, less friction for buyers who already use Shop.
What a buyer sign-in gives you
When a shopper taps Sign in with Shop on your app, you stop guessing who they are. You get a verified buyer instead of an email someone may or may not have typed correctly, and you get a recognition signal you can act on. If Shop already knows that buyer on that storefront, route them to your fastest path. If they're new to Shop, they can sign in or create a Shop account in the same flow, and you still end up with a verified buyer at the end of it.
The session your sign-in creates is good across the storefront. The next partner app the buyer touches can read it, which means fewer prompts, less abandonment, and more buyers who actually finish what they started. It works the other way too: when another partner app authenticates first, your app gets a recognized buyer with no auth flow of your own to run.
For the buyer, all of this lands in the Shop app: saved items, restock alerts, and the partner apps they've connected to live in a single place they already use. That continuity is what compounds. Every integration that captures a session raises recognition for every surface that follows, including checkout.
If you're building in this space, this is the moment to integrate.
The integration steps
- Open the Developer Dashboard and create an OAuth client for Shop APIs — the same place you manage your Storefront and Admin credentials.
- Follow the Sign in with Shop SDK quickstart on shopify.dev.
- Choose the scopes you need.
- Embed the SDK in your storefront app's UI.
- Test sign-in end to end in your sandbox, then ship.
Most teams finish in a single sprint. The platform handles the hard parts — identity, consent, session lifecycle, and revocation — so you can focus on what your app does best.
Use recognized buyers across storefront moments
The integration is short. The decisions that determine whether it actually drives conversion happen after you ship. A few rules of thumb:
- Treat it as additive, not a replacement. If you already have a buyer identity layer, keep it. A/B and route based on the recognition signal: Sign in with Shop is the higher-converting path for shoppers who already use Shop, but plenty of buyers will still prefer email.
- Don't auto-trigger on the first page load. Surface the Sign in with Shop button when the buyer is doing something that benefits from a known identity, like saving an item, joining a back-in-stock list, or claiming a reward. Pre-emptive prompts hurt conversion and the recognition brand.
- Plan for the shared session. Your app may not be the first to authenticate on a store. Handle the case where the buyer is already signed in via another partner app, and request only the incremental scopes you need.
- Test the unauthenticated path. Buyers will decline. Make sure your app fails gracefully and falls back to whatever flow you have today.
The storefront identity problem isn't an app problem, it's an industry problem. Every app fighting to capture an email is losing buyers to login fatigue and capturing unverified data when they do get a tap-through.
Sign in with Shop for your storefront app is the way out. You get a verified, recognized buyer. The buyer gets one sign-in that covers every partner app on the store. The merchant gets a stronger customer story without a new admin task.
If you're building in wishlists, back-in-stock, loyalty, or reviews, this is the moment to integrate. Start with the developer docs, and reach out to your Shopify partner manager for direct support.
