SOUPY FOR BARS
A full bar.A clear head.
The big booking. The regulars. The Friday that turns into Saturday. Bring the people, plans and moving parts of your bar together.
Your kind of venue. Your kind of Soupy.
In the product today
THE PEOPLE BEHIND A GREAT NIGHT
The atmosphere is yours. Keep the operation together.
A table of twelve is more than a reservation. It is a conversation, a plan for the team and a reason to come back. Soupy keeps the useful context with the work, from the first enquiry to the next visit.
Meet the products behind it
A LITTLE LESS EXPLAINING. A LITTLE MORE EXPLORING.
Give it a go.
Step through a fictional night. The controls change this example; they never create bookings, send messages or take payment.
The main bar · Interactive example
One booking. A whole night around it.
Move through Friday and follow the same group from enquiry to guest history.
“There are eight of us for Sarah’s birthday. Could we have a table at seven?”
- Guest
- Sarah Hughes
- Party
- 8 guests · 19:00–21:00
- Note for service
- Birthday group · main bar
The conversation gives the booking context. An operator reviews the reply and booking before confirming.
Explore the shared InboxFirst arrivals selected. Sarah’s example booking stays connected.
Fictional records. Try the controls freely: nothing is booked, sent or charged.
THE RIGHT PRODUCTS FOR YOUR OPERATION
Start with what
earns its place.
A connected system. A practical starting point for bars. Enable the products you need, then build from there.
Bookings
Put tables, groups and private occasions on a running order the team can use.
Explore BookingsCRM
Recognise the guest and their history. Follow up where you have permission.
Explore CRMLoyalty
Give regulars a reason to return with your configured earning and reward rules.
Explore LoyaltyAnd the work
around it.
Products are enabled separately. Availability follows your workspace, permissions and provider setup.
A little less guesswork
Put your numbers
to work.
Change the assumptions. Watch the result. See what a different week could look like, on your terms.
Give the quiet sessions a job.
Choose a few quieter sessions. See what a different guest count or spend would mean for those sessions.
How this is calculated
Weekly sales = sessions per week × guests per session × average spend per guest.
These are sales in the selected sessions, before tax and costs. Additional visits are your assumption, not a forecast of what Soupy will deliver. This does not model the rest of your trading week.
Give the hours back to the room.
Model the time your team spends on recurring work. Use totals for all your sites combined, and keep each task distinct.
Use the hourly employment cost you want to value, including any employer costs. No employment or wage rates are assumed.
What does your current software cost?
Optional. List each tool once, using its monthly cost across all your sites. For an annual bill, enter the monthly equivalent.
Current spending only. This does not assume Soupy replaces any tool or predict a saving. Kept separate from staff time and venue economics.
How this is calculated
Weekly time = task frequency × people involved × minutes per task ÷ 60, summed across the listed tasks. Time released = baseline hours − scenario hours. Annual time value = hours released × hourly cost × operating weeks.
Time value is not cash saved, a staffing reduction or a promise of what Soupy will deliver. A longer scenario takes more time and produces a negative result. Do not count the same work in two tasks. This result stays separate from venue sales and contribution.
ONE VENUE. OR THE NEXT CHAPTER.
Keep your character.
Connect your operation.
For owners
Start with the work that matters most. See the relevant products and work through your own commercial assumptions.
For the team
Clear running orders, shared context and access that follows each person’s responsibility.
For growing groups
Keep businesses, sites and teams organised, with deliberate permissions and the right operating context.
Can I start with just bookings?
Yes. Products are enabled separately. Begin with the work you need to organise, then add customer, team or operational products as your setup grows.
Does Soupy replace my till?
Soupy EPOS connects configured till systems and sales evidence. It is not a replacement till terminal. Ordering and dispatch depend on the supported provider and your setup.
What about live music and ticketed nights?
Talent handles rosters and accepted engagements; Ticketing handles events, sales and admission. Add them where entertainment is part of your operation.
Can I plan sport screenings?
Sport and Displays are preview products. Feed access, broadcast rights, screen compatibility and configuration remain separate from using the core bar workflows.
Explore first. Talk when you’re ready.
Let’s talk about your venue.
Tell us what a better working day would look like. We’ll use your priorities to make the conversation useful.
No calculator figures are sent unless you choose to include your brief.
About the photography
Licensed venue photography sets the scene. Pictured people and venues are not presented as Soupy customers or endorsers. Product examples use fictional records.
Unsplash licence