Categories
Categories let you group items into a hierarchy so they are easier to find, filter, and reference in other parts of the backoffice. There are three independent category types, each scoped to a different kind of item.
The three category types
| Category type | Groups | Typical use |
|---|---|---|
| Product categories | Products | Organise products into a navigation tree (for example, by product family or room type). Useful for filtering the product list and for rules that apply to a whole product group. |
| Attribute categories | Attributes | Group related attributes together (for example, all colour-related attributes in one category). Helps teams navigate large attribute libraries. |
| Attribute value categories | Attribute values (options) | Group individual option values (for example, all RAL colours). Required when you use constrained attributes to limit which options a customer sees based on a previous choice. |
All three types share the same form structure. A name, an optional identifier, a status, and an optional parent that lets you build a tree. The key difference is which items you can link to each type and how the rest of the backoffice consumes them.
Choosing the right type
- If you want to organise or filter products, use Product categories.
- If you want to organise attributes (the questions or options shown in the configurator), use Attribute categories.
- If you want to control which attribute values (the individual choices) are visible to a customer based on what they selected earlier, use Attribute value categories.
note
Each category type is entirely separate. A product category cannot contain attributes, and an attribute category cannot be used to filter attribute values on a constrained attribute.