Skip to content
Request access

One-tap social login for your BigCommerce store

Store Social Login is a BigCommerce app that adds Google, Facebook, X and email code sign-in to a store’s create-account, sign-in and checkout pages, and to the store header. It matches your theme and recognises returning customers.

Request accessSee how it works

18% of US adults who shopped online in the last three months said they had abandoned an order because they did not want to create an account. Source: Baymard Institute, opens in a new tab

  • No theme edits for sign-in or checkout
  • Native BigCommerce accounts
  • No shopper passwords stored

Private rollout: access is by request, and asking commits you to nothing.

  1. The sign-in page opens on the ways your store offers: Google, Facebook, X, an emailed code, or the store's own email and password.
  2. A shopper who would rather type opens the store's own form. Nothing in it is replaced, so your theme's validation still runs.
  3. They type the email address they used before.
  4. The moment they leave the field, the app knows this address already signs in with Google, and offers it, without hiding the password form.
  5. One tap hands them to Google's own account screen.
  6. They land back on your store signed in to the account they already had: same order history, same saved addresses.

From a long sign-up form to one tap.

The sign-up form on Cornerstone’s own demo store asks for 13 things before a shopper has bought anything. Here is that page, then a page with Store Social Login switched on.

  1. The stock Cornerstone demo's create-account form has 13 fields, most of them marked Required. Merchants choose which fields to ask for.
  2. A new shopper starts at the top: their email address.
  3. Then a password to invent. The theme only states its rule when it rejects one.
  4. Then the rest of the page: country, name, street address, city, state, postcode and phone.
  5. Submitting brings back the theme's own password rule, and the shopper is still on the form.
  6. With Store Social Login the page opens on a choice instead, shown here for a sign-up form that needs only a name, email and password. If yours asks for more, your own form finishes the job.
  7. A shopper who already uses Google taps once, and Google's own account screen opens.
  8. They land on their new account, signed in, with no form to fill in and no password to invent.

  • Nothing to type

    When the provider shares a shopper’s name and your sign-up form needs only a name, email and password, a new shopper gets an account without filling in the form.

  • No password rules to fail

    The rule that rejects “Passwords must be at least 7 characters and contain both alphabetic and numeric characters” is never in the way.

  • Your own form stays

    The store’s email and password form is still there for anyone who prefers it, and your theme’s validation still runs.

Make the account an easier yes.

Some shoppers won’t create an account at all, and others are put off by the form, the password rules and the reset email. This gives the second group an easier way in, and leaves guest checkout in place for the first.

18%

of US adults who shopped online in the last three months said they had abandoned an order because they did not want to create an account.
Baymard Institute, opens in a new tabSurvey of 1,026 US adults, “The Current State of Checkout UX”, updated November 2025.

What we do about it:Offer the account in one tap, and keep “Continue as guest” in view beside it.

48%

of consumers surveyed said they had abandoned an online purchase simply because they forgot their password.
FIDO Alliance, opens in a new tabOnline poll of 1,389 adults in five countries, April 2025. Self-reported, and commissioned by the FIDO Alliance, which promotes passwordless sign-in.

What we do about it:A Google tap or an emailed code gets a returning shopper in without a reset email.

  • One customer, one history

    A returning shopper is connected to the account they already have, and past guest orders join it when they sign in, so your customer list stops splitting in two.

  • Every account the app creates starts with a verified email

    The provider has verified the address, or a code has just proved it. A typo in a form field cannot become an account.

A note on expectations

Many people still sign in with a password. Okta’s own data found social login in 14% of logins on its Auth0 platform against 62% for passwords, and Google behind about 73% of social logins across Auth0 and Okta (March 2022 data, not specific to online stores; the whitepaper, opens in a new tab). So this is an easier way in beside your password form and guest checkout, not a replacement for them, and we make no promise about conversion. Measure it on your own store.

Where shoppers can use social login on your store.

Pick a place and watch the whole path. The demos are replicas of a BigCommerce storefront, built from the app’s real screens and wording.

Sign in without leaving checkout. Continue as guest stays wherever your checkout settings allow guests.
  1. Checkout opens on the Customer step as BigCommerce draws it: an email address, Continue, and a link for shoppers who already have an account. Shipping, Billing and Payment wait below.
  2. A shopper types their email address.
  3. BigCommerce finds an account for that address, and the app sees that it signs in with Google. The step says so, offers Google first, and leaves Continue as guest in reach.
  4. One tap hands them to Google, opened on that address. The app accepts only that account for this sign-in.
  5. They land back in checkout signed in. Customer folds to their email with Sign out, the saved address is ready in Shipping, and the Order Summary is as they left it.

Go deeper

Want to see this on your own store?

Private rollout: access is by request, and asking commits you to nothing.

Request access

It offers the way back in that already works.

