> For the complete documentation index, see [llms.txt](https://support.storefront.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.storefront.co.za/release-notes/september-2026/google-sign-in-for-customers.md).

# Google Sign-In for Customers

Customers can now sign in to your storefront with their Google account, configured per store under Login methods.

**This includes:**

* Google as a sign-in option on your storefront
* Configured per store, so you decide which stores offer it
* Client ID and secret entered in the back office, taken from your own Google OAuth client
* An authorised redirect address shown in the back office to paste into your Google configuration

**How it benefits the Merchant**

Fewer customers abandon registration when they do not have to create and remember another password, and you field fewer password reset requests. It also means the email address on the account has already been verified by Google.

**Potential FAQs**

Q: Do customers who already have a password account have to switch?

A: No. Google sign-in is an additional option, and password sign-in continues to work as before.

Q: What do I need before I can switch this on?

A: An OAuth 2.0 Client ID of type Web application from the Google Cloud Console. You then paste its client ID and secret into Login methods under Customer Accounts & Sign-Up.

Q: Customers get a redirect\_uri\_mismatch error. Why?

A: The authorised redirect address shown in your back office has not been added to the Authorised redirect URIs list in your Google OAuth client, or does not match it exactly.