POS for a small venue: what you can skip

A café with thirty covers, an owner who cooks and one person on the floor does not need the same point of sale as a group of twelve restaurants. Yet the systems on offer are often sold with the same brochure: dozens of modules, layers of permissions, dashboards for head offices and reports nobody in a small room will ever open.

Choosing a POS for a small venue is mostly about what to leave out. The right system does a handful of things very well, costs little to run and takes an afternoon to learn. The wrong one costs more each month, slows down two busy people and fills the screen with features designed for someone else.

This guide covers what a small venue actually needs from its point of sale, the features that earn their place, the enterprise list you can skip, the hardware and costs, and how to set it up in a day. Every venue and figure in it is an example.

A small venue's needs are simple to state. Orders must be rung in quickly and reach the kitchen correctly. Tables must be easy to find and checks easy to split and close. Payments must be recorded so the end of the night adds up. The owner must be able to see what sold and when.

Everything else is optional. Some of it may help later; much of it never will. The test for each feature is whether it saves time or money for two people on a busy night, every week, not whether it sounds impressive.

Write down how your service works before you look at any system: how orders are taken, how the kitchen receives them, how guests pay and what you need to know at the end of the day. That list is your shopping list.

A handful of POS features earn their place in a small room. Fast ordering with your own menu. A simple table plan, or a counter screen if you serve at the counter. Modifiers that reach the kitchen clearly. A quick way to hold and fire a course. Splitting and moving checks. Recording payments by method. A few reports.

Each of those is used every service, and each saves time or prevents mistakes. If a system does them well, it is a good candidate, whatever else it does or does not offer.

Our guide to POS features that matter after the first week covers the everyday features in detail.

With two people running the room, speed of ordering matters more than anything else. A server who is also clearing tables, making coffee and taking payments cannot spend fifteen taps on a single order.

Set up the menu so the most common dishes are quickest to find, and so their usual changes are taps rather than typing. Test it with your real menu, not the demo's: a café with forty drinks and twenty dishes needs a layout that makes the common orders fast.

Count the taps for your ten most common orders. If the busiest ones take more than a handful, look for a layout that cuts them down, or a different system.

A small venue needs a table plan that matches its room and nothing more. Ten or fifteen tables, laid out as they are on the floor, showing which are free, which are eating and which are waiting to pay.

A table plan saves the server from remembering which check belongs to which table, and lets the owner see the room at a glance from behind the counter. It does not need zones, sections or complex layouts in a room this size.

If you mostly serve at the counter, a simple list of open checks may be all you need. Choose the view that matches how your guests are served.

In a small kitchen, the cook is often the owner, and there is no expeditor at the pass to catch mistakes. The changes the server enters must arrive on the ticket exactly as intended, so the cook can trust them.

Set up the common changes as modifiers on each dish: the milk for a coffee, the cooking point for a steak, the sides, the usual removals. Keep free-text notes for the unusual. Then check what the kitchen actually receives for a few difficult orders.

Clear modifiers prevent remakes, and in a small kitchen every remake is a few minutes the cook does not have.

Even a small restaurant serving starters and mains benefits from holding the mains and firing them when the table is ready. Without it, the kitchen cooks everything at once, or the server has to remember to send the mains later.

In a small room the routine can be simple: send the starters, hold the mains, fire them with one tap when the starters are nearly finished. If your venue does not serve courses, you can ignore it entirely.

A small venue's end of night should take minutes. Every check closed, every payment recorded by its method, the card terminal's total matching the POS and the cash matching the drawer.

Look at how quickly a check closes, how a split payment is recorded and how a mistake is corrected. A system that makes the close easy saves the owner time every single night, which over a year is a great deal of time.

Keep the card terminal simple too. A terminal from your bank or payment provider that works alongside the POS is often all a small venue needs.

A small venue needs only a few reports: sales by day and by hour, sales by payment method, the best and worst selling dishes, and voids and comps. Those answer the owner's real questions: how did we do, when were we busy, what sold and what was given away.

Most systems offer far more. That is fine, as long as the few you need are clear and quick to open. Our guide to restaurant reporting: six reports, no more covers which ones are worth reading.