The moment a shopper leaves the email field, the app checks that address against your store and shows the sign-in that account really uses, so a shopper does not have to remember which they picked last time.

  1. A shopper opens your create-account page and sees the same sign-up choices as everyone else.
  2. They choose to sign up with email, and your theme's own form slides in.
  3. They type an address that already has a password account in your store.
  4. As they leave the field, the app tells them an account already uses it, and offers to sign in, email a sign-in link, or reset the password. The form stays open.
  5. Sign in takes them to the sign-in page, which opens on the password with their address already filled in.

  • A yes or no, never a list

    The lookup answers only whether an address has an account here, and whether it is linked to a provider. It is rate-limited per visitor and per address. Whether an address has an account is already visible on your create-account form and checkout; the provider link is the new bit.

  • Existing customers connect themselves

    When Google has verified the email and exactly one customer in your store has it, the shopper is connected to that customer, and the old password is retired at that moment, so nobody who registered under that address first can keep a working password. A code sign-in proves the address each time but does not retire a password.

  • Their history comes with them

    Past guest orders under the verified address join the account: up to the newest fifty, once your store has approved the Orders: Modify permission. A returning shopper finds their orders in one place.
    How to link guest orders to customer accounts in BigCommerce

No social account? A six-digit code.

For shoppers who don’t use a social account, or would rather not: they type their email, get a code, and type it back. All on your page, no password. Watch it in the Sign in tab above.

  • Ten minutes, once, on that page

    A code works for 10 minutes, once, and only on the page that asked for it. Five wrong tries cancel it.

  • A typo never becomes an account

    On the sign-in page an address with no account gets a message and no email is sent. The create-account page sends to any address, because there a new address is the point.

  • A first visit asks for a name

    On the create-account page, a shopper new to your store confirms the address with the code, then adds a first and last name. If your sign-up form asks for more than that, your own form finishes the job.

  • Your words on the email

    Its wording, the sender’s display name, the reply address, the accent colour and a logo are all yours to set.

The code email in its default wording, for a fictional store.
How a code differs from BigCommerce’s own link

Your store’s look, with a few things that stay ours.

The app borrows your theme’s fonts, text colour and button shape, and lets you word the rest.

The app reads your theme’s own fonts, colours and buttons and does not restyle your store’s own pages or fields. Google’s button is Google’s, the code button is dark until you choose its colours, and the sender address and email layout stay fixed.
  1. A Cornerstone store on its Light variation. The app's choices take the store's own font, text colour and button corners.
  2. On Bold the whole page restyles, and the app's choices restyle with it: they take their look from whichever theme they are in.
  3. Warm changes the fonts and colours again. Google, Facebook and X keep their own brand buttons in every theme.
  4. Choose email and the store's own form opens, in the theme's own fields and buttons. Nothing is replaced, so its validation still runs.

Put your store’s name on Google sign-in: the step-by-step guide

Switch it on from your control panel.

Open the app from your BigCommerce control panel, choose the methods and where they appear, and check what it found. The script goes in through BigCommerce’s Scripts API, so nothing in your theme has to be edited to switch it on.

  1. Open Store Social Login from Apps. It opens inside your control panel with no separate login, and shows Connected.
  2. Each sign-in method has a page of its own. Google is Off until you switch it on, and nothing changes on your store before that.
  3. One switch puts Google in every place your theme has: the sign-in and create-account pages, checkout, the header menu where your theme supports it, and account settings.
  4. The app reads your theme to see which places it has. The sign-in page and create-account page are found, and so is the header menu, because this theme has an account dropdown in its header; checkout and account settings are drawn in the browser or after sign-in, so they are assumed.
  5. Switching the first method on installed a small script on your storefront through BigCommerce's Scripts API. Your theme files are not edited, and the store’s own form keeps its fields and validation: the app hides it behind “Sign in with email” until a shopper chooses it.
  6. Open your sign-in page: Google is there, above your theme's own email and password form. A change reaches your storefront within about a minute.

Your customers stay in BigCommerce.

It signs a shopper in with Google, Facebook, X and email code. BigCommerce still owns the customer, the orders and the session, and the app keeps no copy of your customer or order records.

  1. 01

    Shopper

    Taps a method on your store

  2. 02

    Sign-in provider

    Verifies who they are

    Name, email, account ID

  3. 03

    Store Social Login

    Matches or creates the customer

    Customer ID

  4. 04

    BigCommerce

    Keeps the customer, orders and session

  • Asks each provider for the basics only

    A provider’s standard sign-in scopes. The app reads the account ID, the verified email address and the first and last name, and ignores the rest. It asks for no access to a shopper’s email, files, contacts or payments.

  • Passwords stay out of it

    It never receives a provider’s password and stores no store password. The store’s own password form and recovery stay in BigCommerce. The one password the app handles is the new one a shopper sets when they disconnect Google, passed straight through to BigCommerce.

  • Pre-registered accounts lose their password

    A Google sign-in joins an existing account only when Google has verified the email and exactly one customer in your store has it. The old password is retired at that moment, so an account someone registered earlier under that address can’t keep a working password. An email code proves the address each time, but does not retire a password.

  • A clean exit

    Uninstalling removes your store’s settings, Google client, sign-in address and counters at once. Customer accounts and orders live in BigCommerce and are never touched.
What it asks for, stores and never touches: the full page

What merchants ask first

Straight answers, including the limits. Anything not covered here, ask us.

