Skip to content

The hospitality operating system

One operating system for every part of your venue.

A full house. A clear head.

Ticketing, bookings, people and venue operations. Connected around the same guests, places and orders.

Made in Belfast.Built for the beautiful chaos of hospitality.
The friendly Soupy team welcomes guests and runs a smooth service around a neatly set table, doorway and stage.
For the people behind a great night.
VenuesBars & restaurantsEvents & groups

For your kind of busy

Step into your world.

Explore all business types

Five kinds of venue. Useful product examples and calculators for each. Venue imagery is illustrative.

01 / The whole night, together

Hospitality moves fast.
Keep the thread.

The table booking. The ticket. The message asking about dinner. Soupy gives each job a proper home, with the useful context already there.

One night. Connected.SOUPY / 001
Everything
has its place.
Tonight’s operationExample venue
Bookings18:30
Dinner before the showConfirmed
Sarah Hughes4 guestsTable 08Main bar18:30–20:0090 minutes
Ticketing / Friday nightGood company.
Great comedy.
Sarah Hughes 2 tickets
20:00Doors open
SHOne guest record.The booking. The order. The next visit.
Illustrative recordsReal product connections
  1. 01

    Before the doors

    Make a night of it.

    Publish the event, book the talent and plan the visit. Tickets, tables, menus and guest choices stay connected.

    Ticketing · Bookings · Talent
  2. 02

    Before the rush

    Get everyone ready.

    Build the rota, share the hand-over and put the right people in the right places.

    People · Rotas · Messages
  3. 03

    In the thick of it

    Keep service moving.

    Check tickets at the door. Track arrivals and service. Pick up the guest conversation with the booking beside it.

    Check-in · Bookings · Inbox
  4. 04

    After the last call

    Remember what matters.

    Keep the visit in the customer history, reward eligible purchases and reconcile stock against sales evidence.

    CRM · Loyalty · Supply
Different jobs. Shared records.Guests · Orders · Places · People · Permissions

03 / Make it your Soupy

Start with the thing
you need most.

A single venue or a whole group. Choose the products that earn their place in your operation, and add more when you need them.

22 product families. Preview modules are labelled.

Compare the products

Soupy Assistant / Built into your workspace

Ask about the work.
Stay in charge of it.

Find the booking. Check the night’s ticket sales. Ask what needs attention. Soupy Assistant works with the records you’re allowed to see and links you back to the source.

For supported bookings and event drafts, review the proposed details, ask for changes and confirm when they’re right. Your team makes the decision.

Explore connected Bookings
From a request to a reviewed actionExample workflow
  1. 01
    Describe what you need.

    “A table for four on Friday at 7pm.” Missing details are clarified first.

  2. 02
    Review the suggestion.

    Check the guest, resource, date, time and price. Edit or cancel before confirming.

  3. 03
    Confirm the exact details.

    Soupy rechecks your access and availability before creating the booking.

Available where Assistant is enabled. Booking creation supports same-day, single-resource bookings that are free or paid on arrival. Event creation saves an unpublished draft.

Connected, with boundaries

Your operation.
Your rules.

The right context is useful. The right access is essential. Soupy connects the work while keeping each organisation, team member and payment account in its proper place.

Take a look around
01

Start small. Stay connected.

Use the products you need. Add the next without starting your customer records again.

02

Give people the right access.

Roles and permissions keep the work with the people responsible for it.

03

Keep a person in control.

Review AI reply drafts and proposed actions. Your team decides what gets sent or approved.

Connected records. Deliberate decisions.

Ready when your venue is

Your stack was soup anyway. It may as well be good soup.