Running a bar next to an attraction, on two systems

Plenty of venues end up here without deciding to. You open with the attraction, add a bar because people want to stay, and now you have booking software that does not understand tables and restaurant software that does not understand sessions.

What actually breaks

The customer exists twice. They booked the experience under one email and the table under another, or the table is not attached to anyone at all because they walked up. You have two records of one night.

You never find out what the visit was worth. The experience takes eighty dollars. The bar takes sixty. Two systems make that two unrelated numbers and nobody ever adds them up per group.

Nobody knows the attach rate. How often does an experience turn into people staying for a drink? That is one of the most useful numbers in a mixed venue and almost nobody can produce it.

The staffing decision gets made blind. If half of Friday's experience bookings stay for food, that changes who you roster. If you cannot see it, you guess.

Here is the version that catches everyone. A group of eight books an experience for seven o'clock and asks whether they can eat afterwards. Somebody writes it on a pad, walks it to the restaurant side, and books a table under a different name because the systems do not talk.

That night looks like two separate customers in your reporting. One booked an experience. One ate. Nobody can tell you they were the same eight people, or what the evening was actually worth.

Why do the systems not join up?

Tables are not sessions. A session starts at seven and ends at eight. A table turns when the people at it leave, and you are estimating rather than scheduling. Walk-ins and bookings compete for the same floor all night, which is a problem experience booking software has never had to solve.

So most platforms built one or the other properly and bolted on a version of the second.

What to look for

Whether the customer record is genuinely shared or just visible from both places.

Whether you can see spend per person across the whole visit rather than per transaction.

Whether adding food to an existing booking is a normal thing to do or a workaround.

Whether the reporting adds the two together without you exporting anything.

That is the shape we are building for on the restaurants and bars page.