🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!
🚨 Last Chance for the All Access Pass 🚨 Going away on 01.08.2026. Don't miss out!

SleekView for WPCafe: menu items, orders & reservations as tables

Read WPCafe's reservation post type plus the WooCommerce orders that back food ordering. Sort, filter, and inline-edit reservation status, table number, and party size from one screen.

♾️ Lifetime License available

SleekView table view for WPCafe

Reservations and orders on one screen

WPCafe runs on a hybrid storage model: menu items are WooCommerce products (product post type), food orders flow through WooCommerce checkout into wc_orders (or the legacy shop_order post type), and table reservations are a separate WPCafe-registered post type with booking date, time, party size, and table assignment in postmeta. Three storage layers, three default admin screens, no joined view.

SleekView builds one tabbed page with menu, food orders, and reservations as separate views over the same shared data layer SleekView already understands for WooCommerce. The reservations view pivots party size, time, table assignment, and location into proper columns — useful when a saved "tonight's dinner service" filter needs to cover all three dimensions at once.

Inline-confirm of pending reservations is the most common WPCafe operational task. Bulk-flip from pending to confirmed via the standard WordPress update hooks fires WPCafe's confirmation emails normally, and the connected QR-code table assignments stay intact. Multi-location installs (Pro feature) get an extra location filter, with each branch's reservations and orders scoped per saved view.

Workflow

Restaurant data across three storage layers

1

Wire all three views

Reservations from the WPCafe post type, food orders from WooCommerce wc_orders, menu items from product with a WPCafe-product filter. Each becomes a tab on one page.
2

Pivot reservation meta

Date, time, party size, table assignment, location, and special requests sit in postmeta. Pivot them into columns so floor managers see everything at a glance.
3

Add service-window filters

Lunch versus dinner service is a time-of-day filter on the date column. Save "tonight's dinner" or "this weekend's bookings" as the recurring views the floor team relies on.
4

Inline-confirm with emails

Bulk pending-to-confirmed in one pass. WPCafe's confirmation emails fire through standard update hooks; QR-code table assignments stay intact across the change.

Sample columns

A typical WPCafe reservations view

SleekView reads reservations from wp_posts and pulls food orders from WooCommerce HPOS tables.
Source: wp_posts (wpc_reservation, product) + wp_wc_orders
Reservation # Name Party Date Time Status
#410 Alex Park 4 Apr 26 19:00 Confirmed
#409 Ria Holm 2 Apr 26 20:30 Pending
#408 Tom Vega 6 Apr 27 13:00 Confirmed
#407 Mia Joro 3 Apr 28 19:30 Cancelled

Comparison

Default WPCafe admin vs SleekView

Default WPCafe admin

  • Reservations and orders are separate screens — no joined view
  • Confirming pending reservations is one-at-a-time
  • Reservation list filters are limited; party-size and time-window filtering needs custom work
  • Menu items live as WooCommerce products but the WPCafe-specific meta isn't surfaced
  • Multi-location filtering (Pro feature) isn't always exposed in the row list

SleekView

  • Reservations, food orders, and menu items in one tabbed view
  • Inline-confirm reservations in bulk by date or location
  • Filter by date range, party size, location, and status together
  • Surface QR-code table assignments as columns
  • Reuse the same WooCommerce HPOS reading SleekView already does for orders

Features

What SleekView gives you for WPCafe

Service-window filtering

Filter reservations by service (lunch vs dinner) and date range. Pull tonight's bookings sorted by time without scrolling through the dashboard or calendar view.

Inline-confirm pending reservations

Switch from pending to confirmed in bulk. Send the customer a confirmation email through WPCafe's normal hooks — no manual emailing.

Multi-location views

If you run a chain, filter reservations and orders per branch, or build one view per location with the right table assignments visible for each.

Audience

Who uses SleekView for WPCafe

Floor managers

Tonight's bookings sorted by time, party size visible, table assignments inline. Confirm in bulk before service starts and the dining room is ready when guests arrive.

Owners

Confirmed orders for the day with totals, payment method, and delivery vs pickup visible — no opening each WooCommerce order during the lunch rush.

Multi-branch ops

Filter reservations and orders by location for franchise-level reporting, with each branch's view saved separately and scoped to that location's table layout.

The bigger picture

Why restaurants need joined reservations and orders

Restaurants running on WordPress live across two operational rhythms: the reservation rhythm (pending bookings to confirm before service starts, tonight's seating, tomorrow's holds) and the order rhythm (food orders coming through delivery, pickup, and QR-code table ordering). WPCafe handles both, but stores them separately — reservations as a custom post type, orders as WooCommerce orders. The default admin reflects that storage split: two screens, two filter sets, two mental contexts.

Floor managers compensate by keeping a paper notebook for the night's bookings and a separate window open for the WooCommerce order list. The data is fully present in WordPress; the surface that joins it isn't. A tabbed view that covers both — same data, two perspectives, one URL — turns the floor manager's job from window-juggling into actual service management.

The same tab structure scales to multi-location chains, where the location filter becomes the first dimension every saved view filters on.

Questions

Common questions about SleekView for WPCafe

Menu items are WooCommerce products (product post type). Food orders run through WooCommerce checkout into wc_orders on HPOS or shop_order on legacy storage. Table reservations are a separate WPCafe post type with the booking date, time, party size, and table assignment in postmeta. Three layers, all readable through SleekView.

 

Yes. Build a tabbed SleekView page with WooCommerce Orders as one tab and WPCafe Reservations as another. Both update in real time and share the same admin surface, so floor managers don't need to switch screens during service.

 

Yes. SleekView writes through WordPress's update hooks, so WPCafe's reservation-status emails (confirmation, cancellation, reminder) fire as expected. Bulk-confirming twenty pending bookings sends twenty confirmation emails just as if each had been confirmed individually through the editor.

 

Yes. The visual layout is a UI on top of the same reservation data. SleekView reads the table assignment as a column and displays it next to party size and time. The visual editor remains the right tool for designing the floor plan; SleekView is the right tool for the per-shift operational table.

 

Yes. WPCafe Pro stores branch ID as taxonomy or meta on reservations and products. SleekView treats it as a filterable column so each manager can scope to their branch, and corporate operations can build network-wide views across all locations from a single page.

 

QR orders are still WooCommerce orders. SleekView reads them through the same WooCommerce HPOS path. Add a column showing whether an order originated from QR or web checkout — useful for measuring in-restaurant adoption of the QR menu after a soft-launch.

 

Yes, indirectly. The reservation status set after the booking time gives the signal — "completed" versus "no-show" if you've configured WPCafe to use that status, or just "confirmed but past" if you haven't. Filter by status and date range to spot patterns by day-of-week or service window.

 

If WPCafe is configured to take deposits through WooCommerce, the deposit becomes a WooCommerce order linked to the reservation. SleekView surfaces both — the reservation row shows deposit-paid status; the order row shows the actual transaction. Useful for finance reconciliation against deposit liability accounts.

 

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 🎁

💎 Want everything forever? The All Access Pass is going away on 01.08.2026.

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