> 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/concepts/strategies/rules.md).

# Rules

Rules are the **foundation of every strategy**. They define *which products* are returned and *how they are ordered*.\
In the builder, rules are created by combining **Rule Blocks** (main sources of products) and **Custom Rules** (filters and transformations).

### How to combine rules

A rule typically looks like this:

1. Start with a **Rule Block** (e.g., *Products sorted by `Sales`*).
2. Apply one or more **Custom Rules** (e.g., *Filter `stock` > 0*, *Exclude `PDP product`*, *Pin `Hero product`*).
3. Define **output constraints** (number of products, fallback if not enough).

**Example:**

1. Rule Block: *Products sorted by `conversion rate` (desc)*
2. Filter: *`Stock` > 0*
3. Exclusion: *`Current product`*
4. Pin: *`Promo SKU` always at top*
5. Limit: *12 products*

This results in a **reliable, business-aligned product list** for your strategy.


---

# 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/concepts/strategies/rules.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.
