EventON QR Codes - WordPress Plugin

A Practical Guide to Setting Up and Verifying EventON QR Codes

EventON QR Codes is not just there to place a nice-looking graphic in an email. It serves a specific operational purpose: linking a ticket or RSVP confirmation to guest verification at the door. In this guide, we will walk through how to prepare your site, enable QR codes, configure the check-in page, choose a scanning mode, and confirm that the whole workflow actually works.

This article is written for WordPress site owners, event administrators, technical staff, and registration teams. It does not cover purchasing or license activation. We are looking at an add-on that is already installed and focusing on its working flow: the event, the ticket or RSVP, the email with the code, scanning, the verification page, and the attendee status.

Special attention is given to limitations. QR verification depends on EventON, Tickets or RSVP, user permissions, the browser, caching, and the real check-in scenario on site. If even one of those pieces is not prepared properly, the add-on may be installed correctly, but guest check-in can still fail at the worst possible moment.

How QR Verification Fits into EventON

EventON QR Codes works as an additional layer on top of an existing event system. By itself, the add-on does not replace the calendar, RSVP form, ticket sales, or order tracking. Its job begins after registration or purchase - it gives each confirmation a scannable QR code and ties the scan to the event data inside EventON.

The official add-on page lists two key requirements: the core EventON plugin and one working attendance source - either the Tickets Addon or the RSVP Addon. That is an important boundary. If your site only has an event calendar with no tickets and no RSVP flow, QR verification will have nothing to validate at the entrance.

In a typical setup, the flow looks like this: a visitor purchases a ticket or submits an RSVP, receives a confirmation with a QR code, arrives at the event, and a staff member scans the code and opens the verification page on the website. On that page, the team can view the status, ticket holder name, event, number of tickets in the order, and other details if they are supported by the installed add-ons.

The main value of this add-on is not generating a QR image by itself, but creating a verifiable link between the code, the EventON record, and the check-in action. That is why, before configuring it, you should not focus on how the code looks. Focus on who will scan it, what device they will use, where the verification page will open, and which details staff need to see at the entrance.

What Changes for the Attendee

For the attendee, the process should stay simple. They receive a ticket or RSVP confirmation, show the QR code on their phone screen or on a printed copy, and then wait for the registration staff to respond. If the entry team asks guests to open the website themselves, find their account, or read out an order number, the operational flow has been designed poorly.

What Changes for the Administrator

For the administrator, this is more than just "a code on the ticket." It becomes a separate operational workflow. You need to create the verification page, restrict access to it, review user roles, prepare devices, test with a sold or test ticket, and define a fallback verification method in case the camera, browser, or network at the entrance behaves unpredictably.

Who This Add-on Is a Good Fit For - and When Another Approach Makes More Sense

EventON QR Codes works well on sites where EventON already serves as the event hub and the team wants to verify attendance without moving to a separate external ticketing platform. It is especially sensible if the site already uses Event Tickets or RSVP and confirmation emails are sent directly from WordPress.

The add-on is a strong fit for concerts, lectures, workshops, club events, small conferences, internal events, and paid meetups where staff need to quickly see whether a person has already been checked in. It is also useful for events where one order contains multiple tickets: the official description says that when a ticket is scanned, staff can also view other tickets from the same order and check them in from the same screen.

EventON QR Codes may be the wrong tool if you need a standalone offline scanner, a complex turnstile system, a dedicated staff mobile app, venue seating with hardware access control, or high-volume entry for tens of thousands of attendees through distributed terminals. In those cases, it makes sense to compare the add-on in advance with full-scale ticketing systems or platforms where the check-in app is the core feature.

If you are still choosing the overall architecture, do not start with the QR code. First decide where registrations are stored, how payment or RSVP is validated, which statuses should allow entry, and who is responsible for check-in. QR verification should support that process, not replace it.

What to Check Before Installing It on WordPress

Before installing the add-on, do a quick technical review. It takes far less time than trying to diagnose a failure at the door when a line of attendees is already forming.

Dependencies and Live Data

Make sure the core EventON plugin is working, events are published, and Tickets or RSVP is already creating records you can open in the admin area. For a ticket-based workflow, it is important that your test order is in a valid state. The QR Code changelog specifically mentions fixes related to incomplete or refunded orders, so do not use a random order with the wrong status for testing.

• EventON is installed and working on the site.
• The Tickets Addon or RSVP Addon is installed, because otherwise the QR code has nothing to link to a visitor.
• There is at least one test event with a ticket or RSVP record.
• WordPress emails are being delivered, or the visitor may not receive the QR code in time.
• Your team knows exactly who will scan codes and which accounts they will use.

Permissions and Check-In Access

