Digital & Data

Restaurant Software Costs: 7 Steps to Cut Subscriptions

Five to ten systems, each with its own invoice — and nobody who still knows the total

The most expensive line on your P&L isn't a line at all — it's eight small direct debits spread across a statement nobody reads any more.

It always starts innocently. First the till. Then a booking system, because the phone kept ringing mid-service. Then a website subscription, an email tool for the newsletter, an app for the rotas, a stock module, the rental on the card terminal, and a link to your accountant. Every single one cost "only thirty or forty a month" on the day you signed.

Each of those decisions was defensible on its own. Together they have never been looked at once. And unlike rent, wages or purchasing — the lines you review every year — this one grows quietly: an indexation here, an extra module there, a per-cover commission that rises with your turnover without anything being added in return.

This guide walks you through 7 steps to map your software stack and prune it back: from your bank statements to your overlap map, from the clauses nobody read to the exit right you now have in law and almost nobody knows about. With a calculator to make your own total visible in one go.

Why the stack grows without anyone saying yes

No operator ever decided to take on nine subscriptions. What actually happened: nine problems on nine busy days, and nine solutions that felt exactly right at the time. The decisions sit years apart, were sometimes made by different people, and have never been reviewed together since. You renegotiate your suppliers every year; you never renegotiate your software.

On top of that, the pricing model works structurally against you. Anything billed per cover, per user or as a percentage of turnover automatically invoices you more the moment you do better — without giving you anything more. And because almost every contract renews by default, your supplier never has to earn that increase. A stack nobody reviews is a stack that can only move one way.

The ultimate guide The ultimate guide to digital & data Turn technology and data into saved hours and higher revenue. Open the guide

The 7 steps to prune your software stack

1. Get your whole stack onto one sheet

Don't start from memory — start from your bank. Pull twelve months of statements plus your card bills and mark every recurring payment. Nearly every operator finds two to four subscriptions they had forgotten: a tool that stopped being used after one season, a second domain name, a module that was switched on as a trial and never off. Don't skip the items that don't look like software either — the rental on your card terminal, an annual compliance charge, your mailboxes, your backup, the maintenance contract on your website.

Give each system one row: what it does, cost per month, cost per year, when the contract ends, how long the notice period is, and who signed it. That last column seems pointless until you realise the person who signed a sixty-month till contract five years ago left the business two years ago. One sheet, everything visible — that sheet alone makes most operators sit up straight.

The stack of a typical business

Each amount feels small on its own. Together it's another member of staff.

Till system €129
Bookings €79
Website & hosting €45
Rotas €39
Email & marketing €35
Terminal rental €32
Stock module €29
Together per year €4,656

Illustrative example based on common monthly prices — you fill in your own figures below. Per-cover commissions and card charges are not included here.

2. Work out the real cost per cover, not per month

A price of €89 a month is chosen precisely so that it feels like nothing. Yet you cost the rest of your business in a completely different unit: food cost per dish, labour per hour, margin per cover. Do the same here. Divide your total annual cost by your annual covers and you get the only honest measure — what every guest who walks in costs you in software — and set that next to the same figure as a percentage of turnover.

Bring the costs that don't arrive as subscriptions into that same unit: per-cover commissions and your card charges. A portal charging €2 per cover costs you nearly €10,000 a year on 400 covers a month — more than most till contracts, and largely charged on guests who were coming anyway. How to move that traffic back to your own channel is covered in our guide to increasing direct bookings.

3. Hunt down the lines nobody read

With the numbers on the table, go looking for where they come from. The usual suspects: an indexation clause that lifts your price automatically every year, "free" hardware whose cost is simply baked into a higher monthly fee, a compliance charge you pay annually with nothing behind it, the rental on a card terminal that paid for itself three years ago, and per-user licences still counting seasonal staff who left long ago.

On card costs it pays to press. In the EU, interchange on consumer cards is capped at 0.2% (debit) and 0.3% (credit) — but that is only the slice going to the card issuer, not what you pay. Between it and your invoice sit the Visa or Mastercard scheme fees and your acquirer's margin, and commercial cards or cards issued outside the EEA fall outside the cap altogether. So ask for a breakdown on the "interchange++" model: a blended rate quoted as one round percentage hides exactly the part you could negotiate. The same approach that works with your food suppliers works here — you only negotiate once you understand the build-up.

