> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/model-amplifications/variant-attributes.md).

# Variant attributes

## Variant attributes

{% hint style="info" %}
Note: Our Model Amplifications feature **only accepts files in CSV format at this time.** Please make sure the files you upload are CSV files.
{% endhint %}

## Overview

The Variant Attribute configuration maps additional attributes per variant that may not be available in the OMS. While the OMS may have fields for capturing some attributes within variants, Brand operators often want more flexibility and control over their products.

This configuration provides the ability to add a three-tiered hierarchy per variant including Category, Sub Category, and Class. Utilizing all three layers is not required.

Additional attributes per variant can also be added and updated here including:

* **Color**
* **Function**
* **Material**
* **Shape**
* **Size**
* **Style**
* **Other** - this can include multiple fields not represented by the above attributes, separated by a comma.

All of these attributes flow through the model and are surfaced in the Line Items Explore.

{% hint style="info" %}
**Note:** The configuration allows for only one row per variant.
{% endhint %}

### Sample use cases

While surfacing additional information is useful, these fields can be used to answer more nuanced questions:

* A brand has recently released a new item and want to see performance by size - not just net revenue, but returns over time. Color can be added to pivot and see the performance over time.
* A brand wants to segment their customers based on the purchase of a certain product and the function.
* A brand has different teams working on specific product lines. The hierarchy can be used to quicky filter a dashboard for the individual teams needs without having to build a custom dimension.

Surfacing these fields opens up the ability to slice the data in more dimensions and manage reports in new way.


---

# 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://docs.chord.co/model-your-data/model-amplifications/variant-attributes.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.