Salesforce ecommerce integration without calling CRM a commerce platform

The store already takes orders. Salesforce already holds accounts, contacts, and the pipeline. The gap is Order and OrderItem — or Opportunity — on the CRM APIs. We will tell you what Sales Cloud should store, and when you are actually talking about Commerce Cloud.

Book a free 30-minute discovery callTalk through your Salesforce connection

Australian ecommerce team. We look at the store and the Salesforce org before anyone talks about a connector.

Still running a store that needs Salesforce?

The store still takes orders. Salesforce still holds the account. That is why the two have been left talking through a weekly CSV into Contacts, or through a project that mixed up Sales Cloud and Commerce Cloud.

Salesforce Platform CRM — Sales Cloud, Service Cloud, and related clouds — is Accounts, Contacts, Leads, Opportunities, Orders and Order Products, plus optional Commerce clouds. SFDC Australia Pty. Ltd. lists an APAC HQ at Salesforce Tower, 180 George Street, Sydney, plus Melbourne, Adelaide, Brisbane, Canberra, Perth, and NZ offices in Auckland and Wellington. That is a legal entity and office list, not an Australian org count. We do not have a Salesforce AU figure to quote.

This page assumes CRM objects. B2C Commerce SCAPI is a different API on *.api.commercecloud.salesforce.com. It only matters if the prospect runs Salesforce Commerce Cloud, not Sales Cloud.

You might recognise one of these:

  • Checkout creates a customer the CRM never sees
  • Opportunities are updated by hand after a web order
  • Someone scoped “Salesforce commerce” and meant Sales Cloud Orders
  • Fulfilment status never returns to the case or the order
  • Marketing wants Contacts; finance wants the ERP; both think Salesforce is the stock system
  • A bulk load of historic orders needs a different API to the nightly drip

You do not need a new storefront, or a Commerce Cloud licence pitch. You need a clear read on the Salesforce org you already have.

Why these connections stall

Salesforce has official APIs. The stall is rarely “there is no API”. It is which cloud, which object, and treating CRM as a warehouse.

CRM not SCAPI

Orders vs Opportunities

Not inventory

Bulk when huge

Sales Cloud REST is not B2C Commerce SCAPI.

The CRM REST API is programmatic access to Salesforce objects, OAuth 2.0 via External Client Apps or Connected Apps. SOAP API (Enterprise / Partner WSDL) is still documented. Place Order REST exists for Order / OrderItem. SCAPI is a different host and a different product. A Sales Cloud build is not a Salesforce Commerce Cloud build. If the brief says “Salesforce ecommerce” and the org is Sales Cloud, you are doing CRM objects. If they run SFCC, that is another page.

The store job is people and orders, not stock.

Typical work: upsert Contact and Account from store customers; create Order plus OrderItem (or Opportunity) from paid carts; sync fulfilment or status back; open service cases. Stock usually does not live in Sales Cloud. If inventory is the real problem, the system of record is elsewhere — Cin7, Unleashed, an ERP — and Salesforce should not be asked to hold it.

Orders and Opportunities are a business choice.

Some orgs want a closed-won Opportunity. Some want the Order object. Some want both and then argue about which one operations trust. Place Order REST is there for Order / OrderItem. Pick the object on the first call. Do not let a plugin decide it.

Bulk is a different door when the volume is real.

Bulk API 2.0 is REST and async. Salesforce suggests Bulk for more than about 2,000 records. Historic order loads and nightly contact backfills belong there. A chatty per-order REST loop that was fine at fifty orders a day will not stay fine.

None of that makes the CRM or the store worthless. It does mean “sync everything to Salesforce on Monday” is not a design.

How we work

We start with the org and the store, not with a Commerce Cloud brochure.

1

Look at what you have

Store platform, Sales / Service Cloud versus SFCC, whether Orders or Opportunities are the target, Connected App state, and where stock actually lives. We will tell you which API this is — CRM REST or a conversation you should not have on this page.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Account and Contact upsert first, then Order / OrderItem (or Opportunity) from paid carts, then status back. A sandbox org beats a Friday write into production automation.

4

Hand it back so the next person can run it

Source, the Connected App, and a short record of which object a web order becomes.

Three honest outcomes

  • Connect the store to Salesforce CRM: upsert Contact and Account, create Order + OrderItem or Opportunity from paid carts, push fulfilment status, use Bulk API 2.0 where the volume needs it. Custom API work. No published CoSource Salesforce ecommerce case.
  • Fix a broken connector when a plugin still almost works: stop writing Contacts as Leads, pick Order versus Opportunity, or move historic loads onto Bulk.
  • Decide not to connect when the real product is Commerce Cloud (SCAPI), when Salesforce is being asked to be the warehouse, or when a Salesforce-native B2B Commerce product already owns the storefront.

We will not tell you Sales Cloud is an ERP. We will not treat a CRM REST build as a Commerce Cloud build. If you already have a Salesforce SI who owns the org, they may be the better first call on that side. If you want an honest fork in the road on the store, talk to us.

What we need for the first call

A store URL and which Salesforce org is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS
  • Sales Cloud / Service Cloud, or actually Commerce Cloud
  • Whether a web order should become an Order, an Opportunity, or both
  • Rough daily order volume, and whether historic orders need a backfill
  • Where stock and invoices really live (not Salesforce, if you are honest)
  • What “done” looks like: a working sync, a repaired plugin, or a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a “Salesforce commerce” estimate for the wrong cloud.

Related work

We have not published a Salesforce ecommerce case. NESS is nopCommerce and Dynamics NAV 2018. Windsor is Peach and Xero. Neither is Salesforce.

CoSource is a Sydney software firm and a nopCommerce Gold Partner. Services include CRM & ERP integration on nopCommerce, AbleCommerce, and Shopify. That is a capability, not a Salesforce case study. A Salesforce org still starts with its own assessment.

FAQ

Is this Salesforce Commerce Cloud?
Only if you run SFCC. This page is CRM objects — Accounts, Contacts, Orders — on the REST API. SCAPI is a different API. Say which cloud you have.
Can checkout create a Salesforce order?
Yes. Place Order REST for Order / OrderItem, or create an Opportunity if that is how the org works. Decide that before the plugin does.
Does Salesforce hold stock?
Sales Cloud is not an inventory system and not an ERP. Stock belongs in the warehouse or ERP product you already run.
When do we need Bulk API?
Salesforce suggests Bulk API 2.0 above about 2,000 records. Historic backfills and large nightly jobs belong there.
Do you have a Salesforce store case?
No. We will not invent one or an AU org count.

Talk through the Salesforce connection you already need

Thirty minutes. Bring a store URL and whether you mean Sales Cloud or Commerce Cloud. We will tell you which objects to write, whether to connect, or whether Salesforce is the wrong system for the job.

Book a free 30-minute discovery call