Storefront popup

The storefront popup is the data-capture moment in Easy Tickets. Before a customer adds a ticket to cart, the popup collects everything you need to issue the ticket - attendee name, custom fields, date/time selection, refund-protection opt-in.

What the popup captures

Standard fields:

• First name, last name.
• Email.
• Phone (optional toggle per event).

Plus, depending on event configuration:

• Custom fields (any you've defined).
• Date / time slot (for recurring date-picker mode or time-slotted events).
• Add-on selection (T-shirt size, meal, parking, etc).
• Refund protection opt-in (if enabled).
• Delivery mode selector (if customer-choice mode).
• Waitlist signup form (if event is sold out).

How the popup is installed

The popup is a theme app extension block. From the Setup Checklist (or any time):

1. Open the theme editor.
2. Navigate to a product page template.
3. Click Add block.
4. Search for Easy Tickets Popup.
5. Drop it in.
6. Save.

The block loads the popup script on every product page. The script only renders the popup when the product is an Easy Tickets event.

Customising the popup

Like emails and PDFs, the popup has a full editor:

• Visual editor with block-level toggles.
• Advanced settings for column widths, field arrangement.
• Code editor for raw HTML.

You can change:

• Modal vs inline display.
• Overlay colour and opacity (for modal mode).
• Modal background colour, accent colour, text colours.
• Button style and copy.
• Input field styling.
• Success messaging after submit.
• Block order (date picker before custom fields, or after).

See Emails and PDF tickets for the editor mechanics - same patterns apply.

Field configuration

Standard and custom field config lives in the event's Attendee info settings, not the popup template:

1. Open the event.
2. Settings → Attendee info.
3. Add/edit/reorder fields.

Each field has:

• Label - what the customer sees.
• Type - text, select, checkbox, date.
• Required - blocks submit until filled.
• Editable after purchase - whether the attendee can change the value later via the ticket page.

The popup picks up these definitions automatically.

Per-attendee vs per-order capture

For a multi-ticket order, you have two capture options (set per event):

• Per attendee. The popup loops - capture details for ticket 1, then ticket 2, etc. Each ticket gets unique attendee data.
• Per order. The popup captures one set of details and applies it to all tickets in the order.

Per-attendee is the common choice for workshops, dinners, classes. Per-order is fine for general admission concerts where you don't need each person's name.

Date and time pickers

For recurring events in "date picker" display mode:

• The popup includes a calendar UI.
• Customers pick a date.
• Available dates are highlighted; sold-out dates are greyed.
• The selected date's variant adds to cart.

For time-slotted events:

• The popup includes a slot picker (list or grid).
• Each slot shows its time, availability, and price.
• The selected slot's variant adds to cart.

Add-on selection

If the event has option groups configured:

• The popup includes a section for each group.
• Per-attendee or per-order selection (configured per group).
• Required/optional per group.

Each selected option adds the option's variant to cart as an additional line item, with pricing and inventory tracked separately.

See Add-ons and option groups.

Waitlist signup

When the event sells out:

• The Add to Cart button changes to Join waitlist.
• The popup shows a waitlist form (name, email, optional phone).
• Submitting adds the customer to the waitlist.
• A Shopify Flow trigger fires (Waitlist Signup) for custom automations.

See Waitlist.

Modal vs inline

• Modal (default) - overlay that opens when the customer clicks Add to Cart. The popup blocks page interaction until completed or dismissed.
• Inline - the form renders directly on the product page as a section. No overlay, no Add to Cart blocking. Add to Cart is enabled only after the form is filled.

Inline is better for:

• Long forms with many custom fields.
• Mobile UX where modals feel cramped.
• Events where the form's content is part of the storefront design.

Modal is better for:

• Short forms.
• Stores where the popup should be impossible to miss.

Phone number capture

The phone field has a per-event toggle:

• On. Phone is shown in the popup. Configure whether it's required.
• Off. Phone is hidden entirely.

Off is fine for most events. Turn it on for:

• Workshops where you need to text "your session is starting".
• Tours where you need a contact number for day-of changes.
• Events with SMS reminders integrated via Klaviyo or other.

What's next

• Attendee management - what happens to the captured data.
• Emails and PDF tickets - the editor pattern.
• Add-ons and option groups - the add-on flow.