Guestit
English
ContactLog inIntroduction

Technology

8

min read

Eighty POS integrations or one database?

A column by the founder of Guestit: where separate hospitality systems jam on a busy night, who picks up the phone, and a demo test in six steps.

Illustration: on the left a gear stick next to two receipt printers and loose receipts, on the right an automatic selector next to one screen, on the bar of a busy restaurant

Do this today

Write down, for your last busy night, which actions your team did by hand because the systems did not take them over from each other.

Friday night, a full house. A guest orders on the tablet at the table. The order shows up on the POS, but it never appears on the grill's screen. The floor staff have to work out where it went wrong, while the guest is simply waiting for his food.

An evening like that, made up but recognisable, is how I look at the choice between a POS system with dozens of integrations and a system in which the POS, the ordering channels and the kitchen all work on the same data. First the honest part: I am the founder of Guestit, and we build our POS, eMenu and kitchen displays on one central database. So I have a stake in this question. Read this as a column, an opinion based on experience, and not as research.

I cover three things: how separate systems can end in chaos on a busy night, what comes to a standstill when one link falters, and who takes responsibility when it does. After that you get the test I would run at every POS demo, in six steps, and one action for today. You don't need Guestit for either of them.

Why I prefer to drive an automatic

It is a bit like choosing between a manual car and an automatic. With a manual gearbox you work the clutch yourself and you pick the gear. With an automatic you accelerate and you brake. The gear changes happen under the bonnet.

That is what I want in hospitality too. When a guest changes his order, I want the POS and the kitchen both to process that change, without anyone having to check whether the integration has done its job. On a Friday night your team already has its hands full, and I don't want someone to have to shift between systems on top of that.

How separate systems can end in chaos on a busy night

The weakest link decides what an integration is worth to you in practice. A made-up example, not a customer's story: suppose your ordering software handles courses and cooking preferences very well, but the integration with the kitchen only passes on the product name and the quantity.

Table 12 orders a starter and two steaks, one of them medium-rare. The kitchen sees: 2 steaks. The information that one steak has to be medium-rare and that both may only go out after the starter still has to be passed on by the floor staff themselves. On a Friday night that same server is carrying three plates, and the grill starts on what is on the screen.

The feature exists. During service your team can do little with it. That is how chaos arises without anything being broken: every system does what it promises, only part of the information gets lost along the way. Your team is then the integration.

The risk when one link fails

A chain is only as strong as its weakest link. With separate systems that chain consists of more than the programs themselves: the ordering software, the integration, the POS, the kitchen display, the internet connection and the suppliers behind them. How often such a link falters I don't know; I have no figures that I can verify. The question you can answer is: what comes to a standstill when it happens?

  • The integration falters: both systems work, but they no longer talk to each other. If nobody sees an error message, you may only notice when a guest asks where his food is.

  • The internet connection drops: ask for each system what keeps working, and what happens to an order that was just on its way.

  • One supplier has an outage or changes something: an update on one side can affect the integration on the other side. Ask who tests that before it is running in your venue.

A single system is a link too. If that one system is down, a lot is down at the same time, and you depend on one supplier. The difference I see lies in the number of handovers where something can get stuck, and in the answer to the next question.

Who takes responsibility?

Two suppliers and an integration between them: who do you call when the order doesn't reach the grill? In the worst case one says the order was sent perfectly well and the other says nothing came in. They can both be right.

So arrange that in advance, on paper. The checklist for agreements with an IT supplier from the Digital Trust Center (a Dutch government initiative) is general and not specific to hospitality, but the questions fit well here. Is it clear what you are still responsible for yourself? Do you know who to turn to when there is a problem? Has it been laid down within what time the service provider responds to a report and within what time there has to be a solution? And when can support be reached?

My own addition for a venue with integrations: have one party put on paper that it is the first point of contact for the whole chain, even if the cause turns out to lie with the other. And call the helpdesk once on a Friday night at nine o'clock, before you sign.

When an integration is exactly right

An external integration can deliver a lot. If your accountant works in Exact, a good accounting integration can save you data entry every week. Nothing has to happen within seconds there, and if it is down for an hour, no guest notices.

For actions your team carries out during every service, such as ordering, changing, preparing, passing and settling the bill, I would set the bar higher. There are also venues for which separate systems are the better choice, for example when a specialist does one component better. Separate systems or one platform for your venue? sets out that trade-off, with a calculation to go with it. What to look for in the POS itself is covered in Choosing a restaurant POS? 14 key do's and don'ts.

Checklist: my demo test in six steps

This is my favourite test at a POS demo, with any supplier at all. Have them do it, not tell it, and at every step look in three places: with the floor staff, in the kitchen and on the POS.

  1. Order through the guest's channel: a starter and two main courses, on the tablet or with the QR code, with a cooking preference such as medium-rare on one main course.

  2. See what the kitchen sees: are the cooking preference and the course on the screen of the right station, or only the product name and the quantity?

  3. Change one main course after the order has arrived in the kitchen: does the kitchen see that something has been changed, and what exactly? What happens if the cook has already started? Put this question to Guestit as well.

  4. Call away the main courses: do they stay on hold until the starter has gone out, and who gives the signal?

  5. Settle the two main courses separately: does the bill match the change, and what is still open on the table afterwards?

  6. Switch off the wifi and order something else: what does the screen tell the guest and your team, and what happens to the order when the connection is back?

Finally, ask who fixes it when the change gets stuck somewhere, until what time that person can be reached, and whether that answer is in the contract.

How it works with us

At Guestit we build ordering, changing, preparing, passing and settling the bill around the same order data, so that the POS, the eMenu and the kitchen work with the same order. What you can check of that in a demo: an order placed on the eMenu only counts once the POS confirms it. If you use QR ordering instead of the tablet menu at the table, orders come in on the kitchen display and in the POS. On the kitchen displays every dish goes to its station, such as the grill, and main courses wait until someone calls them away; the course status follows the POS.

If the wifi drops, an order on the eMenu waits and goes through once as soon as the connection is back. Without a connection the kitchen display keeps every action and shows a bar saying that no new orders are coming in. What happens to a change after the kitchen has started, I am not describing here: that is step 3 of the test, and you have us show it instead of tell it. Whether it saves work in your venue, I cannot promise. So do the six steps with us too, for example during an introduction.

That leaves the question that matters to me: how many actions does your team still have to take over from the software itself during a busy night?

Do this today

Write down, for your last busy night, which actions your team did by hand because the systems did not take them over from each other. Think of walking to the kitchen to pass on a change, ringing up a ticket again or retyping an order from one screen onto the other. Also ask one member of the floor staff and one from the kitchen; they often know better than you do. Next to each action, note which two systems it sat between. That takes pen, paper and thirty minutes at most. The action that comes up most often is your first question to your supplier.

How we put this together

This is a column, based on the experience of the writer, the founder of Guestit. It is not research. The example of the Friday night and the steaks is made up and does not describe an existing venue or customer. We have no figures on how often integrations or connections fail; we did not look for a source for them and that is why they are not in here. We read the Digital Trust Center's checklist in full; it is a general list for outsourcing IT, with no date in the document. The demo test and the advice on agreements are our own advice, not legal advice. The image for this article is an illustration (AI-generated), not a photo of a real venue and not a screenshot of Guestit.

Sources

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

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

Shall we give you a call?

Guestit

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

© 2026 Guestit