Connected isn't unified: why hospitality tech integrations don't give you one guest

"Connected" is the word hospitality tech suppliers use most right now. Tools that talk to each other, a connected ecosystem, best-in-class products with open APIs. Most of it is true. Your till probably does talk to your stock system, and your rota probably does read your sales.

But a connected stack and a unified one aren't the same thing, and the difference shows up in one place: the guest. Hospitality tech integration was built to move transactions between tools. It was never built to tell you who your guests are.

What an integration actually moves

Look at what the typical integrations in a hospitality stack do:

• the order goes from the QR menu to the till

• the covers count goes from the booking system to the labour forecast

• the day's takings go from the till to the accounting software

• the stock depletes when the till records a sale

Every one of those is useful and every one is operational. They exist to make the shift run. The guest appears in them as a field, if at all: a name on a booking, a table number on an order, nothing on the payment.

So you can have a stack where every tool is connected to every other tool, and still not be able to answer the simplest question in hospitality: has this person been in before?

Three guests a connected stack can't see

ART Hospitality runs eight chef-led venues across Hereford, Worcester, Birmingham and Gloucester. Before moving to Stampede, the group's marketing, bookings and guest Wi-Fi came from three different suppliers. Founding director Edwin Kirk is clear that none of those products was bad:

"You start having to deal with multiple different people. But more importantly, the synergy between the software is just not at the standard you need for the modern customer, and even the modern team member."

The cost never appeared on an invoice. It showed up as guests who fell through the gaps, and ART's story describes three of them.

The event guest. Someone buys a ticket for a wine dinner through a separate ticketing site. They come in, eat, drink, and leave. As Ed puts it: "Because the marketing is not picking up how much that customer spent, we have no idea whether they are a regular. They literally come in through a different portal."

The till guest. Someone books, sits down and spends well. The till records the basket, but against nobody in particular. The booking system knows their name and the till knows their spend, and neither knows the other's half.

The walk-in. Someone who never books walks in, eats and pays. In a booking-led stack, they don't exist at all.

All three guests were served well on the night. None of them left a trace anyone could use afterwards.

Why connecting more tools doesn't fix it

The instinct is to add another integration: push the till data into the email tool, or sync the booking list to the CRM. It helps at the edges, but it rarely closes the gap, for reasons we've covered in detail before. Tools match guests on different identifiers, many syncs only run one way, and each tool keeps its own copy of the guest, which drifts from the others.

The deeper problem is design. When every tool owns a slice of the guest, joining the slices is always somebody's afterthought. There's no record for the review to attach to, so it sits in a review inbox. There's no record for the Wi-Fi sign-in to join, so it becomes another list.

What unified means in practice

A unified stack starts from the other end. There is one guest profile, and every system writes to it: the booking, the ticket, the Wi-Fi sign-in, the basket, the review, the campaign they opened.

Unified doesn't mean replacing everything. ART kept Square on its tills, because front of house liked it and the pricing was good. What changed is where the till's data goes. With a two-way POS integration, a booking made in Stampede carries through to the table, and what that table spends comes back onto the guest's record. The till stays exactly as it was for the person holding it.

The other two gaps close the same way. The event ticket runs through the same system as the booking, so it lands on the same record. Walk-ins who never book still appear, because the guest Wi-Fi sign-in picks them up.

Then the record starts working in places the operation can see. Here is Ed on reviews:

"It is the richness of the data, because it is all in one. When someone has left a review and we know who they are, that comes up on our tills. We can see they have left a four star or a three star, alongside our own notes, if we have resolved an issue for them."

That is the practical test of unified. The review doesn't just sit in a dashboard; it reaches the person about to serve that guest.

Five questions to ask any supplier

If a supplier tells you their product is "connected", these five questions tell you whether it gives you one guest:

1. When a guest pays on the till, whose record does the spend land on? If the answer is "the transaction log", it's connected, not unified.

2. If a walk-in signs in to the Wi-Fi, do they become a guest we can recognise next time? Or just another email address on a list?

3. Can a review attach to a named guest? Or does it only attach to a venue?

4. Does data flow back, or only out? One-way integrations send your bookings somewhere and never return what happened next.

5. If we leave, what do we take with us? Can you export your guest records with their marketing consent intact?

The honest trade-off

The standard argument for a connected stack is that you get the best tool for each job, and that a single platform means accepting average tools everywhere. It's a fair argument, and for operational tools like stock, rotas and accounting it often holds.

For the guest, it falls down. You can't pick the best-in-class booking tool, the best-in-class Wi-Fi and the best-in-class CRM and expect them to produce one guest between them. Ed's view, from running eight venues on both models:

"The whole fragmented tech idea, that you cannot have best in class in multiple areas at the same time, is something Stampede is trying to prove otherwise. And doing it successfully, as far as I can see."

If you're not sure which parts of your stack are connected and which are unified, start with a tech stack audit and follow one real guest through it. Then read how ART put eight venues on one guest profile while keeping Square on the tills.