> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/set-payout-rules-for-exception-lists.md).
# 为类别、SKU 或促销码例外列表设置佣金规则
一旦类别、SKU 或促销代码例外列表处于启用状态，您就可以在以下位置的模板条款中将其添加到 **支付组** 选项。
{% hint style="success" %}
**支付逻辑：** 如果满足某个支付组的条件，它将按与模板条款默认支付相同的级别（订单或商品）应用支付变更。例如，如果您的默认支付是在商品级别应用，那么当特定商品属于该支付组中输入的类别时，其支付将会更改。
{% endhint %}
#### 为例外列表设置支付规则
{% hint style="warning" %}
SKU and promo code [exception lists](/brand/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists.md) are not available in every impact.com edition. For example, Product-Led Growth (PLG) edition accounts do not include the **SKU** or **Promo Code** option under *Exception Lists*. If you do not see either option, you may need to upgrade your account. [Contact support](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml).
{% endhint %}
1. 在左侧导航菜单中，选择  **\[参与]** → **合同 → 模板条款**.
2. 将鼠标悬停在您想添加例外列表的模板条款上，然后选择  **\[更多]→ 修改条款**.
* 如果您想创建新的模板条款，请选择 **创建模板条款** 在右上角。
3. 在 *支付组*中，选择  **\[开启]**，然后选择 **新增**.
4. 从第一个  **\[下拉菜单]** 旁边的 *规则*，选择以下选项之一：
* 订单促销代码列表
* 商品类别列表
* 商品 SKU 列表
如果您的版本不包含 SKU 或促销代码例外列表，则这些规则选项不会显示。
5. 继续通过选择以下内容配置规则 **是** 作为运算符和例外列表条目的值。列表名称将根据已设置的内容自动填充。
* 例如 `商品类别列表` `是` `服装`
6. 设置 **支付** 用于列表中的商品。
7. 选择 **添加** 即可完成该过程。
{% hint style="success" %}
**注意：** 您可以在相应的模板条款中查看并下载这些例外列表。
{% 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/set-payout-rules-for-exception-lists.md?ask=&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.
