FooEvents writes every attendee as a WordPress post. Each row lives in event_magic_tickets with meta keys like WooCommerceEventsStatus for unpaid, paid, or checked in, WooCommerceEventsOrderID linking to the WooCommerce order, plus attendee name, email, ticket type, and seat where Seating is enabled. The default Tickets screen shows those rows as a list with status as a column label and seating on a different screen.

SleekView Kanban reads the same event_magic_tickets posts and groups them by WooCommerceEventsStatus into columns. The board shows Unpaid, Paid, Checked in, and Refunded as distinct stacks with a count at the top of each column and a card per attendee. Each card carries attendee name and email, event title, ticket type, and order total from the linked Woo order, so the front of the card holds everything the door staff and the organiser need at a glance.

Dragging writes back to the source. Moving a card from Unpaid to Paid flips WooCommerceEventsStatus and the linked Woo order status when the order is still pending, moving a card to Checked in writes the FooEvents check-in meta and the timestamp, and moving a card to Refunded reverses the linked Woo order through the standard hook. Seated attendees show the seat label on the meta line so the door team picks up the right wristband without opening the row.

FooEvents encodes the full attendee workflow on each ticket row. The Woo order creates an event_magic_tickets post with WooCommerceEventsStatus set to unpaid, the gateway capture flips it to paid, the door scan writes the check-in meta and the timestamp, and a refund either reverses the linked Woo order or moves the row to refunded. The default reading surface is still a single Tickets list with status as a column label, and seating is on a separate screen, so the organiser switches between three screens to read what is really one workflow.

SleekView Kanban reads the same event_magic_tickets posts and lays them out as Unpaid, Paid, Checked in, and Refunded columns with door-ready cards on each one. Approving a batch of unpaid orders is a group drag, marking attendance is a drag at the door, refunds reverse the linked Woo order through the same hook the orders screen uses. The Tickets screen, the orders screen, and the FooEvents check-in app all read the same value the board edits because SleekView writes to the source row, not to a parallel state.