# Keep Password Login Instead of Email OTP

Shopify is moving toward **New Customer Accounts** with **Email + OTP** (one-time code) login instead of classic email + password.\
But some B2B stores still **need** password login for their workflows.

This page explains:

* When it makes sense to keep password login
* What BSS Commerce can do for you
* How to request the **free setup**
* What to expect after it’s enabled

***

**1. When you might want to keep password login**

You may prefer the classic **email + password** login if:

* Your customers are **used to passwords** and log in frequently
* You have **internal or shared accounts** (e.g. staff, distributors) where OTP to personal inbox is inconvenient
* Your B2B workflow or integrations assume a **password-based login flow**
* You want a more “traditional” account system, especially for long-term wholesale customers

New Customer Accounts with Email + OTP are great for security and convenience, but for some B2B scenarios, they can:

* Confuse existing wholesale customers who expect a password prompt
* Make shared or role-based accounts harder to use
* Break existing instructions or training materials you’ve given to partners

That’s why BSS Commerce provides a way to keep a **classic-style password login form**, even as Shopify evolves.

***

2. **What BSS Commerce offers (free service)**

If your store still needs password login, BSS Commerce can:

* Add a **legacy-style password login form** to your theme
* Make sure it uses Shopify’s standard email + password flow
* Integrate it with your **B2B Lock** rules and lock messages
* Tailor it to your current theme layout as much as possible

Key points:

* This setup is **free** for B2B Lock users
* It’s implemented by the BSS Commerce team, not by Shopify
* You can still use B2B Lock’s login-based rules (e.g. “customer is signed in”, tag-based access) as normal

***

**3. How to request password login setup**

To request this:

1. Open **B2B Lock** in your Shopify admin.
2. Use the **in-app chat** or contact support via email:
   * **<support-sbc@bsscommerce.com>**
3. Tell the team you want to **keep password login instead of Email OTP**.

It helps to include:

* Your store URL
* The theme you’re using (e.g., Dawn, custom theme)
* Any special requirements (e.g., “we only want password login on a specific B2B login page”)

The support team will:

* Confirm details
* Implement the custom password login form in your theme
* Ensure B2B Lock’s **Login** buttons or lock messages can point to that password login page

***

**4. What to expect after setup**

After the setup:

* Customers will have access to a **password-based login page** (URL defined during setup).
* B2B Lock’s lock screens can be configured so the **Login button** links directly to that password login page.
* Once a customer logs in with email + password, B2B Lock treats them as **logged-in** like usual:
  * All rules based on “customer is signed in” or tags continue to work.

Some important notes:

* The underlying Shopify direction is still toward **Email + OTP**, so this solution is a **compatibility layer**, not a reversal of Shopify’s roadmap.
* The visual style of the login form will be as close as possible to your theme, but in some cases it may resemble Shopify’s default styling.
* If you change themes later, you may need to **re-apply** or adjust this setup; you can always contact BSS Commerce again for help.

***

**5. Recommended approach**

For most B2B merchants:

* Short term:
  * Use BSS Commerce’s **free password login setup** if your B2B model relies heavily on passwords today.
  * Make sure your lock messages and onboarding instructions match your actual login flow (“Log in with your email and password”).
* Long term:
  * Gradually prepare customers to accept **Email + OTP** as Shopify’s standard.
  * Keep your B2B logic based on **accounts and tags**, so you can later switch login methods without redesigning your access rules.

If you’re not sure which approach is better for your store, you can also ask the support team for **recommendations based on your use case** when you contact them.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-shpf.bsscommerce.com/bss-b2b-lock-login-password-hide-price/customer-accounts-and-login-methods/keep-password-login-instead-of-email-otp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.