Charts reads both. The seating chart CPT holds the seat definitions, zones, and tiers in postmeta, and tc_tickets_instances holds the assignments. SleekView joins the two so cards can group by zone or tier resolved from the chart while counting rows from the ticket instance side.

Yes. The dataset joins tc_tickets through ticket_type_id, so a card can filter to one performance or one event scope. A bar grouped by ticket_type_id with the performance name resolved through the join returns seats sold per performance across the season.

The dataset joins tc_orders on the order_id meta key. Filtering the join to orders with completed status keeps refunded, pending, and failed orders out of the seats-sold count. Switching the filter scope returns the gross count including refunds when finance needs that number.

Yes. The chart CPT's seat list gives the total capacity, and a count of tc_tickets_instances rows with tc_seat_id values gives the sold side. A Number card with both values exposes utilisation per zone or per performance, useful for spotting thin runs early.

Yes. SleekView refreshes the dataset schema from the chart CPT's seat definitions on the next refresh. A zone added in the seating chart editor becomes a slice in the donut on the next chart load, no manual column mapping required from venue ops.

Yes. Both add-ons write to tc_tickets_instances. Attendee Information adds field postmeta, Seating Charts adds the tc_seat_id meta. SleekView reads both layers, so the same dashboard can mix attendee fields and seat assignments without conflict on the underlying ticket instance row.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when the venue partner asks for the seat-level breakdown behind a performance count or finance wants the joined order rows behind a zone total.

Reporting plugins typically build a parallel data layer fed by hooks on the seat assignment save action, which means a second moving part to keep in sync. SleekView Charts reads tc_tickets_instances and the seating chart CPT directly, so the dashboard reflects the same row the seat picker edits without a sync step.