EVENTS AND TICKETS

• Events with a date, description, background image and an automatic publish/unpublish window; a ticket goes off sale at its end date at the latest
• Any number of tickets per event, each with its own price, VAT rate, capacity, sale period and minimum/maximum per order
• Ticket variants (parent and child tickets), such as adult, child or early bird, each with its own price
• An optional "doors open" time per ticket
• Announce a sale that has not started yet with a countdown or just its start date, for an event or for a single ticket
• Copy an event with all its tickets; the copy is unpublished, so nothing goes on sale by accident
• Optional service fee per order: a percentage, a fixed amount, both combined, or none
• Menu items for the event list, a single ticket, a "Lost tickets" page where customers can have their tickets emailed again, and "My orders"
• Event data for Google and other search engines (schema.org), with date, venue, price and availability; you can switch it off

SEATED EVENTS

• Customers pick their own seats on a seat chart that scales to any screen, with zoom buttons and a colour legend
• Hover over or tap a seat to see its row, number and price
• Seat plan editor: place whole rows or blocks at once, drag seats on a grid, renumber, align, add shapes and labels such as a stage, with undo and redo
• Sections with their own prices and colours, and blocked seats that can't be sold
• Save a seat plan as a template of its venue and reuse it for other events, or export it to another site
• Seats are held while the customer checks out and are released automatically when an order is abandoned
• Optionally prevent customers from leaving a single empty seat that is hard to sell

SHOPPING BASKET AND CHECKOUT

• A basket module (mini or full view) that you can place anywhere in your template
• One line per ticket type, with quantities to change and a note of how long the tickets stay reserved
• Check out in separate steps (basket, details, payment) or on one single page: the order sits beside the form, customers can still change quantities, enter a discount code and add a note, and the pay button shows the amount
• A checkout form where you choose which customer details to ask for, with one full-name field and a hint when an email domain is mistyped
• Logged-in customers find their details already filled in, linked to the custom fields of your users
• Discount coupons, which you can limit to certain events or tickets; orders with a total of 0 are completed without a payment step
• A waiting list for sold-out tickets (general admission), which you switch on or off per event
• Your site's default captcha for guests at checkout, when you have one set

PAYMENTS

• Online payments through Mollie or Stripe, both included as payment plugins; you choose which one takes the payments
• Mollie: iDEAL | Wero, credit card (including Google Pay), Apple Pay, PayPal, Bancontact, KBC/CBC, Belfius and gift cards; you choose which methods to offer, and with more than one the customer chooses on your own payment page
• Stripe: customers pay on Stripe Checkout, which offers the methods you switched on in your Stripe Dashboard (cards, iDEAL, Bancontact and more); the documentation explains step by step how to set up the account and the webhook
• Other payment providers can be added as plugins, for instance a regional payment service: a developer guide and an example plugin are in the project repository, and the Stripe and Mollie plugins show how it is done
• A Payments screen in the backend: choose the provider, set the currency, see the installed payment plugins and switch them on or off
• Payments in euros or in more than thirty other currencies, including some without decimals such as the Japanese yen; the list follows what the chosen provider can collect
• Refunds from the box office through the payment provider, and refunds and chargebacks (disputes) made in the provider's dashboard are reported back to you
• No payment account? Switch online payments off and sell through the box office and bookings only
• "Pay again" after a failed or cancelled payment, without choosing the tickets again
• One Live | Test switch on the control panel: in test mode the shop is closed to the public, tickets are marked as invalid test tickets, and Mollie or Stripe switch to their test environment automatically
• Test and live data are kept apart: test orders, payments, invoices and customers never show up in your live screens and statistics or use up live tickets, seats and coupons, and one button deletes all test data

TICKETS AND INVOICES

• PDF tickets with a unique QR code, secured with a random validation token
• Visual ticket layout editor: drag each field into place on your own design (JPG or PDF) or the built-in layout, see the real texts and QR code, and choose the font
• The built-in layout carries your company logo and colour
• All tickets of an order arrive as one compact PDF, one ticket per page in its own size (A4 or A5, portrait or landscape), grouped per event and numbered in a fixed order
• A calendar file (.ics) with the events, on the payment result page and attached to the ticket email
• Automatic PDF invoices showing the payment method, emailed after payment

CUSTOMER PORTAL: MY ORDERS

