I used to use Roman Cart, and its real plus was that it has the differential pricing that Len W describes.
Not only is it easier to maintain prices in that way - as there are fewer records per product - it means that the prices are worked out for the data inputter and also the calculation of price for the end user on the site is way quicker.
I've set up a product with variable pricing in Woocommerce. Because of its design constraints the calculation in the product cart takes ages (over a minute in some cases so completely impractical!).
The developers should also have a look at how the data is indexed as I feel this isn't helping things. I have a case where I offer services at various venues. The venue doesn't affect the price (other attributes do) - but it means that every data row has an *any venue * pricing rule which is causing the price calculation to grind to a standstill.
Anonymous
I used to use Roman Cart, and its real plus was that it has the differential pricing that Len W describes.
Not only is it easier to maintain prices in that way - as there are fewer records per product - it means that the prices are worked out for the data inputter and also the calculation of price for the end user on the site is way quicker.
I've set up a product with variable pricing in Woocommerce. Because of its design constraints the calculation in the product cart takes ages (over a minute in some cases so completely impractical!).
The developers should also have a look at how the data is indexed as I feel this isn't helping things. I have a case where I offer services at various venues. The venue doesn't affect the price (other attributes do) - but it means that every data row has an *any venue * pricing rule which is causing the price calculation to grind to a standstill.