> For the complete documentation index, see [llms.txt](https://docs.yaycommerce.com/yayswatches/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaycommerce.com/yayswatches/how-it-works/how-to-add-attribute-to-products.md).

# How to Add Attribute to Products

The first thing to do is to **Add new** product or **Edit** an existing product, then set **Variable product** as the product data, select **Custom attribute** or choose any of the existing attributes available, define the **values** and check the two options **'Visible on the product page'** and **'Used for variations'** and **Save** changes.

![](/files/znPSTIKmonyPFGVJlLRc)

Next step is to go to **Variation** tab, click the dropdown to either **Add new variation** (as used in the next screenshot below) or select the option to **Create variation from all attributes** available. Add the **Price** and **Image** to all the variations respectivel&#x79;**. Save** the changes.

![](/files/nShcIMpPABpzHiRs4uTz)

The GIF image below shows how it looks like in frontend after saving the settings above:

![](/files/2vbBQJY8AKmyqM7uMx2O)


---

# 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.yaycommerce.com/yayswatches/how-it-works/how-to-add-attribute-to-products.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.
