Skip to content
All products
02BookingsProduct overview

One request. One operating record.

The whole visit. On one record.

Run table service, bookable activities and private events on the same availability, guest and order records. Take the visit from first enquiry to the final bill.

In the product today

Table plans, resources, multi-part visits, private-event sales, menus, pre-orders, Email Studio, guest self-service, booking invoices and reviewed ResDiary CSV imports. Online payments and email delivery require configured providers.

See what’s next

More of the work, connected.

See what you can get done.

Email Studio

Your booking emails. Your house style.

Give confirmations, held-space offers, pre-order messages, approved booking replies and invoice-copy emails a consistent branded layout.

  • Edit the design and preview it with sample booking details.
  • Keep booking facts and essential action links protected.

Connected email journeys use the saved design. Delivery still needs a configured sender; editing a template does not send an email.

Read the guide
Email StudioFictional example
House coloursLogo & copyBooking details
Fictional confirmation design. No message is sent.

Multi-part visits

One visit. More than one booking.

Let guests build a configured visit with activities, a table, menus and extras, then check and hold the parts together on one order.

  • Offer sequential parts that fit the venue’s resources and opening hours.
  • Keep the itinerary and guest choices together for the team.

Available combinations depend on your configured resources and availability. Guests still confirm their selection and complete checkout.

Read the guide
Multi-part visitsFictional example
Saturday together6 friends. One plan.
  1. Games firstActivity space · 60 minutes
  2. Dinner nextTable for six · menu choices attached
Availability checked togetherTwo parts · one order · one guest contact
A fictional visit with two sequential booking parts.

Menus & pre-orders

Turn a PDF menu into a draft, review the dishes and publish when it is ready. Collect each guest’s choices before they arrive.

  • Organise courses, choices, dietary markers and allergen declarations.
  • Bring pre-orders together and print the results for service.

Imported wording and allergens need your review. Publishing a menu is a separate action.

Read the guide
Menus & pre-ordersFictional example
THE DINNER MENUChosen before they arrive.
  • Roast chickenMain course
    18
  • Mushroom risottoMain course
    10
  • Choices outstandingKeep track before service
    4 guests
Guest choices, kept togetherReview dietary requirements before service.
Fictional pre-orders for a group dinner.

Move from ResDiary

Bring the history. Keep the context.

Use reviewed CSV imports to bring bookings across, map source tables to your floor plan and keep the history useful.

  • Match source venues and tables before committing the import.
  • Review repeat exports and conflicts while preserving local changes.

A reviewed import workflow, not a live ResDiary connection. Source exports, mapping and cutover need preparation.

Read the guide
Move from ResDiaryFictional example
Source exportSoupy floor plan
  • Restaurant / T01Dining room / Table 1
  • Restaurant / T02Dining room / Table 2
  • Private / P01Private dining / Table 1
Review changes before importConflicts stay visible. Local edits stay protected.
Fictional source-to-floor-plan mapping.
Explore the workspaceApp preview

The Bookings running order, with guest, cover, area, service and readiness details. Filter by area or switch to the resource timeline.

Current workspace layouts with sample data. Nothing is saved or sent.

Product preview · sample data
MD
Example Hospitality Ltd. / Demo venue / Bookings

Bookings

Live running order across every bookable area.

Friday, 23 October 2026Sample day
4
bookings
15
covers
0
held
Demo venue
Service brief2 expected · 1 arrived · 1 seatedView demand
Arrivals

First booking at 18:00. 15 covers across two areas.

Manager checks

Review payment on arrival and guest notes before service.

18:00to 19:30
4Main bar

Table 08 · Demo venue

Paid · Preorder completeDinner before the show
Expected

£40.00

Booking

18:30to 20:00
2The Workshop

Table 12 · Demo venue

Due on arrivalWindow table
Arrived

£20.00

Booking

19:00to 21:00
6Main bar

Tables 05 + 06 · Demo venue

Paid · Preorder completeBirthday booking
Seated

£60.00

Booking

19:30to 21:00
3The Workshop

Table 14 · Demo venue

Not required
Expected

£0.00

Booking

Showing 4 of 4 bookingsSorted by start time

Explore the current Bookings layout with fictional records. Search, switch views and try both themes. Nothing is saved, sent or charged.

On the other side of the shift

Less friction. More getting on with it.

  1. 01

    Sell the visit against real spaces, resources and capacity.

  2. 02

    Keep enquiries, confirmed visits and service progress in view.

  3. 03

    Carry menus, guest choices, invoices and payments beside the booking.

