Product variant options and attributes

[netzknecht]

Is there a good reason why the product variant differences are represented via the ProductOption and ProductOptionValuemodel instead of simply using Attribute's at the ProductVariant level?

[netzknecht]

Stupid question or are there no reasons for it? 😄 Here's a bit of thought to drive the discussion a bit.

Why is a non-redundant concept pursued in the manifestations of product variants with the ProductOption and ProductOptionValue model and a redundant concept with the Attribute model and attribute_data fields, even if the data collection requirement is essentially the same? Why isn't a uniform approach pursued here?

A ProductOption model 'Size' with ProductOptionValue models 'S,' 'M,' 'L,' etc., could easily be implemented with an Attribute for the ProductVariant model using a ListField or even better, TranslatedListField. For defining a variant manifestation 'Color,' a ColorField could be used, which could also be relevant as an Attribute for a Product model without different ProductVariant models or any other models.

Advantages:

1. More consistent data collection.
2. (Re)use of FieldTypes for defining variant manifestations.
3. Variant manifestations are indexed as attributes for search and can be considered or filtered in full text search (scout/melisearch...)

Disadvantages:

1. Redundant data collection.
2. Revision of variant generation in the hub required.

Fundamentally, a bulk editing function for attributes or the captured attribute data would also be useful at times.

[netzknecht]

Further aspects that speak for the use of attributes:

For example, uniform data collection with attributes would result in simplifications when creating a product comparison function.

When assigning attribute values, additional attributes with values ​​that depend on the input can be automatically defined using attribute rules or special field types. For example, when defining the value "DIN-A4" for an attribute "DIN format", another attribute "Dimensions" could automatically assume the value "297 x 210 mm", and another attribute "Format" could automatically assume the value "rectangular".