4. Draw your overlap map

Most stacks don't have too many systems — they have too many systems doing the same thing. Guest data sits in three tools, email goes out from two, reporting exists four times over, and your table plan lives in both your till and your booking system. Draw it as a grid: your systems down the side, the functions across the top, and a dot wherever a system delivers that function.

The columns with more than one dot are your shortlist. A caveat: not every overlap is waste. A specialist email tool may genuinely be better than the mail function in your till, and then you pay twice on purpose. That is exactly the difference — on purpose. Every duplicated function should be a choice you made, not one you inherited from a supplier who sold you a module along the way.

Where are you paying twice?

Same exercise, your systems: one dot per function that system delivers

Where are you paying twice?
SystemGuest dataEmailTable planReportingPayments
Till system
Booking system
Email tool
Website
Accounting link
Only system that does this Duplicated: two or more systems do this

Red columns aren't a mistake — they're your talking point at the next renewal.

5. Measure the time tax, not just the invoice

There is a second invoice nobody sends you: the hours your team spends moving data by hand between systems that don't talk. Retyping bookings into the till. Exporting a list into your email tool. Copying hours from the rota app into payroll. Pulling a revenue figure together from three screens for your accountant. Time one real week — not your estimate, but what actually happens.

Then value those hours at your true hourly cost, on-costs included. In a lot of businesses that time tax turns out to be bigger than the subscription itself, and it gets worse as you grow: more covers means more rows to retype. That is precisely the argument for not just pruning but connecting — which jobs are worth automating away is set out in our guide to restaurant automation.

6. Know your exit before you negotiate

Never negotiate without knowing how you get out. For every contract, note three dates: when it ends, the latest date you can give notice, and the term it renews for by default. Miss your notice window by a week and you often pay for a full extra year — and a supplier who knows you are locked in has no reason to give you anything.

And now the part most operators don't know: since 12 September 2025 the EU Data Act applies across the Union, and it covers cloud services and software subscriptions too. It gives you a statutory right to switch. The notice period for starting a switch may be no longer than two months; your provider then has to complete it within thirty calendar days (if it needs longer it must justify that in writing within fourteen working days, with an absolute ceiling of seven months); you get at least another thirty days to retrieve your data; and from 12 January 2027 switching charges are banned outright. Until then a provider may only pass on the actual costs of the switch — no penalty, no flat fee.

Check your data processing agreement as well. Under the GDPR your processor must return or delete personal data at the end of the engagement, at your choice. Ask for that export up front, in an ordinary format such as CSV, before you sit down to negotiate. A supplier who cannot or will not hand over your own guest list has effectively answered your question already. What you may keep and take with you is covered in our guide to guest data and GDPR.

7. Choose connectable over all-in-one — and owning over renting where you can

Pruning does not automatically mean "everything from one supplier". That is precisely how lock-in gets built: one party holding your till, your payments, your bookings and your guest data has no competitor left to fear. The real test is not how many systems you run but whether they exchange data without somebody sitting there retyping it. Three systems that connect cleanly cost you less time and less money than one package that does everything half well.

Finally, put the rental model itself up for debate. Some things genuinely are a service that keeps running, hosting and updating. Others are simply software you rent forever because that became the model. Add up what a subscription costs you over five years and set it against buying the same thing once — we've worked that comparison out on our pricing page. For a lot of businesses the difference is exactly the amount that's missing somewhere else in the house.

What are you actually paying? Work it out

The number that matters isn't your monthly total but your all-in annual cost including commissions and retyping hours, expressed in a unit you recognise. Fill in your own figures below. Be honest about the hours: that's the line that appears on no invoice and often turns out to be the biggest piece.

Everything is calculated in your browser — nothing is sent or stored.

Subscription scan

Slide in your own numbers and see what your stack costs per year, per cover and as a share of turnover

Total annual cost of your stack €0
Of your turnover 0% Per cover €0

