> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/catalog/items/item-variants.md).
# Item Variants
Often times, it is necessary to provide a configuration experience to re-sellers or distributors for use on their website/eStore. Additionally, the ability to offer only a subset of a configuration experience is also required. In Threekit, Product Variants are used to address these requirements.
Below are the steps to ensure the configuration experience is consistent and representative of the options specific to a given distributor/re-seller.
### Create a Product Variant
Steps to creating a product variant are as follows:
#### 1.) Navigate to the desired Catalog Item.
#### 2.) Click **Create Variant**
A new Item, "*Item name* Clone", will be created. The master configurator will be connoted and accessible below the variant's Item name.
Note that the variant has no assigned asset. By default, the variant uses the asset referenced in the master item. This ensures any modification made to improve the visual quality of the corresponding master asset propagates to all variants.
#### 3.) Manipulate Attributes/Rules
Add/Remove Attributes and/or Attribute values as necessary. Enforce any business logic unique to the variant by way of Rules.
#### 4.) Click **Save**
Once a variant has been created, it is accessible via the Catalog, as well as the drop down on the master Item.
### Publish the Product Variant
Re-sellers and Distributors are able to publish variants of the configurator by [embedding the Threekit Player ](https://developer.threekit.com/reference/embedding-the-threekit-player#optional-parameters)using their unique [Public Token](/platform-documentation/org-setup/admin-and-security/service-accounts.md), along with the Item Id of the appropriate variant.
---
# 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://community.threekit.com/platform-documentation/project-data/catalog/items/item-variants.md?ask=&goal=
```
`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.