Events and Tickets with QR Check-in

Description

Events & Tickets runs the evening from the first booking to the last guest
through the door. It was built for clubs, bars and party promoters — the people
for whom an event is a door, a list, and a queue outside — and it has since been
used for seated dinners, concerts, conferences and weddings, because they are
the same problem wearing different clothes.

Nothing is capped and nothing is metered. There is no per-ticket fee, no
external service to sign up for, no account to create, and no telemetry. Your
guest list lives in your own database, on your own server.

It speaks seven languages, and it brought them with it

English, French, Spanish, Portuguese, German, Italian and Arabic — not a
promise that somebody will translate it one day, but seven finished catalogues in
the download.
Install it and it is already in your language.

It works the language out for itself. Whatever WordPress is set to, the
plugin follows — and it follows by language rather than by locale, so pt_BR,
pt_PT and pt all land on Portuguese and ar_DZ, ar_MA and ar_SA all land
on Arabic. A site in a language it does not have falls back to French rather than
serving a screen that is half one language and half another. If you would rather
say it outright, there is one setting: Settings → Language.

Everything is translated, not just the buttons. The booking form the guest
fills in, the emails they receive, the words printed on the ticket itself, the
door station held at the entrance, and the admin screens you work in. Dates too —
the month and the weekday come out of the plugin’s own catalogue rather than
WordPress’s, so a French ticket does not print September under a French
heading on an English site.

Arabic really is Arabic. The screens, the emails and the booking form read
right to left. And the ticket — which is a drawn image, not a web page — is drawn
with an Arabic typeface that travels with the plugin, with the letters joined the
way Arabic joins them and the line put in reading order. A time, a price, a table
number or a ticket reference still runs the other way inside the sentence, as it
should. Most plugins that claim Arabic print a row of disconnected letters
backwards on the one thing the guest actually holds.

The language travels with the booking. A guest who booked in Spanish gets
their ticket in Spanish — including a ticket re-sent months later, from a screen
you are reading in French. And your own words stay yours: event titles, venue
names, payment instructions and the success message are your text, and the plugin
will not rewrite them.

Who it is for

• Clubs, bars and late-night venues
• Party and concert promoters
• Seated dinners, galas and weddings
• Conferences, seminars and school evenings
• Associations and community groups
• Anyone taking bookings by card, by transfer, by WhatsApp or in cash

Set an event up by answering questions

Creating an event asks three things first: how guests attend — at a venue,
online, or both — what it is called and when, and whether it repeats. Then an
assistant takes over, and it is the shortest way to describe a night that
exists. It starts with a drawing rather than a form:
fifteen kinds of event, from a standing club night to a banquet, a theatre, a
podium in I or in T, a stadium, a classroom. You point at the one that looks
like your room.

From there every answer decides the next question, and nothing is asked twice.
Are seats numbered? Then how is the room laid out — tables in rows, rows of
chairs, or no order at all? How many rows, how many tables to a row, how many
chairs to a table? Are there levels — a balcony, a terrace, a gallery? Which
parts are sold at which price? Do guests buy a ticket, or simply reply? How
are you paid, and what should somebody who
pays by transfer be told? Does the ticket leave immediately, or once you have
assigned the places yourself? Who chooses the place — the guest, or you?

The panel on the right draws the room while you answer, and shows the prices as
the booking page will show them and the line the ticket will print. When you
finish, the event is ready to sell: places, zones, prices, payment, delivery.

The assistant owns nothing. It adds no setting of its own and keeps no
column of its own — it fills in the panels that already held each answer, and
every one of them stays editable field by field afterwards. An assistant that
knows something the editor does not is a second source of truth, and this
plugin has already paid that bill. For the same reason it refuses to rebuild
the room of an event that already has bookings: it will not renumber a table
somebody has already been sold.

The room is an inventory, and a zone is an interval of it

Say the room once — six rows of eight tables, ten chairs a table, plus a
balcony — and the plugin numbers every place in it. A zone then claims a slice
of that inventory: tables 1 to 5, rows A to C, the whole balcony. It
invents nothing, so nothing can be sold twice and nothing is quietly lost:
whatever no zone claims is named on screen as unclaimed rather than forgotten.

A price category is not a zone. A category has a name and a price, and several
zones can share it — Premium is Premium on the left balcony and on the right.
The booking page sells the categories; the ticket prints the zone, because
the zone is what somebody reads at the door.

Each zone also says what it controls: access only — a standing area where
nobody has a seat — or exactly where each person sits. One event can hold all
three at once: a standing floor, a seated balcony, and a numbered block.

And if you want to draw the room instead of describing it, the builder is
there: drag tables and rows onto a plan, rectangle-select or shift-click,
align, space evenly, nudge with the arrow keys, place a stage, a bar, a door.
The plan you draw is the plan the guest picks from, and the plan you watch on
the night.

One event, many dates

A weekly club night, a play that runs for a month, a course every Tuesday: one
event with several dates, not one event per date. Set the rule once — every
day, week, month or year, on the weekdays you tick, until a date or for a
number of dates — and each date gets its own bookings, its own capacity, its
own door and its own online room. The guest picks a date on the booking page,
and everything they receive carries that date: the emails, the ticket, the
calendar file.

Changing dates works the way every calendar has taught everybody: this date,
this one and the following, or all of them. A date somebody has booked is never
moved with the others — it is named, so you change it knowing who holds a
ticket for it. A booked date is cancelled rather than deleted, and its tickets
are refused at the door with the reason. A date that needs another room or
other prices can be detached into an event of its own, taking a copy of the
room and the ticket categories with it.

