Admin Backend Coupon Codes

[Anonymous]

Hi Franky,

although I’m already happy with the solution I have in place (http://www.e-dynamics.be/wordpress/?topic=coupon-codes) I still think the Coupon Code thing could be more user-friendly and enhanced with optional field settings at the event setup page.

I know you are already planning something in regards to pricing options for multiple bookings so I just wanted to let you know, that I think that some configuration fields at each event would be great to have for reductions as well. I do accept different codes and rebates for bookings.

So there is one code that is valid for recurring users another one is valid for new customers who have been recommended by another participant, another one for advertisements and platforms and more…

Of course they cannot be combined in any way – but each one of these codes is valid for all events, I would need to touch and align the code, if I just want to allow codes for a specific event and I also need to align the RSVP form (or use specific templates) to make the rebates work on for specific events etc.

But that way I can track what the best advertisement methods are or from where the most bookings come from.

Now it would be great to have a configuration in place that would allow to …

enable/disable discounts for an event
give multiple code options and different discount options to a coupon

So it could be something like this

EarlyBird,5%||SPRING10,10%||recommendation,20||…

In order to prevent typos when the user enters the coupon a comparison should be made by setting all letter either to lower or upper 😀

What do you think?

Cheers
JK

[Franky]

The problem is if they require the coupon code to be used only once …
so I think it needs to be a separate table with e.g.

event id, coupon code, percentage or real discount, number of times it can be used

And a second table that tracks the discount codes used per booking.

And then indeed a discount placeholder for the rsvp form …
And of course a whole interface to manage it all. But even that doesn’t take into account other peoples need for formulas based on number of seats reserved etc …
Any suggestions are welcome though! Or maybe something has already been developed and I can integrate that …

Edit, maybe this as a base: http://stackoverflow.com/questions/7278925/creating-discount-code-system-mysql-php

[Anonymous]

Hi Franky!

The problem is if they require the coupon code to be used only once …

Well that is a nice feature but beyond my initial thoughts, I was thinking on a generic coupon code that is available (to those who know the code (more or less public)) so it could be used by many people and multiple times.

What you are going to achieve is a kind of gift certificate, so someone could buy a code and that code can only be redeemed once. This is of course a nice to have and can be implemented in one of the future major releases 😉

For now I would only need a more generic and “simple” solution for different discounts. Because right now, when adjusting the coupon code source code, all discounts are valid to all events, as I do not know the event id (I know it is easy to find out the event ID). If I do know the event ID I can do a check at the discount code source code but the source code will blow up and grow by time and will not be an easy task to maintain and keeping track of codes and ID’s and to know where which discount was/is valid and cleaning up when discounts should not longer be used or assigned to a new or different event…. well I guess you know what I mean!?

Thats why I was asking if there is an easy way to enhance the events (edit) page at the location for example, where you give the price (if not standard) and add a field (or two) for discounts that will only apply to that event (or event series).

Cheers
JK

[Anonymous]

I actually need that exact feature. 🙂

[Franky]

I’m thinking about creating a new section, called Discounts
There you’d be able to define a discount:
– the name
– dropdown for type of discount: percentage, fixed value, code
– discount text label value (optional, and I need to find a better way of describing this field, but it would correspond with the gift certificate you described). If empty: only the type “code” can apply (since the percentage or fixed values would apply all the time then, it is logical to just lower your price …)
– discount value (corresponding with the discount type)
– discount count (how many times this can be used: 0 for infinite times, the database table would need an extra column for keeping track of how many times the discount has been applied)

Then I could link this to an event (by editing the event and selecting via a dropdown the discount) and then do all the checks:
– if there’s a discount textfield, check the value of a new #_DISCOUNT form field
– check the discount count
– evaluate the discount code if that is the discount type (some kind of eval, but it might be too complicate)
– check for a possible new hook that allows you to change the whole discount logic (pass the discount id as optional value too, so you can create different logics). Maybe this hook should only be used if the discount type is “code”
– save the calculated discount in a new column per booking
– save the payed amount in a new column per booking, and set the “payed” status to “yes” if the amount payed equals the amount to pay for the booking minus the calculated discount

It is complicated to do, but would allow for the most flexibility. One issue to solve is how to define multiple “gift certificates” per event then …. still pondering

Edit: maybe also work with something called Discount groups (which groups different discounts together), that would allow multiple “gift certificates” per event. The discount group should have an extra option to indicate how many discounts can be applied (1 or more, 1 by default)

[Franky]

Indeed, the discount group should have an extra option to indicate how many discounts can be applied.
For the text description : it should indicate e.g. the text of the coupon (coupon code), not a description of the discount.

[Anonymous]

Have you made any progress in developing this coupon code system?

[Franky]

Sorry, not yet … busy rearranging parts of the code all the time. But I’m getting there 🙂

[Anonymous]

Good to hear it’s in the works!

[Franky]

Good news: after some heavy coding the coupon system is ready and tested: discounts, discount groups (fixed and percentage values as discount types are working, type ‘code’ is not implemented yet, and upon update of a booking via the admin backend the discount is not recalculated).
The only thing not implemented yet is how to upload the coupons in the database (should be csv upload with specific columns). For now of course phpmyadmin works just as good, but I’ll try to get at least the basics (upload/view/delete) in EME too before releasing. And the doc of course …

[Anonymous]

These are indeed excellent news!

[Franky]

CSV import added too.
If you’re interested in testing, drop me a mail.

[Anonymous]

Hi Franky, will the coupons be case sensitive? I learned that the users mostly do not pay attention using upper or lower cases. So it would be great to not pa attention to case sensitiveness.

[Franky]

Currently it is case sensitive but it can be easily added …

[Franky]

In dev, this has been added now (new extra CSV column ‘case’):
https://plugins.trac.wordpress.org/changeset/1453921/
https://plugins.trac.wordpress.org/changeset/1453952/

[Author]

Posts