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

# Custom Rules

Once the base set is defined, you can **refine** it using custom rules. These are applied in sequence.

* **Filter**\
  Restrict results by conditions (e.g., stock > 0, price < 100).

{% embed url="<https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/changes/383/recommendations-and-merchandising/concepts/strategies/rules/custom-rules/filters>" %}

* **Sort**\
  Reorder the product list (e.g., by conversion rate descending).

{% embed url="<https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/changes/383/recommendations-and-merchandising/concepts/strategies/rules/custom-rules/sorting>" %}

* **Limit**\
  Set a maximum number of products to display (e.g., 12 items).
* **Minimum**\
  Ensure a minimum number of products; if not met, fallback rules can be used.
* **Condition (if)**\
  Apply conditional logic (e.g., if category = “Shoes” then show top sellers, else show new arrivals).
* **Exclusion**\
  Remove specific products or groups (e.g., exclude the currently viewed product on a PDP).
* **Shuffle** \
  Randomize order to add variety.
* **Diversificatin** \
  Ensure variety across rules or globally.
* **Pin products**\
  Force specific products into fixed positions (e.g., always pin Hero SKU at position #1).


---

# 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/custom-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.
