The features a restaurant POS system really needs
At a minimum, a restaurant POS system has to do this: keep orders per table, send tickets to the kitchen and the bar, split a bill, settle card and cash on one bill through an integrated payment terminal, break VAT down per rate, close the day and keep every bill line on file for seven years. On top of that come features that depend on the kind of place you run: a floor plan, permissions per staff member, reporting per product, an accounting link, online ordering and QR ordering at the table.
The line between must-have and nice-to-have is not the length of the feature list. It is what goes wrong on a busy Friday night when a feature is missing. Below you walk the list in the order of a service: from taking the order to the paperwork the next morning.

Ordering: tables, courses and modifiers without detours
The first requirement is simple: an order belongs to a table, not to a loose ticket floating around. Table 12 orders three times during the evening and at the end everything sits on one bill. A POS that keeps a running order per table and shows which tables are seated, ordered or waiting for the bill saves a lot of questions between the kitchen and the floor.
Pay attention to variants and modifiers. A steak comes rare, medium or well done, the burger without onion, the kids' menu with apple juice. If that has to be typed as free text, it arrives in the kitchen wrong or not at all. You want modifiers that belong to the product and show up on the kitchen ticket. How an order moves step by step from table to kitchen to payment is covered in [Restaurant POS: from order to payment](/en/blog/restaurant-kassa-bestellen-afrekenen).
A floor plan is nice, but not every venue needs one. A lunchroom with eight tables manages with a list; a restaurant with two rooms and a terrace wants to see where table 23 is. Choose a POS that lets you draw the floor plan yourself, so a refurbishment does not mean a support call.
Kitchen and bar: tickets in the right place
Every order has to land in the right place automatically: drinks at the bar, hot dishes in the kitchen, desserts at the cold station. In a small venue that is one receipt printer in the kitchen. As you grow, you want production stations so the bar does not get every kitchen ticket as well.
A kitchen display instead of a printer is a choice, not a requirement. On a screen you see how long a ticket has been open and tick off dishes; a printer is cheaper and works without anyone having to look at it. The trade-off is covered in [Kitchen display system: a calmer service](/en/blog/keuken-display-systeem-horeca). Whichever you pick, check that the POS works with your receipt printers. Deskly POS supports printers over Wi-Fi, Bluetooth or the network; USB printers are not supported.
Payment: splitting, integrated card terminal and tips kept separate
This is where most POS systems fall short. A table of six wants to split: two pay together, one only wants to settle their own drinks, the rest share. A restaurant POS has to split per item and per amount, and has to allow a separate payment method per part. Deskly POS splits per item or per amount, with buttons to divide equally by two to five; see [Splitting a bill](/en/kb/kassa/rekening-splitsen).
The second requirement at payment is an integrated card terminal. With a standalone terminal the staff member types the amount over, and on a busy night that goes wrong at some point. With an integrated terminal the POS sends the amount to the terminal and the bill is closed automatically. Deskly POS integrates with terminals from Mollie, CCV and PinDirect; which other payment methods to offer and how the POS keeps them apart is in [Payment methods for restaurants, cafés and bars](/en/blog/payment-methods-hospitality).
Also check whether the POS tracks tips separately. Tips are not revenue, and if they disappear into the bill total your revenue figure is wrong and you end up working out afterwards what belonged to the team.
Admin: VAT per rate, day close and record keeping
A restaurant in the Netherlands works with two VAT rates: 9% on food and non-alcoholic drinks, 21% on alcohol. Your POS has to know the rate per product and break it down per rate on every bill and in the daily report, otherwise you are doing your VAT return with a calculator. Which rate applies when is explained in [VAT rates in hospitality: 9% or 21%](/en/blog/vat-rates-hospitality-netherlands-9-or-21-percent).
The day close is your moment of control. A good POS shows revenue, payment methods and VAT per rate at the end of the day, and therefore what should be in the drawer. You compare that with the count and your terminal's settlement. The steps are in [End of day in hospitality: a practical checklist](/en/blog/dagafsluiting-horeca-kassa).
Less visible, but a legal requirement under Dutch rules: record keeping. You have to keep your records for seven years, and the Dutch Supreme Court confirmed in 2021 that this includes the detailed data from your POS: which products were on which bill, when, for how much and how it was paid. A POS that deletes bill lines after a few weeks does not comply. Ask the vendor explicitly how long bill data is kept. More in [POS data retention rules in the Netherlands](/en/blog/pos-data-retention-rules-netherlands).
Team and numbers: permissions, reporting and accounting
As soon as you have staff, you want to set per employee who is allowed to do what. Giving a discount, removing a line from a saved order or reopening a bill are actions you would rather have a manager approve. In Deskly POS you handle that with roles and a manager PIN, see [Adding staff and setting permissions](/en/kb/kassa/medewerkers-en-rechten).
Reporting does not have to be extensive, but it has to be usable. Revenue per day, week and month is the minimum; revenue per product and per category tells you which dishes carry the menu and which you can drop. And if your bookkeeper retypes the daily totals every month, an accounting link pays for itself quickly. Deskly POS exports to Moneybird, e-Boekhouden, SnelStart and Exact Online; how that is set up is in [Accounting link](/en/kb/horeca-manager/boekhoudkoppeling).
Nice-to-have: online ordering, QR at the table and reservations
These features are not a requirement for every venue, but when you need them you want them in the same POS, not in a separate system you have to maintain on the side. Your own webshop for takeaway and delivery without a commission per order. QR ordering at the table, where the guest scans and orders and staff approve the order before it goes to the kitchen. Reservations next to the table overview, so you can see which table is about to be taken at eight. And a Thuisbezorgd link if delivery is a serious channel.
With Deskly POS, the webshop, floor plan, kitchen view and staff management are part of the Basis plan; QR ordering, production stations and delivery links are in PRO. All prices are on the pricing page and exclude VAT.
The checklist in short
Must-have for every restaurant POS
- Orders per table, with modifiers and variants that show on the kitchen ticket
- Tickets sent automatically to kitchen and bar
- Bill splitting per item and per amount, with a payment method per part
- Integrated card terminal and mixed card and cash payments
- Tips kept separate from revenue
- VAT per rate on the bill and in the daily report
- Day close with revenue per payment method
- Bill data kept for seven years
- Keeps working when the internet drops
Depending on your venue
- A floor plan you draw yourself
- Kitchen display and production stations
- Roles and permissions per staff member
- Reporting per product and category
- Accounting link
- Webshop, QR ordering, reservations and delivery link
Frequently asked questions
What is the difference between a restaurant POS and a regular POS?
A regular POS settles a sale right away. A restaurant POS keeps an order open per table, sends tickets to the kitchen and bar, handles courses and modifiers and can split a bill at the end. A retail POS usually lacks exactly those table and kitchen features.
Does a restaurant POS need to work without internet?
Yes, that is a fair requirement. A cloud POS should keep working when the connection drops and sync as soon as it is back. Deskly POS keeps ringing up and taking payments offline; you do not have to do anything in the middle of a service.
Do I need a kitchen display or is a receipt printer enough?
A receipt printer is enough for most small and medium kitchens. A kitchen display becomes interesting when you want to see waiting times per dish or run several production stations. Start with a printer and switch when the kitchen asks for it.
Which features are included in the Deskly POS trial?
You try Deskly POS free for 30 days, no credit card required. During that period you can set up tables, products, receipt printers and the card terminal link and run a real service. After that you pick the plan that fits your venue; all plans can be cancelled monthly.
Which iPad do I need for a restaurant POS?
Deskly POS runs on iPad and iPhone. Which models are suitable and which receipt printers and card terminals go with them is on the hardware page; hardware can be bought or leased.
Must-haves first, the rest later
Go through the checklist with your own venue in mind: how does your table of six pay, where do the tickets come out, and what does your bookkeeper see on the first of the month. A POS that gets the must-haves right is worth more than one with a long feature list you never open half of. To see which iPads, receipt printers and card terminals fit such a setup, have a look at [the hardware page](/en/hardware).
