b2b-commerce-store-setup

B2B Commerce Store Setup

This skill activates when a practitioner needs to configure or troubleshoot buyer access on a Salesforce B2B Commerce storefront — including WebStore creation, BuyerGroup assignment, entitlement policy linking, and granting individual contacts the ability to transact.

---

Before Starting

Gather this context before working on anything in this domain:

• Confirm whether the org uses B2B Commerce for Visualforce (legacy) or B2B Commerce on Lightning Experience — the admin UI differs, but the underlying data model (WebStore, BuyerGroup, CommerceEntitlementPolicy) is the same.
• The most common wrong assumption: all contacts under a BuyerAccount automatically inherit storefront access. They do not. Only contacts explicitly assigned the Buyer or Buyer Manager role via a BuyerAccountAccess (contact-level role assignment) can log in and transact. Missing this step causes silent access failures that appear identical to entitlement misconfiguration.
• Hard platform limits that cannot be raised via support case:
  • Maximum 200 BuyerGroups per CommerceEntitlementPolicy.
  • A product entitled across more than 2,000 BuyerGroups per store is silently excluded from storefront search indexing beyond that cap — the product remains visible in Commerce admin but disappears from buyer-facing search.

---

Core Concepts

1. The WebStore → BuyerGroup → EntitlementPolicy Access Chain

The complete access model is a chain of junction objects:

WebStore
  └─ WebStoreBuyerGroup (junction)
       └─ BuyerGroup
            └─ CommerceEntitlementBuyerGroup (junction)
                 └─ CommerceEntitlementPolicy
                      └─ Entitled Product2 records

In parallel, buyer membership flows through:

Account (converted to BuyerAccount)
  └─ BuyerGroupMember  → BuyerGroup
  └─ Contact (assigned Buyer or Buyer Manager role via buyer access record)

A buyer contact can only see and purchase products that are:

1. Part of a CommerceEntitlementPolicy linked to a BuyerGroup
2. Where that BuyerGroup is linked to the WebStore the contact is accessing
3. Where the Account is a member of that same BuyerGroup via BuyerGroupMember
4. Where the contact themselves has an explicit Buyer or Buyer Manager role assignment