Yes. MPHB stores accommodations as mphb_room_type, individual rooms as mphb_room, bookings as mphb_booking, and seasons as mphb_season. SleekView discovers these post types automatically and lists the meta keys actually present on each, so you pick from a real list when composing columns rather than guessing key names.

Yes. Base price lives in postmeta on the mphb_room_type post. Current-season price comes from the mphb_season post that covers today's date and applies to that accommodation. SleekView resolves the join and surfaces both as columns, with the active season name visible so you know which rate is in play.

Yes. SleekView writes through WordPress's update_post_meta and post-update layer, which is what MPHB's own admin uses. Pricing changes are picked up on the next front-end search, availability checks query the same booking data, and any plugins listening on save_post_mphb_room_type or save_post_mphb_booking still fire.

Each table is one view, but views are switchable inside a single SleekView page. A property page can have tabs for Bookings, Accommodations, and Season Rates — same data the booking engine uses, just composed for the role looking at it. A kanban view of bookings grouped by status is also a one-line config change.

Bookings store check-in and check-out as meta keys (mphb_check_in_date, mphb_check_out_date). SleekView filters on those directly, so a "This week's arrivals" view is one date-range filter. Sorting by check-in date is index-friendly when the standard MPHB indexes are present, which they are on a default install.

No — it's an additional admin surface. MPHB's calendar and booking screens stay where they are for the people who like them. SleekView gives revenue, reception, and ownership teams the row-level views they need without disturbing the existing admin or rewriting workflows that already work.

Yes. Properties are taxonomy terms or parent posts depending on configuration, and SleekView filters by either. A multi-property hotelier can keep one view per property or compose a single cross-property table grouped by property, whichever matches how the team actually operates.

Yes. Each mphb_season post links to one or more rate posts that store the price per accommodation. SleekView surfaces those rates as rows with accommodation, season, date range, and price columns. Edit the price inline, bulk-apply a percentage change across a season, or duplicate a season for next year — all without opening individual posts.