Technology, data and AI

The restaurant tech stack: what you actually need

The core systems a restaurant, pub or café needs at each size, what to skip or delay, how to keep subscriptions under control and a one-page stack audit.

Ava research teamPublished 7 min read

On this page
  1. Start from the jobs, not the apps
  2. The core stack by venue size
  3. Cash discipline: every subscription has to earn its place
  4. What to skip or delay
  5. Five questions before you buy any new tool
  6. Integration matters more than features
  7. The forgotten channel: the phone
  8. Ownership and security
  9. Plan for the day something fails
  10. A one-page stack audit
  11. Where to get help
  12. Frequently asked questions
  13. References

Key takeaways

  • Build the stack around a few jobs: take orders and payments, take bookings, run the kitchen, pay staff, keep the books and talk to guests.
  • Cash is tight across the sector: 20% of accommodation and food businesses had no cash reserves in October 2026[1], so every subscription has to earn its place.
  • Ease of integration and use was the factor most often influencing new technology use among hospitality businesses[2]; fewer, better-connected systems beat many separate apps.
  • Audit the stack once a year: what each tool costs, who uses it, what it connects to and who owns the login.

Start from the jobs, not the apps

Technology sales in hospitality are relentless. There is an app for rotas, another for stock, another for reviews, loyalty, temperature logs, staff chat, menus, gift vouchers and table QR codes, and each one promises to save hours a week. The result in many venues is a dozen subscriptions, logins scattered across personal email accounts, and data that never joins up.

A better starting point is the handful of jobs every venue has to do. Take orders and payments. Take and manage bookings. Get orders to the kitchen accurately. Plan staff and pay them correctly. Keep the books and file VAT. Talk to guests before and after their visit. Every system you pay for should do one of those jobs better than what you have now, and connect to the systems doing the others.

The core stack by venue size

A core technology stack by venue size
JobSmall café or takeawayIndependent restaurant or pubMulti-site group
Orders and paymentsSelf-serve EPOS with integrated card readerHospitality EPOS with table service and integrated terminalsCentral EPOS with menu and price control across sites
BookingsOften none, or a simple booking linkBooking system with deposits and no-show controlsGroup booking platform with central guest data
KitchenOne printerPrinters or kitchen screens per sectionKitchen screens with ticket-time data
Staff and payrollSpreadsheet rota and payroll bureauRota and time-tracking app linked to payrollWorkforce management with labour forecasting
Books and VATAccounting software fed by EPOS summariesAccounting software with EPOS and supplier invoice linksAccounting plus central purchasing and reporting
Guest communicationGoogle profile and social accountsPlus email newsletter and review repliesPlus CRM, loyalty and central review tools
PhonesOwner's mobileVenue line with call handling for busy periodsCentral or per-site call handling

Cash discipline: every subscription has to earn its place

Technology spending looks small month by month but adds up, and the sector has little slack. In October 2026, 20% of accommodation and food businesses had no cash reserves and a further 13.2% had less than a month's worth[1]. Across all UK businesses, the equivalent figures were 14.4% and 7.8%[3]. Hospitality runs closer to the edge than most.

Businesses with little or no cash reserves, October 2026ONS Business Insights and Conditions Survey, wave 166
Businesses with little or no cash reserves, October 2026Comparison. No cash reserves: Accommodation and food 20%, All UK businesses 14.4%; Less than one month of reserves: Accommodation and food 13.2%, All UK businesses 7.8%.No cash reservesNo cash reserves · Accommodation and food: 20%20%No cash reserves · All UK businesses: 14.4%14.4%Less than one month of reservesLess than one month of reserves · Accommodation and food: 13.2%13.2%Less than one month of reserves · All UK businesses: 7.8%7.8%Businesses with little or no cash reserves, October 2026Comparison. No cash reserves: Accommodation and food 20%, All UK businesses 14.4%; Less than one month of reserves: Accommodation and food 13.2%, All UK businesses 7.8%.No cash reservesNo cash reserves · Accommodation and food: 20%20%No cash reserves · All UK businesses: 14.4%14.4%Less than one month of reservesLess than one month of reserves · Accommodation and food: 13.2%13.2%Less than one month of reserves · All UK businesses: 7.8%7.8%
  • Accommodation and food
  • All UK businesses

Source: Office for National Statistics, 2026[1]

Show the data
ItemAccommodation and foodAll UK businesses
No cash reserves20%14.4%
Less than one month of reserves13.2%7.8%

That is a reason to favour systems with monthly terms over long contracts where the price difference is small, to avoid paying for modules you will not switch on, and to cancel tools nobody has opened in a month. It is also a reason to watch the free tools: they cost nothing until you depend on them and the provider changes the terms.

What to skip or delay

  • A separate loyalty app before you have a working email list. A newsletter to opted-in regulars does most of the same job.
  • Table QR ordering in a venue where guests come for service. It suits some bars and casual formats and irritates guests elsewhere.
  • A standalone stock platform before your EPOS stock module and a weekly count are working well. Our guide to stock software explains when the step up is worth it.
  • Advanced analytics dashboards nobody has time to read. Two or three numbers reviewed weekly beat fifty that nobody looks at.
  • Any tool that duplicates a feature you already pay for in your EPOS or booking system.

