The flavor doesn't affect the price, does it? If not, there is no reason not to have an attribute for each (Flavor and Size); you would read the identifier from each attribute and combine them for the product identifier.
What happens if you set up a product without attributes, and later decide to use them? You would have to remember to go back and check the box in the product editing page. It might be better to automate this - check if the product has attributes, and use them if they are present; otherwise use just the base product id. This simplifies admin coding and the user interface while making it more reliable.
You might use internal code that takes the product and attribute ids and does a lookup to translate that into a relevant supplier model number, to avoid another admin change and user interface. I would think creating a single file or table of corresponding values would be better than inputting things manually for each product attribute.


Reply With Quote
