> 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/what-would-you-like-to-learn-about/platform-features/product-catalogs/product-catalog-field-requirements.md).

# Product Catalog Field Requirements

To have your products appear in areas where partners can see and interact with them, your catalog must include accurate and complete data in key fields. If you're also working with sellers through [retailer seller partnerships](/brand/what-would-you-like-to-learn-about/seller-program/beta-seller-for-retailers/im-a-retailer/seller-explained-for-retailers.md), then there are additional fields that become mandatory. Any product missing a required field may be excluded from Marketplace surfaces like the Product Marketplace and Mobile App.

## Catalog fields list

Every product catalog field is listed below under its requirement level with guidelines on how to populate the field correctly. Once you're done adding the correct fields to your catalog file, make sure it follows the [Product Catalog Best Practices](/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/product-catalog-best-practices.md) before you [upload the catalog to impact.com](/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/add-product-catalogs-as-a-brand.md).

{% hint style="warning" %}
**Warning**: When filling out the fields in your catalog file, avoid placeholders like `TBD` or `N/A`, inconsistent formatting, and leaving critical fields empty.
{% endhint %}

<details>

<summary>Mandatory fields</summary>

These fields are <mark style="color:red;">**always required for all product catalogs and program types**</mark>. Products missing these fields may be excluded from Marketplace surfaces like the Product Marketplace and Mobile App.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Field</th><th>How to populate it</th><th>Why it matters</th></tr></thead><tbody><tr><td>CatalogItemId</td><td>Enter the unique identifier for the item within the catalog, such as a SKU or ASIN.</td><td>Prevents duplicate records, supports reliable updates, and simplifies troubleshooting.</td></tr><tr><td>Product Name</td><td>Use clear, specific names so your products are easy to find in search results, such as <code>Men's Running Shoes—Blue, Size 10</code>.</td><td>Improves search accuracy and sales.</td></tr><tr><td>Product URL</td><td>Use a valid URL that leads to a live product details page (not a generic landing page).</td><td>Sends traffic to the correct page and reduces bounce rates.</td></tr><tr><td>Image URL</td><td>Use high-resolution images hosted on reliable servers.</td><td>Builds trust and improves click-through and conversion rates.</td></tr><tr><td>Stock Availability</td><td><p>Include one of the following product availability statuses:</p><ul><li><code>InStock</code></li><li><code>OutOfStock</code></li><li><code>BackOrder</code></li><li><code>PreOrder</code></li><li><code>LimitedAvailability</code></li></ul></td><td>Avoids promoting unavailable items and shows accurate availability.</td></tr><tr><td>Price (Original/Current)</td><td>Include both values when applicable, especially for discounted items. Only products priced above $2.00 USD appear on <a data-footnote-ref href="#user-content-fn-1">Marketplace surfaces</a>.</td><td>Shows value clearly and avoids pricing confusion.</td></tr></tbody></table>

</details>

<details>

<summary>Mandatory fields for Seller</summary>

