The complete guide
Salesforce Commerce Cloud integration: the complete guide
Updated November 18, 2026 · Published by Danny Rathod, Founder, StackLift AI. Written with AI assistance; how we make content.
Short answer
A Salesforce Commerce Cloud integration connects the storefront to order management, ERP, inventory, payments and Salesforce CRM, marketing and service. It uses the Commerce APIs, OAuth-based API clients and custom code on the platform. Effort depends on headless versus template storefronts, data model changes and how much flows back into Salesforce.
What does a Salesforce Commerce Cloud integration do?
Salesforce Commerce Cloud runs large retail and brand storefronts. An integration moves data between the store and the systems that own it, so catalog, stock, orders and customer records agree everywhere. It also ties shopper activity to other Salesforce products. This page is about the commerce platform; for the CRM itself see Salesforce integration.
- Send orders to an order management system or ERP and return fulfillment status.
- Import catalog, prices and inventory from a PIM or ERP.
- Connect shopper profiles and orders to Salesforce CRM, marketing and service workflows.
- Plug in tax, payment, fraud and shipping providers.
- Build a headless storefront on the Commerce APIs.
- Connect loyalty and customer service tools.
How does a Salesforce Commerce Cloud integration work?
The platform has two API families. The Open Commerce API (OCAPI) is the older one and is in maintenance mode. The Salesforce Commerce API (SCAPI) is the newer one, built for headless storefronts and the direction new work should take. Credentials come from an API client you create in Account Manager, with scopes assigned, and calls use OAuth 2.0 tokens. Shopper-facing calls go through the Shopper Login and API Access Service (SLAS).
Storefronts can be template based or headless. Back-end jobs, custom hooks and import or export feeds run on the platform itself, usually with files exchanged over secure transfer. Use a sandbox instance for development and keep staging and production separate. For general background, read about system integration.
What data moves, and in which direction?
| Data | Direction | How often |
|---|---|---|
| Orders | Commerce Cloud to OMS or ERP | Event-driven or short batches |
| Order status and shipments | OMS or warehouse to Commerce Cloud | Event-driven |
| Catalog and prices | PIM or ERP to Commerce Cloud | Scheduled feeds |
| Inventory | ERP or OMS to Commerce Cloud | Frequent schedule |
| Customer profiles | Both ways with Salesforce CRM | Event-driven plus reconciliation |
What drives the effort of a Commerce Cloud integration?
Use the typical effort shown above as a starting point. These factors change it.
- Moving from OCAPI to SCAPI, or running both during a migration.
- Headless storefront versus template storefront.
- Custom attributes and data model extensions.
- Multiple sites, locales, currencies and price books.
- Two-way sync with CRM and identity matching for customers.
- Feed volume, schedules and failure handling for batch jobs.
- Separate sandbox, staging and production environments.
See e-commerce cost for what shapes commerce budgets.
What are the common Commerce Cloud pitfalls?
- Reusing one API client across OCAPI and SCAPI. They need separate credentials and scopes.
- Building new work on OCAPI when it is in maintenance mode.
- Mixing shopper-facing and admin permissions in one client.
- Feed jobs that fail silently. Add alerts and a reconciliation report.
- Matching customers by email alone. Define a clear identity rule with CRM.
- Skipping a sandbox test of failure paths such as payment declines and out-of-stock items.
Should you build it custom or use a connector?
| Question | Connector or iPaaS | Custom integration |
|---|---|---|
| Setup speed | Fast for supported systems | Slower to start |
| Fit for your data model | Limited to what is mapped | Built to your model |
| Headless storefront | Rarely covered | Designed for it |
| Ongoing cost | Recurring tool fees | Hosting and maintenance |
| Good for | Standard flows to common systems | Order, price and identity flows |
Enterprise platforms like MuleSoft or Boomi often sit in the middle. See iPaaS for the category.
A custom build is not always the answer. If one system only needs a notification when an order arrives, a connector is faster and cheaper. Choose custom code where a failure would cost you orders, stock accuracy or customer trust, because there you want your own retries, queues and alerts. Many teams end up with both: connectors for convenience flows and custom code for the core order and identity flows.
How do you test and launch a Commerce Cloud integration?
- Write down which system owns each field and how records are matched.
- Create API clients with the smallest scopes that work.
- Build and test in a sandbox with realistic catalog data.
- Test failures: declined payments, missing SKUs, partial feeds, repeated messages.
- Rehearse the cutover on staging, including a rollback.
- Release in stages and watch jobs and alerts through the first full order cycle.
How does StackLift scope a Commerce Cloud integration?
StackLift AI integrates with Salesforce Commerce Cloud; we are not a Salesforce partner or reseller. The free estimate scopes feature by feature, and a senior architect reviews it before it becomes a commitment.
Engineers and agents work on feature branches, with CI/CD, observability and rollback in the plan from sprint one.
Questions people ask
What is the difference between OCAPI and SCAPI?
OCAPI is the older REST API family and is in maintenance mode. SCAPI is the newer Commerce API, built for headless storefronts and the choice for new work.
Can Commerce Cloud connect to Salesforce CRM?
Yes. Customers, orders and service data can flow to and from CRM and other Salesforce products. Agree an identity rule for matching shoppers to contacts first.
Can I build a headless storefront on Commerce Cloud?
Yes. The Commerce APIs support headless storefronts, with shopper authentication handled by SLAS. A framework such as React or Next.js is common.
Do I need to migrate from OCAPI?
Salesforce points existing OCAPI users to plan a move to SCAPI. A migration audit lists the endpoints in use and maps them across.
How long does an integration take?
See the typical effort above, then run the free estimate for your own flows. Most first versions of a project take 6–16 weeks depending on scope.