No. The Booking Calendar per-calendar reservation lists and calendar grid stay where they are. SleekView Charts sits alongside as a configurable layer so reservations staff, owners, and finance each get the cross-calendar chart dashboards the plugin doesn't ship today without changing the booking flow.

Yes. Form submission columns on wp_bk_form_data can be pivoted into typed dataset columns by field key. SleekView uses each typed column as a chart's groupBy or valueColumn, so custom intake fields become charts without writing any custom SQL or PHP for the data path.

The calendar_id column on the reservation table joins onto the calendar definitions table and resolves to a readable name. A single saved configuration drives the join, so every chart card on the dashboard uses the same calendar mapping consistently for the board.

Yes. A Number card counting reservations whose check-in date has passed and check-out date is still in the future on the chosen reference date gives the active-reservation KPI for any moment. Useful for daily front-desk readiness checks and capacity planning ahead.

Yes. A date range, calendar filter, or payment-status filter at the dashboard level cascades to each card on the board. A weekly review and a quarterly revenue trend can share the same saved configuration without duplicating filter selections card by card every time.

Cards query the live wpdevart reservation table on render. A new reservation created from the frontend booking form or the admin appears in every card on the next reload, with no separate sync, scheduled refresh, or cache flush step between event and chart update.

Yes. Aggregations run server-side using the indexes the plugin maintains on calendar_id and check-in date. A multi-property install with thousands of historical reservations renders the whole chart board in well under a second on a typical Kinsta host today consistently.

Yes. Each saved board is gated by a WordPress capability so reservations staff, property owners, and finance each open the dashboard that matches their job. The reservations board and the finance revenue board stay separate by default for each user logging in.