If a merchandise is a "set" that comprises of various components, then the set needs to be treated as its own item, which would then have its own price.  That was how my company did it in my old job.  For instance, in a three-piece pant suit that comprises of a jacket, blouse, and pants, then all FOUR items (set, jacket, blouse, pants) need to be entered into the database as individual items, with individual prices, individual bar codes, product IDs, descriptions, pictures, etc.  If a two-piece set is created with the same jacket and pants, then the two-piece set needs to be its own item as well.  In short, any entity that is fundamentally different from the others needs to be an individual item.  And that's how your database should be set up: every entity, whether it's a basic component, a combination of several components, etc., needs to be treated as a unique item in the database.  I believe this is the industry standard as well (at least in our industry of wholesale retail), so it's not something you can avoid.

Thank you for your reply. So if a customer comes in and asks for 300 shirts with a 2 color design printed on the front. I would need to have product IDs for the set, shirts, colors, and location? Pricing per print change with the quantity. A 2 color print on 24 shirts will be more expensive than a 2 color print on 300 shirts. Individual ids would help with this variable?

Do you often sell them by the 300?  If not, and if your customers can order any quantity they want, then you should assign one product ID to the lowest salable unit, i.e. one shirt.  

Also, a unique product is one that has fundamentally different *components*.  If a shirt has red and green colors, it is fundamentally different from a shirt that has blue and orange colors.  So they should have different product IDs, according to industry guidelines.  If a shirt has a red star, it is different from a shirt with a red cross, because the designs are different.  And so on.

The reason for doing all this is so that you (and your trading partners, if any) can track sales of each individual product.  If you want to compare sales of red-star T-shirts and red-cross T-shirts, then they need different product IDs, for example.

Regarding pricing, if you want to charge lower prices for bulk orders, you can give a discount at the point of sale.  In my old job, every product has a suggested retail price that was fixed and never changed.  But at the point of sale, we may charge different prices for the same product, depending on units ordered, whether the customer is frequent, trusted, new, etc.