WP Travel Engine stores every trip booking as a wte_bookings custom post with a post_status like wte-pending, wte-booked, wte-paid, wte-cancelled, or wte-refunded. The default Bookings screen lists those posts in a long table sorted by booking ID with the status as a small label per row, which is fine for occasional inquiries and breaks down for tour operators handling dozens of bookings a week.

SleekView Kanban reads the same wte_bookings posts and treats the post_status column as the natural axis to group by. Each card surfaces the customer name, the trip name, the trip date, the traveller count, and the order total. Columns mirror your real WP Travel Engine statuses, so a glance tells you how many trips are awaiting payment, how many are confirmed, and how many have been cancelled with refunds still to process.

Drag a card from Pending to Booked and SleekView calls the same WP Travel Engine update path the admin uses, which fires the confirmation email, updates the trip availability, and triggers any partial-payment hooks you have configured. Drag to Cancelled and the refund and notification flows run through the plugin so any payment gateway integration handles the money side the same way it would from the admin.

Travel bookings are not just a row in a table, they are a sequence of commitments: enquiry, deposit, balance, departure, debrief. WP Travel Engine stores all of that already in wte_bookings and the linked trip meta. The default admin presents it as a list sorted by booking ID, which is the order they came in, not the order they need attention.

That order makes sense for accounting and useless for operations. The board view fixes this by making the only state that matters, the booking status, the primary axis of the screen. You can see at a glance how many trips are awaiting payment, how many are confirmed for next week, and how many cancellations still owe a refund.

Cards make individual bookings legible at the level of customer, trip, dates, travellers, and money, which is what a tour operator and a guide team actually need. Drag is the natural verb for moving a booking from one stage to the next, and because SleekView writes through WP Travel Engine's own functions, every drag still triggers the confirmation emails, the payment captures, and the availability changes you already configured. List view and board view stop being a tradeoff and start being two reading surfaces over the same trip-booking data.