> 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/partner/what-would-you-like-to-learn-about/platform-features/reporting-for-partners/sku-exception-lists-per-active-io-report.md).
# SKU Exception Lists per Active IO Report
The *SKU Exception Lists per Active IO* report shows SKU items or product variants with payouts that differ from the default in your partnered programs. The report lets you view items from both active and expired contracts — formerly known as insertion orders (IOs).
## Manage the report
1. From the top navigation bar, select **Reports →** **More Reports**.
* Alternatively, from the top navigation bar, select **Reports** **→ More → More Reports**.
2. From the *Category* filter next to the search bar, select **Listing**.
3. Select [**SKU Exception Lists per Active IO**](https://app.impact.com/secure/mediapartner/report/viewReport.report?handle=mp_sku_exception_list_active_IO).
* You can also pin the report to the top navigation bar by hovering over the row and selecting **\[Pin]**.
* You can also add the report to your *Favorited list* by selecting  **\[Heart]**.
4. Below the report title, filter for the data you want to view. Select **Apply** when you have your filters in place.
* See the *Filter* and *Column* references below for more information.
* Use the icons in the upper-right corner of the page to  **\[Schedule]** or**\[Download]** the report in PDF, Excel, or CSV format.
Filter reference
| Filter | Description |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Program | Select a program name from the  **\[Dropdown Menu]** to filter for SKU items associated with a specific brand program. |
| Contract State | Select a status from the  **\[Dropdown Menu]** to view SKU items in *Active*, *Inactive*, or *All* contracts. |
Column reference
| Column | Description |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SKU | The stock-keeping unit (SKU) is the product variant's unique identifier. |
| SKU Name | The name of the product variant as specified in the brand's product catalog, e.g., `Titan Steel Pro Anvil 50kg`. |
| Match Mode | How the brand searched for and identified the SKU in your conversion data — `Exact` indicates an exact SKU value match, while a blank cell indicates the match was determined using a regex search. |
| SKU List | The name of the SKU exception list the brand set up for the item, to pay out differently for it. This may give you insight into why the brand pays out differently for the product — e.g., a list named `Summer Clearance` could mean that the payout is different due to a clearance sale. |
| SKU List ID | The unique identifier of the SKU exception list the brand set up for the item, to pay out differently for it. |
| Contract ID | The unique identifier of the contract between you and the brand. |
| Contract | The brand's name for the contract you're on — e.g., this may be `Public Terms` if you're on their default partner contract, or `Influencer Terms` if you're part of their Influencer partner group. |
| Program ID | The unique identifier of the brand program associated with the SKU item. |
| Program | The name of the brand program associated with the SKU item, e.g., `Summer Fun`. |
---
# 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/partner/what-would-you-like-to-learn-about/platform-features/reporting-for-partners/sku-exception-lists-per-active-io-report.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.