Retyping hours are costed at €28 an hour (wage cost including on-costs). Percentages are for orientation, not a norm: what's acceptable depends on your revenue per cover and on what the systems actually return.

Take the annual figure you're now looking at and set it against something tangible from your own business: a part-timer, a new refrigeration unit, or what you spent on promotion last year. That's the comparison that makes the decision — not "€89 a month isn't much".

Then run down your list once with one simple question per system: what exactly breaks if I cancel this on Friday? For part of your stack the answer is concrete and serious — those you keep. For a surprisingly large part the answer is vague, and vague here means nobody misses it.

Your action plan for this month

You don't have to do this in one sitting. Three evenings spread over a month is enough to get the whole stack under control:

Week 1 — Make it visible

  • Print twelve months of bank statements and mark every recurring payment
  • Put everything on one sheet: cost per month, per year, end date, notice period
  • Convert your total into euro per cover with the scan above

Week 2 — Find the overlap and the hidden lines

  • Draw your overlap map and circle every function that appears twice
  • Ask your payment provider for a breakdown on the interchange++ model
  • Find the indexation clause and the renewal term in every contract

Week 3 — Prune and negotiate

  • Cancel what nobody misses, and put the notice dates of the rest in your diary with a reminder two months ahead
  • Ask your two most expensive suppliers for an export of your own data
  • Open the conversation on those two with your figures and your exit right both on the table

Conclusion: prune your stack once a year

Software is the one large cost line in hospitality that almost never gets reviewed. You review your menu, you review your suppliers, you review your rotas — but the nine direct debits run on year after year, each one a little dearer. So put this exercise in the diary, once a year, on a quiet Monday: everything on one sheet, the overlap out, the notice dates guarded. That's ninety minutes of work for a saving that comes back every month.

And while you're reviewing: HappyChef charges no commission per cover and isn't rented forever — you buy it once, with online bookings, table plan, guest profiles and your own website included. See what that saves over five years and set it against the annual figure you worked out above.

Frequently asked questions

How much should restaurant software cost?

There is no official norm, and any figure presented as one is a sales line. What does work is expressing your total annual cost — subscriptions, per-cover commissions, card charges and retyping hours together — as a percentage of turnover and as an amount per cover, then setting that next to last year's. The direction matters more than the level: a stack growing faster than your turnover is a stack to review. Judge each system separately as well, on what it concretely returns in revenue or in hours saved.

How do I get out of a running software contract?

First find your three dates: end date, last date for giving notice, and renewal term. Give notice in writing and provably, well inside that window. If the contract still has a long way to run you have an extra lever as of September 2025: the EU Data Act gives customers of cloud services and software subscriptions a statutory right to switch, with a notice period of no more than two months to start the switch. Always ask for a full export of your data at the same time — that is both your negotiating position and your starting point with the next supplier.

What is the EU Data Act and what does it do for me as an operator?

The Data Act is EU legislation that has applied since 12 September 2025 and, among other things, governs switching between cloud services and software subscriptions. For you it comes down to this: the notice period for starting a switch may be at most two months, your provider must complete the switch within thirty calendar days (longer only with written justification within fourteen working days, capped at seven months), you then get at least thirty days to retrieve your data, and from 12 January 2027 no switching charges may be levied at all. Until that date only the actual cost of the switch may be passed on.

Is one all-in-one system cheaper than separate tools?

Sometimes, but not automatically — and it's rarely the cheapest question to ask. One package saves you integrations and retyping, but it also makes you wholly dependent on a single supplier for your till, your payments and your guest data, which weakens your position at every renewal. The better test is whether your systems exchange data automatically. Three tools that connect cleanly usually cost you less time and less money than one package that does everything half well.

Can my supplier refuse to hand over my guest data?

No. You are the controller for your guests' data; your software supplier is normally only a processor. Under the GDPR that processor must return or delete the personal data at the end of the engagement, at your choice — and your data processing agreement should say so. On top of that, the EU Data Act obliges providers of cloud services to cooperate technically with a switch. So ask for the export in a common, machine-readable format such as CSV, and preferably do it before you give notice.