Five questions before you buy any new tool

  1. Which of the core jobs does it do, and what does it replace? If the answer is nothing, it is an extra cost rather than an improvement.
  2. Who will use it every day, and have they seen it? Tools chosen by the owner and ignored by the team are the most common waste in a stack.
  3. What does it connect to, and who maintains that connection when either system updates?
  4. What is the full cost over the contract, including hardware, add-ons, payment fees and the cost of leaving?
  5. Can you get your data out, in a usable format, without asking permission or paying a fee?

If a supplier cannot answer the last three clearly in writing, treat it as a warning. The best systems are usually happy to show you exactly how they connect and how you would leave, because they expect you to stay for the product rather than the contract.

Integration matters more than features

When the Office for National Statistics asked hospitality businesses that were using or considering AI what most influenced their use of it, ease of integration and use came top at 25.5%, ahead of business knowledge at 11.7% and affordability at 10.5%[2]. The same logic applies to any technology. A tool that does not connect to your EPOS or accounts creates re-keying, mistakes and a reason for staff to stop using it.

Before buying anything new, ask three questions. What does it need to receive from the systems I already have? What does it need to send back? And can I see that connection working with my own suppliers, not just a logo on a website? Our guide to connecting booking, EPOS and accounting systems covers the flows worth automating first.

The forgotten channel: the phone

Many venues spend heavily on online booking and forget that a large share of enquiries still arrive by phone, often at exactly the moment nobody can answer: the middle of lunch service, or after close. Missed calls are missed bookings, missed private dining enquiries and guests who ring the next place on the list.

Decide how your phone is handled at peak and after hours, just as you decide how online bookings are handled. Options range from a simple voicemail with a booking link to a call-handling service or an AI Employee such as Ava, which answers everyday questions, takes booking requests and passes the right calls to staff.

Ownership and security

Security is a weak spot in the sector. Only 12% of food or hospitality businesses had a board member responsible for cyber security in 2025, among the lowest of any sector[4]. In a small venue, nobody needs a formal title, but someone does need to own the list of systems and logins.

  • Every system should be registered to a business email address, not a manager's personal account.
  • At least two people should hold admin access to each critical system, so nothing is locked away when someone leaves.
  • Turn on two-factor authentication for the EPOS back office, booking system, email and accounting software.
  • Remove leavers' access on their last day, including shared logins whose passwords they knew.

Plan for the day something fails

Every cloud system will be unavailable at some point, whether through a broadband fault, a supplier outage or a failed update. Write a one-page fallback for the systems that stop service: how you take orders, how you take payment, how the kitchen receives tickets, and how you see the day's bookings. A printed copy of the next day's reservations each evening, a card terminal with mobile data backup and a pad of paper tickets in the office cost almost nothing and turn a crisis into an inconvenience.

A one-page stack audit

  1. List every system

    Go through bank and card statements for every software subscription. Include free tools you rely on.

  2. Record five facts for each

    Monthly cost, contract end date, who uses it, what it connects to, and which email address owns it.

  3. Map the jobs

    Match each system to one of the core jobs. Anything that does not fit, or duplicates another tool, goes on the review list.

  4. Check the joins

    Note anywhere staff re-key data from one system to another. Each of those is a candidate for an integration or a consolidation.

  5. Decide and diarise

    Cancel, keep or replace. Put contract end dates in the diary three months ahead so renewals never happen by accident.

Example: a fictional 80-cover pub finds fourteen subscriptions, three of which nobody has opened in months and two of which duplicate features already included in its EPOS. Cancelling those five and moving every login to a shared business account takes an afternoon.

Where to get help

Hospitality owners are less likely than most to ask for outside advice: only 20% of accommodation and food SME employers sought business information or advice in 2025, the lowest of any sector[5]. Your accountant, your trade association and other operators are usually the best sources of honest opinions on systems, because they have seen what works in venues like yours and have nothing to sell.

Finally, remember that technology choices carry data duties. Each system that holds staff or guest details is part of your UK GDPR picture, and most venues that process personal data need to pay the data protection fee.

Frequently asked questions

What is the minimum tech a new café needs?

An EPOS with an integrated card reader, accounting software fed by daily sales summaries, a Google Business Profile, and a simple way to handle staff hours and payroll. Add more only when a clear problem appears.

Should I buy an all-in-one hospitality platform?

It can reduce integration work, but check that each module is good enough on its own and that you can export your data and leave. One weak module can hold the whole venue back.

How often should I review our software subscriptions?

Do a full audit once a year and check contract renewal dates quarterly, so nothing renews automatically without a decision.

Who should own our system logins?

The business, through a shared business email address, with at least two named admins for each critical system.

References

  1. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (opens in a new tab) ↑

  2. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑

  3. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (opens in a new tab) ↑

  4. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  5. Department for Business and Trade (2025). Longitudinal Small Business Survey 2025: SME employers (businesses with 1 to 249 employees) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo