How to organise orders in a small restaurant
A small restaurant has no floor manager or expeditor: the same person takes the order, serves, takes payment and sometimes helps in the kitchen. That is why a badly written ticket is expensive: a dish that never arrives, a steak cooked wrong or an allergic guest given the wrong answer. Here is what works to get each order from the table to the kitchen cleanly.
1. A table system the whole team understands
It all starts with knowing which table each dish belongs to. Number your tables the same way every day and keep the floor plan where new staff can see it. If you have a terrace, give it its own numbering or a prefix (T1, T2…) so nobody mixes up table 3 inside with table 3 outside.
Within each table, many restaurants use seat numbers: seat 1 is the one nearest the door or the bar, then you count clockwise. Whoever runs the food knows who gets what without asking “who had the steak?”. You do not need to record it in the system; it just has to be a habit the whole team shares.
2. Write tickets the kitchen does not have to guess
A good ticket can be read in two seconds. A few rules that help:
- Quantity first, then the dish: “2 Croquettes”, not “Croquettes x2” at the end of the line.
- Changes under the dish, stated clearly: “NO onion”, “sauce on the side”, “medium-rare”.
- Always the steak doneness, even if the guest says “however”: write “medium” and the kitchen will not have to come out and ask.
- Agreed abbreviations, written down on a sheet in the kitchen. If every server invents their own, trouble starts the day the usual one is off.
- A free note only for what the options do not cover: “for a child, half portion”, “bring with the starters”.
Tip: before sending, read the order back to the table (“two croquettes, one salad with no onion and the steak medium”). Ten seconds that save you sending a plate back.
3. Kitchen on one side, bar on the other
Drinks should not wait for the kitchen to read its ticket, and the kitchen does not need to know how many beers the table ordered. Always split what the bar prepares (drinks, coffees, display desserts) from what the kitchen prepares. On paper, use two pads or two colours; with a POS, each product should know where it goes.
4. Courses and “firing” the mains
A small kitchen gets swamped if every dish arrives at once. The usual approach is to send starters when the order is taken and keep mains on hold until the table has finished; then the server “fires” the mains. Agree one single way of doing it with the kitchen (a word, a signal on the screen) and stick to it.
5. Allergens: ask, write it down, make sure the kitchen sees it
In the European Union, Regulation (EU) No 1169/2011 requires businesses to tell customers about the 14 mandatory allergens, including for food that is not prepacked, such as restaurant dishes. In practice:
- Keep the allergen information for each dish up to date and to hand, not just in the chef’s head.
- When a guest mentions an allergy, write it on the ticket so it stands out, rather than passing it on by word of mouth.
- If you change a recipe or a supplier, check its allergens the same day.
If you are unsure how the rules apply to your business, ask your local food safety authority or adviser.
6. One place where the kitchen sees the order
The worst chaos happens when orders arrive by several routes: paper on the pass, a shout from the bar, a message from the manager. Choose a single channel: either the kitchen printer with tickets in a row, or a screen. What matters is that the kitchen sees what came in first and how long each table has been waiting.
7. The rush: fewer decisions, more routine
8. Training new servers
One sheet of paper is enough: floor plan, abbreviations, how mains are fired and how an allergy is noted. Let new staff take orders alongside someone for their first services and correct each mistake on the spot. And decide who can cancel something already in the kitchen: if anyone can, nobody will know later why a dish is missing from the till.
How Bipe helps
Bipe is a cloud POS for bars and restaurants that turns these habits into screens. All of this is included in the Pro plan:
It costs €29.90/month including VAT, with no commitment and a 15-day trial. See everything at Bipe for restaurants, or at our software for bars if your place is more bar than dining room. If you are comparing systems, also read what a hospitality POS really needs and how to keep selling without internet.
Clear orders from table to kitchen
Tables, kitchen screen, dish options and till in Bipe for €29.90/month. No commitment.
Try it free for 15 days →Frequently asked questions
Is a printed ticket or a kitchen screen better?
It depends on your kitchen. A printer is simple and the paper can be hung up; a screen sorts tickets by waiting time and lets the kitchen mark what is ready. In Bipe you can use either or both.
How do I make sure steak doneness is never forgotten?
Make it a required option of the dish, so the server cannot add it without choosing. In Bipe, each dish’s options can be marked as required.
Do I have to give allergen information in a restaurant?
In the EU, yes: Regulation (EU) No 1169/2011 requires information on the 14 allergens for non-prepacked food too. Keep each dish’s information up to date and write any allergy you are told about on the ticket.
Can servers take orders on their phone?
Yes. In Bipe each server logs in with their PIN from the phone or tablet browser, and the order reaches the kitchen and bar when they press “Send”.