> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-catalog-integration/how-to-configure-salesforce-commerce-cloud-integration.md).

# How to configure Salesforce Commerce Cloud integration

Connect your **Salesforce Commerce Cloud (SFCC)** environment with **AB Tasty Recommendations & Merchandising** to sync your product catalog and enable personalized recommendations directly in your storefront.

{% stepper %}
{% step %}

#### **Fill in your Salesforce API credentials**

To connect your Salesforce Commerce Cloud account, fill in the following fields as shown in your AB Tasty dashboard interface.

You can find detailed instructions in the official Salesforce documentation: [Add API Client ID in Salesforce B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_account_manager_add_api_client_id.htm\&type=5)

**Required fields**

| Field             | Description                                                                                           |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| **Catalog Id**    | The ID of the catalog you want AB Tasty to use for product data (e.g. `apparel-catalog`)              |
| **Site Id**       | The ID of your Salesforce Commerce Cloud site (e.g. `RefArch`, `mysite_FR`)                           |
| **Client Id**     | The Client ID from your **Salesforce Account Manager (API Client)** used to authenticate API requests |
| **Client Secret** | The Client Secret linked to the Client ID above                                                       |
| **API Version**   | The version of the Salesforce API you are using (e.g. `v23_2`)                                        |

Once all fields are filled, click **CONTINUE** to validate your credentials.
{% endstep %}

{% step %}

#### **Authentication & connection**

AB Tasty will test your credentials and establish a secure connection to your Salesforce Commerce Cloud instance.\
If successful, you’ll see a confirmation message and the integration status will switch to **Connected**.

If an error occurs:

* Double-check the Client ID and Secret are active in your **Account Manager**
* Ensure the API user has access to the selected **Site ID** and **Catalog ID**
* Verify that your **API version** matches the one used in your SFCC environment
  {% endstep %}

{% step %}

#### **Finalize**

Once connected, AB Tasty will automatically:

* Import your **catalog structure** and product data
* Keep your inventory synchronized
* Allow you to **deploy recommendations** and merchandising strategies directly on your SFCC storefront
  {% endstep %}
  {% endstepper %}

You can then proceed to the **Recommendations deployment** or **Merchandising setup** section in your AB Tasty dashboard.


---

# 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.abtasty.com/recommendations-and-merchandising/how-tos/how-to-configure-your-catalog-integration/how-to-configure-salesforce-commerce-cloud-integration.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.