coupon code wildcards

[mike_howles]

I've been looking through the knowledge base and previous posts concerning wildcards in the coupon code field in the checkout.

I know Bruce said that it was a no-goer, but that was with reference to V7. I take it that it is still a no-goer?

We have couipon codes that include numbers:

BPN1024, BPN1025 etc etc, I need to strip off the actual number to leave just the BPN as I am sure NOT going to set a coupon code for 9999 coupons!!!

I could, of course use the onblur javascript method maybe??

Anyone had a go at doing that?

Mike

[wjcampbe]

Mile,

You need one coupon code for each coupon action. Sounds as though you want to give out hundreds of codes but have them all do just that one action that one single code does. Am I misreading you?

(Example: Expected use - DC123 10% discount, DC124 Free toothbrush, DC125 Free shaving mug. Not supported - DC123 10% discount DC124 !0% discount DC125 10% discount ... DCxxx 10% discount)

[mike_howles]

Bill

No, all coupons do the same thing, well nearly:

BPN0001 to BPN9999 = £5 discount on goods value £20+
BPNO001 to BPNO9999 = £3 discount on goods value £15+
A0001 to A9999 = £2 discount on goods value £12+

Obviously if we have more coupons printed I think we will make them a little more Actinic friendly!!

We have a numbered coupons to prevent duplicating discounts, or, at least preventing buyers trying it twice!!

Mike

[mike_howles]

I have just been doing a bit of javascripty bits (my javascript is a bit basic) but I can extract the contents of the coupon code text box by using:

onBlur="couponcode(this.value)"

going to this function:

function couponcode(content)
{
alert (content)
}

which pops up the value entered into the coupon box.

From this I guess with a bit of manipulation I could convert BPN2134 to BPN

which means I could even convert bpn1234 to BPN which is the bit we need for the coupon code.

Am I doing ok so far?

Mike

[wjcampbe]

Mike,

You can use the onblur of the entryfield to alter its content (your return value would be the original variable reduced in length to three characters), but this will definitely confuse the customer. If they enter BPN1234 and see it change to BPN, they will try to "correct" it again.

Unfortunately, if the entry does not match what you have set up in the Discounts and Surcharges are the discount will not be applied.

If you are going to alter the code entered, then you will need show the customer a very visible explanation for the change - and can still expect confusion.

You could with a bit of work, make the Coupon entry field a hidden field, and have your own custom field show instead. Then in the onblur of that custom field process the code and assign its new value to the hidden coupon value field.

[mike_howles]

Bill

I knew you would notice that!!, yes I'll send the validated value to a hidden field so that:
a) it is seamless to the customer and
b) the customer won't know the 'actual' code

Thanks

Mike