Salesforce B2C Commerce connection
Connect Salesforce B2C Commerce for product browsing and optional customer and order reads.
What it is
Salesforce B2C Commerce (SFCC) supplies store products and filters to INSIDE. You can also enable customer and order reads with separate credentials. A catalogue-only connection remains useful when private record access is unavailable.
Who uses it and why
Administrators with Settings or Developer connect the site and arrange Salesforce permissions. Operators browse products and, when enabled, customer and order records. Visitors receive product cards and can verify access to an individual order.
Where to find it
Open Settings › Commerce › Commerce Providers and select Salesforce B2C Commerce (SFCC) as Provider type. Configure the connection with Settings and relevant AI access, or Developer.
How it works
Choose SCAPI with private SLAS credentials or OCAPI for catalogue access. SCAPI uses private SLAS credentials. OCAPI catalogue access uses its client ID. Private customer and order reads use OCAPI client credentials in either catalogue mode.
The connection checks product, customer and order capabilities independently. Product search returns summaries and store refinements; product lookup retrieves the detail needed for option selection.
Customer operations need Customer list ID as well as private read access. Customer identities use Salesforce customer numbers. Preserve case and leading zeroes in identifiers.
Configure it
- Create the provider and choose Catalogue API.
- Enter Site ID and Storefront URL.
- For SCAPI, enter Short code, Organization ID, Private SLAS client ID and Private SLAS client secret.
- For OCAPI catalogue access, enter Instance hostname, OCAPI version and OCAPI client ID.
- To read private records, turn on Enable customer and order reads, complete the OCAPI fields and OCAPI client secret, and add Customer list ID for customer operations.
- Select operations under Use for, save and use test. Read any partial-access warnings.
Leave a saved secret blank to retain it only while the relevant connection details remain unchanged. Changing the destination or credential identity requires the corresponding secret again.
For a custom shopping site, Product URL template can supply an HTTPS product link on the Storefront URL host. Use exactly one {id} placeholder. Without a template, INSIDE uses a suitable returned product link, then the standard Salesforce storefront product link.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Catalogue API | Settings › Commerce › Commerce Providers | website | SCAPI with private SLAS credentials | Settings role, Developer role | Chooses SCAPI with private SLAS credentials or OCAPI for catalogue access. |
| Enable customer and order reads | Settings › Commerce › Commerce Providers | website | Off | Settings role, Developer role | Enables eligible private customer and order operations using separate OCAPI credentials and permissions. |
| Product URL template | Settings › Commerce › Commerce Providers | website | Not set | Settings role, Developer role | Supplies a custom product link with exactly one {id} placeholder on the storefront host. Without a template, INSIDE uses a suitable returned product link, then the standard Salesforce storefront product link. |
| OCAPI version | Settings › Commerce › Commerce Providers | website | 25_6 | Settings role, Developer role | Selects the API version used for OCAPI catalogue access and private customer and order reads. |
Fields
| Field | Where | Required | What it is for |
|---|---|---|---|
| Site ID | Settings › Commerce › Commerce Providers | Yes | Selects the Salesforce B2C Commerce site. Preserve its case and leading zeroes. |
| Storefront URL | Settings › Commerce › Commerce Providers | Yes | Supplies the public HTTPS shopping address for product links. |
| Short code | Settings › Commerce › Commerce Providers | No | Identifies the Salesforce Commerce API tenant. Required for SCAPI. |
| Organization ID | Settings › Commerce › Commerce Providers | No | Identifies the Salesforce Commerce organisation. Required for SCAPI. |
| Private SLAS client ID | Settings › Commerce › Commerce Providers | No | Identifies the private SLAS client used for SCAPI catalogue access. Required for SCAPI. |
| Private SLAS client secret | Settings › Commerce › Commerce Providers | No | Authenticates SCAPI catalogue access. Required for a new or changed SCAPI connection. |
| Instance hostname | Settings › Commerce › Commerce Providers | No | Identifies the canonical Salesforce instance for OCAPI. Required for OCAPI catalogue access or private reads. |
| OCAPI client ID | Settings › Commerce › Commerce Providers | No | Identifies the OCAPI client for catalogue access or private reads. Required when OCAPI fields apply. |
| OCAPI client secret | Settings › Commerce › Commerce Providers | No | Authenticates customer and order reads. Required when enabling private reads on a new or changed connection. |
| Customer list ID | Settings › Commerce › Commerce Providers | No | Enables customer lookup and search when private reads and the relevant OCAPI permissions are available. |
Permissions
| Permission | Lets you |
|---|---|
| Settings | Configure this provider, subject to AI access and View Only. |
| AI | Allows commerce administration for a restricted Settings role. |
| Developer | Configure the Salesforce B2C Commerce provider. |
Limits and good to know
- This integration does not provide a native basket action or visitor store sign-in.
- Visitor order access uses order-detail verification. Catalogue authentication does not identify a shopper.
- Pages contain at most 50 records. Private searches stop at 10,000 results; narrow the criteria for larger searches.
- Customer name search matches complete words. Phone, status and date filters are unsupported for private search.
- Storefront URL must use HTTPS without credentials, a custom port, query or fragment.
- A replacement connection that fails verification does not replace working credentials.
Depends on and works with
View all connections as a list
This feature uses
- Roles and permissionsConfigured by
Roles control provider administration.
- Commerce provider setup and selectionRequires
Connection operations and availability are selected in Commerce Providers.
- Product search and filtersEnhances
Supplies catalogue search and Salesforce refinements.
- Product options and variant selectionEnhances
Supplies detailed product choices through product lookup.
- Store customer matches and ordersEnhances
Optional private reads supply the CRM customer panel.
- AI customer and order searchEnhances
Optional private reads support restricted customer and order search.
- Customer and order accessConfigured by
Visitor order access supports order-detail verification, without store sign-in.
- Store order details and historyEnhances
Supplies authorised order details and history when private reads are enabled.
Used by
- Commerce provider setup and selectionEnhances
Supplies the Salesforce B2C Commerce provider option.
- Product search and filtersEnhances
Salesforce B2C Commerce supplies catalogue search and native refinements.
- Product options and variant selectionEnhances
Salesforce B2C Commerce lookup completes product summaries with options.
- Store customer matches and ordersEnhances
Salesforce B2C Commerce can supply records with private reads enabled.
- AI customer and order searchEnhances
Salesforce B2C Commerce supplies a narrower set of private search criteria.
- Customer and order accessEnhances
Salesforce B2C Commerce supports guest matching, but not storefront sign-in.
- Store order details and historyEnhances
Supplies Salesforce B2C Commerce order information.
FAQ and troubleshooting
Why do products load but customers do not?
Check Enable customer and order reads, OCAPI permissions and Customer list ID. Catalogue access alone does not enable private reads.
Can visitors sign in through this provider?
No. Configure supported order-detail verification under Customer and order access instead.
Why are product links wrong on a custom storefront?
Check Storefront URL and supply Product URL template for your product route. It must use the same host and exactly one {id} placeholder.
Why must I enter a secret again?
INSIDE retains a blank secret only for the same connection identity. A changed destination or client needs its credentials supplied and verified again.