Lot's of ways to do this sort of thing so you have to kind of break down your concepts of what you are addressing.

For example you know that you ultimately start with an overall category of information such as lingerie may be even higher level such as clothing. Consider how to

You also have fixed conditions such as a specific product, it's sku, it's upc which determine price, this is irregardless of the overall description of the product. So the question is how to most effectively describe the attributes of a product so that you can find products with descriptions matching that availability. You also have to consider how sotkc relates to the product plus the attributes, you don't want to say you have a halter top wth floral roses on it with a 36C when you don't have the specific product.

You just have to break it down logically and keep working on it until you cover potential holes in the design that would allow relational flaws to be injected.

I think I might start with a couple of tables like so

Products - Base product, UPC, SKU information, and providing vendor.

Vendors - Information about the vendor.

Categories - Category of products, this might have an ultimate set of root product categories such as food and clothing or maybe lingerie, pants, etc. Might use some heirarchy of parent child in here.

Product_By_Category - Products associated with the lowest child it would relate to in Categories. I make seperate because you might have multiple Categories a product fits in for the sake of finding.

Attributes - Individual descriptors such as product, attribute type, attribute value (Things Like A, B C, S, M, L, 10, 20, 30, which are an attribute fact, this might even dervie from some other tables information for controlled options).

Attrbiute_Types - Things like Style, Fabric Type, Prints, Print Types, Chest Size, Cup Size

But even here I can think of things I could possibly do and once I decide I would refator the design several times to be sure I am happy with it.