Yes. Group discounts, partial payments, and trip extras stored in meta can all be surfaced as columns. The Trip Reviews, Trip Tabs, and Custom Enquiry add-ons expose data SleekView reads through their meta keys. New add-ons typically work without reconfiguration since the detection is schema-driven rather than per-add-on.

Yes. Date range filters work on departure dates as well as booking creation dates. Use relative ranges like next 30 days for upcoming departures, or absolute ranges for season-specific reports. Combine with destination and status filters to answer questions like which Asia trips depart in Q3 with seats remaining.

Yes. Customer name, email, and booking status are joinable into the trip table or kept as a separate bookings view. Privacy-sensitive fields like phone or address can be hidden from non-admin staff through role-based column visibility, while customer support roles see the full record.

Yes. SleekView calls the same WP Travel Engine update functions so seat counts and pricing stay consistent. If a trip has multiple departures, editing one departure does not affect others. Cap rules, minimum group sizes, and other constraints set in the trip configuration are enforced server-side on every edit.

Yes. Role-based column visibility lets sales staff see availability while keeping customer data hidden. A trip planner can adjust prices and capacity without seeing personal information for booked travelers. Customer support and finance roles get the additional booking columns based on their permissions.

Yes. Currency is read from each booking record so mixed-currency tours render correctly. Sorting and filtering on price work within a single currency view, while a multi-currency report uses currency as a grouping column. Aggregate totals respect the currency context to avoid mixing USD and EUR in a single sum.

Each booking row shows total amount, paid amount, and balance due as separate columns when the Partial Payments add-on is active. Filter to bookings with outstanding balances to drive payment reminders, or sort by balance due to prioritize collection efforts. The data flows from the standard payment meta WP Travel Engine writes.

Yes. Use role-based filters to scope the table to whatever the current user can manage. A guide assigned to specific trips through a guide-assignment meta field sees only those trips. Combine with departure date filters to give each guide a personal upcoming schedule view they can bookmark.