Re: Coupons and Specials ..

Originally Posted by
Wisconsin Dells
We have the same problem and would like to know if it has been solved? We offer many different special offers and discounts for our wisconsin dells vacation packages but they do not apply to all coupon offers and savings.
Wisconsin Dells
I too have looked for a solution and am starting to consider the following.
My customer has products which should never have coupons applied, however he also has existing coupons. I don't want to mass change existing coupons or move items into different categories.
I believe a simple patch (although not desireable in all cases) is to just rename your product model. The pricing module has a bypass the does not apply a coupon code if the item is a gift certificate. If the 1st 4 characters of a product model is GIFT, then a coupon says it is accepted on the checkout screen, but any product model starting with the letters GIFT (like GIFTCOFFEE or GIFT001) will be skipped when adding coupon discounts. If you want to put a product on special for just a few days, the quickest way may just to be modifying the model.
You could also go into INCLUDES/FUNCTIONS/FUNCTIONS_PRICES and perhaps create another exception similar to this:
---
if(substr($product->fields['products_model'], 0, 4) == 'GIFT') { //Never apply a salededuction to Ian Wilson's Giftvouchers
if (zen_not_null($special_price)) {
return $special_price;
} else {
return false;
}
}
---
The quickest way might be to make certain items have a prefix that means they would never have coupons applied. Perhaps start the model with NC for no coupon and make an exclusing that read: if(substr($product->fields['products_model'], 0, 2) == 'NC')
Putting products into seperate different categories is not as clean however my other thought, which needs coding was this.
I thought, hey, duplicate the GENERAL product type and make it GENERAL-NOCOUPON. Then when adding products that may be put on sale and should never have a discount coupon applied would be put into this type. An exception in the FUNCTIONS_PRICES routine could exclude this product type completely. The products could have a regular product model number and they could be sprinkled anywhere in the store it appears. There IS a way to restrict a category to just have one product type in it, but I would think that would be sub-optimal for this discussion.
I believe that you might be able to change product types in the database easily, especially if the new product type is exactly the same as the one you are using.
Anyway, I have done little testing on this, but make the suggestions for others who have a bit more time to test and code. If you run with this, please post your changes.
Aloha from Hawaii! (its a dirty job, but SOMEBODY has to live here...)