Terminal
Terminal/Skill
Walks you through creating a B2B Commerce store in Salesforce, then retrieves its storefront metadata into your project.
By Salesforce
Works with
npx skills add forcedotcom/sf-skills --skill commerce-b2b-store-createInteractive workflow to create a Commerce B2B Store in Salesforce and retrieve the auto-generated storefront metadata to your repository.
Commerce B2B = Store (backend data) + Storefront (frontend metadata). Store must be created first in the org to auto-generate the Storefront. Never create storefront metadata manually.
See Store vs Storefront Reference
Trigger when users request:
Always follow the interactive flow. Do NOT skip steps. Each step requires user confirmation before proceeding.
Never create storefront metadata manually. The Commerce setup wizard generates hundreds of configuration values. Manual creation will fail.
Always list sites before retrieval. Store names get underscores and number suffixes (e.g., "My B2B Store" → "My_B2B_Store1"). Let the user select from the actual list.
Always use --json flag. Include --json on all Salesforce CLI commands for parseable output.
Agent explains: Commerce has Store (data) + Storefront (metadata). Store must be created first.
See: Store vs Storefront Reference
Agent provides these steps:
Navigate to Setup → Commerce → Stores
Click "Create Store" or "Setup New Store"
Select "Commerce Store" as the store type
Follow the wizard:
Complete wizard - it creates:
Optional: Configure payment gateway, tax provider, shipping
Agent then asks: "Have you completed creating the B2B Store in your org? Reply 'yes' when ready and provide the store name you used."
Agent waits for: User confirmation and store name
Agent validates: Store name format (no special characters, spaces will appear as underscores)
Agent acknowledges: "Great! Let me list the available storefronts in your org..."
Agent executes:
sf org list metadata --metadata-type DigitalExperienceConfig --json
Agent should:
Example output:
Available Digital Experience sites:
1. My_B2B_Store1
2. Partner_Portal
3. Customer_Community
Agent asks: "Which site corresponds to your B2B Store? Select the site name:"
Agent validates: Selection matches available sites
Agent confirms: "Got it! I'll retrieve metadata for [site-name]..."
Agent executes:
sf project retrieve start -m DigitalExperienceBundle:site/<selected-store-name> --json
Agent should:
Expected output:
Retrieved: force-app/main/default/digitalExperiences/site/My_B2B_Store1/
├── My_B2B_Store1.digitalExperience-meta.xml
├── sfdc_cms__view/ (home, current_cart, detail_*, list_*, etc.)
├── sfdc_cms__site/
├── sfdc_cms__route/
└── [other sfdc_cms__* directories]
Agent provides:
Metadata retrieved successfully!
Next steps:
sf project deploy start --source-dir force-app/main/default/digitalExperiences/site/My_B2B_Store1/ --jsonResources: DigitalExperienceBundle Docs, B2B Commerce Guide
Store first (creates storefront) → Retrieve → Customize