Event Tickets Plus stores attendees from WooCommerce-backed tickets as tribe_wooticket posts, each joined to a WooCommerce order whose post_status follows the standard WooCommerce values: wc-pending, wc-processing, wc-completed, wc-on-hold, wc-cancelled, and wc-refunded. Check-in writes to _tribe_qr_ticket_checkedin on the attendee post with a timestamp.

SleekView Kanban reads the same attendee posts and orders and groups them into columns by the combined status. The board shows Pending payment, Completed (paid), Checked in, and Refunded as separate stacks. Each card surfaces the attendee name, the event title, the ticket type, the order total, and the check-in indicator, ready to scan at the door or reconcile in the back office without opening the record.

Dragging a card writes the new state back to the source row. Moving a card from Completed into Checked in writes the check-in meta and stamps the time the same way the door scanner does. Moving a card into Refunded refunds the linked WooCommerce order through the standard refund hook, with the Event Tickets Plus attendee flagged accordingly. SleekView keeps an audit log per card so changes made on the board are traceable back to the user who made them.

Event Tickets Plus splits attendee data across the attendee post type, the linked WooCommerce order, and the check-in meta on the same post. The default admin shows the attendees screen, the WooCommerce orders screen, and the check-in report on separate screens, which is fine for accounting and confusing for the team at the door. A registrar confirming tonight's check-ins has to read the attendees list, the orders list, and the scanner report, all of which read the same underlying data.

The board view fixes this by making the only state that matters, the combined order and check-in status, the primary axis of one screen. You can see at a glance how many attendees are awaiting payment, how many have paid and are ready to scan, how many have been checked in, and how many have been refunded. Cards make individual attendees legible at the level of name, event, ticket type, order total, and check-in flag.

Drag is the natural verb for scanning a ticket in, confirming a payment, or refunding an order through to closure, and because SleekView writes through the standard Event Tickets and WooCommerce paths, every drag still triggers the configured emails, the ticket validity changes, and the refund hooks you already rely on.