Support

Home Forums Pre-Sales Trying to determine if Event Espresso meets my requirements

Trying to determine if Event Espresso meets my requirements

Posted: November 25, 2014 at 1:41 pm

Viewing 2 reply threads


KMDG

November 25, 2014 at 1:41 pm

Hi, I have a new project for a travel website and I’m trying to determine if Event Espresso will work for what I need to do. They will be selling bookings, and need to be able to collect either a registration fee or the full amount of the ticket, if a registration fee is paid then an invoice should be sent automatically at a later time for the user to pay the rest of the balance (via the website).

Additionally users will need to be able to add an arbitrary number of passengers, recording various bits of info about each passenger individually (name, DOB, etc) and the total price of the registration will be effected by the number and type (child, adult, etc) of passengers added. If a user is traveling alone then a single passenger fee is charged instead (the default is 2 passengers).

This seems highly specific to me, so I’m not too hopeful – but I am a developer so if this isn’t possible out the box but could be done using your API then it would still be faster than me coding it out myself from scratch, and several of your other features seem perfect for what they want to do.

Thanks for your help!


KMDG

November 25, 2014 at 2:01 pm

Quick update – I was mistaken about one thing, only the number of passengers matters, not their status as an adult/child, and there will be a maximum of 3 per registration.


Lorenzo Orlando Caum

  • Support Staff

November 25, 2014 at 2:37 pm

Hi,

Event Espresso 4 would be a better fit as it support multiple pricing options in a table. For example, you could do something like this:

Adult registration – quantity – pricing
Child registration – quantity – pricing

Then the event could have a limit of three set via the Event Options. This would allow either two adults and a child or one adult and two children. Then their information would be collected during registration checkout.

The issue that remains is full payment vs partial payment. Partial payments aren’t supported so those would need to be handled manually.

For example, you could create Event ABC with the above settings. Then you would need to create Event ABC – Pay Balance to handle the final payment due.


Lorenzo

Viewing 2 reply threads

The support post ‘Trying to determine if Event Espresso meets my requirements’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso