# Designing a Clean Locked Experience

A good B2B lock should feel **intentional and helpful**, not like a broken page.

This page focuses on **UX and messaging**:

* What to say on lock screens
* How to avoid dead ends
* How to guide visitors toward the “right” state (login, register, contact)

***

#### 1. Principles of a good locked experience

A clean locked experience should:

1. **Explain what’s happening**
   * “This content is for wholesale customers only.”
2. **Explain what to do next**
   * “Log in” / “Create a wholesale account” / “Contact us”.
3. **Avoid dead ends**
   * Never just say “Access denied” with no path forward.

In other words:

> Every lock message should answer:\
> \&#xNAN;**“Who is this for?” + “How can I become that?”**

***

#### 2. Core messaging patterns

Here are simple, reusable patterns:

**For locked prices**

> **Title:** Login to see prices\
> **Body:**\
> “We reserve pricing for registered customers. Please log in to your account to view prices, or create a wholesale account to get started.”

Buttons:

* “Log in”
* “Apply for wholesale account”

***

**For locked collections**

> **Title:** Wholesale catalog access\
> **Body:**\
> “This collection is reserved for approved B2B customers. If you already have an account, please log in. If not, you can apply for wholesale access below.”

Buttons:

* “Log in to my account”
* “Apply for B2B access”

***

**For locked pages/portals**

> **Title:** B2B portal access only\
> **Body:**\
> “This portal is for our B2B customers and partners. Please log in with your registered email. If you’re interested in becoming a partner, contact us and we’ll be happy to help.”

Buttons:

* “Log in”
* “Contact us”

***

#### 3. Avoiding dead-end pages

Common mistakes:

* Showing a generic “You don’t have permission to view this page” with no actions.
* Using techy or scary language like “Forbidden”, “Error 403”, “Access denied”.
* Not telling users **how** to gain access.

To avoid this:

* Always include at least **one actionable button**:
  * Login
  * Register / Apply
  * Contact
* Avoid jargon. Use simple, friendly language:
  * “Looks like this area is just for our wholesale customers.”

***

#### 4. Consistency with your login model

With Shopify’s newer **Email + OTP** flows and optional password login:

* Use **neutral wording**:
  * “Log in to your account”
  * “Check your email for a login code” (if you want to be explicit)
* Avoid messages that explicitly reference passwords if you mainly use OTP.

Example:

* ✅ “Please log in to your account to continue.”
* ❌ “Enter your password to see prices.” (if your store uses OTP now)

Keep your lock messages, registration pages, and onboarding emails **aligned** so customers are not confused by mixed terminology.

***

#### 5. Microcopy tips

Small wording changes make a big difference:

* Be **friendly** but clear:
  * “This page is for our wholesale customers” vs “You are not allowed here.”
* Be **specific**:
  * “Apply for a wholesale account” vs “Register” (what kind of registration?)
* Add **benefit framing** where appropriate:
  * “Apply for a wholesale account to access special pricing and bulk ordering.”

***

#### 6. Testing with real users

If possible:

* Ask a few B2B customers or colleagues to:
  * Try accessing locked content as a guest.
  * Follow the prompts to get access.
* Ask:
  * “Was it clear who this was for?”
  * “Did you know what to do next?”
  * “Did any messages feel confusing or too technical?”

Then refine your copy in **Step 3 – Advanced settings** accordingly.

***

#### 7. Summary

A clean locked experience is:

* **Clear** – users understand what’s happening.
* **Guided** – they see the next step right away.
* **Consistent** – matches your login and B2B onboarding model.

If you treat your lock screens as **mini landing pages**, not just error messages, you’ll convert the right visitors into **approved B2B customers** instead of scaring them away.


---

# 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/integration-with-other-b2b-apps/best-practices-and-ux-patterns/designing-a-clean-locked-experience.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.