At the door, a ticket for another date is refused as not tonight, with the
date it is for.

Online, at the venue, or both

How guests attend is the first question of every event. Online, nobody is
seated and nothing waits for a place: the capacity is the size of your online
room. Hybrid, the room people walk into and the online room share one capacity.

Guests never receive the meeting link itself. Each gets a personal link through
your site, checked the moment it is clicked — so the link can be added late or
changed at any time and still reach everyone, a cancelled booking stops opening
it, and you decide who gets in: anyone who booked, only paid guests, or only
once the room opens. Each date of a series can have a link of its own.

Invitations as well as tickets

Any ticket category can be a reply instead of a sale: free, confirmed the
moment the guest answers, with a ticket and its QR code or simply with their
name on the list. When every category of an event is a reply, the booking page
becomes an invitation — count me in or I can’t make it, and no total. A
guest who cannot come says so, you are told, and the place stays free. One
evening can mix both: a free reply for the family beside a paid dinner.

Speakers, performers and the programme

Describe the people who appear once — a photo, a few lines, their links — and
put them on as many events as you like. Each event has a line-up, shown on the
booking page and printed on the ticket, and a programme of sessions: who, what,
when and where, day 2 at 00:30 included. On a series, a session can belong to
one date only.

In the calendar, and in search engines

The thank-you page and the first email offer the date to Apple Calendar and
Outlook (a .ics file), Google Calendar and Outlook.com — with the right time
zone and, online, the way in. And every event page tells search engines what it
is, in the structured data they read: the dates, the venue or the online room,
the line-up, the organizer and the prices.

Your emails carry your name

The top of every email is your event: the organizer’s logo, the title of the
event and who is presenting it, in colours worked out to stay readable on your
brand colour. The plugin’s name appears nowhere in what your guests receive. If
you would like to credit it, one box in Settings → Email adds a small line at
the bottom — off unless you switch it on.

Every guest is a person, not a number

A booking for five asks for five names, and each one gets their own ticket with
its own QR code. One code cannot let five people in, and the door knows who is
standing in front of it.

The booking form also knows what is left while it is being filled in —
counted against what the page was rendered with, what the lines above it have
already taken, and what somebody else is taking in another browser at the same
moment. An option with nothing left is greyed out rather than removed, so
nobody’s choice is ever changed behind their back. The real guarantee is not in
the browser, where it could never be: the event is locked, the places are
recounted and the booking is refused at the moment of writing.

Tickets that look like tickets

Each one is drawn at 100 x 250 mm, 300 dpi, with the QR engraved into the
artwork, and delivered as a PDF by email. Mail servers strip attachments more
often than they admit, so every message also carries a download link for each
guest.

The ticket studio takes your own artwork if you have some — upload it, generate
colour variations, and move every printed field where you want it on a visual
field map — and generates a design for you in the colour of your choice if you
would rather not think about it.

The door works

Open the check-in station on any phone — no app to install. Point it at a
ticket and it answers in one screen: valid, already used, or not for tonight.
Counters update live, several phones can scan the same event at once, and when
the venue’s wifi gives up — it will — there is a printable roll-call list with
every guest and every ticket number on it.

The plan says who is actually in the room. A place that has been sold and a
place whose guest has walked through the door are two different facts, and only
one of them moves all evening: a guest who has scanned turns green, carries a
tick and pulses, and a table whose whole party has arrived wears a green ring.

Payment on your terms

Two ways, and neither is the lesser one.

Take the money yourself: a booking arrives pending, you confirm it however you
actually get paid — bank transfer, WhatsApp, cash at the office — and the
tickets go out the moment you do. Nothing is ever issued for money you have not
received. What the guest is told about paying is your own text, written per
event, because offline that text is the payment.

Or let the card do it: add your own Stripe key and the guest pays on Stripe’s
page, comes back confirmed, and gets their tickets without you touching
anything. Their places are held while they pay and released on their own if
they walk away, so the same seat is never sold twice. The money goes straight
from the guest to your own Stripe account — this plugin is never in between,
and takes nothing.

What the free plugin does

Everything below is in this plugin. There is nothing to unlock.

• Unlimited events and unlimited tickets. No cap, no per-ticket fee.
• Seven languages in the box — English, French, Spanish, Portuguese, German,
  Italian and Arabic, detected from your site or chosen in one setting, covering the
  admin, the booking form, the emails, the ticket artwork and the door station,
  with right-to-left layout and real Arabic shaping on the printed ticket.
• Event assistant — how guests attend first, then fifteen drawn
  archetypes, one question at a time, and a live preview of the room, the
  prices and the printed line — all the way to the day the event opens.
• Event editor — panels for each part of an event: information and
  details, recurring dates, programme, prices and places, rules and terms,
  payment, ticket and link.
• Recurring events — every day, week, month or year; each date with its own
  bookings, capacity, door and online room; change one date, the following ones
  or all; cancel, delete or detach a date.
• Online and hybrid events — a personal, checked join link for every guest,
  four access rules, a link per date, check-in on the first click.
• RSVP — free …

Technical details

Version	1.12.18
Last updated	September 29, 2026
Requires WordPress	5.8 or higher
Requires PHP	7.4 or higher
Author	BitForge Network
Tags	events, multilingual, qr-code, ticketing, tickets