Event Tickets Plus layers paid tickets on top of Event Tickets through WooCommerce, plus custom registration fields stored as attendee postmeta. Attendees live as posts tied to each event, and orders bridge into WooCommerce when paid tickets are involved. The default attendee list is per-event, which works for editing one record but breaks down on the day of a multi-event run.

SleekView reads the attendee CPT, joins the event, the ticket post type, and the WooCommerce order, and surfaces ticket type, check-in status, order total, payment method, and registration question answers as columns. Custom registration fields (meal preference, t-shirt size, accessibility note) promote to typed columns the moment they are registered, so vendor handoffs stop requiring CSV gymnastics.

Inline check-ins write to the _tribe_attendee_checkin meta key the plugin uses internally. Bulk operations on a filtered view (resend tickets, refund a session, mark a row checked-in) route through standard WordPress and WooCommerce APIs so the rest of the stack stays in sync.

Event Tickets Plus turns Event Tickets into a real ticketing system with paid tickets, WooCommerce orders, and custom registration fields. The data quality is excellent: every attendee carries a ticket type, an order link, check-in status, and the answers to every custom registration question. The gap is the working-day admin, where a coordinator wants those answers visible across events without exporting anything.

Treating the attendee CPT plus its joins as a real grid changes the working day: door staff check in from a phone, vendors get clean per-meal counts, support finds every ticket attached to one buyer in seconds. Saved views become the rituals: door velocity, vendor handoff, weekly support review. The plugin keeps owning the registrations; SleekView just makes them editable from the angle each role actually needs.