When using choices, not modifiers, BV Commerce creates choice combination products which are child products of the main product. A product is created for each choice combination (e.g. small green t-shirt, large red t-shirt, etc) so you can calculate your total combinations by multiplying the number of choice options together so in your case that is 10 * 15 = 150. By default we limit the total number of combinations to 100 to maintain performance levels on the product page. There is a WebAppSetting that contains this limit, so you can adjust it. Just be aware that it may negatively impact product page performance. Here is the SQL query to change it:



I would also make sure that you need choices. If you don't need a unique SKU, track inventory for each choice combination, have dependent pricing based on the specific combination of options, or want to display different product images for combinations you would be better served by modifiers, which have no limit since they don't creation child products. Also note that you can mix and match choices and modifiers.

Edited by user Thursday, September 10, 2015 9:33:06 AM(UTC)  | Reason: Not specified

Are you sure that you're not using a choice in conjunction with a modifier? We're not aware of any issues with modifier price calculations. If you think everything is setup correctly, can you post a link to the product page?

After re-reading your reply, should i be using two modifiers one for size choice and one for color choice?

You should be using two. Whether those are both choices, both modifiers, or one of each depends on your requirements per my earlier post.

using the same product as before, i have the choices both set up as modifiers. I changed one color, maroon to increase the cost by $1.00 instead of the $2.00. My account is set up as a wholesale account, 50% of the retail price, when maroon was selected the price was adjusted by $0.50. It appears all price adjustment are controlled by the price group.