|
collectorlive
|
December 11, 2017 at 8:47 am
I know this has been asked a bunch of times, but every event is a snowflake, right? And has its own quirks …
We are creating an event which will have a live component, but will also be streamed into other venues. The event is being targeted at businesses and we expect businesses to purchase multiple tickets for their employees to attend. We want to price tickets in the following manner:
If someone buys up to 10 tickets, the cost is $100 each
If someone buys between 11 and 25 tickets, the cost is $90 each
If someone buys between 26 and 50 tickets, the cost is $80 each
If someone buys more than 51 tickets, the cost is $70 each
We have created one event in Event Espresso. We have created a separate ticket for each of the venues. Our question is this: How can we incorporate this multi-ticket discount into our event?
I know that this question has been asked (and answered) a lot, so I apologize for asking it again. But…
Do we have to apply the discount for each ticket? We would ideally like to do this without giving people a code to use.
Can we code this into the system, somehow? If it’s possible to code it ourselves, can you point us in the right direction?
This is the one of the last steps keeping us from opening ticket sales, so we would appreciate any insight that can help us get this taken care of. Thanks.
-
This topic was modified 6 years, 4 months ago by
 collectorlive.
-
This topic was modified 4 years, 1 month ago by
 Garth.
|
|
Josh
|
December 11, 2017 at 1:04 pm
Hi there,
You can follow this guide that shows how to set up graduated ticket pricing based on a range of ticket quantities:
https://eventespresso.com/wiki/set-graduated-ticket-pricing/
|
|
collectorlive
|
December 11, 2017 at 2:14 pm
Thanks. The problem with that solution is that we would have to create separate tickets for each level on the graduated scale (1-10, 11-25, 26-51, 51+) for each of the venues that will be receiving the streams of the event. Right now, we have 22 venues. That’s 88 different tickets and four different tickets for each of our venues. That will look very busy and very confusing. Is there a way where it can be done all on one ticket?
|
|
Josh
|
December 11, 2017 at 2:33 pm
Is there a way where it can be done all on one ticket?
No.
A better approach would be to create 1 event for each venue. I think you’ll agree that 22 different tickets for one event (where each ticket is for a different venue) will also look very busy and very confusing. Then each event will have 4 different ticket options for the graduated pricing.
|
|
collectorlive
|
December 11, 2017 at 3:20 pm
The problem with separate tickets is that if there are 70 seats in a venue and we create four different graduated pricing levels, each is treated like a separate ticket. So if I buy five tickets, I can still go out and buy 70 tickets at the 50+ price point, even though there are only 65 seats remaining to be sold. The five tickets that were just sold are not reflected in the other ticket quantities.
If we were to try and code something to address this, can you tell us where we should start?
|
|
Josh
|
December 11, 2017 at 3:31 pm
You can set the date time reg limit to 70 (in the Datetime section above where you set up the tickets) and that will cap the ticket sales at 70 for the event.
|
|
collectorlive
|
December 11, 2017 at 3:37 pm
Yes. But if I have 70 seats in a venue and I create four different tickets (one for people buying 0-9 tickets, one for people buying 10-24 tickets, one for buying 25-49 tickets, and one for buying 50 or more tickets), each ticket has 70 seats. So if someone buys five tickets from the 0-9 ticket price point, the number of seats available drops to 65. But the number of seats available for the other three tickets remain at 70. The four tickets are not dependent on one another when it comes to the total number of seats. If someone buys 5 tickets, then the most I should be able to buy in the 50_ ticket price is 65. But I can still buy 70. And that means I don’t have control over how many tickets are being sold if I follow your advice.
|
|
collectorlive
|
December 11, 2017 at 3:41 pm
As well, we have 22 different venues, each with their own number of available seats. If we set the total number of seats available to 70, it would cap how many seats we could sell at all the venues.
|
|
Josh
|
December 11, 2017 at 3:46 pm
Hi there,
There seems to be a disconnect here so I’m going to put together some screenshots and a demo site so you can see that you can set your date time registration limit. This way you’ll see that you will have control if you use the date time registration feature.
|
|
Josh
|
December 11, 2017 at 4:16 pm
In this example of one event the date time registration limit is set to 70:
https://slack-files.com/T02SY781D-F8CDDUBEC-2fa9d89134
Even though there are 3 ticket options that cap out at 70 each, the total number of tickets that the software will allow is 70, not 210. This is because date time registration limit is set to 70.
|
|
collectorlive
|
December 11, 2017 at 4:19 pm
I know what you’re talking about. What you’re not understanding is that we have 22 different venues. And each venue has a different number of seats available. I can’e set a date-time registration limit to 70, because we have about 2,300 total seats available across all the venues.
|
|
Josh
|
December 11, 2017 at 4:24 pm
I understand that you have 22 different venues, and you can set a different date time registration limit for each of the venues.
|
|
Josh
|
December 11, 2017 at 4:26 pm
So for example when you set up another event for another venue, your other venue might have a limit of 120, so your event editor will look like this:
https://slack-files.com/T02SY781D-F8CHU4KUH-f4af0d58ac
|
|
collectorlive
|
December 11, 2017 at 4:26 pm
Scratch that. I think we figured it out. Thanks.
|
|
Josh
|
December 11, 2017 at 4:30 pm
Then when the registration limit is met, the event will automatically switch to sold out status.
https://slack-files.com/T02SY781D-F8CDPKW2U-72bea05b89
|
