WP Travel stores every itinerary booking as a itinerary-booking custom post with a post_status like pending, booked, paid, cancelled, or on-hold. 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 works for occasional inquiries and falls apart once your itinerary catalogue is selling weekly trips.

SleekView Kanban reads the same itinerary-booking posts and treats the post_status column as the natural axis to group by. Each card surfaces the customer name, the itinerary title, the departure date, the traveller count, and the total. Columns mirror your real WP Travel statuses, so a glance tells you how many bookings are pending payment, how many are confirmed, and how many cancellations still need a refund decision.

Drag a card from Pending to Booked and SleekView calls the same WP Travel update path the admin uses, which fires the confirmation email, decrements itinerary availability, and triggers any partial-payment or coupon 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.

Itinerary bookings are not just rows in a table, they are a sequence of commitments: enquiry, deposit, balance, departure, debrief. WP Travel captures all of that already in itinerary-booking posts and the linked itinerary meta. The default admin presents the result 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 tour 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 itineraries 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, itinerary, 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'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 become two reading surfaces over the same data instead of a tradeoff between them.