The hospitality operating system
Ticketing, Bookings, CRM, Loyalty and Payments all use the same customers, orders and venue context. No stitching the night back together later.
Start with what hurts. Add the rest when it earns its place.
One shared layer
Start with what hurts. Add the rest when it earns its place.
Not another layer of integrations wearing a nicer login. Each module starts with the same living picture of the business.
Featured module / Ticketing
Sell the ticket once. Let the same order build the run, recognise the guest, earn loyalty and route the money from programme to payout.
Electric Supper Club
Ticketing preview: Build. 3 dates generated.
3 dates generated
One recurring programme generates the next three events while each night keeps its own capacity and location.
What the ticket leaves behind
Ticketing writes the completed sale once. The guest, order, venue, payment and permissions stay useful when the next module needs them.
Ticketing / completed sale
Electric Supper Club2 tickets · £42.00 · paid
Permanent records
Stored once. Still useful.Modules with context
The same completed sale opens as Sarah's customer record.
One customer record
A completed order becomes history on one customer record. Add CRM and the purchase, programme and consent picture is already there — without turning a ticket sale into marketing permission.
sarah@example.com
Recent context
Electric Supper ClubOrder confirmed / £40.00 / 20 Aug
Late Plates: JuneOrder confirmed / £36.00 / 19 Jun
Pick your pressure point
Choose the module that fixes today's problem. The next one inherits the same customers, orders and venue — so you do not pay for your own context twice.
Plan the whole visit
Guest journey / one request
Six people want a Thursday night out. They do not want four booking confirmations. Soupy turns one request into a continuous plan — then prices each part for the demand it actually carries.
Journey created: four spaces from 18:00.
Suggested journey / Thu 20 Aug / from 18:00
Settle in together before the first game.
Recovers a quiet slot before the peak rush.
Starts as pool ends. The group keeps moving.
Suggested nearby because the night should not end at darts.
A better night for them.
A fuller venue for you.
From first table to last drinks, still one booking.After Bookings / six operations
Bookings plans the visit. Now the same trusted context makes each daily decision clear, explainable and reversible.
Know who to bring back
CRMCustomer intelligence
Choose a guest and Soupy rebuilds the rank, the evidence and the relevant return moment. The smartest result can still be not to send.
Asha Quinn selected. Rank 04; a relevant return moment is ready to review.
Return opportunity / eligible
Nothing is sent from this preview.
3 / Guardrails applied
Make the points worth earning
LoyaltySmart loyalty
Pick a real venue reward. The wallet shows what it unlocks, what remains and why demand-shaping never has to hide the value.
Reward shelf ready. Choose a sample reward; nothing is redeemed from this preview.
Run the shift from one complete team record
Rotas + TeamSmart people operations
Cover the gap from the same trusted record that holds each person's contract, required training, workbook sign-offs, rest, overtime, incentives and team handover.
Priya is selected for review. Six checks pass; this is an illustrative coverage decision, not a live rota change.
142 covers / sold-out show / bar-close skill required / preview only
Report it once, fix it in the right visit
MaintenancePhoto to contractor pack
Choose compatible repairs and build a single visit. The critical electrical fault refuses to join the folder, because safety is part of the intelligence.
Two compatible plumbing jobs are selected for an illustrative visit. Add the glasswasher leak or review the draft; nothing is sent.
Leak beneath
glasswasher
Cellar hand-sink tapCellar / Medium / access before 16:00
30 minStaff WC slow cisternFirst floor / Low / no service impact
30 minCritical hazards always bypass consolidation.
Let the tills write the first draft
AutomationEPOS to reviewed stock plan
Follow one stopped stock line from EPOS evidence to a verified pack calculation. Only the resolved line advances—and a manager still owns the decision.
Pale ale is blocked by an unresolved EPOS pack size. Nothing is exported, ordered or moved.
House lager 50LCellar A → Main bar / par gap · unchanged
18ReadyHouse tonic / 24 packBelow par / delivery Friday · unchanged
2 casesReadyGuest pale ale / SKU 882Pack-size mismatch in EPOS mapping
—BlockedEvery tap becomes a custody record
Asset ManagementNFC equipment custody
Check out the radio. Its equipment passport picks up the employee, area and return clock, then reveals exactly who hears about an overdue asset.
Radio kit 04 is in the Cellar store and unassigned.
Service comms / operational
Waiting for tapNo holder assigned
Return dueTap into any approved area
Alert only if missingHolder first / duty manager copied
Less explaining.
More understanding.
Nothing hidden.
Six distinct module chapters / one product language.Ready when your venue is