When working with sellers through [retailer seller partnerships](/brand/what-would-you-like-to-learn-about/seller-program/beta-seller-for-retailers/im-a-retailer/seller-explained-for-retailers.md), <mark style="color:red;">**these fields are required in addition to the**</mark> [<mark style="color:red;">**Mandatory fields**</mark>](#mandatory-fields). Products missing these fields cannot be correctly mapped to a seller.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Field</th><th>How to populate it</th><th>Why it matters</th></tr></thead><tbody><tr><td>Seller ID</td><td>Enter the internal unique identifier of the <a data-footnote-ref href="#user-content-fn-2">3P seller</a> offering the product.</td><td>Identifies which products belong to each 3P seller.</td></tr><tr><td>Seller Name</td><td>Enter the name of the <a data-footnote-ref href="#user-content-fn-2">3P seller</a> offering the product, or for a <a data-footnote-ref href="#user-content-fn-3">1P product</a>, enter the retailer (your) name.</td><td>Identifies who is making the offer, often shown under 'Sold by'.</td></tr><tr><td>Retail Strategy</td><td><p>Enter one of the following options:</p><ul><li><a data-footnote-ref href="#user-content-fn-3"><code>1P</code></a></li><li><a data-footnote-ref href="#user-content-fn-3"><code>WHOLESALE</code></a></li><li><a data-footnote-ref href="#user-content-fn-4"><code>3P</code></a></li><li><a data-footnote-ref href="#user-content-fn-4"><code>MARKETPLACE</code></a></li></ul></td><td>Identifies whether this is a 1P or 3P offer.</td></tr><tr><td>Manufacturer</td><td>Include the brand of the product.</td><td>Improves search results and powers the <em>Top Product Brands</em> filter partners use.</td></tr><tr><td>Category</td><td>Use consistent, clear product categories so your products appear in the right category.</td><td>Helps products appear in relevant searches and category views.</td></tr></tbody></table>

</details>

<details>

<summary>Strongly recommended fields</summary>

These fields are not enforced unless noted otherwise, but products missing these fields perform worse in search, filtering, and partner discovery. <mark style="color:red;">**Including these fields is recommended for every catalog**</mark>, regardless of whether you work with partners, sellers, or both. Fields marked with an asterisk (\*) become mandatory in the circumstances described.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Field</th><th>How to populate it</th><th>Why it matters</th></tr></thead><tbody><tr><td>Manufacturer<strong>*</strong></td><td>Include the brand of the product. <strong>*Mandatory</strong> when working with sellers through <a href="/pages/oEgpKn1A37wLJwfTxmLu">retailer seller partnerships</a>, and whenever you provide an MPN.</td><td>Improves search results, powers the <em>Top Product Brands</em> filter partners use, and makes MPN values unambiguous.</td></tr><tr><td>Category</td><td>Use consistent, clear product categories so your products appear in the right category.</td><td>Helps products appear in relevant searches and category views.</td></tr><tr><td>GTIN<strong>*</strong></td><td>Provide a valid, unique Global Trade Item Number (GTIN) for the product, for example its UPC or EAN. <strong>*GTIN Type is mandatory</strong> whenever you provide a GTIN.</td><td>Deduplicates your products and matches them to the same item listed elsewhere.</td></tr><tr><td>GTIN Type</td><td>Enter the standard the GTIN follows: <code>EAN</code>, <code>UPC</code>, <code>ISBN</code>, or <code>JAN</code>. Mandatory whenever you provide a GTIN.</td><td>Tells impact.com how to read and validate the GTIN.</td></tr><tr><td>MPN<strong>*</strong></td><td>Provide the Manufacturer Part Number (MPN) assigned by the product's manufacturer. <strong>*Manufacturer is mandatory</strong> whenever you provide an MPN.</td><td>Identifies products that have no GTIN, and keeps compatible parts and variants matched correctly.</td></tr><tr><td>Description</td><td>Provide meaningful, concise product descriptions.</td><td>Gives partners and shoppers the context they need.</td></tr><tr><td>Is Parent</td><td>Indicate whether the SKU is the parent for a set of variants.</td><td>Groups variants correctly and improves browsing.</td></tr><tr><td>Parent SKU</td><td>If the product is a variant, enter the SKU of its parent product.</td><td>Connects each variant to the correct parent product.</td></tr><tr><td>Currency</td><td>Include the 3-digit ISO 4217 currency code for the product price.</td><td>Displays prices correctly and avoids regional pricing errors.</td></tr></tbody></table>

</details>

{% hint style="danger" %}
**Important**: Meeting the mandatory requirements only gets your products onto Marketplace surfaces. To help them stand out and perform well once they're there, see [Product Catalog Best Practices](/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/product-catalog-best-practices.md).
{% endhint %}

## Additional requirements for Seller

When working with sellers through [Retailer Seller partnerships](/brand/what-would-you-like-to-learn-about/seller-program/beta-seller-for-retailers/im-a-retailer/seller-explained-for-retailers.md), your catalog must also contain the following:

* **All seller SKUs** — Every SKU that sellers will use in their Seller Programs must appear in your catalog. If a seller lists a product on your site but the SKU isn't in your impact.com catalog, that product can't be tracked, attributed, or surfaced to partners.
* **All variant SKUs**: Include every variant of a product, not only the parent. For example, if a t-shirt is sold in 3 colors and 4 sizes, each of the 12 combinations must appear as its own row with its own SKU. Parent-only catalogs miss the specific product a shopper actually buys, which prevents accurate attribution.
* **All Buy Box contenders**: If multiple sellers offer the same product, include a row for each seller's offer, not only one row for the winning offer (i.e., include all buy box contenders, not just the buy box winner).

[^1]: The places where partners actually see and interact with your products, such as the Product Marketplace and Mobile App.

[^2]: A seller who lists and sells their own products on your marketplace independently.

[^3]: Products you purchase from a vendor and sell directly to customers as your own stock.

[^4]: Products listed and sold by outside 3rd-party sellers on your marketplace.


---

# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/product-catalog-field-requirements.md?ask=<question>&goal=<endgoal>
```

`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.