By restaurant type · Michelin-star restaurant

Know the guest before they arrive.

A restaurant management system built for high-touch service — guest history, spend, and allergens on one record, and deposits held to the cover. Every service shift shaped to the room’s own rules.

Built by operators who ran two Michelin Guide restaurants.

A regular should never feel newly met.

Service and policy

Service shifts shaped to the room’s rules.

Fine dining rarely runs one rule for every night. Each service can carry its own covers, pacing, deposits, and cancellation terms.

Build the shift

Set covers, pacing, turn times, and seatings for each service individually.

Cancellation policy

Define the window and the charge per service, applied automatically when a guest cancels late.

Deposit and no-show cover

Hold a deposit or card on the cover, captured only against the policy. The deposit sits on the guest record.

On one record

Deposits and policy, held to the cover.

UK-14
allergens carried on every guest record, shown to the floor and the pass, and sent to the kitchen with every order.
£100
a typical deposit held against the cover, captured only against the cancellation policy
1.4% + 20p
on standard UK cards, with no per-cover fee on the booking

Questions

Common questions.

Does the system store guest allergens?

Yes. The UK-14 allergens are captured at booking and shown to the floor and the kitchen on the guest record, alongside dietary and occasion notes.

Can a deposit be required for some services and not others?

Deposits and card holds are set per service shift, so a Saturday dinner can carry a deposit while a weekday lunch does not.

How are cancellation policies enforced?

Each service carries its own window and charge. A late cancellation applies the charge to the card held against the cover, automatically.

Can each service shift be configured individually?

Yes. Each service shift is configured individually, with its own covers, pacing, seatings, deposits, and cancellation rules — built around what is needed.

See it run against a real service.

A short walkthrough with the guest record, deposits, and service shifts on one system — and the current vendor stack totalled alongside.