database table design, different property values will have different prices

May I ask the great gods, how this structure is implemented, is currently the following practice:
There is a property name table Goods_attr
There is a property value table Goods_attr_value
However, different attribute value choices will have different prices,
This number of values determine a value of the situation really did not meet, how to solve?

Reply content:

May I ask the great gods, how this structure is implemented, is currently the following practice:
There is a property name table Goods_attr
There is a property value table Goods_attr_value
However, different attribute value choices will have different prices,
This number of values determine a value of the situation really did not meet, how to solve?

http://www.widlabs.com/article/item-unlimited-specifications.html Reference

Example:
There is a product: id=10021
Available in two sizes: color, size
Then the value of the specification is stored in addition to itself, and other fields that need to meet the business logic, such as inventory and price
For example, the table of specification values might look like this:

10021 Black M 100.55 100
10021 Black L 200.55 123
10021 Yellow M 300.55 333
10021 Yellow L 400.55 222
....

The content of the property name table is not: freight, version, color, package these?

Multi-spec Price list!

