A small restaurant, run on fewer systems

A small restaurant has one great advantage and one great constraint. The advantage is closeness: the owner knows every regular, tastes every plate and sees every table. The constraint is time: with thirty covers and three staff, there is nobody else to manage the systems, read the reports, update the menu on five websites or reconcile three sets of numbers. Every hour spent on software is an hour not spent cooking, serving or resting.

That makes the choice of systems more important in a small venue than in a large one, not less. A large restaurant can absorb a tool that takes three hours a week to manage; a small one cannot. The aim is a setup so simple that it runs in the background: a few tools that do the essential jobs, that one person can manage in a couple of hours a week, and that do not need a manual.

This guide sets out what a small restaurant actually needs, what to buy and what to skip, how to choose a POS for a small venue, how a small menu and a small dining room change the decisions, and how to think about loyalty for a small venue without an app. It ends with a weekly routine that fits into one person's time.

A small restaurant typically has an owner who works on the floor or in the kitchen, one or two other staff on each shift, a short menu, a single dining room, and a small budget for anything beyond food, wages and rent. The owner usually handles the bookings, the suppliers, the accounts, the social media and the cleaning rota as well as the service.

Every system has to earn its place against that reality. A tool that saves time is worth buying; one that adds time is not, however impressive it looks.

Start with the jobs a small restaurant must do every day, not with the tools on offer:

Then the back office: accounts, wages and stock. Everything else is optional.

For most small restaurants, the essential purchases are:

Ideally, the first four come from one system, so there is one login, one bill and one set of numbers.

A POS for a small venue should be quick to learn, quick to use and cheap to run. It should run on ordinary tablets or phones, rather than specialist terminals; handle a short menu with modifiers and allergens; send orders clearly to the kitchen; split bills; and produce a simple end-of-day report.

A point of sale is the record of every order and payment, and in a small venue it is often the only system the whole team touches every shift. Avoid systems priced for large venues, with charges per terminal, per user or per order that add up quickly. Our guide to choosing a POS: twelve questions in order covers what to ask.

In a small restaurant, the kitchen may be a few metres from the till, and orders could simply be called out. But calling out orders fails on busy nights, when changes and allergies get lost. A single kitchen screen, or a small printer, keeps every order clear and in sequence.

One screen for the whole kitchen is usually enough. Multiple stations and complex routing are for larger kitchens.

A card terminal is essential. Choose one with fair rates for your volume, and check how it works with the till: connected, or used side by side with the total entered by hand. In a small venue, side by side is often fine, as long as the end-of-day totals are checked against each other.

Make splitting bills easy. Small venues often have tables of friends who want to pay separately.

If the venue takes bookings, a booking page on its own website and map listing is usually better than a booking platform that charges per guest. A small restaurant with thirty covers cannot afford fees on every booking, and its regulars are happy to book directly.

The booking page should send reminders and make it easy for guests to cancel, because a no-show at a table for four is a large share of a small venue's evening.

A small restaurant lives on its regulars. The owner knows many of them by sight, but a simple guest record, with their name, visits, preferences, allergies and whether they have agreed to hear from the venue, helps when the owner is away and helps the team recognise them.

The record should build itself from bookings and orders, not from a separate spreadsheet someone has to keep.

Most small restaurants can skip:

Each of these may suit a larger venue. In a small one, they usually add more work than they save.

A small menu is one of the small restaurant's strengths. Fewer dishes mean less preparation, less stock, less waste and faster service. They also make the systems simpler: fewer items to set up, fewer allergens to track, fewer prices to update.

A small menu also changes what is worth measuring. With twelve dishes, the owner can see what sells by watching the pass. Detailed menu analytics matter less than in a venue with sixty dishes.

A small dining room changes the booking decisions. With eight or ten tables, every table matters: a no-show, a long sitting or a badly placed booking affects a large share of the evening. A simple table plan, with clear sitting lengths and a few tables kept for walk-ins, helps the room turn well.

Our guide to designing a restaurant floor plan that sells covers how to get the most from a small room.

Loyalty for a small venue rarely needs a points app. Regulars in a small restaurant come back because they are recognised: their name remembered, their favourite table offered, their usual drink started before they ask. That recognition is the most valuable loyalty scheme there is, and it costs nothing.

Where something more is wanted, keep it simple: a thank-you for a regular's birthday, an invitation to a new menu tasting, or a small gesture on their tenth visit. Our guide to loyalty program ideas that are not points has more.

A small restaurant does not need a complex email strategy. An occasional email to guests who have opted in, announcing a new menu, a special evening or the summer hours, is enough. Write it in the owner's voice, keep it short, and send it when there is something worth saying.

Our guide to an email calendar for a venue with no marketer covers a simple plan.

A small restaurant needs only a few numbers each week: covers, sales, spend per head, food cost and labour cost, and the bookings for the week ahead. Most of these come from the till and the booking page; food and labour costs come from the supplier invoices and the wages.

Our guide to restaurant KPIs worth tracking every week suggests starting with four numbers in a small venue.

The back office of a small restaurant is usually best handled with the accountant's help: accounting software they recommend, a simple process for passing on invoices and the daily sales, and a payroll service if there are employees. A small venue should not try to build its own accounting system in a spreadsheet.

Agree with the accountant what they need each week or month, and make it a routine.

