> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/manage-improve-product-data/categorize-products/manual-categorization/add-category-rule.md).

# Add category rule

Create a category rule for products that match a field value.

Create a category rule when you need complete control over a mapping.

{% stepper %}
{% step %}

#### Open manual categorization

Open the channel where you want to create the rule.

1. In Channable, open your channel.
2. Go to **Categories**.
3. Click **Manual categorization**.
   {% endstep %}

{% step %}

#### Define the products to categorize

Set the condition that identifies the products for this mapping.

1. Click **+ Add category rule**.
2. Select the field that identifies the products.
3. Select a filter.
4. Enter the value that the rule should match.
   {% endstep %}

{% step %}

#### Select the channel category

Choose the category that the matching products should use.

1. Click **Set to category**.
2. Select the appropriate channel category.
3. Repeat these steps for each mapping you need.

For example, create a rule where `categories` contains `shoe`, then select **Clothing & Accessories > Shoes**.
{% endstep %}

{% step %}

#### Save and review coverage

Save the rules, then confirm that they categorize the intended products.

1. Click **Save** to run the category rules.
2. Review the categorized and uncategorized item counts.
3. Click a category count to inspect the matched products.
   {% endstep %}
   {% endstepper %}

{% hint style="info" icon="lightbulb" %}

#### **Tip**

Use the `contains` filter when a keyword appears in several source categories. This can reduce the number of rules when they map to the same channel category.
{% endhint %}


---

# 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://helpcenter.channable.com/manage-improve-product-data/categorize-products/manual-categorization/add-category-rule.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.