Reference · built on requestConnectorCommerce & orders

Salesforce B2C Commerce

Orders, customer records, and Omnichannel Inventory availability from a B2C Commerce realm through the SCAPI Admin APIs.

Request accessPricing ↗

About

Salesforce B2C Commerce runs storefront sites inside a realm of instances: sandboxes, staging, development, and production. The B2C Commerce API (SCAPI) serves each instance at {shortCode}.api.commercecloud.salesforce.com, split into Shopper APIs and Admin APIs. Admin APIs such as Orders, Customers, and Inventory Availability take a bearer token from Account Manager. The older Open Commerce API (OCAPI) is deprecated as of April 2026.

An operator on Fibric searches orders by status and date, reads customer records from a customer list, and proposes an order status, export status, shipping status, or shipping address change for your approval, with a receipt for each.

This is a reference listing. It documents what Fibric would read from Salesforce B2C Commerce and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Orders by order number, or by search on status, export status, payment status, shipping status, and creation or modification date
  • Order status values created, new, failed, completed, and cancelled, plus confirmation, export, external, payment, and shipping statuses
  • Customer records, addresses, and customer groups in a customer list through the Customers Admin API
  • Inventory availability by SKU for a group or a set of locations from Omnichannel Inventory
  • A delta stream of inventory changes since a token was issued, for groups and standalone locations
  • Sites, catalogs, products, and price books through the other Admin APIs in the reference

Proposed actions

  • Target capability: propose an order status change, for example new to cancelled, or export status to exported
  • Target capability: propose a shipping address update on a placed order
  • Target capability: propose payment status or shipping status values such as paid or shipped
  • Target capability: propose an inventory availability update for one SKU at one location

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Move an order from placed to exported without a spreadsheet

    Search orders with export status ready, hand them to the warehouse feed, and propose setting export status to exported once the file is confirmed.

    With Short Pick, Tracking Sync

  • Cancel cleanly when the shopper asks

    Read the order and its payment status, then propose cancelled, which releases inventory reservations and coupon redemptions, for one-click approval.

    With Cancellation Window, Order Risk

  • Fix the address before the label prints

    When support flags a bad address, propose the shipping address change on the order while shipping status is still not_shipped.

    With Address Repair, Ship-To Change

  • See stock the way the storefront does

    Read group availability for the SKUs on open orders and flag lines that will short before the pick wave.

    With Oversell Watch, Stockout Forecast

Requirements

  • A B2C Commerce realm with a short code requested under Administration > Site Development > Salesforce Commerce API Settings
  • An API client in Account Manager set to client_secret_post and JWT, with allowed scopes such as sfcc.orders.rw and sfcc.inventory.availability
  • The organization ID of each instance, for example f_ecom_zzte_053, and the tenant ID for Omnichannel Inventory
  • A scope string of the form SALESFORCE_COMMERCE_API:{realm}_{instance} followed by the API scopes
Authentication
An Account Manager API client holding the Salesforce Commerce API role; a client_credentials grant against account.demandware.com/dwsso/oauth2/access_token returns a bearer token for one instance.

Limits

  • A token covers one instance; production, staging, and each sandbox need their own token request
  • An API client made for SCAPI cannot be used for OCAPI, and the reverse
  • Order search filters cover the status fields and dates; anything else needs the order number
  • A newly requested short code can take up to 24 hours to propagate before requests route

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Salesforce B2C Commerce ↗

Questions and answers

What is the difference between SCAPI and OCAPI here?
SCAPI is the current B2C Commerce API and what this connector reads. OCAPI is the older API, marked deprecated in April 2026 and kept for two more years with security updates only. The two need separate API clients, and an OCAPI client must not carry the Salesforce Commerce API role.
Which order statuses can be set through the Orders API?
Order status: created, new, failed, failed_with_reopen, completed, cancelled. Confirmation status: not_confirmed, confirmed. Export status: not_exported, ready, exported, failed. Payment status: not_paid, part_paid, paid. Shipping status: not_shipped, part_shipped, shipped. Setting new places the order; cancelled releases its inventory reservations.
How is a request addressed to the right instance?
Every URL follows https://{shortCode}.api.commercecloud.salesforce.com/{apiFamily}/{apiName}/v1/organizations/{organizationId}/. The short code belongs to the realm; the organization ID, such as f_ecom_zzte_053, names one instance. Both appear in Business Manager under Salesforce Commerce API Settings.
Ask about Salesforce B2C Commerce

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Salesforce B2C Commerce through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy