> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/data/products.md).

# Products

Select, filter, and sync the catalog data available to Sagent.

The **Products** section determines which catalog items Sagent can recommend. A focused, current catalog keeps conversations relevant and prevents unsuitable products from appearing.

Use these settings to select a source feed, limit the available assortment, and sync changes before testing.

### Select the data source

Open **Data → Products**. The configured product feed serves as Sagent's data source and syncs per locale.

Select the locales that Sagent should support. Sync the default locale so visitors without a matched locale receive results.

### How Sagent uses product properties

Sagent uses only selected **faceted properties** and their **list options**. It cannot use non-faceted properties or free-text values during conversations.

Sagent uses these values to:

* answer shopper questions about product attributes;
* ask clarifying questions that narrow product matches;
* compare products and explain meaningful differences.

Select properties with clear, complete option values. Incomplete or inconsistent values can produce unclear questions, answers, and comparisons.

### Choose product properties

Sagent requires these default properties for every product card:

* **Title** identifies the product.
* **Image** provides the product image.
* **Product ID** identifies the catalog item.
* **Description** provides product context.
* **URL** links to the product detail page.
* **Price** and **Sale price** show current pricing.
* **Rating score** and **Rating count** show review information.

Select faceted properties that help shoppers narrow the catalog. Use properties with consistent list values, such as product type, size, material, features, capacity, or use case.

Use selected faceted properties for discovery, recommendations, and comparisons. They must distinguish meaningful product differences.

For each supported locale, provide localized product-card values and property options. Sync every locale after changing its data.

### Select properties and products

{% stepper %}
{% step %}

#### Select product properties

Click **Manage columns** to select the faceted properties Sagent needs. Include properties and list options that support questions, answers, and product comparison.
{% endstep %}

{% step %}

#### Filter the assortment

Use **Filter** to limit the assortment when needed. For example, filter to a specific category or brand.
{% endstep %}

{% step %}

#### Save and sync

Click **Save**, then click **Sync**. Sagent uses the selected properties and filtered products after the sync completes.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Sync the default locale before launch. Visitors without a matched locale use this catalog.
{% endhint %}

### Locale and sync requirements

Each supported locale needs a synced product feed. Sagent uses the selected locale's most recent successful sync.

Changes to product data, selected properties, filters, or list options are unavailable until you sync again. Visitors without a matched locale use the default locale.

{% hint style="warning" %}
Sagent cannot return catalog results for an unsynced locale. Sync the default locale so unmatched visitors can receive results.
{% endhint %}

### Search and validate products

Use product search and filters to confirm the expected products are available. Adjust filters or source data when results are missing or incorrect.

### Troubleshoot catalog issues

Use this matrix after every sync and before publishing.

| Issue                      | Check                                                       | Change                                                                                                              | Then                                         |
| -------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| Missing products           | Search the affected locale and review the Sagent filters.   | Update the **source feed** if the product is absent. Update **filters** if it is excluded.                          | Sync the locale again.                       |
| Missing attributes         | Check the product record and selected faceted properties.   | Update the **source feed** or mapping. Select the property in **Manage columns**.                                   | Save and sync again.                         |
| Unexpected recommendations | Review matching products, selected properties, and filters. | Update **filters** for assortment issues. Correct **source feed** values or selected columns for incorrect matches. | Sync, then retest the same query.            |
| Stale catalog data         | Check whether the upstream feed contains the latest values. | Update the **source feed** or its scheduled fetch.                                                                  | Run the feed update, then sync Sagent again. |

### Frequently asked questions

<details>

<summary>When should I sync?</summary>

Sync after changing selected properties, filters, or locale data. Test Sagent after every sync.

</details>

<details>

<summary>Why does the default locale need a synced feed?</summary>

Visitors without a matched locale use the default locale. A synced default feed ensures they receive product results.

</details>

<details>

<summary>Why is Sagent not using a product property?</summary>

Select it in **Manage columns** and confirm it is faceted with list options. Save and sync before testing again.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/how-to-guides/sagent/data/products.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.