Can someone explain the difference of Attributes (config, custom, default, hidden, variant)

[KyleDev]

I'm finding the docs quite lacking in explaining what a lot of the types are.

When creating a product, under "Characteristics" there are 5 different types of attributes. What are the differences/use cases for these?

config
custom
default
hidden
variant



Thank you so much.

[aimeos]

I'm finding the docs quite lacking in explaining what a lot of the types are.

The different attribute types are fully documented here:
https://aimeos.org/docs/latest/manual/p ... cteristics

When creating a product, under "Characteristics" there are 5 different types of attributes. What are the differences/use cases for these?

config
custom
default
hidden
variant

From the docs:

Articles which are part of a selection product need at least one variant attribute that distinguishes it from the other atrticles of the selection product. The variant attribute or the combination of several variant attributes must identify the article unique within the selection product.

Each product can have an unlimited number of regular attributes. Clothing for example usually has an attribute like color. Attributes are shared between products and if you change the attribute value, it will be the same for all other products referencing this attribute too. Additionally, you can use all attributes to build filters in a facetted search.

Hidden attributes are not shown in the frontend but are stored along with the ordered product. You can use them to pass data to the fulfillment or any other backend system that shouldn't be displayed to customers.

Each product type can have configurable optional parts like an additional printing on a T-Shirt. They are realized by product attributes, which can have their own text, image and price. Customers can also choose to add options more than once if the frontend offers an input field for the quantity.

With customizable product options, customers can enter custom values into the provided input fields and these values will be stored along with the order. In the T-Shirt example, customers could enter the text that should be printed on the T-Shirt. Custom options can also be dates, e.g. for training courses. It's possible to create more customizable option types but the handling has to be implemented in addition. The example products from the demo shows the basic usage.