According to the documentation, administrators can scan and check in guests by default, but in EventON > Settings > QR Code you can allow other roles to perform verification. This is useful if volunteers or event managers will be working the entrance and do not need full WordPress access.

Do not use one shared administrator account for the entire entrance team. It is better to create separate roles or user accounts with only the required access, test them with a sample ticket, and keep administrator access in reserve for technical support only.

Cache, Theme, and Browser

In its troubleshooting documentation, EventON recommends starting with cache, JavaScript errors, and correct script loading through the theme. That matters for QR verification as well: the check-in page needs to load fresh, buttons must work, and the result of a check-in should never be replaced by an outdated cached version of the page.

Before the live event, clear both the site cache and browser cache, open the verification page in a private window, and make sure the staff member's mobile browser opens your actual website page rather than an in-app scanner browser where they are not authenticated.

Installing the Add-on and Running the First Check

EventON add-ons are installed using the standard WordPress plugin flow: upload the ZIP file through Plugins > Add New > Upload Plugin, install it, and activate it. It is important not to unzip the archive manually on your computer if the browser does that automatically, and not to remove files from an older working version without a backup.

Once activated, do not jump straight to live attendees. First, do a control check in the admin area. The QR Code documentation says that after installation, an already sold ticket in Events > All Event Tickets should display a QR code. That is your first reliable indicator: if the QR code is not there, it is too early to test scanning at the entrance.

Basic Verification Sequence

1. Open the WordPress admin area and make sure EventON, Tickets or RSVP, and QR Code are active.
2. Go to EventON > Settings > QR Code and enable the QR verification options you need, if they are available in your version.
3. Create a test event or use an existing test event.
4. Generate a test ticket or RSVP confirmation without involving a real guest.
5. Open the ticket record in Events > All Event Tickets and verify that the QR code is present.
6. Check the ticket email or RSVP confirmation in the inbox, because that is what the attendee will actually see.

The short version of this stage is simple: the add-on is installed correctly if the QR code appears in the ticket record or confirmation, and the test email contains the same working flow that the guest will use.

Detailed Setup: Verification Page, Roles, and Visual Status Cues

The most useful configuration area revolves around three questions: who is allowed to verify guests, where the check-in page opens, and how staff can immediately understand the result of a scan. If those answers are not clearly defined, the QR code may work technically, but the entry process will still be awkward.

Where to Find the QR Code Settings

The main path confirmed by the official documentation is EventON > Settings > QR Code. That is where you choose the verification mode, grant access to roles, and manage check-in settings. The official product page also notes that the verification page can be embedded using a shortcode.

[evo_qr_checkin]

This shortcode is useful if you want to use your own custom entry-control page rather than an automatically generated one. For example, you can create a private page called "Ticket Verification," insert the shortcode there, and share the link only with registration staff.

How to Choose the Verification Page

For a small event, a separate page with a short URL is the easiest option to open on a phone. For a team working from a laptop or a fixed registration desk, you can bookmark the page in the browser. The key point is not to place check-in in a public menu or mix it with the normal event page used by attendees.

How to Verify Roles

Create a test user account with the role you plan to assign to entrance staff. Log in with that account on a phone, scan a test QR code, and make sure the page does not require administrator-level access. If you see a login screen or access denied message, go back to EventON > Settings > QR Code and review the list of allowed roles.

Page Appearance and Color-Coded Statuses

The official add-on page mentions color coding in the scan section based on status and ticket type, and the FAQ says that the colors used on the verification page can be configured through EventON > Settings > Appearance. This is not a cosmetic detail. At the entrance, staff need to distinguish a successful check-in, a duplicate scan, and an invalid entry state almost instantly.

The best settings here are the ones that help staff make a quick decision. If you adjust colors to match your brand, do not make successful, duplicate, and problem states too similar. The person checking tickets should understand the result in one or two seconds, especially in dim lighting and heavy foot traffic.

Three Scanning Modes and How to Choose the Right One

EventON QR Codes supports several ways to scan. The official product page lists a mobile camera, a scanner gun, and an HTML5 web scanner in beta mode. The scanner gun documentation also describes both mobile and fixed-location workflows using an input field.

Mobile Camera or Scanner App

The simplest option is a staff member's smartphone. The documentation describes an iPhone workflow: first open Safari and sign in to the site, then scan the QR code using an app that can open the link in Safari. The key issue here is not the camera itself, but authentication. If the app opens the link inside its own built-in browser, the staff member may no longer be logged in and may see the login screen instead of the verification page.

On Android, the same logic applies: you need a scanner that passes the link into a browser where the staff member is already signed in. Before the event, test the exact devices that will be used at the entrance, because different apps handle links differently.

Scanner Gun at the Entrance

A scanner gun is a better fit for a registration desk where guest flow is dense and staff are working from a laptop or tablet. In the QR Code settings, select scanner gun mode, then open the check-in page and place the cursor in the input field. After scanning, the device enters the code and the page automatically displays the result.

The official documentation specifically recommends checking the scanner's keyboard settings and enabling Carriage Return if the device supports it. In practice, that means this: if the code appears in the field but verification does not start, the issue may not be EventON at all - the scanner may simply not be sending the final input trigger.

HTML5 Web Scanner

The HTML5 web scanner makes it possible to scan through the browser directly on the verification page using the device camera. The official page labels this feature as beta. That means it should be tested especially carefully: the browser must request camera permission, the site must load over a secure protocol, and the staff member must already be authenticated.

For small events, this can be a convenient option, but for high-stakes entry control, you should always have a backup path: a standard scanner app or a scanner gun. Do not tie the entire process to a single browser-based mode without rehearsing it on site first.

Practical Scenario: Checking In Guests for a Workshop

Imagine a training school website hosting a paid workshop for 80 attendees. Tickets are sold through EventON Tickets, some guests arrive with a PDF or email open on their phone, and two staff members work the entrance: one scans, the other helps guests find the email. The goal is to check people in quickly and avoid admitting the same ticket twice.

Goal

You need a working flow where the guest has a ticket with a QR code, staff have a separate verification page, the status after scanning is immediately clear, and ticket details are easy to review. The real success condition is not just "the code scans," but "after scanning, staff can tell whether this guest should be admitted."

Preparation

• Create a test event and a test ticket that is not tied to a real attendee.
• Make sure the order or RSVP is in a state that should allow entry.
• Create a verification page with [evo_qr_checkin] if you want to use your own URL.
• Assign a separate role or user account for the entrance staff member.
• Open the verification page on every device that will be used at the entrance.

Steps

1. Log in to the site using the entrance staff role and open the verification page.
2. Send the test ticket email to a separate inbox and open the QR code on the guest phone.
3. Scan the QR code using your chosen method: camera, app, or scanner gun.
4. On the result page, click the check-in button if your workflow requires one-click confirmation.
5. Scan the same code again to see how the system behaves when the ticket has already been used.
6. Check the ticket record in the admin area and confirm that the status changed as expected.

Verification and an Important Detail

The expected result is that the page shows a successful check-in, ticket details, and a clear status. When the same code is scanned again, staff should see that the ticket has already been used rather than getting a second "successful entry" without a warning. If the system opens the WordPress login page instead, the problem is almost always device authentication or the QR link opening in the wrong browser.

Run your rehearsal somewhere that feels like the real entrance, not just at a desk: use the actual venue Wi-Fi or mobile connection, the real staff phone, similar lighting, and the same way guests are likely to present their ticket.

How to Read the Scan Result and Ticket Data

Scanning should not end with a simple green or red response. EventON QR Codes can display additional information on the check-in page: the ticket holder's name, the event title, the number of tickets in the order, the event type category, and data from Booking, Seats, and Variations & Options if those add-ons are used on the site.

That information keeps entry from turning into a blind yes-or-no action. For example, if someone shows a ticket for the wrong event, staff can see the event title immediately. If there are multiple tickets in one order, the quantity can be verified. If seat assignments or variations are in use, the check-in page may explain why two guests with similar names should not be treated as the same ticket.

What to Check After the First Successful Scan

• The ticket holder or RSVP attendee name appears as expected.
• The event title matches the event currently being admitted.
• The status changes after check-in, and a second scan shows a different result.
• If the ticket was purchased together with others, the screen makes the order relationship clear.
• If additional ticketing add-ons are in use, their data is visible and does not break the mobile layout.

When You Should Roll Back a Setting

Roll back any questionable setting if it slows down entry. For example, if scanner gun mode is unstable because of keyboard behavior, temporarily return to a mobile scanner app. If the color scheme makes statuses hard to distinguish, switch back to high-contrast colors. If the HTML5 scanner cannot access the camera on some devices, do not use it as your only verification channel.

Practical Use Cases for Different Event Types

QR verification is most valuable when it is built into a real event workflow. Below are several examples based on confirmed add-on capabilities: tickets or RSVP, a check-in page, selected roles, multiple scanning modes, ticket data, and the ability to view other tickets from the same order.

Small Paid Seminar

For a seminar with 30 to 100 attendees, one phone and a dedicated staff account are usually enough. The main thing is to open the verification page in advance and confirm that the guest's ticket email is readable from the phone screen. In this kind of flow, you usually do not need a dedicated scanner gun if traffic is moderate.

Concert or Club Event

