How it works
Stampede runs the whole diary from one model. A booking is a party, a time and a set of tables, and every reservation writes back to the guest profile.
Only real slots.
Opening hours, turn times and table capacity decide what a guest can even see.
The booking lands.
A party, a start and end time, and the tables it occupies. One model for the whole diary.
It writes back.
Made, seated or cancelled, the booking publishes an event that enriches the guest profile.
When you'd use it
Read this first. It explains how the pieces fit together before you configure booking types, tables or charges on the pages that follow.
How it behaves
A booking is the single unit of the diary: a party size, a start and end time, and the tables it occupies. Everything else configures how bookings are made, priced and seated.
Availability is worked out live from your opening hours, turn times and table capacities, so guests only ever see slots you can actually seat. When a booking is made, changed, seated or cancelled it publishes an event in real time, which is what lets a reservation enrich the guest profile and trigger follow-ups.
The moving parts
- Availability and turn times
- Slots computed from hours, durations, turn times and capacity.
- Booking type or event
- Everyday services, plus dated events that can sell tickets.
- Tables, areas and combinations
- The room the diary seats bookings onto.
- Deposits and charges
- Deposits or cancellation charges that protect covers.
- Walk-ins, waitlist and enquiries
- The intake paths for guests who do not book online.
Good to know
A guest books either a booking type or an event, never both on the same booking.
Reservations are unlimited, with no per-cover commission.