There's a concept in database design called normalisation, it gets really techy when you look it up, but in most situations it's common sense. One table for each entity.
So
Products
ProductId
ProductCategoryID
Size
Colour
....
ProductCategories
ProductCategoryID
ProductCategoryDescription
Sizes
ProductCategoryID
ProductSize
Colours
ColourID
ColourDescription
It looks a bit over the top, but it's future proofing
You should also resist using variable length strings for keys and sort indexes.
The design I used above without ProductCategtoryCode
Would have Menswear in every menswear product and every menswear size. That's 8, btytes per instance, 16 if you are on unicode. An Integer 4. Less space, quicker to load, to sort, to look up and if you boss comes along and says, I want it to be
"Mens wear". You only have to change it in one place.
The disadvantage, you'll be doing a join or two for the front end
Good habits are as hard to break as bad ones.