Source connector

Salesforce Commerce Cloud connector

Salesforce Commerce Cloud integration for databases, warehouses and BI tools

Salesforce storefront, catalog, and order management. Datrise captures Salesforce Commerce Cloud entities such as orders, products, customers, baskets, promotions and inventory records, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Salesforce B2C Commerce API (SCAPI); legacy Open Commerce API (OCAPI, deprecated April 2026) authenticates with OAuth 2.0, incremental runs key on creationDate, and Salesforce Commerce Cloud caps calls at SLAS token endpoint: 24,000 requests/minute per tenant in production (500/minute in sandboxes); most other SCAPI/OCAPI resource categories carry their own published per-10-second limits (e.g. Omnichannel Inventory availability reads at 10,000 requests/10s) rather than one account-wide number.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `salesforce_commerce_cloud_orders`) with a schema derived from the Salesforce Commerce Cloud API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Salesforce Commerce Cloud pipeline page, and join the waitlist to get the Salesforce Commerce Cloud connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Salesforce Commerce Cloud data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
orders	salesforce_commerce_cloud_orders	Upsert by primary key, incremental on updated-at
products	salesforce_commerce_cloud_products	Upsert by primary key, incremental on updated-at
customers	salesforce_commerce_cloud_customers	Upsert by primary key, incremental on updated-at
baskets	salesforce_commerce_cloud_baskets	Upsert by primary key, incremental on updated-at
promotions	salesforce_commerce_cloud_promotions	Upsert by primary key, incremental on updated-at
inventory records	salesforce_commerce_cloud_inventory_records	Upsert by primary key, incremental on updated-at

Salesforce Commerce Cloud API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Salesforce B2C Commerce API (SCAPI); legacy Open Commerce API (OCAPI, deprecated April 2026)
Authentication	OAuth 2.0 — Shopper-facing SCAPI endpoints authenticate through SLAS (Shopper Login and API Access Service) using OAuth 2.1 client_credentials (guest) or authorization_code with PKCE (registered shoppers); Admin APIs instead use an Account Manager OAuth2 client-credentials token.
Pagination	offset — SCAPI search/list endpoints use `offset`/`limit` query params with a `total` count in the response; the legacy OCAPI uses `start`/`count` (0-200 per chunk, default 25) with `next`/`previous` links.
Rate limit	SLAS token endpoint: 24,000 requests/minute per tenant in production (500/minute in sandboxes); most other SCAPI/OCAPI resource categories carry their own published per-10-second limits (e.g. Omnichannel Inventory availability reads at 10,000 requests/10s) rather than one account-wide number
Incremental cursor	creationDate — Search resources such as Orders Search accept a `sorts` list of field/direction pairs including `creationDate`, but there is no platform-wide `lastModified` sort across every resource, so incremental strategy varies by object type.
Webhooks	No
Bulk export	Yes — Business Manager Import/Export jobs (XML feed export of catalogs, customers, price books, etc., scheduled via WebDAV)
Deletes detectable	No

Official API reference

What bites when replicating Salesforce Commerce Cloud

OCAPI carries a `(deprecated)` label on every reference page as of April 2026, and Salesforce stops offering OCAPI settings to newly provisioned realms starting September 1, 2026, so a connector built against OCAPI resources needs a SCAPI migration path.
SCAPI previously allowed `offset` up to 200,000 on search endpoints, but the 24.5 release lowered the maximum allowed offset to 10,000, so deep pagination into large result sets now errors instead of returning empty pages.
There is no platform-wide `lastModified` field or deleted-records feed across SCAPI/OCAPI resources; detecting deletions (e.g. discontinued products, removed customers) requires diffing full snapshots rather than polling a delta endpoint.
Shopper APIs must respond within 10 seconds and Admin APIs within 60 seconds; SCAPI also applies load shedding (HTTP 503) on top of the documented per-endpoint rate limits (HTTP 429) during traffic spikes.

Compare this against every other documented API

Popular destinations for Salesforce Commerce Cloud

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Salesforce Commerce Cloud connector FAQ

What Salesforce Commerce Cloud data does the connector extract?: 6 objects: orders, products, customers, baskets, promotions and inventory records. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Salesforce Commerce Cloud integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Salesforce Commerce Cloud data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Salesforce Commerce Cloud → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Salesforce Commerce Cloud pipeline with guided onboarding

Join the waitlist to get priority access for Salesforce Commerce Cloud integrations with guided setup, schema-aware mapping, and production-grade incremental sync.