Product documentation
How TablePace fits together
Understand the few building blocks that connect online bookings, tables, service and venue operations.
TablePace works best when you think of it as one connected venue model rather than a collection of separate screens.
Venue
Your venue holds its timezone, currency, team access, integrations and communications settings.
Services and capacity
A service describes when you take bookings and how much demand you want to accept. It can include table time, booking and cover limits, pacing rules and one-off exceptions.
Floorplan
The floorplan describes where guests can sit. Every table has a real seated capacity. Published floorplans can be used for automatic assignment and live Service Mode.
Booking widget
The widget is the guest-facing booking path. It uses your live service rules and available seating rather than offering times from a separate calendar.
Bookings and guest profiles
A booking carries the date, time, party size, guest details and current service status. TablePace also keeps useful guest context such as occasions, notes and venue-level guest flags.
Service Mode
Service Mode turns the published floorplan and today's bookings into a live operating view. It is where arrivals, seating, table moves, walk-ins and waitlist activity come together.
Operations
Operations covers the back-of-house information that affects profitability and preparation: suppliers, ingredients, purchase costs, recipes, menu costing and prep lists.
Integrations
Integrations bring useful external information into TablePace. The current Square connection is read-only: TablePace can use sales context without changing your Square payments, orders or catalog.
The important idea is that these parts share the same venue. A capacity change affects online availability. A floorplan change affects table assignment. A booking update appears in Service Mode. That is why accurate setup matters.