Insights/SYSTEMS / 14 June 2026
Why your POS isn’t the problem: the gaps between hospitality systems
Venues don’t need another platform. They need Lightspeed, Deputy, Xero, the book and the inbox to stop making people copy things by hand.
When operators get frustrated they often blame the POS. The POS is rarely the villain. It is doing what a POS does: taking money, printing dockets, holding product.
The pain sits in the gaps. Deputy does not know what the book looks like tonight. Xero does not know the function that landed at 11pm. The inbox does not know which of those emails is worth a GM’s time. WhatsApp becomes the integration layer because it is already open.
A typical stack, and why it frays
- POS for sales and product
- Reservations for the book
- Deputy for labour
- Xero for money out
- Google Workspace or Microsoft for mail and files
- A functions spreadsheet that should have been retired
- A group chat that now holds operational truth
Each product is competent. None of them were hired to be the venue’s operating system. The copy-paste between them is unpaid integration work performed by the most expensive people in the building.
What “another piece of software” usually means
A new dashboard that asks staff to log in one more time. If the work is “get last night’s numbers to the owner”, the answer is not a sixth login. It is a report that appears, with the weird bits highlighted.
Most venues don’t need another piece of software. They need the systems they already have to work better together.
That is the entire job of Hospo 2030. Not a platform. Not a replacement for SevenRooms or Lightspeed or Xero. The messy distance between them.