Tickera writes every order and every ticket instance as a row. Orders live as tc_orders posts with statuses like order-paid, order-pending, order-cancelled, and order-refunded, plus a buyer name, email, and total. Ticket instances live in tc_tickets_instances with a serial number, an event link, and a used flag plus a check-in timestamp. The default Orders and Tickets screens show those rows as lists with status as a column label.

SleekView Kanban reads the same posts and rows and groups them on a board. The Orders board has Pending, Paid, Cancelled, and Refunded as columns with a count at the top of each, and a card per order carrying buyer name, event title, ticket count, and total. The Tickets board has Issued and Used as columns with a card per ticket instance carrying serial, event, ticket type, and the check-in time. Both boards write back to the same Tickera rows.

Dragging writes to the source. Moving an order from Pending to Paid flips post_status to order-paid and triggers the configured Tickera email, moving an order to Refunded reverses the linked WooCommerce order when Tickera Bridge for Woo is active, and moving a ticket instance to Used writes the used flag and the check-in timestamp. Custom Tickera statuses registered by third party gateways appear as their own columns without code changes.

Tickera tracks orders and ticket instances as two related but distinct workflows. An order moves from order-pending to order-paid when the gateway captures, and to order-refunded or order-cancelled when something goes wrong. Each paid order issues one or more ticket instances, and each instance flips from issued to used the first time it is scanned at the door.

The default admin is two separate screens that read these two workflows as lists with status as a column label, so a busy weekend means switching between Orders for finance work and Tickets for door work, with the Orders list sorted by date and the Tickets list filtered per event. SleekView Kanban gives each workflow a purpose-built board. The Orders board has Pending, Paid, Cancelled, and Refunded with a count at the top and buyer plus total on the cards.

The Tickets board has Issued and Used with a serial on each card. Dragging writes back to the same posts the plugin reads, so the Orders screen, the Tickets screen, the linked Woo orders, and the gateway reports all stay in sync without manual reconciliation between views.