From salesforce-commerce
Builds B2B/D2C storefronts with Salesforce Experience Builder: LWR templates, page types (Home, Product, Category, Cart, Checkout), components, themes, navigation, SEO, publishing.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin salesforce-commerceThis skill is limited to using the following tools:
Build B2B Commerce storefronts using Salesforce Experience Builder (formerly Community Builder).
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
Build B2B Commerce storefronts using Salesforce Experience Builder (formerly Community Builder).
Fetch live docs BEFORE writing code:
Web-search the latest:
Web-fetch official sources:
developer.salesforce.com/docs/commerce/salesforce-commerce/guide/experience-builder.htmlhelp.salesforce.com/s/articleView?id=sf.b2b_comm_lightning_storefront_setup.htmdeveloper.salesforce.com/docs/platform/lwc/guide/lwr-get-started.htmlVerify current LWR template structure, standard component catalog, page types, buyer group configuration, and SEO metadata options.
| Feature | LWR (Modern) | Aura (Legacy) |
|---|---|---|
| Performance | Faster, optimized rendering | Slower, heavier framework |
| Standards | Web standards (ES modules, Shadow DOM) | Proprietary component model |
| Components | LWC only | Aura + LWC |
| SEO | Better server-side rendering | Limited |
| PWA support | Progressive Web App capable | No |
| Future | Active development | Maintenance mode |
Always use LWR templates for new B2B Commerce storefronts.
| Page Type | Purpose | Key Components |
|---|---|---|
| Home | Landing page | Hero banner, featured products, category nav, search |
| Product Detail (PDP) | Single product view | Gallery, pricing, inventory, add-to-cart, variations |
| Product List (PLP) | Category/search results | Product grid, filters, sorting, pagination, breadcrumbs |
| Cart | Shopping cart | Line items, quantities, pricing summary, promo codes |
| Checkout | Multi-step purchase flow | Shipping, delivery, payment, review, submit |
| Order Confirmation | Post-purchase | Order number, details, shipping, continue shopping |
| Search Results | Query results | Product matches, filters, sorting, suggestions |
| Account Management | Customer self-service | Order history, addresses, payment methods, profile |
Theme Configuration
├── Company Settings (logo, favicon)
├── Color Palette (primary, secondary, text, bg)
├── Typography (headings, body, font families)
└── Custom CSS (advanced overrides)
Layout components: Header (logo, nav, search, cart, account), Footer (links, contact, social), Sidebar (filters, category tree), Grid System (responsive columns).
Responsive breakpoints: Desktop (1024px+), Tablet (768-1023px), Mobile (<768px). Component visibility can be configured per device type.
Buyer groups are collections of accounts that share product catalog visibility, pricing rules, entitlement policies, and payment terms.
| Concept | Description |
|---|---|
| Product entitlements | Which products each buyer group can see |
| Pricing rules | Group-specific pricing (negotiated, volume, contract) |
| Payment terms | Net 30, Net 60, credit limits per group |
| Guest browsing | Limited catalog, list prices only, no checkout (configurable) |
Use cases: VIP customers, regional buyers, partner tiers (Gold/Silver/Bronze), contract-based pricing.
| Element | Configuration |
|---|---|
| Page title | <title> tag, 50-60 chars, set per page |
| Meta description | Search snippet, 150-160 chars |
| URL slug | User-friendly path (no random IDs) |
| Open Graph tags | Social media sharing metadata |
| Canonical URL | Prevent duplicate content |
| Structured data | Schema.org (Product, Breadcrumb, Organization) |
| Sitemap | Automatic XML generation; submit to Search Console |
Experience Builder supports conditional component visibility:
Custom LWC components are exposed to Experience Builder via js-meta.xml (see sf-b2b-lwc skill for development details):
isExposed: true and target lightningCommunity__Page / lightningCommunity__Default| Stage | Description |
|---|---|
| Draft | Build pages, add components, configure settings (not visible to visitors) |
| Preview | Preview as different user types (guest, authenticated, buyer groups) |
| Publish | One-click publish; changes go live immediately; version history for rollback |
| Activate/Deactivate | Control site availability; set maintenance page when deactivated |
Fetch Experience Builder docs, LWR template guide, and B2B Commerce setup documentation for exact page configuration, component catalog, and buyer group setup before implementing.