You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eventyay-common: The ticket system already has a voucher system for tickets of an event. Implement the same kind of functionality a) for a voucher per event and b) for all events of an organizer in the admin area of the platform.
The text was updated successfully, but these errors were encountered:
Hi @mariobehling,
since admin area feature is completed #370
Please give me more detail on this issue so we can implement it.
Setting voucher:
In Admin area /control/admin, on the left sidebar, we will add a new page call 'Vouchers'
In 'Vouchers' page, we will list all vouchers and have a button to create new voucher.
In Voucher creation page, there will be some input field.
Voucher code
Maximum usages
Valid until
Product (select dropdown): list of all event and an options using for all events of an Organizer
Price effect with 2 options: reduce price by %, set Price to
For Organizer using voucher:
Where should we allow Organizer to input voucher code? In billing settings or we add another page in Organizer Area called "Voucher usage".
And for input voucher code, do we allow Organizer to use multiple voucher at a time?
My suggestion will be:
we add another input field in billing settings call voucher, next to the input voucher is "check" button, when organizer click 'check' button, the system will verify that voucher code (how many time it can be used? event its got applied, valid until, price affect).
If organizer save billing settings with that voucher, when generate the invoice, we will deduce the price of that voucher and count 1 time usage for that voucher.
eventyay-common: The ticket system already has a voucher system for tickets of an event. Implement the same kind of functionality a) for a voucher per event and b) for all events of an organizer in the admin area of the platform.
The text was updated successfully, but these errors were encountered: