Skip to content

Check-in Scanner

Eventonomy overviewFree + ProGet Eventonomy →

Pro - Check-in requires Eventonomy Pro.

Every attendee ticket carries a QR code that encodes a check-in URL. At the door, the event’s organizer, an Editor or a site administrator scans the QR with any phone camera and the attendee is checked in automatically, with no app to install and no token to type. Manual check-in is available too, from the Check in section of the member dashboard (and as the eventonomy-pro/checkin block or [eventonomy_checkin] shortcode, for hardware readers).

Check-in scanner with the Find attendee field, a Check in button, and guest-list matches with their own Check in buttons

  • How the QR check-in flow works
  • Where attendees find their QR ticket
  • The Check in dashboard section, and the manual block and its settings
  • What happens on a repeat scan, a refunded ticket, and an attendee’s own scan
  1. The attendee gets a QR ticket. (Online-only events have no door, so their confirmation emails and My tickets leave the QR code out. Hybrid and in-person events keep it.) Every confirmed order/RSVP mints a unique check-in token, rendered as a QR code on the order-confirmation card, in the order-confirmation email (as an image, with a plain check-in link as a fallback), and in My Tickets on their dashboard. The QR is self-contained: Eventonomy generates it in-plugin, with no external image service.
  2. The organizer or an administrator scans it. Someone authorized to manage that event’s attendees scans the attendee’s QR with any phone camera. The QR opens …/?evnm_checkin=<token>. In practice that means the event’s own organizer (the person who created the event), anyone who can edit other people’s events (Editor and up) or a site administrator - see Access Control below.
  3. The attendee is checked in through the idempotent check-in service, and the person scanning sees a “Checked in” confirmation.
  • Repeat scan - a second scan of the same ticket shows “Already checked in” (it never double-counts).
  • Refunded / cancelled ticket - a voided ticket is refused at the door (the check-in returns a 409), so a refunded seat cannot get in.
  • Attendee scans their own code (or anyone without check-in permission / logged out) - they get a neutral “present this at the door” page. No check-in happens and the token is never displayed. This is intentional: only authorized staff can redeem a ticket.

For hardware readers, or as a backup when a ticket cannot be scanned, add the eventonomy-pro/checkin block. It has one Find attendee field:

  • Type a name or email and the event’s guest list is searched as you type. Each match shows the person’s name, email and RSVP status with a Check in button. Only people marked Going can be checked in; anyone else shows Not going. Press Enter when exactly one person matches to check them in.
  • Scan or paste a ticket. A USB barcode reader types the QR’s check-in link and presses Enter, which checks the ticket in exactly like a phone scan.

Option 1: Single-event page - add the block to the event’s single-event page. Set the eventId attribute to filter check-ins to that event only.

Option 2: Dedicated check-in page - create a page (e.g. /check-in/) and add the block there so you can check in attendees from one place. Each person still checks in only for events they may manage: their own events, or every event for an Editor and up (including a site administrator).

To add the block: open the page in the Block Editor, click +, search Eventonomy Check-in, insert, and configure.

Setting Default Description
Event ID 0 The ID of the event to check attendees in to. Leave 0 to accept tokens from any event (multi-event pages).
Show stats On Show a summary line below the result area.
Allow finding attendees by name or email On Show the Find attendee field (guest-list search, and scanned or pasted tickets) and the Check in button. Turn off if you only use a hardware reader that calls the REST endpoint directly.

Since 1.6.0 manual check-in lives in the member dashboard rather than only on a page you build.

Where it is. Members who run events get a Check in item in the dashboard rail. It appears only for a member who has created at least one event, so attendees never see a door tool they cannot use.

Getting to an event. Open Check in in the dashboard and pick the event, or use the Check in action on its row under Hosting. The picker lists the upcoming events you can check in: an organizer sees their own, an Editor or a site administrator sees every event. It is searchable and paged, so it stays quick on a large site. That opens the section with the event already selected. Reaching Check in from the rail without picking an event first shows “Choose an event first” with a link back to My Events, rather than an empty box.

What the door sees.

  • The event’s name, so staff know which door they are working.
  • A live “N / M checked in” count that increases as tickets are admitted.
  • A Find attendee field: type a name or email to search the guest list, or scan / paste a ticket link.

Results. A valid ticket, or a guest-list match you check in, shows Checked in and the count goes up. A ticket already used shows Already checked in and the count does not move. A ticket that does not belong to this event shows Ticket not recognised. A search with no match says so.

Recurring events. Registration covers the whole series, but check-in is per date: the same QR code admits once on each date. The door works on the date happening now and shows a Checking in for picker; choose another date and press Change date to admit or count for it. A second scan on the same date says Already checked in, the next date is a new admission, and the count, the attendee list and the CSV all follow the chosen date. Events with a single date work as before.

Who can use it. A member can only check attendees in for an event they manage. Opening the section for someone else’s event shows “You can only check attendees in for an event you manage” and renders no input field. The same rule applies to the shortcode and the block, so putting [eventonomy_checkin id="123"] on a public page is safe: a visitor is asked to sign in, and a signed-in member who does not manage that event sees the refusal.

For developers. Filter evnm_event_checkin_link to point the rail item and the per-row action at your own check-in destination.

Check-in is authorized per event, and only these logged-in users can redeem a ticket - both via the QR scan and via the manual block:

  • The event’s own organizer, meaning whoever created the event. Ownership alone is enough; they need no WordPress editing permission.
  • Editors and up, meaning anyone who can edit other people’s events (evnm_manage_rsvps maps to edit_others_posts). They are admitted on any event they can edit.
  • Site managers, meaning anyone with the manage_options WordPress capability. On a default site that is the Administrator role.

Everyone else sees the neutral door page or a “Sign in to check attendees in” notice. A member who did not create the event is not admitted.

Changed in 1.9.2. Door access follows the right to edit other people’s events. To widen or narrow it per site, use the evnm_capabilities map or the evnm_user_can_manage_event filter. Full map: capability reference.

Configure paid ticket checkout with a payment gateway.

Payment Gateways →