What’s included

Made for the job.

The practical details behind the promise. Built around the people doing the work, and connected to the information they need.

  1. 01

    Spaces, resources and capacity

    Publish table plans, approved joins, bookable resources and shared capacity. Availability respects operating hours, duration and setup buffers.

  2. 02

    The whole visit, bookable

    Offer guided booking widgets with activities, extras and sequential parts in one venue. Check and hold the configured visit together on one order.

  3. 03

    Service and guest self-service

    Manage the running order, walk-ins, waiting lists, arrivals and departures. Secure guest links support permitted changes, cancellation and rebooking.

  4. 04

    Private events and group business

    Take an enquiry through availability, an option hold, a proposal, a signed contract and required payments. Publish a versioned function sheet for the team.

  5. 05

    Menus, Email Studio and money

    Import a PDF menu into a reviewable draft, collect guest pre-orders and design branded booking emails in Email Studio. Keep invoices, payment links and refunds attached to the visit.

More of the working product

What you can do with Bookings.

Explore the tools behind the overview, then open a workflow for the steps, settings and availability that apply. Product access, rollout and connected providers determine what your workspace can use.

Service views

  • Follow the day’s running order.
  • See bookings against resources on a timeline.
  • Review occupancy on the table plan and reassign bookings explicitly.

Venue inventory

  • Organise Spaces, nested Areas and bookable resources.
  • Reuse inherited defaults and identify tables by number.
  • Save named layouts and approve connected table joins.

Booking journey

  • Set operating hours, buffers and closures.
  • Guide guests through a visit with several parts and extras.
  • Publish booking widgets and offer secure guest self-service.

Private events

  • Move enquiries through options and proposals.
  • Keep versioned agreements and payments together.
  • Publish function sheets for the team.

Menus and guest choices

  • Turn a PDF menu into a draft for review.
  • Offer choices with dietary and allergen information.
  • Collect each guest’s pre-order and print the results.

Email Studio

  • Design branded layouts for connected outgoing booking emails.
  • Preview confirmations, held-space offers and pre-order messages with sample details.
  • Keep required booking facts and action links protected while editing the design.

Connected journeys use saved designs. Email delivery requires a configured sender; template editing does not send messages.

Move from ResDiary

  • Map source venues and tables to the existing Soupy floor plan.
  • Review booking history from CSV exports before import.
  • Reconcile repeat imports and conflicts while retaining local changes.

Reviewed imports, not live sync. Source exports, mapping and cutover need preparation.

Financial/service evidence

  • Keep invoices and payment links with the booking.
  • Review invoice issue, voids and replacements, and report by sales category.
  • Retain accessibility notes, communications and reviewed historical booking records.

Payment, card-security and provider-dependent features require setup and rollout. Historical import and report availability follow the selected venue and source permissions.

Explore every workflow in the guides.

Choose a guide to see all its topics. The detailed guides include setup requirements, preview features and supported limits.

Bookings, resources and private events13 workflow topics
Menus, PDF import and pre-orders4 workflow topics
Orders, Payments, refunds and financial evidence9 workflow topics
Contracts and private signing5 workflow topics

Part of the bigger picture

The context comes with it.

The guest, the venue, the team. Useful information should follow the work. Bookings connects to shared records, with access controlled for your organisation and your people.

Bookings
Shared recordsCustomersVenuesPayments

A clear picture

Today. And what’s next.

Available today

Table plans, resources, multi-part visits, private-event sales, menus, pre-orders, Email Studio, guest self-service, booking invoices and reviewed ResDiary CSV imports. Online payments and email delivery require configured providers.

Product direction

Guests can build configured multi-part visits today. Automatic itinerary optimisation remains direction; the optional booking assistant proposes an editable draft and leaves reservation and payment to the guest’s checkout.

Good questions

Bookings FAQs.

What can be booked in Soupy?

Tables, rooms, activities and other configured resources, including shared-capacity sessions and approved combinations. Private-event enquiries use the same availability and booking records.

How are paid bookings confirmed?

Soupy keeps the reservation and order together, and confirms the booking after the required payment succeeds. Payment collection requires a configured provider.

How does Bookings connect to other products?

It shares the customer, venue, order and payment context with CRM, Loyalty, Ticketing and Automation.

Can guests book more than one activity?

Yes. A published widget can offer up to six sequential parts at one venue, with one seller and currency. Guests review the complete visit before checkout; automatic itinerary optimisation is separate future work.

Start with the pressure point

Put Bookings on the same system.

Try Bookings