b2c-scapi-shopper
About b2c-scapi-shopper
A skill for developers implementing Salesforce B2C Commerce storefront flows with SCAPI, covering products, baskets, checkout, customers, and shopper context. It emphasizes contract discovery, SLAS authentication, and using the application’s Shopper SDK or client for execution.
Key features
- 01Discover Shopper API contracts
- 02Guide SLAS shopper authentication
- 03Support basket and checkout flows
- 04Inspect schemas and custom attributes
Use cases
- 01Plan a storefront API integration
- 02Implement shopper login and token flows
- 03Build basket-to-order checkout
- 04Check tenant schemas and API versions
MCP support
When B2C MCP is available, the skill describes reading its guidance and using tools such as `scapi_search` and `scapi_schemas_list` for discovery. Shopper execution itself is not supported by `scapi_execute`; flows run through the application’s Shopper SDK or client.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ salesforcecommercecloud/ b2c-developer-tooling --skill b2c-scapi-shopperAfter installing, type/b2c-scapi-shopperin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
evals/trigger-evals.jsonreferences/CHECKOUT-FLOW.mdCLIENT-EXAMPLES.mdCOMMON-PATTERNS.mdSCOPES.mdDetails
From the project READMEShopper Commerce APIs
Build storefront product, basket, checkout, customer, and context flows with SCAPI.
For backend management use the b2c-scapi-admin skill.
Tool choice
When B2C MCP is available:
- Read
skill://mcp/b2c-mcp-scapi/SKILL.mdonce through resources orskills_readbefore code-mode tools; passskillRead: true. scapi_searchwithauthType: "shopper"discovers bundled contracts offline. Find method/path/operationId first, then selected inputs, response fields, and security. Mixed Admin/Shopper operations can appear in either filter.- Shopper execution is unsupported in
scapi_execute; adding a SLAS client cannot enable it. Execute storefront flows through the application's Shopper SDK/client with the appropriate SLAS token flow. Prefer dedicated tools where available. scapi_schemas_listretrieves live tenant contracts and custom attributes;scapi_custom_apis_get_statuschecks custom registration. Code mode does not execute custom APIs.config_inspectreports configured values with masking.docs_search/docs_readanswer platform semantics, authentication, and limits; avoid duplicate contract reads.
CLI alternatives: b2c scapi schemas list,
b2c scapi schemas get <family> <name> <version>, and b2c setup inspect.
These schema commands use live Schemas API access; MCP discovery is offline.
Integration essentials
- Reuse configured shortCode, organizationId, and siteId; do not invent identifiers.
- Shopper authentication uses SLAS guest/registered flows and client scopes; Account Manager credentials are not a substitute. Keep private-client secrets and token exchange on the backend.
- Discover the contract for the selected API version. Examples are illustrative; verify version-specific behavior and limits in official docs.
- Preserve basket/order state and handle errors explicitly. Page/filter responses and return only fields needed by the next operation.
- For headless payment authorization, inspect
the order-PI hooks in the
b2c-hooksskill ("Headless Order Payment") and the order lifecycle in theb2c-orderingskill before choosing a placement flow.
Conditional references
- Client examples: implementing auth and API calls.
- Checkout: basket-to-order workflow.
- Common patterns: errors, pagination, field selection.
- Scopes: Shopper grants by family.
b2c-slasskill: CLI client management.b2c-slas-auth-patternsskill: OTP, passkeys, session bridge.- Official docs:
commerce-api/use-shopper-api,commerce-api/slas,commerce-api/work-with-baskets-orders,commerce-api/shopper-context-best-practices,commerce-api/auth-z-scope-catalog,commerce-api/performance.