If buyers just view the total price of the product and make their choice, then ACBC would be a good approach.
If in the real world buyers see the prices for each add-on feature and also see the price of the main component, then make their choice by configuring their final product to buy, then MBC (menu-based choice) could be more appropriate.
If you decide that ACBC is a good approach, and price is involved, then I generally recommend using summed price. Even if you can only approximately guess what the average street price is for the add-on options, then this allows the software to create more realistic tradeoffs, where the products are closer in general to their expected street price.
Of course, you need to allow ACBC to give a random shock (recommended in the range of +/-30%) to the expected calculated street price per product to allow for precise price sensitivity estimation.
Be on the lookout for significant interaction effects between each of the features and the overall price attribute (you often won't find them, but it's a good idea to watch out for the possibility). This can help you obtain more accurate estimates of the price sensitivity for different features. You can examine this possibility using our "CBC/HB model explorer", which is an advanced (free) tool available for folks with CBC/HB licenses (for example, if you have a CBC license, you also have a valid CBC/HB license).