Support

April 19, 2016 at 4:09 am

Hi Andy,

Based on the screenshot you have provide, your event has NOT oversold.

Regs Value = The number of ALL registrations created that are linked to that datetime.

Sold Value = The number of APPROVED registrations that are assigned to that datetime.

Approved registrations should be the registrations that have paid (or you have manually changed the status)

By default, if a user selects tickets but then does NOT complete payment, they will be added to your ‘Regs’ value, but will NOT be added to the Sold value.

Please kindly clarify in simple words if the limit of tickets IS or IS NOT related to the number of Attendees Registered.

Ticket limits are completely separate from datetime limits. You can set limits on specific tickets, for example you may want to sell 10 VIP tickets out of the 110 total datetime limit. That’s where you use ticket limits.

The DATETIME limit, is the limit of SOLD registrations for that datetime.

April 19, 2016 at 6:33 am

My first reply is a little misleading as it assumes a single datetime, your event is still not oversold by that screenshot, but my reply may cause some confusion with multiple datetimes.

Can you take a screenshot that shows how you have the datetime setup within your event too please? (like the ones below)

Datetimes are an ‘instance’ of an event.

Lets say you have Event A and this event will happen event Monday for 4 weeks.

You could create 4 events for people to register on, but those 4 events are the same event, just happening multiple times, correct?

So this is where ‘datetimes’ come in useful. A datetime is an instance of an event that a ticket provides access to. So a single event can have multiple datetimes, for example – http://take.ms/BaWPf

A ticket gives you access to 1 or more datetimes. So if you want a user to register onto a single datetime, they can have a ticket that only applies to 1 datetime – http://take.ms/5PwTk

The sales for the Datetime 1 ticket, ONLY apply to Datetime 1 – http://take.ms/oMJiv

If you want them to have a ticket for all datetimes, you can apply a ticket to all datetimes – http://take.ms/okKY2

Then sales of that ticket apply to all datetimes – http://take.ms/qBBwO

It depends on how you want to setup your event as to what you use.

Datetime limits should generally be used as your registration limit, but not always.

April 19, 2016 at 7:31 am

Ok, so lets use THIS LINK as an example.

Within that event, ALL of those tickets are assigned to the single datetime you have. Which means sales from ANY ticket apply to a single datetime.

You have a DATETIME limit of 300, which means 300 of any combination of those 3 tickets you have available can be sold. So 110 is your maximum sales value right? After that you can’t take anymore registrations AT ALL for that event?

If so you want you want your DATETIME limit to be 110 – http://take.ms/YNdqc

When any combination of your ticket sales add up to 110 the datetime will change to sold out. As all of your datetimes are then sold out, the event switches to sold out.

It’s a little different for your setup but the ticket limits are how many of EACH ticket type you have. The datetime limit is how many spaces you have available overall on your event.

So you have 110 ‘spaces’ (datetime limit)

But you could sell 50 ‘early bird’ tickets, then 55 ‘standard’ tickets, then finally 5 ‘last minute’ tickets to make up that 110.

(or you could just sell 110 early bird tickets)

April 19, 2016 at 8:28 am

My apologies, I misunderstood.

In that case your event is setup correctly and should work fine.

April 19, 2016 at 8:43 am

You’re most welcome and you too 🙂

Note everything else still applies (it just applies a little differently with your events) but it sounds like you have it covered.