Much of what is sold with a POS is built for large operations: head offices, area managers, central kitchens and dozens of staff. In a small venue, most of it adds cost and complexity without adding value.

That does not make those features bad. It makes them someone else's features. A small venue that pays for them, or has to work around them every day, is paying for a problem it does not have.

The next sections cover the most common items on the enterprise list, and why a small room can usually do without them.

Large operations need detailed permissions: who can void, who can discount, who can see which venue's reports. In a venue with two or three staff, simple roles are enough: an owner who can do everything, and staff who can take orders and payments.

Set staff up properly, with their own sign-in, so every order and void is recorded against the right person. But do not spend hours on permission matrices for a team that fits around one table.

Tools for running many sites, such as central menu management, consolidated reports and head-office dashboards, matter greatly to a group and not at all to a single café. If you have one venue and no plans for a second, they are features you will never open.

If you do plan to grow, check that the system can add a second venue later. You do not need to pay for it today.

Points schemes, tiers and digital stamp cards can work for chains with thousands of regular guests. In a small venue where the owner knows the regulars by name, an elaborate loyalty scheme often costs more than it returns.

A simple record of who your guests are, what they like and when they last came can do more for a small venue than a points scheme. Build the relationship first, and add a scheme only if guests ask for one.

Many systems include stock management: counts, recipes, suppliers and purchase orders. In a large kitchen with a dedicated manager, that can save money. In a small kitchen where the owner cooks and orders, a stock module that needs daily updating is often abandoned within a month.

If you want to track stock, start with a simple weekly count of your most expensive items on a sheet. Our guide to a small restaurant, run on fewer systems covers keeping the number of tools down.

A small venue's menu is usually short, which is an advantage on the till. Set it up so the layout matches how guests order: drinks first for a café, starters and mains in order for a bistro. Group the dishes the way the menu groups them, so a new member of staff finds them without searching.

Keep the till's menu in step with the printed one and any menu guests read on their phones. In a small venue, the owner often changes the specials board on a whim; make sure the till changes too, or the price charged will not match the price shown. A short routine, such as updating the till whenever the board changes, avoids most mismatches.

A small venue rarely needs dedicated terminals. A tablet on a stand at the counter, a second tablet or a phone for the floor, and a screen or printer for the kitchen are usually enough. Many systems now run on ordinary tablets and phones, which cost less to buy and replace.

Protect what you buy. A tablet in a busy café needs a sturdy case, a stand that does not tip and a spare charger. Our guide to tablet POS: cheaper until it is not covers the hidden costs of ordinary devices.

A small kitchen can work with a printer or a screen. A printer is cheap and familiar; a screen avoids lost tickets, shows how long each order has waited and makes changes clearer. In a kitchen with one or two cooks, either can work well.

If you choose a screen, a single one is usually enough in a small kitchen, mounted where the cook can read it without walking. Our guide to kitchen printers: what a screen does better covers the trade-offs.

The cost of a POS for a small venue has several parts: the software, usually a monthly subscription; the hardware, from tablets to card terminals; any setup or training fees; and card processing, often charged separately by the payment provider.

Look at the total cost over a year or more, not only the headline monthly fee. A low monthly price with expensive hardware, a long contract or high fees for every extra can cost more than a higher price with everything included. The idea of total cost of ownership is useful here: add up everything you will pay, over the time you will use it.

Our guide to how much does a POS cost in the first year sets out the full sum.

Small venues are especially exposed to long contracts. A system that locks a café into three years, with expensive hardware it cannot return, is a heavy commitment for a business that may change its menu, its hours or its whole concept within that time.

Prefer monthly terms or short contracts, hardware you own or can use with other systems, and a clear way to export your data if you leave. Read the notice period and any fees for leaving before you sign.

Choosing a POS takes time a small venue rarely has. Keep it short: list your must-haves, look at three systems that suit small venues, try each with your own menu for an hour, and pick the one your staff found quickest.

Ask other small venues what they use and what they would change. Their experience is worth more than any brochure. Our guide to choosing a POS: twelve questions, in order gives the questions in the order to ask them.

