✨ 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 WooCommerce Bookings: bookings & resources as tables

WooCommerce Bookings stores each booking as a wc_booking post with start, end, and resource ID in postmeta. SleekView pivots that into a flat schedule view filterable by resource, date range, and status — without per-booking clicks.

♾️ Lifetime License available

SleekView table view for WooCommerce Bookings

Booking ops as a real schedule

WooCommerce Bookings stores each booking as a wc_booking post with the booked product reference, resource ID, start time, end time, person count, and customer details in postmeta keys like _booking_start, _booking_end, _booking_resource_id, _booking_persons, and the standard WooCommerce billing keys. Bookable products are product CPT entries with bookings-specific postmeta, and resources are bookable_resource posts.

The default Bookings admin lists bookings with fixed columns and a calendar tab. Cross-resource availability filtering, per-product booking counts, and bulk status changes (confirming a batch of pending bookings, marking no-shows after a workshop) all require either per-row clicks or custom queries. The postmeta values that drive scheduling — start, end, resource — aren't surfaced inline, so spotting a double-booked resource means opening each row.

SleekView reads wc_booking directly, pivots the booking postmeta into proper columns, and joins to the parent product for product name and to wc_orders for payment status. Resource availability becomes a date+resource filter, the daily schedule becomes a sortable view, and pending bookings become a single bulk-confirm queue.

Workflow

Booking ops as a real schedule table

1

Map the booking CPT

Point SleekView at wc_booking and add _booking_start, _booking_end, _booking_resource_id, and _booking_persons as columns. Each booking renders as one schedule row.
2

Join product and resource

Join the product CPT for booked-product name and bookable_resource for resource name. Add the parent wc_orders for payment status so the schedule shows whether each booking is paid.
3

Build the schedule views

Save views for today's schedule, this week by resource, pending confirmations, and cancelled-but-still-allocated. Filter on the start/end date columns or by resource_id directly.
4

Confirm or cancel inline

Update booking status (pending to confirmed, confirmed to no-show) inline. Status writes route through the WooCommerce Bookings API so email triggers and resource releases fire as expected.

Sample columns

A typical bookings view

One row per booking with start/end, resource, product, and status visible.
Source: wp_posts (wc_booking) + wp_postmeta
Booking # Product Resource Start End Status
#B-820 Studio rental Room A Apr 26 10:00 Apr 26 12:00 Confirmed
#B-819 Photoshoot Studio 2 Apr 27 14:00 Apr 27 17:00 Confirmed
#B-818 Workshop Hall Apr 28 09:00 Apr 28 13:00 Pending
#B-817 Studio rental Room A Apr 25 14:00 Apr 25 16:00 Cancelled

Comparison

Default Bookings admin vs SleekView

Default Bookings admin

  • Bookings list shows fixed columns — resource and product details aren't inline
  • Bulk status changes go one row at a time
  • Cross-resource availability filters aren't a saved view
  • Postmeta values (start, end, resource_id) hidden from the list
  • Per-customer booking history requires custom queries

SleekView

  • Pivot booking postmeta into proper columns
  • Filter by resource, product, and date range together
  • Inline-edit booking status (pending → confirmed → cancelled)
  • Join bookings with the parent wc_orders for payment status
  • Save views per resource owner or operations role

Features

What SleekView gives you for WooCommerce Bookings

Schedule-aware filters

Filter bookings by date range, resource, and status in one saved view. Useful for checking availability without leaving WP admin and for spotting the day's pending confirmations before the morning starts.

Postmeta as columns

Start, end, resource ID, person count, and customer details pivot from postmeta into named columns automatically. Each booking shows the full schedule context in one row.

Inline status edits

Confirm pending bookings or mark no-shows in place. Bulk-update across many bookings without per-row clicks; status hooks fire so reminder emails and resource releases happen as expected.

Audience

Who uses SleekView for WooCommerce Bookings

Booking ops

Daily schedule view with status, resource, and customer columns — confirm pending bookings inline before the day starts and mark no-shows in batch after.

Resource owners

Per-resource calendar filtered to active and upcoming bookings only. Spot conflicts and over-allocations without scrolling the global schedule.

Customer support

Per-customer booking history visible during chat or call. Sort by booking date to surface a customer's recent and upcoming bookings without jumping to the orders screen.

The bigger picture

Why bookings need a real schedule view

Bookings are time-shaped data and the default WordPress posts list isn't. A studio renting four rooms or a class operator running daily workshops thinks in terms of resource availability over a date range — which slots are filled, which are pending, which conflict. The data to answer those questions lives in wc_booking postmeta: start, end, resource_id, person count, status.

The default admin shows the bookings as a list and offers a calendar tab, but neither lets ops sort the daily schedule by resource and confirm a batch of pending bookings inline. With multiple resources running concurrently — three rooms, two photographers, four shift instructors — ops staff need a flat schedule that columns by resource and rows by booking, with status visible inline. SleekView's pivot delivers that.

Confirming a Saturday's pending workshop bookings, marking yesterday's no-shows, and spotting an over-allocated resource all happen in the same workspace, and the WooCommerce Bookings API still fires the same emails and resource-release logic that the default admin would.

Questions

Common questions about SleekView for WooCommerce Bookings

Yes. Bookable products are product CPT entries with bookings-specific postmeta — block-cost, base-cost, max-bookings-per-block — and resources are bookable_resource posts with their own metadata. SleekView can show either as a separate view, or join them to the booking entries for richer scheduling context.

 

Yes when SleekView uses WooCommerce Bookings' status-change API. The plugin's hooks for confirmation, cancellation, and reminder emails fire on each transition. Direct table writes skip hooks by design — useful for bulk migrations, but reach for the API path when you want emails to send.

 

Yes. Person count is stored as _booking_persons in postmeta and pivots into a numeric column. Filter to bookings of three or more for resource-capacity planning, or sort to find unusually large bookings that may need additional setup time.

 

Yes. Both plugins store data in posts and postmeta, and SleekView reads them together. Build a view that joins recurring bookings to their parent subscription for renewal-aware scheduling — useful for class passes, gym memberships, or any recurring booking model.

 

Yes. Save a view filtered by _booking_resource_id matching the resource(s) the user owns, and gate by capability. Each resource owner logs in and sees only their bookings — same data model, scoped per account.

 

SleekView is primarily tabular. It supports a kanban-style view grouped by date or resource for visual scheduling, which works well for daily and weekly views, but it's not a full month-grid calendar. The default WooCommerce Bookings calendar tab stays available for that visualisation.

 

Yes. Join wc_booking to the parent wc_orders via the order ID stored on the booking and filter to order-status pending or failed. That's your unpaid-bookings queue — the bookings that are confirmed in the schedule but haven't yet been paid for.

 

Blocked time slots in WooCommerce Bookings are stored as availability rules on the bookable product or resource. SleekView reads those as a separate view if needed, but the booking-schedule view itself focuses on confirmed/pending/cancelled customer bookings rather than the underlying availability windows.

 

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