Register

The Register module handles everything between “someone wants to attend” and “that person has a badge in their hand”: registration forms, pricing tiers, merchandise, payment, check-in, and badges.

For attendees

Registering for the event

1. Open your event’s registration page (linked from the event landing page).

2. Complete the registration form. Depending on the event this can include contact details, badge name, accessibility needs, and more.

3. Choose a registration tier. Each tier has a price and may include merchandise (for example, a t-shirt) or options (for example, a shirt size).

4. Optionally add extra merchandise or a donation.

5. Check out with Stripe. You can pay by card; some events also accept coupons/discount codes.

6. You will receive a confirmation and a QR code. Keep it — you scan it (or show it) at check-in to pick up your badge.

Managing your registration

From your event dashboard you can view your registrations, and — if the event allows it:

• Edit your own registration details (self-edit).

• Upgrade your tier and pay the difference (self-upgrade). If you close the payment page before finishing, you can resume the pending upgrade later, or cancel it and start over with a different tier.

• Associate a registration with your account (for example, a registration someone else bought for you).

If self-edit or self-upgrade is disabled, that is an organizer decision; contact them to make changes.

At check-in

Bring your QR code (printed or on your phone). Staff scan it, hand you your badge and any merchandise, and you are checked in. Some events also run self-service kiosks where you scan yourself before seeing a staffer.

If you need accessibility accommodations (for example evacuation assistance, disability seating, or an elevator escort), ask at check-in — staff can enroll you in the event’s Accessibility Services on the spot.

For event organizers

Prerequisites

Before attendees can register, complete this third-party setup:

Mandatory	Stripe — for registration payments.
Optional	Pagem — paging/notification integration.

Requirements:

• A valid Stripe API key, unrestricted, in LIVE mode, for registration payments.

Setting up a registration form

Registration forms are built with the visual form editor. A form is a list of fields (text, select, checkbox, merchandise, tiers, signature pad, and more) that render dynamically.

Warning

An event must have exactly one form marked as the default registration form. If none is marked default, attendees see error E:REG:1 (see Error e-reg-1). To fix it, edit a form’s details and tick Default Registration Form.

Setting up a registration check-in flow

The check-in flow is built with the visual form editor per-registration type. Select the “Check-in” Tab on the registration type form editor to create a check-in flow.

The check-in procedure is the sequence of steps a staffer walks through when checking in an attendee. Each step type does a specific job, and you compose and reorder them in the form editor’s Check-in tab:

Step type	What it does
ID Check Step	Shows the legal/identifying information captured on the form (for example, name or date of birth) so staff can verify the attendee. One per form.
Merchandise Check Step	Shows the attendee’s purchased and tier-included merchandise so staff can pull and box it. One per form.
Badge Print Step	Performs the actual check-in and renders a badge label for printing. One per form.
Text Instruction Step	Shows free-form instructions to staff (for example, “Direct the attendee to the photo booth”). Multiple allowed.

When a staffer checks someone in, the procedure runs the steps in order (with Back/Next); if no steps are defined, check-in happens immediately.

Where: open a registration form in the form editor (Register menu → Admin dropdown → Forms) and select the Check-in tab. Permission: admin on the Register module.

Registration Additional Screens and Kiosks

Where: Register menu → Admin dropdown → Kiosk Management (/app/register/system/checkin-kiosks/). Permission: admin on the Register module to create and configure kiosks. The kiosk display itself is a public URL (no sign-in) so a device can be left open on it; connecting a tether kiosk happens from the staff Check-in page, which needs staff permission on Register.

A kiosk is a check-in station you run on a tablet or screen. It is created in Kiosk Management and run from its own display URL; the Mode you choose decides who drives the check-in.

Creating a kiosk

1. Click Create Kiosk and configure:

   • Name and Description (for example, where it is located).

   • Mode:

     • Self Service — an unattended station where attendees scan their own QR code and Midsummer checks them in automatically.

     • Tether — a staffer operates the scanner from the Check-in page while the kiosk screen reflects what the staffer is doing.

   • Welcome Message shown on the idle screen.

   • Registration Forms (optional) — restrict the kiosk to specific registration forms; leave empty to accept all.

   • Display Settings — whether to show the registrant name, registration level, and registration form on the screen.

   • Audio Feedback — success and/or error beeps.

   • Auto Reset (seconds) — how long before the kiosk returns to the welcome screen after a check-in.

   • Status — Active or Inactive.