A POS for a small venue setup can usually be done in a day. Build the menu first: categories, dishes, prices, the common modifiers and allergens. Draw the table plan to match the room. Add your staff, each with their own sign-in. Set up the payment methods you accept.

Then connect the devices: the counter tablet, the floor device, the kitchen screen or printer and the card terminal. Run a test service with the team, ringing in real orders and closing real checks, and fix whatever surprises you.

Keep the setup simple at first. You can always add more later, once you know how the system works in your room.

A small team has nobody to call when the system goes wrong except the provider. Check what support is available in the hours you trade, how quickly it answers and whether it can be reached by phone or chat during service.

Ask other small venues how support has treated them. A system with fewer features and quick, friendly support is often a better choice for two people on a busy night than one with every feature and a support line that answers next week.

Keep a short note of how to do the few things that go wrong most often: restarting a device, reconnecting the card terminal, finding a closed check. It saves a call on the night.

Training in a small venue is quick, because there are few people to train. Spend an hour with each member of staff before their first shift: ringing in orders, holding and firing, splitting and closing checks, and recording payments.

Practise the awkward cases: a table that changes its order, a bill split three ways, a dish sent back. Those are the moments that cause stress on a busy night, and they are easy to learn when nobody is waiting.

Once the system is running, resist adding everything it offers. Each new feature is something else to set up, train and maintain. Add one only when you can name the problem it solves, and remove anything nobody uses. A small venue's till should stay small: quick to use, easy to teach and cheap to run.

Small venues grow: a second room, a terrace, more staff, a second site. When choosing a POS, check that it can grow with you: more devices, more staff, more tables and, if you might open another venue, more sites.

You do not need to pay for growth now. But you should know that the system can handle it, so you are not forced into a painful switch at the moment the business is busiest.

An invented café with twenty-eight covers uses a POS designed for restaurant groups, on a three-year contract. The owner pays for modules for stock, loyalty and multi-site reporting, none of which are used. Ringing in a flat white with oat milk takes six taps, and the end-of-night report runs to eleven pages.

When the contract ends, the owner lists what the café actually uses: fast drinks ordering, a simple table plan, modifiers for milk and extras, payments by card and cash, and a daily sales summary. They try three systems built for small venues and choose the one their two staff found quickest.

The new system costs less than half as much each month, runs on two tablets the café already owns, and the oat flat white now takes two taps.

servearound runs in a browser, so a small venue can run the point of sale on a tablet it already owns, the kitchen screen on another, and bookings, the floor plan, guest records and the menu guests open from the table's QR code in the same system. Staff sign in with their name and a four-digit PIN, checks open from the floor plan, dishes are rung in with their options and removals, and rounds can be held and fired.

Checks can be split, merged, moved or handed to another member of staff, and payments are recorded against the check by method, with cards taken on your own terminal: servearound does not process card payments or print kitchen tickets today. Plans are priced per venue; see pricing, and Order Fulfillment for the point of sale and kitchen.

Fast ordering, a simple table plan or counter screen, clear modifiers, holding and firing, splitting and closing checks, payments by method and a few reports.

Complex permissions, tools for many sites, elaborate loyalty schemes and stock modules that need daily updating.

Rarely. Tablets on sturdy stands, a phone or tablet for the floor and a kitchen screen or printer are usually enough.

Add the subscription, hardware, setup, any extras and card processing over a year or more, rather than comparing monthly fees alone.

Avoid it if you can. Monthly or short terms, owned hardware and a clear data export protect a small business.

Usually a day: the menu, the table plan, staff, payment methods, devices and a test service.

Yes. Every order, void and payment should be recorded against the right person, however small the team.

Check before you buy that the system can add another venue later, without paying for it now.

A POS for a small venue should do a few things very well: fast ordering with your own menu, a simple table plan, clear modifiers, holding and firing, easy splitting and closing, payments by method and a handful of reports. The enterprise list, complex permissions, multi-site tools, elaborate loyalty and stock modules, can usually be skipped.

Run it on ordinary devices where you can, compare the total cost rather than the monthly fee, avoid long contracts, set it up in a day, train each person for an hour and make sure the system can grow with you.