> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/products/catalog/filters-advanced.md).
# Filters (Advanced)
The main difference between simple filters and advanced filters is that advanced filters stay on till you disable or change them.
{% hint style="success" %}
Filtering by SKU is limited to 1000 SKUs.
{% endhint %}
To start using them click on the *FILTERS* button.
This will open a space where you can drag one or more attributes to. You can use both Product and System attributes.
If you are using attributes that are not simple text there may be additional options on the drop-down list for you to choose from.
It's possible to add categories to the filter as well but here instead of using drag\&drop, you need to check the category or categories you wish to add to the filter.
To clear the values of filters but leave them as set up use the ***Clear*** button.
As advanced filters stay till changed or disabled you need to remove them manually, to do so click on *Remove filters*.
---
# 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://usermanual.ergonode.com/products/catalog/filters-advanced.md?ask=&goal=
```
`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.
