Creating B2b Commerce Store
Create Salesforce Commerce B2B stores in the correct order—runtime Commerce Store data before storefront metadata—so solo builders avoid undeployable B2B setups.
Overview
creating-b2b-commerce-store is an agent skill for the Build phase that sequences Salesforce B2B Commerce Store runtime setup before storefront work, covering entitlements, pricing, payments, and catalog integration.
Install
npx skills add https://github.com/forcedotcom/sf-skills --skill creating-b2b-commerce-storeWhat is this skill?
- Explains Commerce Store versus Storefront and why creation order matters for B2B
- Documents runtime WebStore data: buyer groups, entitlements, price books, tax, shipping, payments
- Clarifies Commerce Store records are not Metadata API-deployable unlike storefront components
- Maps standard objects including WebStore, BuyerGroup, EntitlementPolicy, and ProductCatalog associations
- UI-first Commerce app path when backend store configuration must exist before storefront work
- Documents WebStore, BuyerGroup, EntitlementPolicy, CommerceEntitlementProduct, ProductCatalog, and Pricebook2 object rol
Adoption & trust: 580 installs on skills.sh; 513 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are standing up Salesforce B2B Commerce but risk building a storefront before the non-deployable Commerce Store backend exists.
Who is it for?
Solo builders or consultants provisioning a first B2B storefront on an org that already uses Salesforce Accounts and needs account-based entitlements.
Skip if: Greenfield D2C-only Shopify-style shops, teams without Salesforce org admin access, or projects expecting full Commerce Store creation via Metadata API deploy alone.
When should I use this skill?
Planning or implementing a Salesforce Commerce B2B store where Commerce Store backend configuration must precede storefront metadata and deployments.
What do I get? / Deliverables
You leave with an ordered plan to create WebStore runtime data via Commerce UI, wire entitlements and commercial policies, then attach the storefront layer safely.
- Ordered Commerce Store then Storefront implementation checklist
- Entitlement and price book mapping plan
- Runtime versus metadata deployment boundary notes for the agent
Recommended Skills
Journey fit
B2B Commerce assembly is core product construction on Salesforce, not launch SEO or growth analytics, so it sits in Build. The skill navigates org-bound Commerce integrations (payments, tax, catalogs, entitlements) that cannot ship via Metadata API alone, matching integrations.
How it compares
Salesforce B2B sequencing skill, not a generic headless ecommerce theme generator or Stripe-only checkout tutorial.
Common Questions / FAQ
Who is creating-b2b-commerce-store for?
Builders implementing Salesforce Commerce B2B who need agents to respect Store-versus-Storefront boundaries and standard object setup order.
When should I use creating-b2b-commerce-store?
Use it in Build → integrations when configuring a new B2B store, entitlements, and commercial policies before connecting a storefront experience.
Is creating-b2b-commerce-store safe to install?
It describes privileged org configuration; check the Security Audits panel on this page and use least-privilege Salesforce users before letting an agent drive Commerce admin steps.
SKILL.md
READMESKILL.md - Creating B2b Commerce Store
# Commerce Store vs Storefront: Technical Reference ## Overview Understanding the distinction between Commerce Store and Storefront is critical for successful Commerce B2B development. This document provides technical details about these two components and explains why they must be created in a specific order. --- ## The Two Components ### 1. Commerce Store (Backend Data) **What it is:** - Runtime data and configuration created in the Salesforce org - NOT source-controllable metadata - Created through Commerce app UI **What it includes:** - Store configuration and settings - Default buyer groups (associated with Accounts) - Entitlement policies (who can see which products) - Pricing policies and price book mappings - Payment gateway configuration (Stripe, Adyen, etc.) - Tax provider configuration (Avalara, Vertex, manual) - Shipping methods and configurations - Product catalog associations - Inventory locations - Search index configurations **Where it lives:** - Data records in standard Commerce objects: - `WebStore` - Store settings and configuration - `BuyerGroup` - Account-based buyer segments - `EntitlementPolicy` - Product visibility rules - `CommerceEntitlementProduct` - Product-policy associations - `ProductCatalog` - Catalog definitions - `Pricebook2` - Price books - Additional payment, tax, shipping records **How to create:** - Via UI: Setup → Commerce → Stores - Cannot be created via Metadata API - Cannot be deployed via `sf project deploy` --- ### 2. Storefront (Frontend Metadata) **What it is:** - Digital Experience (LWR site) for buyer-facing shopping experience - Source-controllable as ExperienceBundle metadata - Created automatically when you create a Commerce Store **What it includes:** - ExperienceBundle metadata (`StorefrontName.digitalExperience-meta.xml`) - URL routing configuration (`sfdc_cms__route`) - Page definitions (`sfdc_cms__view`) - Homepage - Product List Pages (PLP) - Product Detail Pages (PDP) - Shopping cart - Checkout flow - Order confirmation - Search results - Lightning Web Components (product cards, cart components, checkout) - Branding and theme configuration (`sfdc_cms__brandingSet`, `sfdc_cms__theme`) - Page layouts (`sfdc_cms__themeLayout`) - Navigation structure - Custom LWCs for extensions **Where it lives:** - `force-app/main/default/digitalExperiences/site/StorefrontName/` - Example: `force-app/main/default/digitalExperiences/site/My_B2B_Store1/` **How to create:** - Automatically generated by Commerce Store setup wizard - Retrieved from org using Salesforce CLI - Cannot be manually created from scratch **How to deploy:** - Retrievable: `sf project retrieve start -m DigitalExperienceBundle:site/<name>` - Deployable: `sf project deploy start -m DigitalExperienceBundle` - Source-controllable in Git --- ## Why You Cannot Create Storefront Metadata from Scratch ### Technical Reasons 1. **Complex Dependency Chain** - Create merchandisers store - Create DigitalExperienceBundle - Integrate both together 2. **Hundreds of Auto-Generated Configurations** - Component IDs and region IDs (UUIDs) - WebStore associations - Commerce-managed component configurations - Default routing rules - Search configurations - Cart and checkout flow definitions - Payment integration settings 3. **Commerce-Managed Components** - Product List Page (PLP) components - Product Detail Page (PDP) components - Cart components - Checkout components - Search components - These require specific configurations from Store data 4. **Metadata API Limitation** - Metadata API deploys metadata types (Apex, LWCs, objects) - Metadata API CANNOT create SObject data (WebStore records) - Store creation requires data operations, not metadata operations --- ## The Required Creation Order ### Step 1: Create Commerce Store (Must Be First) ``` User Interface (Commerce App) ↓ WebStore Record Created ↓ BuyerGroup Records