Make sure you have your free Mollie account configured. Without it you can only use RSVP events or sell free etickets (0.00 amount).


To use Fast Events, a one-time configuration is required. To do this, go to the settings of the plugin. The settings can only be changed by an account with WordPress administrator rights.

This plugin allows you to sell tickets for different types of events. Per event there are all kinds of possibilities to impose restrictions such as, time of sale, maximum number of tickets that can be purchased, group membership, purchase once, limit ticket type stock and much more. A few examples

  • online sale of etickets for a single event

  • sell etickets for a group of events. The user can only choose a single event

  • sell etickets for a group of events. The user can select multiple events

  • sell a passe-partout. Customers may attend all events in the group

  • use it for a bicycle tour with multiple checkpoints for scanning and use the FE Tracking App

  • sell tickets for a theater and use a seating plan

Have look at the detailed examples to get an idea what type of event you can create.

Checklist for creating an event

Before you start creating an event, it is a good idea to go through the questions in the checklist below and collect the answers before creating the event.

  • The name of the event.

  • The exact date and perhaps the starting time

  • When will the ticket sale start and when will it end?

  • How many tickets are available (stock on event level)?

  • Do you need multiple ticket types? Eg. a tickets for adults and a ticket for children, each with a different price and stock. Do they need to be counted (Deducted from the stock)?

  • How many tickets can be ordered in a single order?

  • Do you want to use volume pricing?

  • Are users allowed to place multiple orders?

  • Do you need a seating plan?

  • Is this an sports event and do you want to use the FE Tracking App ?

  • Is it a single event or are there multiple events eg. 1 event per day for a series of days?

  • Do you need an passe-partout (access to all events for a reduced price)?

  • Are there different access-rights for some tickets. Eg. all tickets are scanned at the main-entrance but some ticket types (fi. Backstage) have ‘Backstage’ access and can be scanned at the Backstage-entrance. Or for sports events, a scan at the start of the route, several scans along the route as checkpoints and a scan at the end.

  • Design the email the user receives after a successful order (see example)?

  • Create a “Thank you for your purchase” page (See thank you example below).

  • Do you need more information from the user during ordering. Normally only the name and emailaddress are needed. Be very careful adding too many fields, as users tend to bailout if they see a huge list of mandatory fields.

  • Design your eticket. Do you need different designs per ticket type?

  • Scanning of the etickets: are multiple entries used and do you want to measure how many pass a specific entry?

  • Do you want to give free tickets to, for example, sponsors?

PDF etickets

Customers will receive an email with an unique link to download the etickets as a pdf-file. You have to create a PDF-template which the plugin can use to create the eticket. This is an example of a template.

How to create a template?

Use for example Word, LibreOffice, … and design a single-page A4 e-ticket. Leave a 120 mm x 40 mm block somewhere on the page. Smaller is possible as you can scale the qrcode-block. You can position it either vertical or horizontal or even in any angle you want. This is the block where Fast Events will print the qrcode block and some other information. Save the design as PDF and upload it to your WordPress Media library.


Keep the PDF as small as possible, preferable below 200kb for a single eticket. Don’t use full blown images. Bring them back to an acceptable resolution. And pull the images first through sites like https://kraken.io to squeeze the size. An image resolution of 150 DPI for etickets is enough. Make use of use the PDF system fonts. For example use for your text the Helvetica font. Try to prevent the use of special fonts, because these are embedded in the PDF and then the PDF becomes larger. You can analyse your PDF here.

Thank you page

Example thank you page

An example “Thank you for the purchase” page

Order pages

Order example with event id

Once you have defined your event(s), you should create one or more order pages, depending on your requirements. If you just have a single event, use the shortcode-format as shown in the example. The id is the number of the event.

[fast_events id=2]
Order example with grouping

Or use this shortcode-format. Your OpenAir festivals is running for 2 days and visitors can attend 1 or more days. You need to create an event for every day, which are linked together by the group name.

[fast_events group="OpenAir"]

See Event type in the Type settings for more explanation.

Next steps

  1. Goto the orders menu and add via de the dashboard a new order. Make sure you have Dashboard orders switched on in the Event settings of the event.

  2. Check if the email arrives and if the content is ok.

  3. Download the eticket and check it.

  4. Use the Scan App to scan the eticket.

  5. Check in the Orders popupmenu the order details if the ticket is scanned. You can remove the scan with the Checkin menu choice in the popupmenu.

  6. Now test the orderpage. Make sure you have Test payments switched on in the Event settings of the event.

  7. Check again the email, eticket and scan the eticket.

  8. Do a refund of the last order.

  9. Check the stock value.

  10. If you are happy with the results, you should remove all orders and tickets via the contextmenu in the events menu and uncheck Test payments in the Event settings of the event.

  11. Your event is now live.

  12. If you have a sports event, you can switch on the Tracking in the Event settings of the event and configure the other tracking fields.


Once your event(s) has orders you, never change the following fields:

  • don’t add, remove or change ticket names in the Ticket types. You can change the price and stock.

  • don’t change the Link stock event-id field in the Stock settings.

  • don’t change Event type or Event group name in the Type settings. You may change Date and/or Date format.

  • don’t add, remove or change extra input fields in the Input fields

  • don’t change Scan key, Level and Scan location in the Scan keys

  • don’t change User groups in Groups

  • don’t change the Seat configuration in Seats. You can add at the end new seats, but you should never remove seats.