Guestit
English
ContactLog inIntroduction

Technology

10

min read

Separate systems or one platform for your venue?

POS, reservations, ordering and kitchen separate or with one supplier? Work out what retyping costs you and ask seven questions about integrations.

Cover with the words 1 platform and a large orange number 1

Do this today

Write down every place where you or your team move data by hand from one system to another, and put the number of minutes per week next to each place.

Do the systems in your venue work together, or are you the integration? As we read it, software gets added step by step: each package solved one problem when you bought it. Only later does it become clear whether POS, reservations, orders and accounting share data with each other.

This article is not a plea for one platform, nor for separate systems. With separate systems you can pay in time: entering things twice and figures that do not match. With one platform you pay in dependence on one supplier. Which price is lowest differs per venue.

Why now? According to the Netherlands Authority for Consumers and Markets (ACM), European rules have given customers of cloud services more rights to switch and to combine services. Whether that also applies to your POS or reservation system is not certain; more on that further down. After this article you can calculate what retyping costs you per year, you know when separate systems are the better choice and you have seven questions for every supplier that promises an integration.

What separate systems cost you in work

The work of separate systems does not appear on an invoice. As we read it, it sits in three places:

  • Entering things twice: a reservation you copy into the table plan, an online order someone retypes into the POS, a price change you make separately on the menu, in the POS and on the website.

  • Figures that do not match: one system counts revenue including VAT and the other excluding it, one closes the day at midnight and the other at the end-of-day close.

  • More points of contact: every supplier has its own contract, its own helpdesk and its own login.

If the systems hold guest data, such as names and phone numbers with reservations, a fourth point is added. A supplier that processes personal data on your instructions is, according to the Dutch Data Protection Authority (AP), a processor. You must conclude a data processing agreement with a processor, and you remain responsible yourself for what you outsource.

Worked example: what does retyping cost per year?

Worked example. Suppose: a restaurant is open six days a week, fifty weeks a year, and uses a POS, a reservation system, an online ordering channel and an accounting package that exchange nothing with each other. All numbers are made up; measure them in your own venue. The €24 per hour is an assumption for what an hour of work costs the business, including employer costs, and not a standard.

  1. Copying reservations into the table plan: 10 minutes per day

  2. Retyping online orders into the POS: 30 orders times 40 seconds is 1,200 seconds, which is 20 minutes per day

  3. Copying daily revenue into the accounts: 8 minutes per day

  4. Together per day: 10 plus 20 plus 8 is 38 minutes; times 6 days is 228 minutes per week

  5. Changes to menu and prices in three places: 30 minutes per week

  6. Sorting out differences between systems: 45 minutes per week

  7. Together per week: 228 plus 30 plus 45 is 303 minutes, a little over 5 hours

  8. Per year: 303 minutes times 50 weeks is 15,150 minutes; divided by 60 that is 252.5 hours

  9. In money: 252.5 hours times €24 is €6,060 per year, or €505 per month

You do not get that amount back automatically: the hours are only worth money if you actually take them out of the roster or spend them differently.

The tipping point

So calculate the other way round: how much time does an integration or an integrated package have to save to be worth the extra price? In words: extra price per year divided by what an hour costs you is the number of hours the integration has to remove per year. Suppose the extra price is €150 per month, excluding VAT (also made up).

  • Extra price per year: €150 times 12 is €1,800

  • Hours that have to offset it: €1,800 divided by €24 is 75 hours per year

  • Per week and per day: 75 hours divided by 50 weeks is 1.5 hours per week, which is 90 minutes; divided by 6 days that is 15 minutes per open day

In the example that is comfortably met. If the integration only removes the 38 minutes per day, that saves 228 minutes per week, 3.8 hours. Times 50 weeks is 190 hours, times €24 is €4,560 per year; minus €1,800 leaves €2,760.

Change the numbers and the outcome flips. Suppose the only manual work is 6 online orders per day. That is 6 times 40 seconds, 4 minutes per day, 24 minutes per week and 20 hours per year. Times €24 that is €480: the €1,800 integration then costs €1,320 per year more than the manual work. In that case retyping is cheaper.

When separate systems are the better choice

Four situations in which, as we read it, separate systems can be the better choice:

  • A specialist does one thing better: if reservations, delivery or accounting is decisive for your venue, a system that does only that can offer more than the component of a broad package.

  • Less dependent on one supplier: the ACM writes that customers who use different cloud services at the same time are less dependent on one provider and can look for the best provider per service.

  • Easier to switch per component: if you are not happy with the reservation system, you replace only that. With one platform, switching quickly becomes all or nothing.

  • Little exchange: if systems need almost nothing from each other, as in the second worked example, integrating yields little.

On the other hand, a platform can give you one contract, one helpdesk and one place for your menu and your figures. How to assess the POS itself is covered in Choosing a restaurant POS? 14 key do's and don'ts.

What the rules say about integrating and switching

Status as of 19 November 2026. We are not lawyers; check what applies to your contracts.

Cloud services (Data Act). According to the ACM, the European Data Act has applied since 12 September 2025. Providers of cloud services may not put up barriers to switching, customers must be able to take their data with them, and providers must make it possible to connect other parties' software to their own software. As an example, the ACM mentions the exchange between ordering software and stock software; for that, a provider may only charge costs that are directly related to it. From 12 January 2027, providers may no longer charge costs for switching.