In a small restaurant, the owner's phone is often the office. Systems that work on a phone let the owner check tomorrow's bookings on the bus, update a price between services, or see how the evening went from home. Systems that need a desktop computer in a back office tend to be checked less often.

Check that every tool you choose works properly on a phone, not just on a large screen, before signing up.

A small team cannot run long hours seven days a week without burning out. Look at the covers by day and service, and close or shorten the services that earn least. Many small restaurants close one or two days a week and open for fewer services, which protects the team and often protects the profit.

Publish the hours clearly on the booking page and map listings, and keep them stable, so regulars always know when to come.

A small venue does best with a short list of suppliers it trusts: a main food supplier, a few specialists for the things that make the menu special, and a drinks supplier. Fixed delivery days make ordering a routine rather than a daily scramble.

Small orders can carry delivery charges or minimums, so agree terms that suit the venue's volume, and combine orders where possible.

Online reviews matter a great deal to a small restaurant, because a handful of reviews can shape how new guests see it. Reply to reviews personally and briefly, thank guests for good ones, and respond calmly to criticism. The owner's own voice is a strength here.

Our guide to responding to reviews in four sentences covers a simple approach.

Most small restaurants do not need inventory software. A weekly count of the ten or twenty most valuable items, written on a sheet or in a simple spreadsheet, and a full count once a month, is usually enough to keep food cost visible. Order from a short list of suppliers, on fixed days.

Our guide to spreadsheet vs inventory software covers when a small venue might need to move.

For a small restaurant, one system covering bookings, the till, the kitchen screen, guests and simple reports is usually far easier than several tools connected together. One login, one bill, one set of numbers, and no integrations to break.

The exception is a tool the owner already uses happily that does one job well. There is no need to replace it for the sake of tidiness. Our guide to one system or several covers the trade-offs.

Count the full cost of the systems: subscriptions, card fees, hardware, and the owner's time to manage them. In a small venue, the owner's time is the scarcest resource. A tool that costs a little less but takes two hours more each week is not cheaper.

Avoid long contracts. A small venue needs the freedom to change if a tool does not work out.

A small restaurant's systems should be simple enough to set up in a weekend: the menu with its prices and allergens, the table plan, the booking rules, the staff logins and the card terminal. If a system needs weeks of setup and training, it is probably built for a larger venue.

Test it with a quiet service before relying on it on a Saturday.

With three staff, training is quick, but it must be thorough. Every person should be able to take a booking, open a table, take an order with an allergy, send it to the kitchen, split a bill and close the day. If one person is ill, someone else must be able to do everything.

Short training on real tasks, during quiet moments, works better than a long session.

A small restaurant's systems should fit into about two hours a week:

If the routine takes much longer, look for the tool or process that is eating the time.

A small restaurant is vulnerable when the owner is away: on holiday, ill, or simply at home. Simple systems help, because the team can run them without the owner. A booking page, a till and a kitchen screen that anyone on the team can use keep the venue running.

Make sure at least one other person can open, close, cash up and handle a problem with the systems.

If the small restaurant grows, with more covers, a second room or a second venue, the systems may need to grow too. Choose tools that can grow with the business without a complete change: more devices, more users, more venues, all on the same system.

Our guide to a second venue: what breaks first covers what changes when a business grows.

Here is an illustrative small restaurant. The details are examples.

servearound can run a small restaurant on one system. Each part works on its own, so a small venue can start with what it needs, such as the booking page or the till, and add the rest later. It runs in a browser, on iPhone and iPad and on Android, so the till and a kitchen screen can be ordinary tablets, paired with an 8-character code, and each member of staff signs in with their own PIN.

The booking page carries no commission, sends reminders with a link to change or cancel, and builds guest records from bookings and orders, with tiers such as Regular and VIP set by rules you choose; there are no loyalty points. Pricing is per venue, per month, with no fees per cover, order, screen or user. See pricing, or get in touch.

A point of sale, a card terminal, a booking page if you take bookings, simple guest records and email, and an accountant.

Separate loyalty apps, extra reporting tools, social media schedulers, inventory software and multiple booking platforms.

One that runs on ordinary tablets, is quick to learn and use, handles a short menu with allergens, and has no fees per terminal, user or order.

One screen or a small printer is usually enough to keep orders clear on busy nights.

Mainly through recognition: names, favourite tables and drinks, and small gestures for regulars.

About two hours for a small venue. Much more means something is too complicated.

Usually its own booking page is better, because per-guest fees are hard to carry on thirty covers.

Choose systems that can add devices, users and venues without a complete change.

A simple one, yes: the menu, the hours, the address, the booking link and a few good photos. Many small venues also rely heavily on their map listing, so keep that just as current. Our guide to the restaurant website that only needs five pages covers what to include.

A small restaurant has the advantage of closeness and the constraint of time, so its systems must be few and simple. Start from the jobs: bookings, orders to the kitchen, payment, knowing the regulars and the week's numbers. Buy a POS for a small venue that runs on tablets, a card terminal, a booking page and simple guest records, ideally in one system, and leave the books to the accountant.

Skip separate loyalty apps, extra reporting tools and inventory software. Use a small menu and a small dining room to keep things simple, think of loyalty for a small venue as recognition rather than points, train everyone on everything, and keep the weekly admin to about two hours.