> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/products/catalog-setup/properties.md).

# Properties

Properties are custom attributes you can add to products – like Size, Color, Weight, or Certifications. They help you describe products in more detail and are essential for creating product variants.

***

### Why properties matter

**Product variants** Properties like Size and Color are used to create configurable products. A t-shirt in sizes S, M, L, XL needs a "Size" property.

**Filtering and search** Staff and customers can filter products by property values to find what they need faster.

**Product information** Store additional details on products – like weight, material, or certifications – for reference or integrations.

***

### Property types

| Type                | What it does                        | Example                               |
| ------------------- | ----------------------------------- | ------------------------------------- |
| **Single Select**   | Choose one option from a list       | Size: S, M, L, XL                     |
| **Multiple Select** | Choose multiple options from a list | Certifications: CE, FSC, Organic      |
| **Text**            | Free text entry per product         | Weight: "2.5 kg", URL to product page |

{% hint style="warning" %}
**For configurable products:** Only Single Select properties can be used to define variants. Each variant needs one clear value per property so the system can identify it uniquely – a t-shirt can be Size M or Size L, not both.
{% endhint %}

***

### How do I add a property?

{% stepper %}
{% step %}

#### Create new property

Head to **Admin → Products → Properties** and select **New Property**.
{% endstep %}

{% step %}

#### Name it and choose the type

Give your property a name (e.g., "Size") and select the type – Single Select, Multiple Select, or Text.
{% endstep %}

{% step %}

#### Add options and save

For Single Select and Multiple Select, click **Add Option** to add the options (e.g., S, M, L, XL). Then click **Save**.
{% endstep %}
{% endstepper %}

The property is now available when adding or editing products.

***

### How do I assign a property to a product?

{% stepper %}
{% step %}

#### Open the product

Find the product in **Admin → Products → Products**.
{% endstep %}

{% step %}

#### Add property and save

Head to the **Properties** tab, select the property, choose an option, and click **Save**.
{% endstep %}
{% endstepper %}

For many products at once, use spreadsheet import instead.

***

{% hint style="success" %}

#### Tips

**Plan for variants first** If you're selling products in different sizes or colors, set up those properties before adding products. It's easier than going back later.

**Keep options consistent** Use "Red" everywhere, not "Red" on some products and "red" or "RED" on others.

**Don't overdo it** Only create properties you'll actually use for filtering, variants, or integrations. Too many clutters the product form.
{% endhint %}


---

# 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.flowretail.com/docs/day-to-day-operations/products/catalog-setup/properties.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.