Static attributes
A static attribute holds a single fixed value that does not change based on what the customer selects. The customer cannot choose between multiple values, the attribute simply stores data that the configuration engine or downstream systems (such as BOM, pricing, or mapping) can read.
Think of it like a fixed product property in a PIM: the value is set once by you and stays the same for all configurations.
When to use
- You need to attach a fixed piece of data to a product. For example, a fixed material name, a product code prefix, or a base weight, without exposing a selection to the customer.
- A rule or BOM component needs to read a value that never changes for that product.
- You want to store a localised text label that the template always displays, regardless of other choices.
Static attributes are not typically shown as a customer-facing selector. If you need the customer to choose between options, use a Configurable attribute instead.
Type-specific settings
Static attributes do not have additional settings beyond the General fields described in Create attribute. The type-specific settings card will only show a field for the value.
Value types
When you create a Static attribute, choose the Value Type that matches the data you want to store:
| Value Type | What it stores |
|---|---|
| String | A text value; supports multiple locales. Use for names, labels, or any text you want the configuration engine or template to read. |
| Number | A numeric value. Use for quantities, weights, dimensions, or any fixed number. |
Values for a static attribute
A static attribute has exactly one value. Once created, that single value holds the string or number you configured.
Use static attributes to hold data that drives rules or BOM logic without cluttering the customer-facing configurator. For example, store a base width in a static Number attribute and reference it in a rule that calculates available size options.
If a fixed text label needs to appear in the customer UI regardless of any other choice, assign a Static String attribute to the product layout and configure the template to display it. This keeps the value in the backoffice rather than hard-coded in the template.