Yes. WooCommerce Bridge, Multiple Tickets, and Custom Fields add-ons all expose data SleekView can render. Custom fields registered through the Custom Fields add-on appear as columns automatically. The WooCommerce Bridge order data is joinable into the ticket view for support flows that need order context alongside ticket info.

Yes. Embed the table on a frontend page, scope it to the door-staff role, and hide every column except attendee and check-in. Door staff log in via a custom login page, get a ticket-search view tailored to scanning, and never touch wp-admin. The check-in toggle is large enough for fast tablet input at the venue entrance.

Yes. Toggling check-in fires the standard tc_check_in action so any add-on listening keeps working. If you have a custom plugin sending check-in notifications to Slack or marking sessions complete in an LMS, those automations continue to fire as expected. Bulk check-ins dispatch the hook one row at a time to keep the audit trail consistent.

Yes. Multi-select filters work on ticket type, event, and any custom field you add as a column. Combine ticket type with check-in status to find unchecked-in VIPs, or with sale date to spot late-purchase patterns. Saved presets let you switch between filter combinations without rebuilding them each time.

No. Server-side pagination and indexed lookups keep it fast even with tens of thousands of tickets. The visible page loads first, and filter changes use indexed queries rather than full table scans. Door scanning stays responsive even at peak ingress when hundreds of check-ins happen per minute.

Yes. Custom fields added to tickets become columns and are included in any CSV export. Filter to the rows you want, hit export, and the visible columns including custom fields end up in the file. Useful for handing a post-event attendee list with session preferences to the speaker who wants to follow up.

Set up a refund column action that calls the Tickera or WooCommerce refund flow depending on which gateway processed the original purchase. The action fires the same hooks a manual refund would, so payment provider sync, accounting integrations, and confirmation emails all run normally. For multi-step refund flows requiring additional confirmations, route through a custom action button that opens a modal first.

Yes if you store session attendance as custom field data per ticket or as a separate per-session check-in record. SleekView surfaces that data as filterable columns: filter to attendees who checked into session A but not session B, or sort by total session check-ins to find your most engaged attendees. Useful for measuring conference engagement post-event.