How to build e-ticketing in Bubble

The simplest way to build e‑ticketing in Bubble is to create a Ticket data type, generate a unique ticket code when a user buys a ticket, store it in the database, display it as a QR code, and create a scanning page that checks the code against the database and marks the ticket as used. Bubble provides everything you need: backend workflows, database fields, Privacy Rules, and QR‑code plugins.

Main Structure

You need three core things: a Ticket data type, a workflow that creates a ticket on purchase, and a page that can verify the ticket when scanned at the event.

• Create a data type Ticket with fields: Event (type Event), Owner (type User), Code (text), QR_Image (image), Is_Used (yes/no).
• Use a backend workflow to create Ticket after successful payment.
• Use any Bubble QR plugin to generate the QR from the Code text.

Creating Tickets After Payment

Connect Stripe (or other) via Bubble’s built-in Stripe plugin. On the payment’s “When Stripe payment is successful” event, trigger a backend workflow.

• The backend workflow should create a Ticket, generate a unique Code (using Bubble’s “Calculate formula → Generate random string”).
• Store the generated QR image in the Ticket.

// In backend workflow action "Create a new Ticket":
Code = Generate random string (length 20)
Is_Used = no

Displaying the Ticket to the Buyer

On the user's “My Tickets” page, show a repeating group of Ticket items. Use an image element showing QR\_Image so the user can show it at the event.

Scanning and Checking the Ticket

Make a separate page for staff only. Add a QR scanner plugin element. When it detects a code, run a workflow:

• Search for Ticket where Code = scanned\_code.
• If found and Is_Used = no → mark Is_Used = yes and show “Valid”.
• If not found or already used → show “Invalid”.

// On scan detected:
Search for Ticket:first item's Is_Used = no
If yes → Make changes: Is_Used = yes

Privacy Rules

In the Data tab, set privacy so only the Ticket Owner can see their tickets. Create an additional “Event Staff” Role for the scanning page so staff can access Tickets by Code.