2. Save, then use the kiosk’s Copy Link action to get its display URL (/app/register/checkin-kiosk/<id>/) and open it on the kiosk device.

Running a self-service kiosk

Open the kiosk display URL on the device and leave it there. Attendees scan their QR code on the device’s hardware scanner; Midsummer looks up the registration, checks the attendee in, plays the success/error sound, shows the result, and then auto-resets to the welcome screen.

Connecting a tethered kiosk

In tether mode the kiosk screen is driven by a staffer, over a live WebSocket link:

1. Open the kiosk display URL on the kiosk/screen device — it connects as the display and waits.

2. On a separate device, open the staff Check-in page (/app/register/system/checkin/) and open the kiosk panel.

3. The panel lists active tether kiosks — choose one to connect. The staffer side connects as the operator.

4. When a QR is scanned on the kiosk’s scanner, it is sent to the staffer, who looks up the registrant and can push registrant info, the form, or check-in success to the kiosk screen. The staffer controls the display; on a successful check-in the kiosk shows the success screen and sound, then auto-resets.

Tiers and merchandise

• Registration tiers carry the price, the badge prefix (optional), and any included merchandise.

• Registration items are the merchandise catalog available for purchase during registration.

Merchandise that is part of a tier is snapshotted into each registration at checkout. If you edit a tier’s included merch later, existing registrations are not changed automatically — use the Merchandise Adjustment admin tool to correct individual registrations (every change is recorded in an audit log).

Badges

Badge numbers can be assigned automatically (a global sequence, optionally per-tier, with configurable width, prefix, and blackout numbers/ranges) or manually. All badge number changes are written to a badge-number audit log.

Check-in operations

Register’s ops views serve the at-show team:

• Check-in — scan QR, view the attendee’s form data, flag problems, check in.

• Merch summary / merch pick — pull and box merchandise by badge number.

• Rapid check-in terminals — high-throughput POS-style stations.

• Self-service kiosks — attendees scan themselves.

• Staff ↔ Management ping — a discreet chat for check-in staff to reach management without leaving the flow. Replies show which manager answered.

Accessibility services

Attendees can be enrolled in Accessibility Services during check-in: staff record the services the attendee needs (evacuation assistance level, disability seating, chair-in-line, elevator escort, group access) plus staff-only notes shared with public safety. Registration Settings shows enrollment statistics.

Warning

Accessibility data is sensitive personal information. Once the event is over, use the Purge Accessibility Data tool in Registration Settings to delete all of it in one action. Enrollments and the purge are both recorded in the registration audit log.

Reports & metrics

The reports center and metrics dashboards cover registration counts, year-over-year timelines (if data is imported into Midsummer or you have used Midsummer for previous events), merchandise, and (for superadmins) live Stripe transaction reporting. You can also get reports on Merchandise sales including breakdowns by tier inclusion or ala-cart sales.

Check-in metrics (Register menu → Admin → Check-in Metrics) measure how long each staffed check-in takes, from the staffer clicking a registration to the check-in completing — with averages, percentiles, a duration histogram, and a per-form breakdown. Use it to spot bottlenecks in your check-in procedure. Recording is on by default and can be turned off (or restricted to kiosk-connected stations) in Registration Settings. Kiosk and rapid-terminal check-ins are not timed — the metric is specifically about the staffed flow.

Note

Year-over-year timelines are available for all events, but is currently a beta feature. Please contact the Support Team if you would like to use this feature. support@midsummer.cloud

Warning

The Shop Module and the Register Module track sales differently. Creating a duplicate merchandise item in the shop will require you to use the shop module’s metrics to track sales using the shop module.

For event technical staff

• Point scanners at the check-in, rapid check-in, or kiosk routes.

• Rapid check-in terminals and kiosks have separate display routes — make sure the tablet/terminal is opened on the correct URL.

• If an attendee sees E:REG:1 or E:MID:404, it is almost always a configuration or URL issue, not a Midsummer bug — see the error reference.