For heavier traffic, a scanner gun or at least two devices is a better choice. One staff member scans while the other handles exceptions: the email cannot be found, the ticket has already been used, or the guest arrives with multiple tickets. The ability to view other tickets in the same order is especially useful when one person purchased tickets for a group.

Free RSVP Registration

Even for a free event, a QR code is still useful: it reduces manual list searches and helps track actual attendance. But in an RSVP workflow, it is important to define in advance which statuses should allow entry. For example, if there is a waitlist or a declined RSVP state, the entrance team should know which screens mean admit and which require manual review.

Printed Tickets and Backup Entry

If your audience often prints tickets or the venue has weak connectivity, the combination of QR Code and PDFer can work well. In that case, the QR code should be large enough and high enough in contrast to scan reliably, and staff should have a backup method for finding the ticket in the admin area or on the verification page by number if the camera cannot read the printout.

Security, Speed, and Operational Limits

A QR code on a ticket is not a magic security layer. It helps staff open a verification link quickly or pass an identifier efficiently, but the actual security of the process depends on access permissions, ticket status, order integrity, the behavior of the verification page, and how disciplined the entrance team is.

Staff Permissions

Do not give staff more access than they need for the job. If the add-on allows you to choose which roles can verify guests, use a separate role or a limited-access account. After the event, you can disable those accounts or remove them from the allowed role list.

Cache and Minification

Check-in pages should not be treated like regular marketing pages. If a caching plugin aggressively caches the result or delays JavaScript, a staff member may see an outdated screen. It is usually reasonable to disable caching for the verification page at the caching-plugin level if your stack supports that.

Venue Connectivity

EventON QR Codes validates data through the website, which means the staff device must be able to open your WordPress page reliably. Before the event, test the venue Wi-Fi, mobile internet, and a backup option. If connectivity at the venue is unstable, prepare several devices in advance and keep a manual guest list as a backup instead of relying on a single phone.

REST API for Developers

The official documentation describes a REST API with GET endpoints for the event list, the attendee list for a specific event, a single attendee, and check-in status. This is useful for developers building a custom dashboard or integration around verification. But a typical site administrator should not start with the API: first make sure the standard check-in page works reliably.

Briefing the Entrance Team Before the Event

Even a well-configured QR workflow can fail if the entrance staff do not understand what the different statuses mean. That is why it is worth running a short rehearsal not only for the technical administrator, but also for the people who will actually manage the line.

Create a short one-page internal instruction sheet. It does not need to explain WordPress or EventON from scratch. It only needs to document which browser to open, which account to log in with, where the check-in page lives, which status means successful entry, what to do when a scan is repeated, and who should handle disputed cases.

Mini Scenarios for Practice

Prepare several test QR codes for the rehearsal. One should scan successfully, another should simulate a repeated scan, and a third should represent a ticket for the wrong event or an RSVP that requires manual review. If you have multiple tickets in one order, include that case as well, because it often raises questions for staff.

• Successful ticket: the staff member sees an approved status and checks the attendee in.
• Repeated ticket: the staff member does not automatically admit the guest and instead confirms the situation with the responsible team member.
• Wrong browser: the staff member sees the login screen and knows the link must be opened in the authenticated browser.
• Scanner issue: the staff member checks input focus or switches to the backup scanning method.

Backup Procedure

Your backup process should not be more complicated than the main workflow. If the QR code cannot be scanned, staff can direct the guest to a separate desk where someone responsible verifies the ticket manually by name, order number, or RSVP data. If venue connectivity is unstable, prepare a device with an alternate connection in advance and keep a separate list of expected guests. That backup does not replace QR verification, but it greatly reduces the risk of stopping the entire line because of one device.

A good readiness test is this: the staff member at the entrance can explain what to do without an administrator standing next to them. If they do not know what a repeated scan means, where to click after using a scanner gun, or why the link opened to the login form, the setup is not finished yet.

When EventON QR Codes Is the Right Choice

EventON QR Codes is worth using if your site already runs on EventON, registrations or tickets are created through supported add-ons, and your team wants to verify guests without moving data into a separate system. In that setup, QR Code solves a clear operational problem: it links a ticket or RSVP directly to check-in at the entrance.

Before the live event, run three checks: does the QR code appear in the ticket or RSVP email, can a staff member with the correct role open the check-in page, and does the status change correctly on the first and repeated scan. If all three work on a real device, you can move on to staff preparation and your entrance procedure.

If you are still building a test copy of the site or moving an event to a new venue, it is safer to first get the WordPress version, test it on a sample event, and only then enable QR verification for real guests. That sequence reduces the risk of surprises at the door and helps you decide whether the add-on truly fits your event workflow.