Let’s clear the table.

Pace is designed for hospitality teams managing table bookings, menus and customer loyalty, from independent cafés to restaurants, pubs and bars. It is intended for teams that want a clearer operational view without stitching together several disconnected tools.

Pace brings the information behind a good service into one connected system. Teams can plan reservations, maintain menus and manage customer rewards from the back office, while guests get a clearer way to book, browse and keep track of their visits.

Both. Pace Core, Growth and Complete are priced per venue, while Pace Group is tailored to multiple sites, shared standards and the permissions or support model your organisation needs.

Pace focuses on the operational areas covered by the platform: bookings, tables, venue hours, menus and loyalty. During an initial conversation we can map those responsibilities against the tools you already use and identify a sensible starting point rather than assuming everything should change at once.

The visual diary brings reservations, times, guest counts, booking lengths and table assignments into one view. Your team can understand the shape of the service before guests arrive and review the same information during the shift.

Yes. Configure table numbers and seat capacities to reflect your floor, then assign tables to bookings. Availability can be reviewed against the selected date, time, party size and booking duration.

Yes. Opening hours and kitchen closing times can be configured for each day. The booking flow uses those rules so a reservation cannot begin after the kitchen has closed or run beyond the venue’s closing time.

Existing bookings remain visible so the team can review them rather than lose track of them. New booking availability follows the updated configuration, while the diary keeps the operational record available for follow-up.

The back office is designed for staff to review booking details, notes and dietary requirements, make updates and cancel reservations from the same service view.

The booking flow supports configurable guest options and larger party sizes. The right table and service rules can be discussed during setup so the configuration reflects how your venue handles larger groups.

Teams can organise menus into sections, maintain dish names and descriptions, update prices, manage availability and keep dietary information alongside the catalogue.

Yes. Menu sections and dishes can be maintained as your offer changes. Pace gives the team one place to keep the information behind the customer-facing menu organised and current.

Availability can be managed in the back office so your team has a consistent source for what is currently offered. Service messages and unavailable items can also be maintained where your configuration needs them.

No. Dietary labels support communication, but staff should always confirm specific allergy requirements with the kitchen and follow the venue’s own food-safety procedures.

The platform supports menu service periods and categories, so menus can be organised around the way your venue serves different offers during the day.

Create a single-use reward worth 0–1,000 points, choose an expiry date and download its QR code. You can also add points to an existing customer account manually when a reason is recorded.

Each manual credit requires a reason and updates the customer balance and loyalty ledger. This gives your team a history of what changed rather than leaving points unexplained.

Yes. Reward expiry defaults to three calendar months and can be changed when a code is created. Expiry applies to an unclaimed reward code, not points that have already been credited to a customer.

No. The system is designed to enforce single use and expiry when a reward is claimed. Viewing or downloading a QR code does not consume it.

Yes. Individual rewards can be created within the current 0–1,000 point range, allowing the team to match the gesture to the occasion or campaign.

The data model and reward rules support customer redemption, but customer app scanning and the staff code-entry screen are planned for a later update. Manual points credits are available now.

The guest experience is designed to let customers book a visit, choose an experience, browse menus, keep booking details close, view upcoming visits, manage profile preferences and stay connected to loyalty points and rewards.

The app and back office are two sides of the same service journey. Venue configuration, opening hours, menu information, bookings and loyalty data provide the operational foundation for the guest-facing experience.

Yes. Upcoming visits are presented as part of the guest experience, making dates, times and booking details easier to find than searching through old messages.

The app experience is designed to keep profile preferences and dietary needs available to support more relevant bookings and conversations. Venue teams should still confirm specific requirements with the kitchen.

The app is designed around venue content and configuration, including menus, events, rewards and venue details. A rollout conversation can establish the appropriate branding and content requirements.

Staff with customer access can search by name, email, phone or booking reference, then review contact details, visits, loyalty activity, notes, preferences, tags and marketing consent in one chronological profile.

Yes. Segments can combine visit count, recency, loyalty points, tags and dietary preferences. A consent-aware preview separates eligible, suppressed and unreachable customers and explains why each matching guest was included.

Yes. Booking access can be set to none, read or write. Customer access, rewards and each configuration area can be assigned separately to staff accounts. Administrators have full access.

No. A user who can manage accounts cannot give another person access to functions beyond their own permissions.

Yes. A rewards setting hides rewards in both the back office and guest app when disabled, while keeping existing reward data.

Pace Core is £79, Growth £139 and Complete £199 per venue per month before VAT. Introductory monthly prices apply for the first three months; Pace Group is quoted for your rollout. Setup and onboarding may be quoted separately.

Pace Core covers bookings, tables, hours and menus. Growth adds customer management, loyalty points and rewards. Complete adds the customer-facing Pace mobile app. Group is for multi-venue rollouts.

The timeline depends on the number of venues, the information you want to bring across and how your team works today. We can define a practical first phase and identify the configuration needed before launch.

Pace is designed for hospitality teams, not specialist developers. The important setup decisions are operational: your tables, service hours, menus, permissions and reward approach.

Yes. A focused rollout can begin with the area that creates the most friction, such as the booking diary or menu administration, then expand as the team is comfortable.

Support and rollout expectations are part of the initial conversation. We can discuss setup guidance, team onboarding and the level of ongoing help appropriate for your venue or group.

No. The marketing site is separate from venue operations. The contact form collects the details you choose to submit so the Pace team can respond to your enquiry.

Start by describing your current booking, menu and loyalty workflow, where staff lose time and what guests struggle to find. We can then map the relevant Pace capabilities to that process.

The marketing site includes product views and app screens, and a product conversation can walk through the relevant workflows in more detail.

The product is being developed in stages. Customer app scanning and the staff reward code-entry screen are planned for a later update; current capabilities are described on the platform and feature pages.

Use the contact form to share your venue, role and the workflow you want to improve. A clear description helps us make the first conversation useful.