Connect Salesforce Commerce Cloud
Write-back updates your Salesforce B2C Commerce prices through Salesforce's current Commerce API (SCAPI) — specifically the Price Books Admin API. The older Data API this used to rely on is retired and can no longer write prices, so every connection uses SCAPI now.
What you need
- Access to Salesforce Account Manager to create an API client.
- Your instance's short code, organization ID, and the ID of the price book you want write-back to update.
- The Max or Enterprise plan — Salesforce Commerce Cloud write-back, like the other platform connectors, ships on Max and Enterprise.
Set up an Account Manager API client
- Sign in to Account Manager with an admin account for your Salesforce org.
- Create an API client (or reuse one set aside for this), and set its grant type to
client_credentials. - Add the Salesforce Commerce API role to the client, and scope that role to your tenant using its tenant filter — restrict it to the realm and instance you're connecting.
- Grant the client the
sfcc.price-books.rwscope. This is the only scope write-back needs: it can read and update price-book entries, and nothing else. - Save the client and note its client ID and client secret. You'll enter both when you connect.
Find your short code, organization ID and price book
- Short code — an 8-character code unique to your instance, for example
kv7kzm78. It's the piece before.api.commercecloud.salesforce.comin your instance's API host. You can find it in Business Manager or in URLs your Salesforce team already uses for this instance. - Organization ID — looks like
f_ecom_zzte_053(an ecommerce realm/instance code, usingprd,stg,dev, or a numbered sandbox suffix). Business Manager shows this alongside your other instance details. - Price book ID — the ID of the price book whose prices write-back should update. It must be a standard price book with a currency assigned — not a feed-based price book, which doesn't support individual entry writes. Find it in Business Manager's list of price books.
Connect
- Go to Settings → Integrations.
- Choose Salesforce Commerce Cloud.
- Enter your short code, organization ID, price book ID, client ID and client secret.
- We verify everything before saving anything: we request a token with your credentials, then read the price book you named. The connection is only saved once both succeed — if anything is wrong, nothing is saved and you'll see exactly what to fix.
Once connected, the integration shows your short code, organization ID, price book and its currency, so you can confirm it's pointed at the right instance.
Which prices write-back can update
Write-back updates one price per product in your chosen price book — a single, open-ended amount with no quantity tiers, no date range, and no percentage discount. That's the shape a straightforward "current price" has in Salesforce's price-book model.
- If a product's entry in the price book already has that simple shape, write-back can read and update it.
- If a product has no entry in the price book yet, write-back can't create one — connect the product to your price book in Business Manager first.
- If a product's entry uses quantity pricing, a scheduled price change, or a percentage discount, write-back leaves it alone and flags it rather than risk overwriting your other pricing rules.
- Product variants have their own entries in the price book, so each variant's price is read and written independently of its parent product.
Troubleshooting
While connecting:
| What you'll see | What it means |
|---|---|
| Short code, organization ID or price book ID doesn't look right | The value you entered doesn't match the expected format — double-check it against Business Manager. |
| Price book not found | The price book ID doesn't exist for this organization, or the API client can't see it. |
| Price book uses external pricing | The price book you named is feed-based; choose a standard price book with a currency instead. |
| Currency doesn't match | The price book's currency doesn't match your workspace currency. Connect a price book in your workspace's currency, or update your workspace currency to match. |
| Couldn't verify your credentials | The client ID/secret or scope was rejected. Confirm the client uses the client_credentials grant, has the Salesforce Commerce API role scoped to this tenant, and has the sfcc.price-books.rw scope. |
Once connected, on individual price changes:
| What you'll see | What it means |
|---|---|
| Reconnect required | Your credentials, role or scope no longer work — reconnect with a valid API client. |
| Product not found in the price book | The product has no entry in this price book, so there's nothing to update. |
| Price can't be read cleanly | The product's price-book entry has quantity tiers, a date range, or a percentage discount, so there's no single price to update automatically — check it in Business Manager. |
| Update rejected | Salesforce rejected the price update, or the product's entry was removed since we last checked. |
| Temporary connection problem | A network or Salesforce-side issue interrupted the request. It's usually safe to try again shortly. |
Reconnecting from OCAPI
If your Salesforce Commerce Cloud connection was set up before this update, it's still using the retired Data API and needs to be reconnected. You'll see a reconnect banner on the integration, and price changes won't go through until you do. Because the old and new setups use different Salesforce API clients, this can't be migrated automatically — follow Set up an Account Manager API client and Connect above to reconnect using SCAPI.
Tips
- Test a new connection on a single low-risk product before approving a full batch of recommendations through it.
- Keep the API client's tenant filter scoped to the instance you're connecting — a client that spans multiple tenants is harder to audit and rotate.
- If your workspace currency ever changes, reconnect with a price book in the new currency; a mismatched currency blocks price changes rather than writing the wrong amount.
Go further
- Push accepted prices to your store — how write-back and approvals work across every connector.
- Set pricing policies & guardrails — the rules write-back respects.
- Invite your team & set roles — assign the approver role.

