POS integration: the four systems it must talk to

A guest books a table online and mentions a nut allergy. On the night, the host seats them, the server takes their order on the till, and the kitchen cooks it. The allergy never reaches the kitchen, because it was in the booking system, and the booking system and the till do not talk to each other. Nobody did anything wrong; the systems simply did not share what they knew.

The point of sale sits at the centre of a venue's technology, and most of what goes wrong between systems goes wrong at its edges. POS integration is how the till shares information with the other systems a venue relies on, so each one knows what the others know, and so nobody has to type the same thing twice.

This guide covers the four systems a point of sale must talk to, bookings, the kitchen, the accounts and online orders, what each connection gives you, what breaks when it fails, and how to judge integrations before you buy. Every venue and figure in it is an example.

POS integration means connecting the point of sale to another system so information flows between them automatically. An order rung in on the till appears on the kitchen screen. A booking becomes an open table on the till. The day's sales reach the accounting software without anyone typing them in.

Integrations are usually built through an application programming interface, a defined way for one system to ask another for information or send it some. Some are built by the POS provider, some by the other system's provider and some by third parties that sit between the two.

The alternative to an integration is a person: someone who reads one screen and types into another. That works at a small scale, but it costs time and introduces mistakes every time.

Venues use many systems, but four connections to the point of sale matter most. The bookings system, which knows who is coming and what they need. The kitchen, which must receive every order correctly. The accounts, which must receive every sale. And online orders, which bring in orders from outside the venue.

Each connection solves a different problem, and each fails in a different way. Understanding all four helps you decide which ones you need, which ones your system must handle itself and which can be handled by hand.

Our guide to restaurant technology: what a venue really needs covers the wider set of tools.

The bookings system knows who is coming, when, how many and what they need: allergies, celebrations, preferences and history. The till knows what they ordered and spent. When the two are connected, the guest's details reach the server and the kitchen, and their spend reaches their guest record.

That connection makes service better and records more useful. A server who can see that the table is celebrating a birthday, that one guest has a shellfish allergy and that they are regulars who always order the same wine can serve them far better than one who knows nothing.

Without it, information has to be passed by hand: a note at the host stand, a word to the server, a reminder to the kitchen. Each handover is a chance for something to be lost.

When the booking system and the till are separate, three things tend to break. Allergies and preferences recorded at booking do not reach the kitchen ticket. Tables shown as free on the till may be booked in the diary, or the other way round. And guest records never learn what each guest spent, so the venue cannot tell its most valuable guests from its occasional ones.

Each of those has a workaround, usually a person checking two screens. In a quiet venue that works; on a busy night it is exactly the job nobody has time for.

The kitchen connection is the one no venue can do without. Every order rung in on the till must reach the right station, with every change, allergy and note, at the right time. Whether the kitchen uses printers or screens, the connection between the till and the kitchen must be reliable and immediate.

Most POS systems handle this themselves, through their own printers or kitchen screens. Some venues use a separate kitchen display from another provider, connected to the till through an integration. That can work well, but it adds a point where orders can be delayed, lost or shown differently from how they were entered.

Test the kitchen connection with your hardest orders: changes, allergies, held courses, voids after sending. If the kitchen does not receive exactly what the server entered, the connection is not good enough.

When the connection between the till and the kitchen fails, orders stop reaching the cooks. The server thinks the order has gone; the kitchen has never seen it. The first sign is often a guest asking where their food is.

Ask how the system shows that an order has reached the kitchen, and what happens when it has not. A system that warns the server, or that shows the kitchen's own view of what is waiting, catches the failure early. A system that fails silently leaves it to the guest.

Have a fallback too: a way of getting orders to the kitchen on paper if the connection fails in the middle of service.

The accounts need to know what the venue sold, how it was paid and what tax was charged. Without an accounting integration, someone has to take the till's figures each day or week and enter them into the accounting software, or send them to the accountant to enter.

