> 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/merchandising/how-merchandising-works.md).

# How Merchandising Works

Each merchandising strategy creates a **ranked list of products** based on rules and algorithms (bestsellers, new arrivals, margin, etc.).

**Key principles**

* Every strategy has a unique **MERCH\_ID**.
* **Scores** are automatically computed and synchronized via API.
* Your **CMS consumes these scores** to reorder products in its catalog.
* **Filters** on your website only hide products — they **don’t change AB Tasty’s ranking**.

**Data flow overview**

1. **Score generation** – AB Tasty calculates a merchandising score per product and strategy.
2. **API sync** – Scores are sent to your CMS or search engine.
3. **Catalog update** – The CMS reorders products using these scores.
4. **Front-end display** – The ordered list is shown on your website; filters simply hide non-matching items.

**Integration logic**\
Your CMS retrieves scores via API:\
`GET https://api.abtasty.com/reco/<MERCH_ID>` → returns product SKUs with their scores.

The CMS then applies these scores as a **sorting layer**. AB Tasty doesn’t recalculate dynamically, ensuring **stable performance**.

**Sync frequency**

* Scheduled (daily/hourly) or manual


---

# 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.abtasty.com/commerce/merchandising/how-merchandising-works.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.