Build, package, and distribute installable extensions for Salesforce Commerce Cloud storefronts.
Quick Start • Published Apps • Contributing • Disclaimer
Commerce Apps are packaged extensions that add capabilities to Storefront Next storefronts. A single app can bundle frontend UI components, backend API adapters, platform configuration, and merchant setup guidance into one installable unit called a Commerce App Package (CAP).
Merchants install Commerce Apps through Business Manager with a click-to-install experience. Developers build them here.
Three ways to build:
| Path | You Build | Platform Provides | Example |
|---|---|---|---|
| UI Target Only | React components for storefront extension points | Build-time injection via Vite plugin | Ratings widget, store locator, loyalty badge |
| API Adapter Only | Script API hooks implementing platform contracts | Hook dispatch, lifecycle management | Tax calculation (Avalara), fraud detection |
| Full App | Both UI components and backend adapters | All of the above | Shipping estimator, BNPL provider |
If you're using Claude Code, Cursor, Copilot, or another IDE with plugin support, install the cap-dev plugin for skills that streamline the full development workflow — see Agent Skills below.
Build your app directory with the following CAP structure:
commerce-{app-name}-app-v{version}/
├── commerce-app.json # App metadata
├── README.md # Documentation
├── app-configuration/
│ └── tasksList.json # Post-install merchant setup steps
├── icons/ # App icon (required)
│ └── {icon-filename}.png # CI extracts to commerce-apps-manifest/icons/
├── cartridges/ # Backend-only or Fullstack apps
│ ├── site_cartridges/{name}/ # Script API hook implementations
│ │ ├── package.json
│ │ ├── cartridge/scripts/
│ │ │ ├── hooks.json # Registers hooks with the platform
│ │ │ ├── hooks/ # Hook implementations
│ │ │ ├── helpers/ # Business logic
│ │ │ └── services/ # Service framework wrappers
│ │ └── test/ # Unit tests
│ └── bm_cartridges/ # Business Manager extensions (optional)
├── storefront-next/src/extensions/{name}/ # UI-only or Fullstack apps
│ ├── target-config.json # Maps components → storefront extension points
│ ├── index.ts # Barrel exports
│ ├── components/
│ └── locales/ # Required: en-US, en-GB, it-IT
│ ├── en-US/translations.json
│ ├── en-GB/translations.json
│ └── it-IT/translations.json
├── impex/ # Backend-only or Fullstack apps
│ ├── install/ # Service configs, custom attributes, preferences
│ │ ├── services.xml
│ │ ├── meta/
│ │ │ ├── system-objecttype-extensions.xml
│ │ │ └── custom-objecttype-definitions.xml
│ │ └── sites/SITEID/
│ │ └── preferences.xml
│ └── uninstall/ # Cleanup for uninstalled apps
│ └── services.xml
Three architectures:
- UI-only: Has
storefront-next/, nocartridges/orimpex/ - Backend-only: Has
cartridges/andimpex/, nostorefront-next/ - Fullstack: Has all three:
storefront-next/,cartridges/, andimpex/
Apps are organized by domain and app name:
{domain}/{appName}/
├── {appName}-v{version}.zip # The installable CAP
└── catalog.json # Version history (updated by CI)
commerce-apps-manifest/
├── manifest.json # Root manifest with all app entries
├── icons/
│ └── {iconName}.png # App icons
└── translations/
├── en-US.json # App translations (minimum)
├── de.json
├── fr.json
└── ... (13 locale files)
Example structure:
tax/
├── avalara-tax/
│ ├── avalara-tax-v0.2.8.zip
│ └── catalog.json
└── vertex-tax/
├── vertex-tax-v1.0.0.zip
└── catalog.json
payment/
├── stripe-payment/
│ ├── stripe-payment-v1.0.0.zip
│ └── catalog.json
└── adyen-payment/
├── adyen-payment-v1.0.0.zip
└── catalog.json
commerce-apps-manifest/
├── manifest.json # Contains all app entries
├── icons/
│ ├── avalara.png
│ ├── stripe.png
│ └── bazaarvoice.png
└── translations/
├── en-US.json # All app translations
├── de.json
└── ... (13 locale files)
Note: Extracted app directories (commerce-{app-name}-app-v{version}/) are for development only and should NOT be committed to the repository.
Every app's domain field must be one of these. Domains use hyphen-case. Provider domains (tax, payment, shipping) show under "Providers" on the checkout hub; all other domains show under "Additional Setup".
| Domain | Section | Description | Example Apps |
|---|---|---|---|
tax |
Providers | Tax calculation and compliance | Avalara, Vertex |
payment |
Providers | Payment processing | Stripe, Adyen, PayPal |
shipping |
Providers | Shipping and fulfillment | ShipStation, EasyPost |
gift-cards |
Additional Setup | Gift card purchasing, redemption, and balance | Salesforce Gift Cards, Adyen Gift Cards |
ratings-and-reviews |
Additional Setup | Product ratings and reviews | Bazaarvoice, Yotpo, PowerReviews |
loyalty |
Additional Setup | Loyalty programs and rewards | LoyaltyLion, Smile.io |
search |
Additional Setup | Search and merchandising | Algolia, Elasticsearch |
address-verification |
Additional Setup | Address validation and standardization | Smarty, Google Address Validation |
analytics |
Additional Setup | Analytics and reporting | Google Analytics, Segment |
approaching-discounts |
Additional Setup | Approaching discount notifications | Salesforce Approaching Discounts |
fraud |
Additional Setup | Fraud detection and prevention | Signifyd, Forter, Riskified |
Commerce App frontend extensions target the Storefront Next stack:
| Layer | Technology |
|---|---|
| Framework | React 19 |
| Language | TypeScript (strict) |
| Build | Vite |
| Styling | Tailwind CSS 4 (@theme inline, no config file) |
| Components | ShadCN UI (29 primitives on Radix UI) |
| Variants | CVA (class-variance-authority) |
| Routing | React Router 7 |
| i18n | react-i18next |
| Component docs | Storybook 10 |
| Unit testing | Vitest + React Testing Library |
| E2E testing | CodeceptJS + Playwright |
Backend adapters use the Commerce Cloud Script API (CommonJS, require('dw/...') modules).
Turn your coding agent into a Commerce Apps specialist. Skills give Claude Code, Cursor, GitHub Copilot, and Codex deep expertise in scaffolding, packaging, validating, and submitting Commerce App Packages.
Skills follow the open Agent Skills standard and work with Claude Code, Cursor, GitHub Copilot, VS Code, Codex, and others.
Tip
For B2C Commerce development and operations skills, also install the B2C Developer Tooling plugins. See the B2C DX documentation for installation instructions.
Install via your IDE's plugin marketplace or manually copy skills into your IDE's skills directory.
claude plugin marketplace add SalesforceCommerceCloud/commerce-apps
claude plugin install cap-dev --scope projectUse --scope user instead to install globally across all projects.
In VS Code, open the Command Palette (Cmd/Ctrl+Shift+P) and run:
Chat: Install Plugin from Source
Then enter: SalesforceCommerceCloud/commerce-apps
copilot plugin marketplace add SalesforceCommerceCloud/commerce-apps
copilot plugin install cap-dev@commerce-appscodex plugin marketplace add SalesforceCommerceCloud/commerce-appsThen in Codex, run /plugins, select the "Commerce Apps" marketplace, and install the cap-dev plugin.
The B2C CLI can install skills to any supported IDE:
# Interactive — choose skillset, IDE, and skills
npx @salesforce/b2c-cli setup skills
# Non-interactive — install to a specific IDE
npx @salesforce/b2c-cli setup skills cap-dev --ide cursor
# Install globally (user scope)
npx @salesforce/b2c-cli setup skills cap-dev --ide cursor --globalFor IDEs without marketplace support, copy the skills directory:
| IDE | Project Path | User Path |
|---|---|---|
| Cursor | .cursor/skills/ |
~/.cursor/skills/ |
| Windsurf | .windsurf/skills/ |
~/.codeium/windsurf/skills/ |
| Codex | .codex/skills/ |
~/.config/codex/skills/ |
| OpenCode | .opencode/skills/ |
~/.config/opencode/skills/ |
Copy the skills from this repository's .claude/skills/ directory into the appropriate path for your IDE.
| Skill | Description |
|---|---|
scaffold-app |
Generate complete app structure (UI-only, Backend-only, or Fullstack) |
package-app |
Package app into registry-ready ZIP (handles new apps and version bumps) |
generate-service-impex |
Generate service credentials, profiles, and definitions |
generate-site-preferences-impex |
Generate custom site preference configurations |
generate-custom-object-impex |
Generate custom object type definitions |
validate-impex |
Validate impex XML syntax, structure, and common errors |
validate-app |
Comprehensive pre-submission validation (structure, manifest, SHA256, impex) |
submit-app |
Guided PR submission with automated GitHub CLI integration |
Once installed, skills are available as slash commands in your IDE:
/scaffold-app → Start a new Commerce App
/package-app → Package for submission
/validate-app → Run full validation suite
/submit-app → Submit PR to registry
Or ask your agent naturally:
"Create a new tax app called my-tax"
"Package the my-tax app for submission"
"Validate my app before I submit"
"Generate service impex for a REST API integration"
See CONTRIBUTING.md for complete submission requirements.
Using Agent Skills (Recommended):
- Scaffold new app:
/scaffold-app - Build your app code (cartridges, extensions, etc.)
- Generate impex:
/generate-service-impex,/generate-site-preferences-impex - Package app:
/package-app - Validate:
/validate-app - Submit PR:
/submit-app
Manual Process:
- Build your app directory with required structure
- Package as a CAP ZIP file:
zip -r my-app-v1.0.0.zip commerce-my-app-app-v1.0.0/ -x "*.DS_Store" -x "__MACOSX/*" -x "*/.*" - Generate SHA256 hash:
shasum -a 256 my-app-v1.0.0.zip - Update root manifest at
commerce-apps-manifest/manifest.jsonwith app entry (id, name, description, iconName, domain, version, zip, sha256) - Add translations to
commerce-apps-manifest/translations/en-US.json(minimum requirement) - Create
catalog.jsonwith INIT placeholder (new apps only) - Place ZIP at
{domain}/{appName}/where{appName}matches the "id" field (e.g.,tax/avalara-tax/oraddress-verification/loqate-address-verification/) - Delete old ZIP versions:
rm -f {app-name}-v*.zip(keep only the latest version) - Commit ONLY the ZIP, root manifest, icon, translations, and catalog.json (do NOT commit extracted directories)
- Open a PR
CI Validation: Validates ZIP structure, manifest format, and SHA256 hash. On merge, creates a Git tag, extracts app icons to commerce-apps-manifest/icons/, and updates the catalog automatically.
Updating an app: Update the ZIP, root manifest entry, and icon/translations (if changed). Do NOT add new versions to catalog.json (CI handles it). You may add "deprecated": true to existing versions if needed.
Only commit these files to the repository:
✅ DO commit:
{domain}/{appName}/{appName}-v{version}.zip- The packaged appcommerce-apps-manifest/manifest.json- Root manifest with app entrycommerce-apps-manifest/translations/en-US.json- App translations (minimum){domain}/{appName}/catalog.json- Version catalog (new apps only, with INIT values)
Note: App icons are automatically extracted from the ZIP by the CI workflow and added to commerce-apps-manifest/icons/ - do NOT manually commit icons.
❌ DO NOT commit:
commerce-{app-name}-app-v{version}/- Extracted app directories (dev only).DS_Store,Thumbs.db- System filesnode_modules/- Dependencies- Old ZIP versions - Delete before committing
- IDE files (
.vscode/,.idea/)
The repository .gitignore is configured to exclude extracted directories and system files.
All external contributors must sign the Contributor License Agreement (CLA). A prompt to sign the agreement appears when a pull request is submitted.
This repository may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, results could differ materially from those expressed or implied. For more information, see Salesforce SEC filings.
© Copyright 2026 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners.
Built for ISV developers by the Commerce Apps team at Salesforce Commerce Cloud.