Menu

#5544 Introduction

Parent Category:
DPCalendar
Category:
Booking system
Last Updated:
Allon Moritz, Friday, 03 September 2021 18:41 (3 weeks ago.)
Created:
Tuesday, 19 December 2017 09:15 (Tuesday, 19 December 2017)
Hits:
3121

Introduction

DPCalendar comes with a full featured event booking system to turn your visitors into attendees of your events. We know that a booking system can become a complex matter, but DPCalendar aims to make the setup as easy as possible without loosing any flexibility. It's possible to define unlimited prices, discounts and different tickets per event, or enable the booking list when the ticket limit is reached. Payment providers like PayPal or Stripe are implemented trough Joomla plugins to have maximum configuration possibility and extendability. With it's powerful geo location based Taxes you can also charge easily taxes per country.

The booking system consist of two main entities, the booking and the tickets. During the booking process the visitor can create one booking with multiple tickets. There is always a relation between the booking and the ticket. While you can attend a whole series of events every ticket has also a relation to an event, but the booking not.

Booking form

Series bookings

If an event is a series then there are three different modes for the booking form available which is controlled by the "Book Series" option in the Event booking configuration:

  1. Only single event No If only the single instance of the event can be booked.
  2. Individual events Option Attendee can select from the different instances.
  3. While series Yes The whole series will be booked. In this case only one ticket is created for the original event.

Waiting list

If an event has enabled the waiting list flag, then bookings can still be made, but are added to the waiting list when the capacity is full. The admin has to put the booking from the waiting state into either reviewed (paid bookings) or invited/activated (free bookings) once there is some free space available.

Booking waiting list

Payments

If an event has ticket prices, then the payment system of DPCalendar comes into action. Are the tickets selected, then the attendee has to confirm the booking on an extra step where a payment options needs to be selected. It is like a checkout option on the web shop. Each payment provider in DPCalendar can be configured in the respective plugin settings. Each payment plugin allows to add inlimited different configurations. This is very handy when you have a plaform with multiple authors and you want to give them the possibility to directly integrate their prefered method to receive payments.

Booking payment providers

Booking states

A booking (tickets do inherit automatically) can have different states, depending on where it is in the process. We describe the steps here for better understanding:

  • 0 State inactive Is set initially when the booking is created after the tickets selection screen.
  • 1 Active When a booking is confirmed. If the booking has a price, then the state will be set when the payment was done.
  • 2 Tickets reviewed Is set when the tickets are reviewed and saved.
  • 3 Confirmed Is set when the booking is confirmed but needs a payment.
  • 4 On hold When a booking is paid offline and needs an action from an administrator. For example the manual plugin shows wire information to make the payment by E-Banking. When the payment arrives on the bank account, then the administrator needs to manually activate the booking.
  • 5 Invited When a booking is created from an invitation.
  • 6 Canceled When a booking gets canceled by the attendee. This is only possible when the booking is activated and it is one with a price. Then the admin knows that here are some actions needed like a refund needs to be issued.
  • 7 Refunded When a booking got refunded, then the admin can set this state.
  • 8 Waiting When an event has the waiting list feature enabled, bookings can be put in a waiting state when the event is booked out.

The set up process

Basically setting up the booking system is a three step process. While the first two steps are needed only once.

Configure the system

Review and adjust the DPCalendar options for the booking system. Define the address for the invoice, etc.

Define the permissions

Every DPCalendar calendar has a permission setting where the site admin can define which user groups can book tickets for the events of the calendar. Adjust the permissions to your sites needs.

Set up the event

Create an event which happens in the future and set the capacity value to a number higher than 0 (empty means unlimited). Additionally define some optional prices, discounts and other configuration options in the booking tab.

The booking process

When a visitor is opening an event which accepts bookings, then a booking panel is shown in the event details and an information box to head on to the booking form. There are three steps involved to finish the booking.

Create the booking

In the first step the booking form gets opened when the visitor wants to attend the event. The visitor has to define how many tickets should be booked. Some basic information like name and email (which are required) and some optional information like address and telephone number can be added here too.

Review tickets

In the second step, the attendee has to review the tickets. The tickets inherit the fields of the booking but can be changed here.

Booking confirmation

In the third step the booking will be confirmed, afterwards it will be activated. If the booking needs a paymant then the list of available payment providers is shown where the attende has to choose one from. After the "Confirm booking and pay" button is hit, then booking gets redirected to the payment provider page where the payment can be done.

Comments (0)

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.