OvaBooking (the booking engine that ships with several Ovatheme demos) stores bookings as a custom post type with check-in, check-out, persons, service reference, and status in wp_postmeta. The bookable services themselves are related CPTs such as tour, hotel_room, or rental_car depending on which Ovatheme demo is in use.

The default admin lists bookings with fixed columns and a calendar tab. Cross-service filtering ("all tours starting next week" plus "all hotel rooms for the same dates") is awkward because each service type sits in its own list, and pivot postmeta values like dates and persons stay hidden until each booking is opened.

SleekView reads the booking CPT directly, pivots postmeta into named columns, and joins to whichever bookable-service CPT the row references. Operators see tours, rooms, and rentals in one grid, filterable by date range, service type, and status, and edits route through the plugin's own status methods so confirmation emails still fire.

Many Ovatheme sites sell more than one thing: tours and a hotel, or a rental fleet alongside experiences. The default admin treats those as separate worlds because each lives behind its own service CPT, but the operational view is one shared schedule. A booking arrives, somebody confirms it, somebody chases payment, somebody assigns staff or a vehicle.

The data to do that work is already in the OvaBooking schema, postmeta keys for dates and persons, the linked service CPT for the name. Without a column-aware grid, that data stays one click away on every row, and the operator's morning becomes a series of tabs and copy-pastes. SleekView pivots the postmeta into columns, joins the service CPT for friendly names, and shows tours, rooms, and rentals next to each other in one filterable view.

Confirmations route through OvaBooking's own status methods so the rest of the plugin keeps working, and finance, reception, and field staff each get a saved view scoped to their role.