Integrating B2b Commerce Open Code Components

Name: Integrating B2b Commerce Open Code Components
Author: forcedotcom

forcedotcom/sf-skills

1.6k installs
763 repo stars
Updated July 24, 2026
forcedotcom/sf-skills

integrating-b2b-commerce-open-code-components helps agents extend Salesforce B2B Commerce storefronts with Open Code Components.

About

The integrating-b2b-commerce-open-code-components skill from Salesforce sf-skills guides agents building B2B Commerce buyer experiences with Open Code Components. Although the cached catalog doc may point at a sibling Data Cloud query skill, the listing targets B2B Commerce OCC integration: wiring Lightning Web Components into B2B storefront pages, extending product discovery, cart, checkout, and account self-service flows, and aligning with Salesforce Commerce APIs and org configuration. Agents gather org alias, storefront context, and whether work is component authoring, API integration, or deployment packaging. Workflows cover OCC project structure, commerce cloud SDK usage, authenticated buyer sessions, and delegation to platform SOQL or Data Cloud skills when the task shifts to CRM or Data Cloud SQL only. Use when users mention B2B Commerce Open Code Components, storefront LWC customization, or headless B2B buyer UI integration.

Targets B2B Commerce Open Code Components for custom buyer storefront UI.
Covers LWC integration with cart, catalog, and checkout commerce flows.
Requires org alias and storefront context before implementation steps.
Delegates pure CRM SOQL or Data Cloud SQL to sibling sf-skills.
Aligns component work with Salesforce Commerce APIs and deployment packaging.

Integrating B2b Commerce Open Code Components by the numbers

1,587 all-time installs (skills.sh)
+6 installs in the week ending Jul 28, 2026 (Skillselion tracking)
Ranked #304 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
Security screen: MEDIUM risk (skills.sh audit)
Data as of Jul 28, 2026 (Skillselion catalog sync)

At a glance

integrating-b2b-commerce-open-code-components capabilities & compatibility

Capabilities: occ storefront integration · commerce api alignment · buyer flow customization · org context gathering · sibling skill delegation
Works with: salesforce
Use cases: api development · frontend

