SleekView for WCFM Bookings: vendor bookings as tables
WCFM Bookings adds appointment-style products to WCFM vendors, with bookings, time slots, and availability stored across booking posts and meta. SleekView reads them as a vendor-scoped schedule operators can sort, filter, and edit inline.
♾️ Lifetime License available
Bookings across vendors, in one schedule
WCFM Bookings is built on WooCommerce Bookings and exposes appointment-style products to WCFM vendors. Bookings live as wc_booking posts with start/end timestamps, resource references, and vendor (author) context. The default admin lists bookings per vendor through the front-end manager, but the marketplace operator's view across all vendors is limited.
SleekView reads wc_booking posts joined with vendor users and source orders. A row shows vendor, service, customer, start/end time, resource, and status side by side. Operators scope to a date range, filter by vendor or service, sort by start time, and surface bookings without resource assignment for follow-up. Cancellations, rescheduling, and resource assignment edit inline.
Where bookings use WooCommerce Bookings' resources or persons fields, those are first-class columns. Where availability is stored in wp_woocommerce_bookings_availability, SleekView reads it for a per-vendor availability view useful for spotting double-bookings or empty days.
Workflow
From per-vendor calendars to one schedule
Read booking posts
wc_booking joined with wp_users for vendor and wc_orders for the source order. Availability tables are in scope too.
Compose columns
Save views
Edit inline
Sample columns
A typical bookings view across vendors
wp_posts (post_type=wc_booking) + wp_postmeta + wp_woocommerce_bookings_availability + wp_users (vendor)
| Booking | Vendor | Customer | Start | Resource | Status |
|---|---|---|---|---|---|
| #B-4128 | Atlas Studio | alex@studio.co | May 18, 10:00 | Room 1 | Confirmed |
| #B-4129 | Riverside Workshop | ria@design.io | May 18, 14:00 | Trainer A | Pending |
| #B-4130 | Maker Den | tom@hello.dev | May 19, 11:00 | Unassigned | No resource |
| #B-4115 | Old Lane Goods | mia@brew.coop | May 12, 09:00 | Room 2 | Cancelled |
Comparison
Default WCFM Bookings admin vs SleekView
Default WCFM Bookings admin
- Cross-vendor schedule view isn't part of the default admin
- Unassigned-resource bookings require checking each booking
- Availability is configured per product, no consolidated view
- Bulk-reschedule for a shift change isn't supported
- Customer email and order number aren't side by side
SleekView
-
Read
wc_bookingposts joined with vendor users and orders - Spot unassigned resources via a saved filter
- Filter bookings by vendor, service, status, and date range together
- Inline reschedule and resource assignment via WooCommerce Bookings APIs
- Switch between table and kanban (by status) on the same query
Features
What SleekView gives you for WCFM Bookings
Cross-vendor schedule
Today's and tomorrow's bookings across all vendors with customer and resource inline. The marketplace operator sees the whole day at a glance instead of per-vendor screens.
Resource triage
Saved view scoped to bookings without resource assignment, sorted by start time. Operations sweeps it daily and assigns inline before customers notice.
Bulk reschedule
Cancel or shift a set of bookings (vendor outage, room closure) in one action. WooCommerce Bookings' notification emails fire for each affected customer.
Audience
Who uses SleekView for WCFM Bookings
Marketplace ops
Whole-day booking view across vendors, with unassigned resources and pending confirmations surfaced for action.
Vendor managers
Per-vendor occupancy and cancellation rate over a rolling window, useful for spotting vendors with capacity issues or service quality problems.
Customer support
Customer-scoped booking lookup with vendor, time, resource, and order in one row, so support handles reschedule requests in one screen.
The bigger picture
Why bookings marketplaces need a shared schedule
Bookings marketplaces (gyms, studios, salons, professional services) share a data shape: vendors offer services with availability, customers book slots, and operators sit between them making sure things actually happen. The data sits in wc_booking posts with vendor authorship and time-range fields, which is exactly what a relational scheduling system needs. The trouble is that vendor-side admin (the WCFM Frontend Manager) handles each vendor's view and the marketplace operator's role is left without a consolidated view that the same data fully supports.
SleekView builds that consolidated view as a saved query over the existing tables. The marketplace operator scopes the day across vendors. The vendor manager watches occupancy and cancellation patterns per vendor.
Customer support pulls a customer's booking history in one row. The data has been there since the booking was created and the plugin still owns every write. The missing piece was a list interface, and adding one shifts a bookings marketplace from running on per-vendor calendars to running on a real shared schedule that scales with the marketplace.
Questions
Common questions about SleekView for WCFM Bookings
Yes. WCFM Bookings extends WooCommerce Bookings for vendor use and keeps the same wc_booking post type and meta keys. SleekView reads those directly and adds the vendor join.
Yes. Reschedule, cancel, and resource assignment write through WooCommerce Bookings' CRUD layer, so notification emails fire and availability recalculates. Bulk operations run the same hooks per row.
Availability blocks for the booked product live in wp_woocommerce_bookings_availability and surface in SleekView as a related view. Useful for spotting per-vendor availability gaps or accidental double-bookings.
Both fields are on the booking record. SleekView shows resource and persons as separate columns where the vendor's product uses both, and the filter combines them so a 'two-person, room-A' search is one click.
Yes. Vendor scoping in WCFM uses the booking post author. SleekView joins authors with the wcfm_vendor role so per-vendor views are a saved filter, not a manual query.
Yes. Occupancy is bookings divided by available slots over a window. SleekView computes the ratio in a derived column, useful for vendor reviews or for spotting under-used capacity worth promoting.
Cancellation reason is typically captured as booking meta. SleekView surfaces it as a column and a filter, so reviewing cancellation patterns per vendor or per service becomes a saved view instead of a report build.
Booking queries hit indexed columns (post status, vendor author, start timestamp). Marketplaces with tens of thousands of bookings still see sub-second load times on the cross-vendor view.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Woocommerce Additional Variation Images
- Woocommerce Composite Products
- Woocommerce Stock Manager
- Woocommerce Name Your Price
- Woocommerce Product Bundles
- Presta Shop Bridge
- Woocommerce Australia Post Pro
- Dokan
- Edd Frontend Submissions
- Woocommerce Quote Request
- Woocommerce
- Woocommerce Warehouse Management
- Woocommerce Product Search
- Woocommerce Dpd Shipping
- Woocommerce Deutsche Post