Ovatheme Booking ships with several Ovatheme demos (Hotel WP, Travel Tour, Car Rental). Reservations are stored as a custom post type backed by wp_postmeta, with the booked item (room, tour, vehicle) referenced by post ID and check-in/check-out plus guest count stored in dedicated postmeta keys. Customer details land in postmeta or are joined to a customer CPT depending on theme variant.

The default admin works through theme-specific screens that show one type of booking at a time. SleekView reads the reservation CPT directly, pivots check-in date, check-out date, item type, guest count, and status from postmeta into named columns, and joins the booked item's CPT for room/tour/vehicle name. One filter spans date range, item type, and status across all booking variants.

Updates to status route through Ovatheme's own booking hooks where they exist, so confirmation and payment emails fire normally. Direct postmeta writes are reserved for internal ops tags and reconciliation flags that the plugin does not surface in its own UI.

Ovatheme demos sell because they look polished out of the box and they almost work as a hotel, tour, or rental site. The shared Ovatheme Booking plugin handles the actual reservations and stores them as a CPT with postmeta, which is the right structural choice for flexibility. The cost shows up in the admin: the default reservation list sorts by post date, hides check-in and guest count in postmeta, and offers a different sub-screen for each booking variant.

Daily ops for a property with three rooms and two cars ends up jumping between screens to answer one question. SleekView reads the same CPT, pivots wp_postmeta into named columns, and offers combined filters for item type, status, and check-in date. Status writes respect the plugin's existing hooks.

The outcome is one daily-ops grid that works the same way regardless of whether the demo is selling rooms, tours, or vehicles.