What is the solution for each vendor custom field?

Hi
If a vendor want to sell product with custom field A and another need create custom field B, how to implement that? must superuser work for each vendor separately these needs? It seems the vendors can not create custom fields for his own products. What is the solution with hikamarket to do that?

Hello Jerome,
Thank you for your detailed answer. However, I’m still uncertain and I need your guidance.

For example, imagine one vendor sells children’s toys, another vendor sells mobile phones, and another vendor sells books. If I try to cover all these cases with standard custom fields, the number of additional fields would become very large.

What do you think about developing a plugin where the vendor-specific extra information is stored as JSON inside a single HikaShop textarea custom field?
This way, the default HikaShop search could still search within that field, the number of database columns would not grow, and all the values (together with their field IDs) could be saved inside one textarea column.

At the same time, the plugin could manage its own separate table to let each vendor create and manage their own custom “dynamic fields” (similar to Joomla custom fields, or even by reusing Joomla’s custom fields structure). The plugin would then render those fields on the product form and pack/unpack the data into/from the JSON stored in that single textarea field.

1-Do you think this approach is reasonable? Are there any major drawbacks or limitations in HikaShop/HikaMarket regarding search/filtering, performance, or compatibility with the existing custom field system?

2-If I store vendor dynamic fields in JSON, will HikaShop search index it properly or would it require LIKE queries?

3-Would it break filters or product listing performance?

4-Is there any recommended way in HikaShop to store dynamic per-product attributes without creating many database columns?