Which sign-in methods can shoppers use?

Google, Facebook, X and email code. You choose which ones appear, and on which pages: the create-account page, the sign-in page, checkout and the header: an account dropdown where your theme has one, or a small sign-in window from plain Sign in and Register links.

What does it cost, and is it in the BigCommerce App Marketplace?

It is in a private rollout, so there is no public pricing and no marketplace listing yet. Request access and we will tell you where things stand for your store.

How long does setup take?

Switching a method on is a few clicks in the dashboard, and the script installs itself through BigCommerce. We do not publish a setup time, because it depends on what you choose. Putting your own store’s name on Google’s sign-in screen is optional and takes extra steps; the guide for it estimates about 30 minutes.

Do I need to edit my theme?

Not for the sign-in page, the create-account page, checkout or account settings. Store Social Login adds its sign-in options through BigCommerce’s Scripts API. The script finds your theme’s own forms, reuses their styling, and leaves your fields, labels and validation alone. The header menu is the exception: it appears only where your theme’s header account panel carries one specific element the app looks for; the app does not search the theme for a place. Stock Cornerstone does not have it, so there the app leaves the header alone, and the theme scan in the dashboard says “Not found”. The developer guide says how to add the element.

Which themes does it work with?

It is built around Cornerstone, BigCommerce’s open-source base theme for theme developers, and it adopts a theme’s own button and field styles. It has been checked on a small number of themes so far, so tell us yours when you request access; the theme scan shows what it finds. Older Blueprint themes (BigCommerce’s themes from before Stencil) cannot run scripts added through the Scripts API, so they are not supported. Checkout works with the Optimized One-Page Checkout, and a custom checkout can opt in through a documented set of data attributes.

Will shoppers end up with duplicate accounts?

Not for the same email address. When a provider has verified a shopper’s email and exactly one customer in your store has that address, the shopper is connected to that customer and keeps their order history and saved addresses. If several customers share an address, the app does not guess: the shopper signs in with their password first. A shopper who signs in with a different address is a different customer, and duplicates that already exist are left as they are.

What kind of account does a new shopper get?

An ordinary BigCommerce customer account, made with their verified email and name. It has no password until they set one. Accounts the app creates send no BigCommerce welcome email and are not opted in to review or abandoned-cart emails; shoppers opt in themselves.

What happens to an existing customer’s password?

Their account, orders and addresses stay. The first time an existing customer signs in with Google, from anywhere except their account settings, their old password is retired so nobody else can use it. (An email code proves the address each time but does not retire a password.) Password recovery keeps working, and in account settings they can disconnect Google, which asks for a new store password and removes the connection.

Does it work at checkout?

Yes, on the customer step of BigCommerce’s Optimized One-Page Checkout. A shopper who types an email that already has an account is offered the method that account uses, and “Continue as guest” stays wherever your checkout settings allow guests.

What happens to orders a customer placed as a guest?

When a shopper signs in with Google or confirms their address with an emailed code, orders placed as a guest under that verified email join their account, up to the newest fifty, so their history is in one place. Orders already owned by an existing account are never moved. This needs your store to approve the “Orders: Modify” permission.

What is the emailed code?

A six-digit code the shopper types back in the same page, for people without a social account or who would rather not use one. It is valid for 10 minutes, works once, and only on the page that asked for it (reloading the page means asking again).

Can I make it look like my store?

Yes. You can change the wording and colours of the code, email and guest buttons, the code email’s wording, sender name, colour and logo, and choose Google’s button style within Google’s rules. With your own Google client and a sign-in address on your domain, Google’s consent screen shows your address, and your store’s name once Google has verified your brand.

What data does it keep?

BigCommerce stays the system of record for customers, orders and sessions. The app keeps your store’s installation, settings, sessions, hashed identity links and counters, not a copy of your customers or orders. The one personal detail it holds readably is the address a shopper types to receive an emailed code, inside the email that carries it, which the app deletes a week after sending; an email delivery provider sends it. The privacy policy covers both sign-in methods and order access.

Who on my team can change the settings?

The store owner changes sign-in settings. Authorised staff can open the dashboard from the BigCommerce control panel with their existing access. There is no separate login to create.

What if I uninstall it?

Your store’s settings, Google client, sign-in address and counters are removed at once. Customer accounts and orders live in BigCommerce and are never touched. Shoppers’ Google links are kept for 30 days, so reinstalling inside that window finds them still connected.

Does it support more than one storefront?

Today it runs on your store’s primary storefront channel, which is your main storefront.

Who do I contact for help?

Email support@storesociallogin.com with your store’s public URL and a description of the problem. Never send passwords, API secrets or sign-in links.

Does it work with B2B Edition or customer groups?

We do not claim B2B Edition support, and the app does nothing special with customer groups. Ask us about your setup before you rely on either.

Give your shoppers a faster way in.

Store Social Login is in a private rollout, so access is by request. Tell us about your store and we will reply about getting sign-in onto your storefront.

Request accessSee how it works

Asking costs nothing and commits you to nothing. You will need your storefront address and, if you know it, your theme.