An accounting integration sends the sales, payments and tax to the accounting software automatically, often as a daily summary. That saves time, reduces typing mistakes and means the accounts are up to date without waiting for someone to enter them.

The value depends on the venue. A group with several sites and an in-house finance team can save days each month. A single café whose accountant works from a monthly export may save very little.

Without an accounting connection, the risk is delay and mistakes. Figures typed in by hand can be wrong; figures entered monthly mean the owner does not know the month's position until it is over. Reconciling the till with the bank and the card provider becomes a slow job at the end of each month.

A good export can remove most of that pain. If the till can export its sales, payments and tax for any dates, in a form the accountant can use, many venues manage well without a live connection. Ask your accountant what they need before deciding.

The fourth connection is online ordering: orders that arrive from outside the venue, through the venue's own ordering page, a delivery platform or a guest's phone at the table. Each needs to reach the kitchen and the till like any other order.

When online orders are connected, they appear on the kitchen screen and in the till's sales like orders taken in the room. When they are not, they arrive on a separate tablet, often one per delivery platform, and someone must type them into the till or run them separately.

Separate tablets are one of the most common sources of mistakes in venues that do delivery. Orders are missed, typed in wrongly or left out of the day's figures.

Unconnected online orders break the kitchen's view of its work. The cooks see the dining room's tickets on one screen and the delivery orders on another device, or on paper, and nobody sees the whole load. At a busy hour, that can mean the kitchen accepts more than it can cook.

They also break the figures. Sales that never reach the till must be added to the day's totals by hand, and the menu report shows only part of what sold. Decide whether online orders matter enough to your venue to need a connection, or whether running them separately is acceptable.

Beyond the four core systems, a venue's guest records benefit from a connection to the point of sale. When the till knows which guest is at the table, their visit and spend can be added to their record, and their preferences and allergies can be shown where they are needed.

That turns a list of names into a record of relationships: who comes most often, who spends most, who has not been back for months. Those are the guests worth thanking, welcoming back or inviting to an event, and the till is often the only system that knows what they ordered.

Without a connection, guest records are built from bookings alone, which miss walk-ins and say nothing about what was ordered.

There are two ways to get these connections. One is a single system that does bookings, the till, the kitchen and online orders itself, so nothing needs integrating. The other is separate systems, each chosen for its strength, connected through integrations.

A single system avoids the gaps between tools, because there is only one set of data. Separate systems can each be the best at their job, but every connection is another thing to set up, maintain and fix when it breaks. Our guide to one system or several: the honest comparison covers the trade-off in detail.

Neither is always right. What matters is that the information flows, by whatever route.

The most dangerous integrations are the ones that break without telling anyone. A connection to the accounting software stops sending data after an update, and nobody notices for three weeks. A connection to a delivery platform drops orders on one day a month. A booking integration stops sending allergies after a settings change.

Ask how each integration reports its own failures. Does it warn someone? Does it keep a log? Can you see when it last worked? Check each connection regularly: compare a day's figures in both systems, send a test order, look at a booking on the till.

An integration you trust without checking is an integration you are hoping works.

POS data is the record of everything a venue sells: every order, payment, void and comp, and often every guest. That record is valuable, and the question of who owns it, and how you can get it out, matters as much as any feature.

Ask what data you can export, in what form, how often and at what cost. Ask what happens to your data if you leave. Ask whether integration partners can see your data, and what they may do with it.

A system that makes your data hard to reach makes integrations harder too, because every connection depends on the data being available.

Before choosing a POS, ask about each of the four connections:

Write down the answers and compare them across systems. Vague answers usually mean a connection that will need work.

Every missing integration has a person behind it: the host who copies allergies from the diary to a note for the kitchen, the manager who types delivery orders into the till, the bookkeeper who re-enters a week of takings. Each of those tasks takes time every day, and each is done when people are busiest.

Count that time when weighing up an integration. A connection that saves a manager twenty minutes a night saves more than a hundred hours a year, which is often worth more than the integration costs. A connection that saves five minutes a week may not be.

