No. Pinpoint still runs the calendars, pricing, availability rules, and front-end booking flow. SleekView is a back-office reservation table for the operations side. The guest-facing booking widget is unchanged, and any ICS or sync integrations Pinpoint manages continue to work because SleekView only reads and edits, it does not own the data.

Only via Pinpoint's own update paths, so its hooks and notifications keep firing. SleekView never writes directly to wp_dopbsp_reservations behind the plugin's back. That means audit logs, owner notifications, guest emails, and any custom integrations you have built on Pinpoint's hooks continue to behave exactly as before.

Yes. Any custom field stored on the reservation can be added as a sortable column. Special requests, internal notes, cleaning fees, deposit status, all of it can become a column. For multi-property setups, custom columns can be scoped per calendar so each property's view shows only the fields its team uses.

Yes. If Pinpoint runs on WooCommerce, order status and totals appear next to the booking row. The order ID becomes a clickable link to the WooCommerce order screen for refunds or detail edits, and refunds processed in WooCommerce reflect in the reservation's payment status the next time SleekView refreshes.

Yes. Per-role row filtering can scope each user to the calendars they manage, which is essential for property management companies running on behalf of multiple owners. Owner A's manager sees only Owner A's properties, with no risk of cross-contamination on bulk actions.

Yes. SleekView runs per site, with separate table configs per blog. Network admins can deploy SleekView on the network and let each property site configure its own views, which is useful when each property is its own subsite for SEO or branding reasons.

Yes. Filter to status Pending and a date range covering the overnight window, select all rows that pass your manual checks, and bulk approve. Each approval routes through Pinpoint's standard hook, so guest confirmation emails fire as if you had clicked approve on each booking individually.

SleekView shows all reservations as separate rows, so an overlap is visible as two rows for the same calendar with conflicting check-in and check-out windows. Pinpoint itself prevents most overlaps at booking time, but historical overlaps from imports or bulk edits become easy to spot in a sorted list view.