The Leidraad Cloud (the ACM's cloud guidance, October 2026) states what a contract must lay down as a minimum: which data are and are not portable, and the time limits for switching. Those are a notice period of at most two months before the switching process begins, and after the switch at least thirty calendar days in which you can still retrieve your data. With a fixed-term contract, the provider may, according to the guidance, charge a penalty if you stop early. Two caveats: the guidance is a provisional version, and custom-built services are exempt from part of the obligations. The guidance mentions software as a service over the internet as one of the forms; whether your POS or reservation system falls under it, our sources do not say. Ask your supplier.

Guest data (GDPR). The right to data portability in the GDPR is a right of people, not of businesses. A guest can request the digital personal data he has provided himself, if you process them with his consent or to perform a contract. You supply them in a structured, commonly used and machine-readable format and respond within one month. So this right does not arrange for you to be able to retrieve your revenue figures from a supplier. You do need to know in which system a guest's data are held.

Your records (Dutch Tax Administration). The Handreiking voor een betrouwbaar afrekensysteem (the Tax Administration's guide to a reliable POS system) says that the data in your POS are part of your records, mentions a retention period of seven years and places the responsibility for outsourced processes with the business owner. So with every switch, ask where the old POS data stay and whether you can access them.

Checklist: seven questions about integrations

Put these questions to every supplier that promises an integration, and also to a supplier of one platform. Ask for the answer in writing.

  1. Who is responsible for the integration? Who maintains it and who do you report a problem to? The checklist of the Digital Trust Center (a Dutch government body) also asks whether you know who to turn to and what you remain responsible for yourself.

  2. What exactly goes back and forth? Only orders, or also prices, sold-out dishes, payments and VAT rates?

  3. How fast? Immediately, every quarter of an hour or once a night?

  4. What happens during an outage? Do orders wait, are they lost or do they come in twice? Ask about the response time, the resolution time and the availability. According to the Digital Trust Center, 99.9% per year leaves room for a long working day of downtime. Our sum: 0.1% of 8,760 hours is 8.76 hours.

  5. What happens with an update or a price change? Who adapts the integration if one of the two systems changes, how fast, and who pays for that?

  6. Can you take your data with you? What can you export, in which file format, at what cost and for how long after termination? Does the contract state which data are not portable, and what it costs if you stop early?

  7. Who processes which personal data? Is there a data processing agreement, does the supplier engage other parties, and who supplies the data if a guest asks for them?

Then have it demonstrated: follow one order from the ordering channel through to the end-of-day close, with a change and a cancellation.

Common mistakes

Our own list, not the outcome of research:

  • Comparing subscriptions only: your team's time is not on the invoice, but it does belong in the sum.

  • Mistaking a logo for an integration: that two systems mention each other does not say what is exchanged and how fast.

  • Asking about the data only at termination: arrange at the start what you can take with you.

Do this today

Write down every place where you or your team move data by hand from one system to another, and put the number of minutes per week next to each place. To do so, walk through one working day in your mind: reservation, order, change to the menu, end-of-day close, accounting. Estimate the minutes; you can time the largest item later with a stopwatch. Add up the minutes, divide by 60, multiply by the number of weeks you are open and by what an hour of work costs your business. Put that amount next to the extra price per year of an integration or a different package. That takes pen, paper and at most thirty minutes.

Where technology helps

Guestit sells a platform itself and so has an interest in this trade-off; put the seven questions to us as well. What you can verify: at Guestit, orders placed via QR ordering arrive on the kitchen display and in the POS, and you manage the menu in one place. If you use the tablet menu at the table (eMenu) instead of QR, dishes, prices and availability come from the Guestit CMS and the POS. The POS shows today's reservations and the waiting list on one screen and has reports per period with a CSV export. Those are features, not a promise that it saves your venue time or money: work that out with your own minutes. If you want to walk through this with your own way of working, book an introduction.

How we put this together

The topic comes from two blog posts by Nory, an Irish software supplier for restaurant chains: on building yourself or buying and on an operating system for restaurants. We read those posts only through an automatic summary. We took over the topic, not text, examples or figures; Nory sells a platform itself. We read the pages of the ACM and the AP and the checklist of the Digital Trust Center in full. Of the Leidraad Cloud we read the summary and the passages on scope, time limits and costs; of the Tax Administration's guide, the main text. We did not read the Data Act itself. All numbers in the worked examples are made up; we checked the sums with a calculation script. We found no research into the time Dutch hospitality businesses lose to entering things twice; that is why there is no figure about it in this article. The lists of work, reasons and mistakes are our own reasoning. A correction or a better source? Email hey@guestit.nl.

Sources

  1. Netherlands Authority for Consumers and Markets, Clouddiensten (last modified 14 August 2026 according to the page data; read in full)

  2. Netherlands Authority for Consumers and Markets, ACM publiceert leidraad over overstappen tussen clouddiensten (news item, 19 October 2026; read in full)

  3. Netherlands Authority for Consumers and Markets, Leidraad Cloud. Dataverordening: overstappen, interoperabiliteit en internationale doorgifte van data (October 2026; provisional version, for consultation; summary and the passages on scope, time limits and costs read)

  4. Dutch Data Protection Authority, Recht op gegevens overdragen (dataportabiliteit) (updated 1 April 2026; read in full)

  5. Dutch Data Protection Authority, Verantwoordelijke en verwerker (updated 11 November 2025; read in full)

  6. Dutch Tax Administration, Handreiking voor een betrouwbaar afrekensysteem (2023; main text read)

  7. Digital Trust Center, Afspraken maken met een IT-leverancier. Checklist Service Level Agreement (undated document, file path from June 2020; read in full; general checklist, not specific to hospitality)

About Guestit

Guestit is one system for reservations, ordering, preparation and payment.

Want to see this work in your business?

Book an introduction and we’ll look together at which of these ideas fit your business. If Guestit isn’t a fit, we’ll say so.

Book an introduction
See the solutions
Guestit

The operating system for hospitality. Connects every step of the guest journey with the processes behind it.

© 2026 Guestit

Privacy · Terms