When an integration fails, the venue often finds itself between two providers, each saying the problem is on the other side. Before relying on a connection, agree who supports it: the POS provider, the other system's provider or a third party. Keep their contact details with your outage plan, and note what you need to tell them: what stopped, when and what changed beforehand.

Integrations have costs that are easy to miss. Some are charged monthly by the POS provider, some by the other system and some by a third party in between. Some need setting up by a consultant. All need maintaining, because each side updates its software independently.

Count those costs over a year or more, alongside the time saved. An integration that costs a small amount each month and saves a day of typing is good value. One that costs a great deal and saves an hour may not be.

Not every connection needs to be live. For many small venues, a weekly or monthly export from the till, sent to the accountant, is perfectly adequate. A venue that rarely does delivery may run its few delivery orders separately without much harm.

Decide which connections genuinely matter to your venue: usually the kitchen, then bookings, then the accounts and online orders, depending on how you trade. Invest in those, and handle the rest simply.

Test every integration before you rely on it in service. Make a booking with an allergy and check it reaches the till and the kitchen. Ring in a complex order and check what the kitchen receives. Close a day and check that the figures in the accounting software match the till. Send an online order and follow it to the kitchen and the report.

Test again after any update to either system. Integrations that worked last month do not always work after a change.

Integrations that are easy to live with in one venue can become a burden in several. Each new venue multiplies the connections to set up and check, and each new system added to the mix adds connections to every other.

When planning for growth, prefer fewer systems that do more, or integrations maintained by the providers themselves rather than by a consultant. Check how each connection handles more than one venue: whether it can send each venue's data separately, and whether the reports can still be compared.

An invented restaurant uses a booking system, a till, a kitchen display from a third provider and two delivery platforms on separate tablets. Allergies from bookings are passed by hand, delivery orders are typed into the till by whoever is free, and the accountant spends two days a month reconciling the figures.

The restaurant lists its four connections and decides which matter most. It moves to a system that handles bookings, the till and the kitchen together, so allergies reach the ticket and guest records learn what each guest spent. It sends the accountant a monthly export rather than paying for a live connection. It keeps one delivery platform and drops the other, entering its orders through a single process.

Allergy mistakes stop, the kitchen sees all its work in one place and the month-end reconciliation shrinks from two days to an afternoon.

servearound is one system rather than four. Bookings, the floor plan, the point of sale, the kitchen screens, guest records, campaigns and reports share the same data, so a booking becomes a seated table, the guest's allergies from their profile reach the head of the kitchen ticket, and settling the bill completes the booking, with nothing to integrate between them. Card payments are taken on your own terminal and recorded against the check.

servearound does not connect to accounting software, delivery platforms or other booking platforms today. Bills for any range of dates can be downloaded as a spreadsheet for your accountant, and guests order online only from the menu they open with the table's QR code, for seated tables. See Order Fulfillment and pricing.

Connecting the point of sale to other systems so information flows between them automatically, rather than being typed in twice.

Usually the kitchen first, then bookings, then the accounts and online orders, depending on how the venue trades.

Not always. A good export the accountant can use may be enough for a small venue.

Allergies and preferences do not reach the kitchen, table status can disagree, and guest records never learn what guests spent.

Unconnected platforms mean separate tablets, retyped orders and a kitchen that cannot see its whole load.

One system avoids gaps between tools; several can each be the best at their job. What matters is that information flows.

Check it regularly: compare figures in both systems, send test orders and look for a log of failures.

Check the contract, and check what you can export before you sign.

POS integration connects the till to the four systems it must talk to: bookings, so guests' needs reach the floor and the kitchen; the kitchen, so every order arrives complete; the accounts, so sales reach the books; and online orders, so every order reaches the kitchen and the figures. Each connection solves a real problem, and each can break quietly.

Decide which connections matter to your venue, get those right through one system or reliable integrations, handle the rest simply, test every connection before you rely on it and after every update, and make sure you can always get your data out.