> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/ecom-platforms/salesforce-commerce-cloud.md).

# Salesforce Commerce Cloud

Overview of Violet's Salesforce Commerce Cloud (SFCC) integration for channel developers

Salesforce Commerce Cloud (SFCC), formerly known as Demandware, is an enterprise ecommerce platform. SFCC uses the Open Commerce API (OCAPI) for backend integrations. This is one of the more involved platform setups due to SFCC's access control model.

## Connection

SFCC credentials are passed as a JSON blob containing the following fields:

| Field                   | Description                                         |
| ----------------------- | --------------------------------------------------- |
| `ocapi_client_id`       | OCAPI client ID configured in Business Manager      |
| `ocapi_client_password` | OCAPI client password                               |
| `access_key`            | Business Manager access key for the connecting user |
| `username`              | Business Manager username (email)                   |
| `site_id`               | The SFCC site ID to connect (e.g. `RefArch`)        |

The store URL is also required.

## Required OCAPI Permissions

Violet validates OCAPI permissions during authentication. Both **Shop API** and **Data API** resource access must be configured in Business Manager for the provided client ID. Violet checks for a defined set of required resources across both API types and returns a detailed error listing any missing scopes if they are not present.

To simplify setup, merchants can grant wildcard (`/**`) access to the client ID rather than configuring individual resource paths.

## Merchant Setup Requirements

* **Customer Group**: The SFCC site must have a customer group named `VIOLET_API`. Violet-submitted orders are placed under this customer group.
* **Payment Method**: A payment method must be configured on the site that Violet can reference when submitting orders.

## Webhooks

SFCC does not support traditional real-time webhooks for the OCAPI integration. Product and order data is synchronized via scheduled sync jobs rather than push notifications.

## Notable Behavior

* **Order management**: SFCC order management is handled separately from the core OCAPI integration. If merchants use a standalone Order Management System (OMS) alongside SFCC, additional configuration may be required.
* **Locales and sites**: SFCC supports complex multi-locale and multi-site configurations. Violet connects to the site specified in the `site_id` credential field.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.violet.io/ecom-platforms/salesforce-commerce-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.