My current system houses different variants of Products in different tables;
Products can reside under 1 Productgroup and can have multi-variance Colors, Sizes and Models.
The logic on filling the database now fully relies on the website-scripts; meaning when I make a new Product in my back-office I am filling and relating the Colors, Sizes and Models to the product and make sure they have a combination of themselves.
This structure quickly grows; like 3 Color-variants of 6 Sizes and 2 Models already convert into 36 different products.
I wonder if there is a more logical way to this Database-wise. The problem is that in the future it might be possible that a product will get another property (let's say Sublabel). How could I make this method ever-extendable?
I read about EAV, but that's really too much info to go on for now. Before I dive in the deep, I wonder if there are other approaches on this matter.