✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for BookingPress: appointments & customers as tables

BookingPress writes appointments, customers, and payments to wp_bookingpress_* tables that never share a screen. SleekView joins them and adds the flat, editable grid the plugin never shipped.

♾️ Lifetime License available

SleekView table view for BookingPress

Every BookingPress appointment, side by side

BookingPress is calendar-first like most appointment plugins, with a flat list that is fixed in column order and shared by no filters. Customers in wp_bookingpress_customers never appear next to bookings. Payments live separately. Reconciling money with bookings is manual, custom fields per service are invisible outside the booking detail modal, and there is no way to save a filter for repeat use.

SleekView builds the join the database already supports. Each row pairs a single appointment from wp_bookingpress_appointment_bookings with its customer, service, staff, and payment row. Inline edits cover start time, status, payment, and staff. Filter by service, location, status, or payment state and save the view — front desk runs reception, bookkeepers run reconciliation, owners run the day's overview, all from the same grid.

Bulk approve, cancel, or refund operations work over filtered selections. Refunds trigger the same gateway calls BookingPress would on a single-record action. Custom fields stored against an appointment turn into columns automatically and become filterable like any other field. Performance stays sharp because the grid avoids loading the calendar UI on every page — pagination is server-side and built around the indexes BookingPress puts on its tables.

Workflow

Join BookingPress tables into one editable grid

1

Base on appointment bookings

Use wp_bookingpress_appointment_bookings as the source so each row is one appointment with date, time, status, and the foreign keys for customer, service, and staff.
2

Pull customers and payments

Join wp_bookingpress_customers and wp_bookingpress_payments so customer details, gateway, and payment status sit on the same row as the booking.
3

Save reusable views

Add views for today's pending bookings, this week's refunds, and per-staff schedules. The team opens the right slice with one click instead of re-applying filters every morning.
4

Enable inline edits and bulk actions

Mark time, status, and payment editable. Bulk approve, cancel, or refund through BookingPress so notifications fire and gateway calls happen exactly as they would on a single edit.

Sample columns

A typical BookingPress appointments view

One row per appointment booking with customer, service, staff, and payment state.
Source: wp_bookingpress_appointment_bookings, wp_bookingpress_customers, wp_bookingpress_payments
Date / time Customer Service Staff Status Total
May 04 — 09:00 Naomi Wright Eyebrow lamination Eli Approved $60
May 04 — 10:30 Kenji Mori Sports massage Tara Pending $120
May 05 — 15:00 Lila Brooks Initial consult Dr. Vega No-show
May 05 — 16:30 Eitan Cohen Personal training Mateo Approved $80

Comparison

Default BookingPress admin vs SleekView

Default BookingPress admin

  • BookingPress's calendar shows time slots, but a flat list with proper filters is missing.
  • Customer data lives in wp_bookingpress_customers and never surfaces alongside the appointment.
  • Payment status is on a different page, so reconciling money with bookings is manual.
  • There is no inline editing of price, deposit, or staff member.
  • Reporting is limited and there is no way to save a filter for repeat use.

SleekView

  • Joins appointments, customers, services, and payments into one editable grid.
  • Inline edit start time, status, payment, or staff right in the cell.
  • Filter by service, location, status, or payment state and save reusable views.
  • Bulk approve, cancel, or refund selected appointments in two clicks.
  • Export the filtered rows as CSV with only the columns you need.

Features

What SleekView gives you for BookingPress

Joined tables

Brings appointments, customers, services, and payments onto a single row per booking, surfacing the relationships BookingPress's own admin never shows together.

Saved booking views

Pin filters per staff member, service, or payment state so each team opens its own view — reception, finance, individual practitioners — with one click.

Inline edits

Update time, status, or amount inside the table and BookingPress notifications fire as normal, with the gateway behaving exactly as on a single edit.

Audience

Who uses SleekView for BookingPress

Service businesses

Run today's schedule from a flat list instead of dragging through calendar weeks — pending and confirmed bookings filtered side by side.

Bookkeepers

Pull paid and unpaid appointments into a single export for reconciliation, with gateway, amount, and refund status as filterable columns.

Reception staff

Find a customer, edit their booking, and confirm payment in one window — the per-customer history sits on the same grid as the current day's schedule.

The bigger picture

Why bookings need a flat list, not just a calendar

Service businesses need both views and most plugins ship one. The calendar shows the day. The flat list shows the operation: how many bookings need confirming, which payments did not capture, who has booked twice this month and not at all this week, which custom field came back blank for the new intake form.

Asking those questions inside BookingPress today means clicking through booking detail modals one at a time, because the data is in tables the admin never joins on a single screen. The cost is small per booking and large per business — minutes per appointment, multiplied by every operational moment, repeated every week. Replace that with a saved filter and the math flips.

Reception confirms a morning's pending bookings before doors open. Bookkeepers reconcile a week of payments against booking status in one filtered export. Owners see the whole business as a flat list when they want it and as a calendar when they need it.

The grid is not a replacement for the calendar; it is the missing half of the same plugin.

Questions

Common questions about SleekView for BookingPress

No. Customers still book through the usual frontend forms, and BookingPress handles the booking lifecycle as it always has. SleekView only changes how staff manage existing bookings inside wp-admin — the public side and the customer journey stay untouched.

 

Yes. Use the calendar for visual scheduling and conflict detection, and SleekView for flat-list operations, audits, and per-customer history. The two share the same underlying wp_bookingpress_* tables, so an inline edit in the grid shows up immediately on the calendar.

 

Custom fields stored against an appointment can be turned into columns and filtered like any other field. Useful for intake forms, special-requirement flags, or any per-service question, since those fields are otherwise hidden inside the booking detail modal.

 

Filter by staff, service, or location and save a view per team. All filters work off the same wp_bookingpress_* tables, so a multi-location operation can run a per-branch view alongside a global view from the same grid.

 

Yes. Bulk or single-row refund actions trigger the same gateway calls BookingPress would on a normal refund. Filter to a date range, select the rows, and the refund flow runs through Stripe, PayPal, or whichever gateway the booking used — with status updated on the row when the gateway responds.

 

SleekView paginates server-side and avoids loading the calendar UI, so even thousands of bookings open instantly. Only the visible rows are fetched, and the grid uses the indexes BookingPress already places on its tables for filter and sort operations.

 

Build a filter on customer total bookings equals one and last booking older than ninety days. Save it as a re-engagement view, and a single bulk action sends a BookingPress reminder email or pushes the segment to a marketing tool. The base data is already in the customer table.

 

Yes. Recurring occurrences appear as separate rows so a single instance can be edited without touching the rest of the series. Filter on recurring parent ID to see the whole series, or filter on date range for the next month's occurrences only.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView