Yes. Any meta field added by WP Travel Pro or its add-ons is detected and available as a column. Difficulty rating, group size, included activities, and custom enquiry fields all surface automatically. Type-aware filters appear based on the field type, so numeric fields get ranges and select fields get dropdowns without manual configuration.

Yes. Add a bookings table view alongside itineraries with customer name, email, and travel date. Hide privacy-sensitive fields from sales staff via role-based visibility while letting support staff see the full record. The two views can live on the same dashboard page for ops teams who need both.

Yes. Stripe, PayPal, and other gateway statuses sync from the booking record into the table. Filter to bookings with payment failures to drive recovery emails, or sort by amount paid to spot deposit-only bookings needing balance reminders. Refund actions fire through the same gateway integration WP Travel uses.

Yes. Each scheduled date appears as its own row so you can manage availability per departure. Filter to a single itinerary to see all its dates, or filter across itineraries to find every June departure. Capacity is tracked per date, so a parent itinerary with three dates can be partially full on one date and sold out on another.

Yes. Use role-based filters to scope the table to whatever the current user is allowed to manage. If guides are assigned via a meta field, the filter binds to that field automatically. Combine with date range filters to give each guide a personal upcoming schedule view as a bookmarkable URL.

Yes. Status changes trigger the same hooks WP Travel uses, so confirmation emails still go out. If you have customized the notification logic with a custom plugin, it continues to work because SleekView never bypasses the WP Travel update API. Bulk status changes fire one hook per row, keeping the audit trail clean.

Day-by-day itinerary content lives on the parent itinerary post and is not duplicated per row. Surface a summary column or include the daily plan as a side-panel preview when a row is expanded. For ops reporting, the row-per-trip-date model is what matters, and itinerary content stays at the itinerary level where guides reference it.

Yes for the cancellation, with a caveat for refunds. Selecting bookings and changing their status to cancelled fires the WP Travel cancellation hooks, which most payment gateway add-ons listen to for refund initiation. Test in staging first if your gateway integration uses async refund queues so you do not double-refund a customer mid-recovery.