the table structure I suggested will already accommodate for multiple options.
all available options are stored in the options table, each with a unique ID.
The product options table is used to relate the required options with a particular product.
a record is created in the productOptions table for each option that should apply to a particular product. in each record, the product ID is stored in the productoptions.ProductID column, and the option ID is stored in the productoptions.OptionID column.
really, the examples I have provided already account for having more than one option per product. If there is a particular part of this that you are having trouble with, please let us know.
For the price, you could do it the way you describe as well.