• An optional page where customers look at their orders themselves: tickets, seats and total, with buttons to download the tickets and the invoice and to add them to their calendar or wallet
• No account needed: the customer enters the email address they ordered with and gets a link by email; the page gives the same answer for every address, so it can't be used to find out who has ordered
• The ticket mail carries a link to that one order, which works until its last event is over
• Pick some of the tickets of an order to download them as one PDF, or mail them to yourself or to someone else with a short message; the other person gets only those tickets, with their own wallet buttons
• Upcoming events come first; past orders are folded away and keep their invoice, for as long as you choose
• Optionally link an email address to a Joomla account, after confirming it with the link in a mail; the customer sees those orders whenever they are logged in
• You switch the portal, and sending tickets to someone else, on or off in the Configuration

RIGHT-TO-LEFT AND OTHER SCRIPTS

• Arabic and Persian names and texts on tickets and invoices are printed the way the script requires: letters joined and running from right to left, also when mixed with Latin letters and numbers
• Cyrillic, Greek and letters your ticket font lacks, such as Polish or Turkish ones, are printed in an embedded font, so a customer's name never turns into question marks
• Text alignment per ticket: left, or right so that a text ends at its position, which is how you place Arabic and Persian
• The layout editor shows mixed-script texts as the PDF prints them, and it works in right-to-left backend languages
• Dates follow the calendar of the site language, including the Persian (Jalali) calendar, on screen and in the exports

WALLET PASSES

• Customers add their tickets to Apple Wallet or Google Wallet with one tap, using the official "Add to Apple Wallet" and "Add to Google Wallet" buttons in the ticket mail and on the payment result page
• Passes follow the ticket: a refunded or blocked ticket makes its pass void, a new QR code replaces the old one, and a changed date, time or venue can be brought in line with one click
• Send a message to the buyers of an event as a notification on their pass, by mail, or both
• A Communication screen per event: write the message (with suggestions for a new time, another location or a cancellation), send a test to yourself, update the passes, and see what has been sent
• Deleted orders and tickets leave the wallets
• You turn each wallet on yourself in the Configuration; live updates are optional for both Apple Wallet and Google Wallet

BOX OFFICE AND ADMINISTRATION

• Box office: search orders by name, phone number, order number or the code of a ticket's QR code, filter them, and export a guest list as CSV or XLSX
• An order reference on every order, shown in the box office and printed on the ticket when the design has a place for it
• Resend tickets or invoices, send payment requests, and replace a lost ticket with a new QR code
• Mail templates for every email, with a preview, a test mail to yourself and a button to restore the default text
• An automatic reminder mail before the event (a Joomla scheduled task), and a message to everyone who bought a ticket for an event, for instance when the time or the location changes
• Take walk-in and phone bookings from the backend, including complimentary tickets
• A dashboard with weekly and monthly sales, a chart of tickets sold per day, availability per event, and warnings when something needs attention
• Joomla permissions for every task: box office, bookings, registering payments, finance, deleting orders, ordering in test mode and scanning
• Unfinished orders are cleaned up automatically

TICKET SCANNING

• Scan tickets at the entrance with any phone or tablet through the website, with no app needed
• Scanning hardware or an external scanner app can be connected as well
• Each scanner account only accepts tickets for its own events, and every scan records who checked the ticket and when
• A live seat map for seated events while scanning

MORE

• Works with any Joomla site template
• Widgets for Joomla's own dashboard: what needs attention, sales, upcoming events, quick links, the entrance on the day of an event and the latest orders, plus a bar while the shop is in test mode
• The administration fits on a phone
• Site and backend in English and Dutch
• Your own price, date and time notation, with a live example while you set it up
• Built-in, searchable documentation in the backend, with a Help button on every screen
• Updates through Joomla's own update system, with the release notes shown after each update
• Open source (GPL); the bundled libraries and their licenses are listed in THIRD-PARTY-NOTICES.md

REQUIREMENTS

• Joomla 6
• PHP 8.3 or newer
• A payment account for online payments, with Mollie or Stripe (optional: without it, sell through the box office)
• For online payments the site must be reachable from the internet, so the payment provider can confirm payments
• For wallet passes (optional): an Apple Developer account for Apple Wallet and a Google Wallet issuer account for Google Wallet; live updates for Apple Wallet need https