> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/manuals/product-management/product-configuration/parameters/variants.md).

# Variants

This article covers what are product variants and how manage them

## Overview

This guide will help you efficiently manage product variants within the HESH application. Whether you're working with a default variant that is automatically created or customizing a list of variants based on specific product parameters, this documentation offers all the essential information you need.

<figure><img src="https://2718719119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2iEmashkfYYrRZjhJnSk%2Fuploads%2F29iTtq6lVVWVAru9GYfF%2Fimage.png?alt=media&amp;token=6602e78a-e59f-47fa-8517-1023d7e0b1bd" alt=""><figcaption></figcaption></figure>

## What are product variants?

Product variants are different versions of a product that can feature various attributes, such as size, color, or other customizable options.&#x20;

## How product variants are created?

The list of variants is automatically generated based on the [parameters](/manuals/product-management/product-configuration/parameters.md) you add to the product's configuration. If a product does not have any parameters specified, the system will automatically create a "default" variant to ensure that there is at least one option available for customers.

## Use cases

### Updating variant's SKU

By default, variants inherit their SKU from the product's configuration value. To update a variant's SKU, follow these steps:

1. Select the variant for which you want to edit the SKU
2. Click on the "Individual SKU" field of the selected variant
3. Type in the new SKU value that you wish to assign to the variant
4. Click :heavy\_check\_mark: to save new SKU

{% embed url="<https://app.arcade.software/share/wTChDZ6U2gKmKSBwKQQc>" %}

### Updating variant's barcode

1. Select the variant for which you want to edit the barcode
2. Click on the "Barcode" field of the selected variant
3. Type in the new barcode value that you wish to assign to the variant
4. Click :heavy\_check\_mark: to save new barcode&#x20;

{% embed url="<https://app.arcade.software/share/2JZnC68IkbMscDzi1BiY>" %}

### Adding photo to the variant

1. Click on the icon for uploading a photo near product variant's name
2. Select a photo from the available options that were added to the product configuration previously
3. Click "Apply" button to add the photo to the variant

{% embed url="<https://app.arcade.software/share/lzPfDJSFLbcaLojSWUGX>" %}

{% hint style="warning" %}
To remove photo, simply click "Cancel application" button
{% endhint %}

### Deactivating variant

1. Select the variant you want to deactivate
2. Untick the checkbox

{% embed url="<https://app.arcade.software/share/a94colYShKxi9CggR9zp>" %}

{% hint style="warning" %}
Deactivated variants won't be be available for [launching in production](/manuals/production/launching-productions.md).
{% endhint %}

### Searching for the variant

1. Enter the value in the search field
2. Click enter

{% embed url="<https://app.arcade.software/share/gHNWdSQJt3ndpi8XDes4>" %}


---

# 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://docs.hesh.app/manuals/product-management/product-configuration/parameters/variants.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.