A POS system, short for point of sale system, is the software a restaurant takes orders and settles bills on, plus the devices that software runs on. It is where an order lives between the moment a guest says it out loud and the moment the table pays. A server enters it, the kitchen reads it, the floor tracks it and the bill adds it up.
That loop is the whole job. A card reader is not a POS system, even though it is often sold as part of one. Inventory, payroll, loyalty and online ordering are not a POS system either. They are modules sold on top of one, and they are only as useful as the order loop underneath them.
So for most restaurants the real question is not whether you need a POS. It is which parts you need, who you have to buy each part from, and what it will cost to leave.
What a POS system is, and what it is not
“Point of sale” originally meant the spot where money changes hands: the till. In a shop that is still close to true, because the sale happens in the ten seconds it takes to scan a barcode and pay.
A restaurant sale does not work like that. It starts at the table, passes through a kitchen, picks up a second round, and ends at the same table an hour later, often paid by three people in two different ways. A restaurant POS exists to keep that sale in one piece the whole way through.
It is not a cash register
A cash register adds up a sale, holds the cash drawer and prints a receipt. It does not know that table 12 exists, that one burger has no onions, or that two guests want separate bills. A POS system tracks the order from the moment it is taken, not only the moment it is paid.
It is not a card terminal
The card terminal (card reader, card machine) takes the card and moves the money through a payment processor. Some POS systems come with their own terminal and require their own processor. Others simply record that a card was paid on whatever terminal you already use.
Confusing the two is the most expensive mistake in this category. A terminal that only talks to one processor decides your card fees for as long as you keep it.
It is not a full restaurant management suite
Inventory, recipe costing, scheduling, payroll, loyalty and delivery-app connections are often sold under the POS name. They are separate jobs with separate price tags. Plenty of small rooms run well on a POS, a spreadsheet and a good accountant.
How a POS system works in a restaurant
The easiest way to understand a restaurant POS is to follow one order through a Friday night.
- 19:04, the order. Table 12 orders two burgers, one without onions and one with extra cheese, plus a lemonade. The server taps the items on a tablet or phone, adds the change and the note, and sends the order.
- 19:04, the kitchen. The order appears on a kitchen screen or prints as a ticket at the pass. The “no onions” note is attached to the right burger, not scribbled in the margin of a pad. A kitchen display system is the screen version of this step.
- 19:18, the floor. The burgers go out and are marked served. Anyone looking at the floor plan can see which tables are still waiting on the kitchen and which are close to paying.
- 19:40, another round. Two more drinks join the check that is already open.
- 20:02, the bill. The table splits. One guest pays for her burger and lemonade by card on the terminal; the other pays the rest in cash. The POS records both parts and the table is settled.
- The next morning, the record. What sold, what was paid in cash and what by card, and what was sent back, readable without rebuilding the night from paper.
A paper system does all of this with tickets, a spike and memory. It breaks at the handoffs: the note that never made the ticket, the round that landed on the wrong table, the split nobody can reconstruct at close. A POS system fixes the handoffs by making every device read the same order.
The parts of a POS system: software, hardware and payments
Every POS system is three things, and they are often sold by different companies. Knowing which is which is how you read a quote.
Software
The software holds the menu and the orders. In a restaurant it typically covers:
- The menu: categories, items, prices and modifiers such as “no onions” or “extra shot”.
- The order screen: built to be tapped quickly during a rush.
- The kitchen view: a screen, a printed ticket, or both.
- Tables: a floor plan showing what each table is waiting for.
- The bill: totals, splits, and how each part was paid.
- Staff access: what a server, a cook and a manager can each see and change.
- Reports: what sold, when, and who sold it.
Older systems install this software on a computer in the back office. Newer ones keep it on the vendor’s servers and reach it through an app or a web browser.
Hardware
| Device | What it does | Do you need it? |
|---|---|---|
| Order device (terminal, tablet, phone, laptop) | Where orders are entered | Yes, at least one |
| Handheld for servers | Takes the order at the table | Optional; saves trips to a fixed station |
| Card reader or terminal | Takes card payments | Only if you take cards, and it can be separate from the POS |
| Kitchen screen or kitchen printer | Gets the order to the cooks | One or the other |
| Receipt printer | Prints the guest’s bill | Common, depending on your guests and local rules |
| Cash drawer | Holds cash | Only if you take cash |
| Router and a reliable connection | Links the devices | Yes, for any cloud POS |
Ask of every row: whose hardware is it? A tablet from an electronics store works with many systems. A proprietary terminal works with one.
Payments
Card processing is a service, not a device. A payment processor moves the money from the guest’s card to your bank and charges a fee on every transaction, usually a percentage plus a few cents.
Card data is covered by an industry standard, PCI DSS, which the PCI Security Standards Council describes as “a baseline of technical and operational requirements designed to protect payment account data”. It applies to merchants, processors and everyone else that handles card data, which is one reason card details usually stay inside the terminal.
A POS and a terminal can work together in two ways:
- Integrated: the POS sends the amount to the terminal, so nobody types it twice. Convenient, but it usually ties you to the processor the POS vendor chose.
- Standalone: the server types the amount into the terminal, then marks the bill paid in the POS. One more step, but you can use any terminal and shop around for processing.
Types of POS systems
These are the categories that change what you pay and what happens when something breaks.
| Type | Where it runs | Good at | Watch out for |
|---|---|---|---|
| Legacy (on-premise) | A server in the building and fixed terminals | Keeps working when the internet drops | Large upfront cost, repairs by a technician, hard to check from home |
| Cloud | Vendor servers, reached over the internet | Readable from anywhere, updates arrive on their own | Needs a connection; offline support varies a lot by vendor |
| Tablet | A cloud POS on an iPad or Android tablet | Low hardware cost, easy to move | Consumer tablets wear out; some systems run on iPad only |
| Mobile or handheld | A phone or handheld device at the table | Orders taken where the guest sits | Small screens, batteries that die mid-shift |
| All-in-one, processor-bundled | Software, hardware and card processing from one company | One bill, one support line | Hardware and card fees tied to one processor, often with a contract |
| Browser-based | A cloud POS that opens in a web browser | Runs on almost any device, nothing to install | Needs a connection, like any cloud system |
The categories overlap: one system can be cloud, tablet, handheld and processor-bundled at once. Two questions cut through the labels:
- Where does my data live? On a box in the building, or on a server you reach online. That decides what happens when the internet or the box fails.
- Whose hardware and whose processor am I tied to? That decides what leaving costs.
For the longer version of the cloud question, see what a cloud based restaurant POS system runs on.
What a restaurant needs that a retail POS does not
A retail POS is built around a barcode and an instant sale. It can take a coffee order at a counter, and it starts to struggle when table 12 orders a second round. When comparing systems, check for:
- Modifiers and notes that reach the kitchen. “No onions” travels with the item.
- A kitchen view. A screen or printed tickets, so cooks never need the order repeated.
- Tables and a floor plan. Which tables are seated, waiting on food, or ready to pay.
- Open checks. One bill that stays open across rounds.
- Split by item. Not only “divide by four”, but “she had the burger and the lemonade”.
- Corrections both ways. A plate that comes back is handled without shouting at the pass.
- Roles. A cook does not need the bill screen; a server does not need the price editor.
- Speed in a rush. Count the taps for your most common order, then again with a modifier.
A counter-service café or a food truck can live without some of this. A full-service room with tables and a kitchen needs nearly all of it.
What a POS system costs
Cost has its own guide: how much a restaurant POS system costs. The short version is that you pay for up to four things, and the percentage on card sales usually outweighs the rest. The figures below are published US prices as of 2026.
| Cost line | What US vendors publish (2026) |
|---|---|
| Software | Square for Restaurants: $0, $49 or $149 per month per location. Toast: $0 Starter Kit, or $69 and up per month for its Point of Sale plan |
| Card processing, in person | Square: 2.6%, 2.5% or 2.4% plus 15¢, depending on the plan. Toast: 2.49% plus 15¢ with hardware bought upfront, or 3.09% plus 15¢ and up on pay-as-you-go |
| Hardware | Square Reader $59, Square Terminal $299, Square Register $799–$899. Toast Go 3 handheld $599, countertop starter kit $1,203, or $0 with higher processing fees |
| Contract | Toast can lock you into a contract for two to three years, according to NerdWallet’s 2026 review |
Notice the pattern in the $0 options: the software or the hardware is free, and the processing rate goes up to pay for it.
Here is why processing matters most. Say your restaurant takes $30,000 a month on cards, with an average ticket of $20. That is 1,500 card payments. At 2.5% plus 15¢, processing costs $750 plus $225: $975 a month, or about $11,700 a year. On the same sales, a rate 0.2 points lower saves $60 a month. Compare the effective rate after every fee, not the headline.
How to choose a POS system
For a side-by-side of specific products, see how restaurant POS systems compare. Whatever ends up on your list, this process works:
- Write down your service first. Counter or tables? How many order stations? Kitchen screen, printer, or both? How do you take cards today, and are you happy with the rate?
- Get the three bills separately, in writing. Software per month, hardware up front, processing per transaction. One bundled number hides where the money goes.
- Ask whose terminal and whose processor. Can you keep your card reader? If you leave, does the hardware still work?
- Ask what happens when the internet drops. Can staff keep taking orders, and what happens to them when the connection returns? Test the wifi where orders are actually taken.
- Run a real test, not a demo. Have a server take five orders in a busy hour, including a modifier, a plate sent back and a split bill. Watch where they hesitate.
- Read the exit before the entry. Contract length, auto-renewal, cancellation notice, and whether your menu and sales history come out without a support ticket.
- Check what your local rules require. In some countries every sale must produce an official tax document. If a POS does not do that, you need a second system alongside it.
Where Platevio fits, and where it does not
Platevio is a restaurant POS that runs in the browser. Free. No card, no plan. In the terms above it is a cloud, browser-based system, and it is not processor-bundled. It runs on the phones, tablets and laptops a venue already owns, and it is written for independent cafés, bars, food trucks, bakeries, quick-service spots and small restaurants.
What it covers is the order loop described in this guide:
- A menu with categories, items, prices, descriptions and extras, edited from any device.
- Orders at a table or with no table at all, each with a number staff can call out. Extras and notes travel to the kitchen, and a later round joins the open check.
- A kitchen display where items are marked cooked, then served, and moved back when a plate returns. Receipts and kitchen tickets print over WiFi, Ethernet, USB or Bluetooth to ESC/POS and Star Micronics thermal printers; the kitchen can use a screen, a printer or both.
- A floor plan of your room, each table showing seated, waiting on the kitchen, ready to pay or settled.
- Bills split by item, each part recorded as cash or card.
- Roles for owners, managers, waiters and cooks, and every device reading the same live service.
What it does not do, plainly:
- It does not process cards. Your own terminal takes the card; Platevio records that it was paid. No integrated payments, and no percentage of your sales.
- It does not work offline. An order needs an internet connection to reach the kitchen.
- No inventory, recipe costing or food-cost calculation.
- No payroll, scheduling, loyalty, gift cards or discounts.
- No takeaway or delivery order type yet. Every order is labelled dine-in, even without a table.
- Nothing guest-facing: no QR menu, online ordering or kiosk, and no delivery-app connection.
- No reservations, no multi-location view, and no deeper analytics such as item trends.
- No fiscal or tax documents in any country.
If your room already has a card reader and a reliable connection, and what you need is the order, the kitchen, the floor and the bill working in one place, you can see how Platevio runs a service. Signing up asks for a name, the restaurant and a password. If you need offline mode, integrated payments or inventory, choose a system that has them.