Vik Booking stores reservations in plugin-specific tables (commonly prefixed wp_vikbooking_*) including wp_vikbooking_orders for reservations, wp_vikbooking_rooms for room records, and rate-plan plus availability tables alongside. Reservations link to one or more rooms via join records and reference rate plans and channels for OTA-originated bookings.

The default Vik Booking admin offers a strong calendar and dedicated screens per concept (reservations, rooms, rates, channels). The cost is fragmentation: front desk sees the calendar, revenue manages rates on another page, and channel sync errors live in yet another report. SleekView reads wp_vikbooking_orders directly, joins to wp_vikbooking_rooms for room name, and pivots check-in, check-out, channel, and rate plan into named columns.

Status edits route through Vik Booking's reservation API so notifications and channel-manager sync fire as they would from the default admin. Internal ops tags stay in plugin-specific meta or extra columns added to the order table, with direct writes guarded by conflict detection.

Independent hotels and small chains adopt Vik Booking because it gives them a real property management plugin without leaving WordPress: reservations, rooms, rate plans, and channel manager all in one ecosystem. The cost shows up in the admin, where each concept lives on a different screen. Front desk sees the calendar, revenue manages rates on another page, and channel sync errors land in yet another report.

The data, though, is well-modelled: wp_vikbooking_orders joins cleanly to wp_vikbooking_rooms and wp_vikbooking_rates. SleekView pivots those tables into named columns and adds the filters daily ops actually need: by channel, by room, by status, by check-in date. API write-back preserves the existing notification and channel-sync logic.

Internal ops tags stay in WordPress. The result is a single daily-ops grid that works for the morning's arrivals, the afternoon's OTA reconciliation, and the evening's revenue review.