Variant Options
Welcome note
Data hub is our new upgraded platform, which we rolled out in August 2025. It offers a single unified integration for passing your data through to your Bloomreach products.
You have access to Data hub if you've implemented with Bloomreach after August 2025.
Customers who have implemented before August 2025 should follow the existing documentation for Engagement, Discovery, and Clarity.
-
Display Name:
Variant Options -
System Name:
variant_options -
Data Type:
List.String -
Levels:
Product -
Used By Apps:
Data Hub -
Required By Apps:
None
An ordered list of variant attribute names that define the grouping and organization
structure for a product's variants.
Specifies which variant attributes should be used to group, organize, and display
variants for products containing multiple variants.
The order of attributes in this list determines the hierarchy and priority of variant
grouping. Values should be fully qualified attribute names using the format
family.attribute_name (e.g., system.color, main.attribute_1). If a name is
provided without a namespace qualifier and matches a system attribute name, it will be
assumed to reference the system attribute rather than a custom attribute of the same
name.
Format
-
Each value should be a fully qualified attribute name:
family.attribute_name -
Supported families:
systemfor system attributes,mainfor custom attributes -
If namespace is omitted and the name matches a system attribute, system namespace is
assumed -
The order of attributes in the list determines grouping priority
General Usage
-
Defining the primary variant differentiation axes for a product
-
Establishing variant selection UI structure (e.g., color selector, then size selector)
-
Determining variant grouping logic for display and navigation in Bloomreach dashboards
-
Providing metadata for automated variant management and organization
Examples
["system.color", "system.size"]
["system.color", "system.size", "system.material"]
["main.attribute_1", "main.attribute_2"]
["color", "size"]
Note: In the last example, because color and size are system attributes, they will
be interpreted as system.color and system.size.
Application Usage
Engagement
Not currently used - planned for future variant display and selection features
Discovery
Not currently used - planned for future variant faceting and SKU selection
enhancements
Updated 3 months ago
