Restaurant Reservations Pro stores each booking as a rtb-booking-style custom post with party size, table assignment, service time, deposit amount, and customer details in wp_postmeta. Service definitions and table layouts are configured through the plugin's settings, and notifications fire on status changes.

The default admin lists bookings with fixed columns and a calendar. Service-by-service grouping, deposit reconciliation, and bulk confirmations all require opening individual records because party size, table, and deposit live in postmeta rather than as first-class columns.

SleekView reads the booking CPT directly, pivots the postmeta into named columns, and joins to the configured table and service settings. Status, table, and deposit-paid columns become inline-editable, and the host stand runs each service from one filterable grid.

Restaurants live or die on their service planning, and the data to plan a service well is already in Restaurant Reservations Pro's database. Each rtb-booking carries party size, table, deposit, and service time. The default admin shows them as a list and a calendar, but neither layout matches the way a host stand actually works.

The morning brief wants covers per service, deposits per booking, and a pending-list to chase. The host stand wants a flat grid for the night, with table and party visible and walk-in reseats one click away. Finance wants a deposit reconciliation by week, and owners want to know which services are running hot.

SleekView pivots the postmeta into typed columns, joins the table layout for friendly labels, and surfaces deposit and status as inline-editable cells. The result is a working tool for each role, built on the data Restaurant Reservations Pro already keeps.