npx skills add https://github.com/forcedotcom/sf-skills --skill integrating-b2b-commerce-open-code-components

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/forcedotcom/sf-skills/integrating-b2b-commerce-open-code-components.svg)](https://skillselion.com/skills/forcedotcom/sf-skills/integrating-b2b-commerce-open-code-components)

Installs	1.6k
repo stars	★ 763
Security audit	2 / 3 scanners passed
Last updated	July 24, 2026
Repository	forcedotcom/sf-skills ↗

How do I add custom LWC components to a Salesforce B2B Commerce buyer storefront?

Integrate Salesforce B2B Commerce storefronts with Open Code Components (LWC) for custom buyer experiences, cart flows, and headless commerce extensions.

Who is it for?

Salesforce developers customizing B2B Commerce buyer experiences with Open Code Components.

Skip if: Standard CRM SOQL-only tasks or pure Data Cloud SQL without commerce UI work.

When should I use this skill?

User mentions B2B Commerce Open Code Components, storefront LWC, or B2B buyer UI integration.

What you get

Integrated OCC components and commerce flows aligned with org storefront configuration.

Copied open-source commerce components
Experience Builder-ready labels

By the numbers

Skill version 1.0 in metadata
Copies all open-source B2B Commerce components and labels from one GitHub repository

Files

SKILL.mdMarkdownGitHub ↗

data360-query: Data Cloud Retrieve Phase

Use this skill when the user needs query, search, and metadata introspection for Data Cloud: sync SQL, paginated SQL, async query workflows, table describe, vector search, hybrid search, or search index operations.

When This Skill Owns the Task

Use data360-query when the work involves:

sf data360 query *
sf data360 search-index *
sf data360 metadata *
sf data360 profile * or sf data360 insight * inspection
understanding Data Cloud SQL results or query shape

Delegate elsewhere when the user is:

writing standard CRM SOQL only → platform-soql-query
designing segment or calculated insight assets → data360-segment
analyzing STDM/session tracing/parquet telemetry → agentforce-observe

---

Required Context to Gather First

Ask for or infer:

target org alias
whether the user needs quick count, medium result set, large export, schema inspection, or semantic search
table/index name if known
whether the task is read-only SQL or search-index lifecycle management

---

Core Operating Rules

Treat Data Cloud SQL as its own query language, not SOQL.
Run the shared readiness classifier before relying on query/search surfaces: node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json.
Use describe before guessing columns.
Prefer sqlv2 or async query flows for larger result sets.
Use vector search or hybrid search only when the search index lifecycle is healthy.
Keep STDM/parquet/session-tracing workflows out of this skill family.

---

Recommended Workflow

1. Classify readiness for retrieve work

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
# optional query-plane probe, only with a real table name
node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json

2. Choose the smallest correct query shape

sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query sqlv2 -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query async-create -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null

3. Use describe before guessing fields

sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null

4. Use vector or hybrid search only when an index exists

sf data360 search-index list -o <org> 2>/dev/null
sf data360 query vector -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Insurance_Index --query "weather damage coverage" --prefilter "Type_of_Insurance__c='Home'" --limit 10 2>/dev/null

5. Reuse curated search-index examples when creating indexes

Use the phase-owned examples instead of inventing JSON from scratch:

examples/search-indexes/vector-knowledge.json
examples/search-indexes/hybrid-structured.json

---

High-Signal Gotchas

Data Cloud SQL is not SOQL.
Table names should be double-quoted in SQL.
sqlv2 is better than ad hoc OFFSET paging for medium result sets.
async query is preferable for large results.
search-index operations and vector/hybrid queries depend on the index lifecycle being healthy.
Hybrid search can use --prefilter, but only on fields configured as prefilter-capable when the search index was created.
HNSW index parameters are typically read-only on create; leave userValues: [] unless the platform explicitly documents otherwise.
query describe is not a universal tenant probe; only run it with a known DMO or DLO table after broader readiness has been confirmed.

---

Output Format

Retrieve task: <sql / sqlv2 / async / describe / vector / search-index>
Target org: <alias>
Target object: <table or index>
Commands: <key commands run>
Verification: <query rows / schema / status>
Next step: <segment / harmonize / follow-up>

---

References

README.md
examples/search-indexes/vector-knowledge.json
examples/search-indexes/hybrid-structured.json
../data360-orchestrate/assets/definitions/search-index.template.json
../data360-orchestrate/references/plugin-setup.md
../data360-orchestrate/references/feature-readiness.md

{
  "label": "<INDEX_NAME>",
  "developerName": "<INDEX_NAME>",
  "description": "Hybrid search index on a structured Data Cloud DMO",
  "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
  "chunkDmoName": "<INDEX_NAME> chunk",
  "chunkDmoDeveloperName": "<INDEX_NAME>_chunk",
  "vectorDmoName": "<INDEX_NAME> index",
  "vectorDmoDeveloperName": "<INDEX_NAME>_index",
  "searchType": "HYBRID",
  "vectorEmbedding": {
    "vectorEmbeddingRelatedFields": []
  },
  "rankingConfigurations": [],
  "chunkingConfiguration": {
    "fieldLevelConfigurations": [
      {
        "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
        "sourceDmoFieldDeveloperName": "<TEXT_FIELD>__c",
        "config": {
          "id": "passage_extraction",
          "userValues": [
            { "id": "max_tokens", "value": "512" },
            { "id": "strip_html", "value": "true" }
          ]
        }
      }
    ]
  },
  "vectorEmbeddingConfiguration": {
    "embeddingModel": {
      "id": "e5_large_v2",
      "userValues": [
        { "id": "dimension", "value": "1024" },
        { "id": "max_token_limit", "value": "512" }
      ]
    },
    "index": {
      "id": "HNSW",
      "userValues": []
    },
    "similarityMetric": "COSINE"
  }
}

{
  "label": "My_kav",
  "developerName": "My_kav",
  "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
  "chunkDmoName": "My_kav chunk",
  "chunkDmoDeveloperName": "My_kav_chunk",
  "vectorDmoName": "My_kav index",
  "vectorDmoDeveloperName": "My_kav_index",
  "searchType": "VECTOR",
  "vectorEmbedding": {
    "vectorEmbeddingRelatedFields": []
  },
  "chunkingConfiguration": {
    "fieldLevelConfigurations": [
      {
        "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
        "sourceDmoFieldDeveloperName": "ssot__Name__c",
        "config": {
          "id": "passage_extraction",
          "userValues": [
            { "id": "strip_html", "value": "true" },
            { "id": "max_tokens", "value": "512" }
          ]
        }
      }
    ]
  },
  "vectorEmbeddingConfiguration": {
    "embeddingModel": {
      "id": "e5_large_v2",
      "userValues": [
        { "id": "dimension", "value": "1024" },
        { "id": "max_token_limit", "value": "512" }
      ]
    },
    "index": {
      "id": "HNSW",
      "userValues": []
    },
    "similarityMetric": "COSINE"
  },
  "rankingConfigurations": []
}

data360-query

Query and search workflows for Salesforce Data Cloud.

Use this skill for

quick SQL counts
paginated SQL (sqlv2)
async query lifecycles
table describe
vector search
hybrid search with optional prefilter
search index inspection and lifecycle work

Example requests

"Run a Data Cloud SQL query against unified profiles"
"Describe this Data Cloud table before I write SQL"
"Help me troubleshoot vector search in Data Cloud"
"Run a hybrid search with a prefilter in Data Cloud"
"Create and inspect a search index"

Common commands

sf data360 query sql -o myorg --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query describe -o myorg --table ssot__Individual__dlm 2>/dev/null
sf data360 search-index list -o myorg 2>/dev/null
sf data360 query vector -o myorg --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o myorg --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null

Example payloads

examples/search-indexes/vector-knowledge.json
examples/search-indexes/hybrid-structured.json

References

SKILL.md
../data360-orchestrate/assets/definitions/search-index.template.json
CREDITS.md

Related skills

Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.471k

Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.382k15.8k

Lark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.381k15.8k

Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k37

Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.230k15.8k

SupabaseGet accurate, up-to-date Supabase implementation guidance across database, auth, realtime, storage, edge functions and vector search without relying on outd182k2.4k

Forks & variants (1)

Integrating B2b Commerce Open Code Components has 1 known copy in the catalog totaling 285 installs. They canonicalize to this original listing.

forcedotcom - 285 installs

How it compares

Pick integrating-b2b-commerce-open-code-components over manual LWC imports when you need the entire forcedotcom open-source B2B Commerce library copied into Experience Builder at once.

FAQ

What does this skill integrate?

Salesforce B2B Commerce storefronts with custom Open Code Components for buyer-facing flows.

When should I use a different sf-skill?

Use platform-soql-query for CRM SOQL or data360-query for Data Cloud SQL without commerce UI.

What context is required first?

Target org alias, storefront scope, and whether the work is LWC authoring or API wiring.

Is Integrating B2b Commerce Open Code Components safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Backend & APIsintegrationsbackend

About

Integrating B2b Commerce Open Code Components by the numbers

integrating-b2b-commerce-open-code-components capabilities & compatibility

Add your badge

How do I add custom LWC components to a Salesforce B2B Commerce buyer storefront?

Who is it for?

When should I use this skill?

What you get

By the numbers

Files

data360-query: Data Cloud Retrieve Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

Recommended Workflow

1. Classify readiness for retrieve work

2. Choose the smallest correct query shape

3. Use describe before guessing fields

4. Use vector or hybrid search only when an index exists

5. Reuse curated search-index examples when creating indexes

High-Signal Gotchas

Output Format

References

Credits & Acknowledgments

data360-query

Use this skill for

Example requests

Common commands

Example payloads

References

Related skills

Forks & variants (1)

How it compares

FAQ

What does this skill integrate?

When should I use a different sf-skill?

What context is required first?

Is Integrating B2b Commerce Open Code Components safe to install?

This week in AI coding