What is it your database actually holds information about? Is it actually shoes? It just seems unwise to get recommendations on how to design a database but not tell us what the database is going to hold. There is also no idea of scale ie number of different types? how many layers there might be ie shoes - shoe laces - aglets (I've learnt a new word). Or how much data is going to be held. This might make a difference on the design.

It would also help if you could provide more detail as to what benefits you want from the new design over your existing design. As Rudy has already pointed out - if there are no real benefits from all this change other than it being better normalised then someone at some point is going to ask why you spent a load of time and money making all these changes while running the risk of ending up with a system that might not be as effective as the original system.

Can I also ask why you don't just have a single field holding a short description of the spec ie "black laced stileto shoes" and save yourself all the hassle?

Mike