> 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/commerce/catalog.md).

# Catalog

Your catalog is the foundation of AB Tasty Commerce. It is the **single shared product source** consumed by every other module, **Recommendations**, **Merchandising** and **Search**. The quality and freshness of your catalog directly determine the quality of the strategies you build on top of it.

This section covers everything from connecting a catalog source, through structuring its datasets and fields, to keeping it continuously up to date.

### The Catalog page

Open **Catalog** in the left navigation to inspect the products currently loaded into Commerce.

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FH5N8eyvVSv51Po8RBJQq%2Fimage.png?alt=media&amp;token=a654bcce-2540-4e2b-99f0-13b6dea1566d" alt=""><figcaption></figcaption></figure>

#### Catalog table columns

The product table lists each product with the following columns:

| Column                   | Description                                                        |
| ------------------------ | ------------------------------------------------------------------ |
| **Image**                | Product thumbnail.                                                 |
| **Name**                 | Product display name.                                              |
| **id**                   | Unique product identifier.                                         |
| **price**                | Product price.                                                     |
| `pageviews_last_30_days` | Number of product-page views in the last 30 days (from analytics). |
| `purchases_last_30_days` | Number of purchases in the last 30 days (from analytics).          |
| `revenues_last_30_days`  | Revenue generated in the last 30 days (from analytics).            |

{% hint style="info" %}
The `*_last_30_days` columns are populated from your connected analytics source. They are also the fields used by default ranking rules such as **Best sellers** and **Most consulted products**.
{% endhint %}

#### Page actions

The toolbar above the table provides:

* **Manage catalog** (gear icon), opens the catalog manager, where you define how your source catalog is imported and create **Smart Tags**. See smart-tags.
* **Display settings**: choose which columns are shown in the table.
* **Filters**: narrow the product list, including filtering by a **Smart Tag**.
* **Search**: the *"Search in your catalog..."* box for finding individual products.

### In this section

| Article                 | What it covers                                                                        |
| ----------------------- | ------------------------------------------------------------------------------------- |
| Connecting a catalog    | Supported sources (Shopify, Magento, Catalog API, CSV…) and how to connect each.      |
| Datasets and fields     | Source, Required and Custom datasets, and Source / Calculated / Enriched field types. |
| Formula fields          | AI-assisted custom fields built with formulas.                                        |
| Smart Tags              | Tag a list of products once and reuse it across strategies and filters.               |
| Catalog synchronization | Keep the Commerce catalog current with its source.                                    |
| Catalog API             | Manage your catalog programmatically without a CMS feed.                              |


---

# 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/commerce/catalog.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.
