> 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/rules-bulk-edit-and-enrich/using-rules/check-rule-results-and-exclude-items.md).

# Check rule results and exclude items

Preview selected items, check rule results, and exclude items from your channel.

Check a rule before you rely on it. You can inspect selected items and confirm which data changes.

### Check affected items

After you save a rule, use the count above it to see how many items it affects. Click **View items** to inspect those items.

Use the counts below a rule to compare items before and after it runs:

* **Before this rule** shows the data before the selected rule runs.
* **After this rule** shows the data after earlier rules and the selected rule run.

Click **View items** for either count to inspect the result.

### Create a check rule

A check rule identifies items without changing them. For example, use this rule to find items missing an image link:

* IF `image_link` **`is empty`**
* THEN take `all fields` and **`do nothing`**

The count above the rule shows the selected items. The count below the rule remains unchanged because **`do nothing`** does not modify items.

### Exclude items

Use an exclusion rule when selected items must not be sent to a channel. For example, exclude items that are out of stock or do not meet channel requirements.

Set a condition that identifies those items. Then use the **`exclude item(s)`** action on `all fields`.

{% hint style="warning" %}

#### Important

Excluded items do not continue through later rules. Place exclusion rules after any rules that must update those items first.
{% 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/rules-bulk-edit-and-enrich/using-rules/check-rule-results-and-exclude-items.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.
