> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/product-design/attributes.md).
# Attributes
Learn what attributes are, compare the 12 attribute types, and manage the attributes grid, from creating to batch actions.
{% hint style="info" %}
A single Gallery, File, and Multi select type attribute is limited to a maximum of 100 elements (options) attached to it
{% endhint %}
The idea of attribute management is at the core of efficient product catalog enrichment and distribution. On the following pages, we will show you our thinking behind the role of attributes in our Ergonode PIM system.
## What is an attribute?
Photos, videos, technical data, file numbers, price and shipping information, or product descriptions in the right context become key tools to help customers make purchasing decisions on the Internet. They allow for describing and mapping product data in the digital world.
This set of tools is called product information, it is a comprehensive collection of all information describing the product.
The illustration below shows some specific attributes designed for an assortment of lightbulbs:
* image (to upload photos e.g. JPG, PNG)
* unit (to describe height, diameter, and luminosity)
* select (for selecting color variants of a lightbulb)
## Different types of attributes in Ergonode
There are 12 attribute types in Ergonode.
| Attribute | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Text | This attribute is a field with a single line of text. Maximum 255 characters. |
| Textarea | This is a multi-line text field attribute with the possibility of enabling rich-text functionality, with a built-in JS Editor, allowing for block-styled editable modules of content, including paragraphs, headings, images, lists, and more. |
| Unit | Used to present units according to the SI system (i.e., 200hz or 3m) and fully customized units (for example special custom packaging units). When used a unit selector appears underneath. This unit will appear with the entered attribute value. |
| Image | Used to present photos in the most popular formats, such as main product image or context use product image. |
| Gallery | An attribute used to present multiple images in the most popular formats. Users can view images in “slider mode”. The Gallery attribute is linked directly with assets and any image uploaded to the media directory can be attached to it. |
| File | With this attribute, you can link any file uploaded to the asset directory (for example doc/sheets/presentations/images/zip files). |
| Numeric | Used to present numbers only, for instance, the number of products in stock. The number cannot start with 0 (zero) Ex: 01 will be trimmed to 1. To store a number that starts with 0 please use text type attribute. |
| Select | Used when out of multiple options only one can be chosen i.e., country of origin. Options are added on the *Options* tab once the attribute is created: type the option code in the *Option code* field and click on *Add*. This can also be done directly from the product card. To remove an option click the ***bin icon***. To change the order of options, double click on the number in the *Position* column. |
| Multi select | Used to present multiple options where one or more can be chosen, for instance, colors on a bicycle or constituent materials of the fabric used in the manufacture of an article of clothing. To add an option, type its code in the *Option code* field on the *Options* tab and click on *Add*. This can also be done directly from the product card. To remove an option click the ***bin icon***. To change the order of options, double click on the number in the *Position* column. |
| Date | Used to specify a date in a selected format, for example, to denote a product’s expiry date. |
| Price | Used to denote prices in selected currencies. While creating this attribute, a currency selector will appear. |
| Product relations | Used to denote relationships between two different products for the purposes of cross-selling or upselling. Two-way relations can be created by editing the product relation attribute on the [product template tab](https://usermanual.ergonode.com/products/catalog/template#product-relation-attribute). |
{% hint style="info" %}
The limit on the number of products linked to a single product via the product relations attribute is 100
{% endhint %}
{% hint style="info" %}
Information on how to work with the grid can be found [here](https://usermanual.ergonode.com/products/catalog/system-views/table-view-grid-view)
{% endhint %}
The attributes grid shows the *Index*, *Attribute code*, *Name*, *Type*, *Scope*, *Group*, *Templates* and *Sections* columns. *Templates* and *Sections* list the product templates and [Sections](https://usermanual.ergonode.com/product-design/product-templates/sections) that use the attribute.
To add an attribute, click on ***New attribute*** in the upper right corner ([Create a new attribute](https://usermanual.ergonode.com/product-design/attributes/create-a-new-attribute)).
Above the grid, the table view icon ([System views](https://usermanual.ergonode.com/products/catalog/system-views)) and the ***settings (gear)*** icon ([Display settings](https://usermanual.ergonode.com/products/catalog/system-views/display-settings)) change how the grid is displayed.
Tick the checkbox in the first column to select attributes for [Attributes Batch Actions](https://usermanual.ergonode.com/product-design/attributes/attributes-batch-actions). The arrow next to the checkbox in the column header selects or deselects all attributes or the current page.
To edit an attribute click on the ***edit (pen)*** icon. There are three tabs in edit mode [General](https://usermanual.ergonode.com/product-design/attributes/general), [Translations](https://usermanual.ergonode.com/product-design/attributes/translations), and [Metadata](https://usermanual.ergonode.com/product-design/attributes/metadata).
{% hint style="info" %}
There may be two more tabs called [Options](https://usermanual.ergonode.com/product-design/attributes/options) and [Custom fields](https://usermanual.ergonode.com/product-design/attributes/custom-fields) if you are editing attributes with options ex: select or multi select. Text, Textarea, Numeric, Unit, Price, Image, Gallery and File attributes have a [Validation](https://usermanual.ergonode.com/product-design/attributes/validation) tab instead.
{% endhint %}
To delete an attribute click on the ***bin icon***.
{% hint style="info" %}
Attributes cannot have any relations in order for them to be deleted.
{% endhint %}
You can also use the ***three dots*** menu on the attribute edit page, which offers *Clone attribute* and *Remove attribute*.
---
# 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://usermanual.ergonode.com/product-design/attributes.md?ask=&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.
