I was wondering what would happen if there was a sale for all products and a customer is in the middle of shopping. So I tried out this scenario:
1. Before sale: customer adds an item to cart.
2. I log in to the admin and create a catalog price rule, and apply it.
3. Now there's a sale going on, and the new sale price is immediately reflected on customer's cart, whether or not he notices it.
The above is acceptable and definitely recommended. The customer should be happy as prices are lower than before. But if the reverse occurs, when a catalog price rule is removed while the customer is still shopping, and prices go up...there may be an issue here, especially if the customer doesn't notice the price increase in his cart or even if he notices, he might be wondering what happened to the sale price. And it would be worse if the customer's at the checkout page and about to pay.
I'll probably be using the cat. price rule fairly often so I'm thinking this is likely to happen. Or is there a way to implement a rule only when no one has anything added to their cart?
Btw, you should update the LS demo regarding discounts and cart total. I notice "cart total" and "estimated total" have the same values even when a coupon is applied. I think "cart total" should show the price before discount, otherwise it doesn't really make sense, IMO.
On a side note, just purchased LS. Hands down the best cart I've used. Take advantage of the pre-order discount!
Page 1 of 1
Catalog Price Rules - Lock In Prices?
#2
Posted 24 July 2010 - 08:28 PM
Hi, zone!
That is a good point. We will implement the cart price locking feature. I just added this task to our to-do list.
LemonStand applies discounts on cart items before calculating the cart total, because this is the only correct way to calculate taxes. We came to this approach during the tax engine developing. It is very flexible now and can work with any imaginable tax jurisdiction and tax structure (we hope so, at least). But the cost of the flexibility are some compromises in the implementation. Cart row totals display amounts with discounts already applied, so the cart total already includes all discounts.
Thank you!
That is a good point. We will implement the cart price locking feature. I just added this task to our to-do list.
Quote
Btw, you should update the LS demo regarding discounts and cart total. I notice "cart total" and "estimated total" have the same values even when a coupon is applied. I think "cart total" should show the price before discount, otherwise it doesn't really make sense, IMO.
LemonStand applies discounts on cart items before calculating the cart total, because this is the only correct way to calculate taxes. We came to this approach during the tax engine developing. It is very flexible now and can work with any imaginable tax jurisdiction and tax structure (we hope so, at least). But the cost of the flexibility are some compromises in the implementation. Cart row totals display amounts with discounts already applied, so the cart total already includes all discounts.
Thank you!
Share this topic:
Page 1 of 1

Help












