First restaurant job: what do I need to know about the till?

What really matters on your first day on the till

If this is your first restaurant job, you do not need to know every edge case on day one. You mainly need to enter sales cleanly, choose the right sale, ask as soon as you are unsure, and never push a payment through “somehow.” That is the core of it. As an operator, I do not treat the till as a speed test. I treat it as an ordered workflow: take the order, check it briefly, collect payment correctly, keep an eye on any remaining balance, and only close the sale when it is actually settled. That is why I do not throw new staff straight into every special case. First standard situations, then split payments, then difficult groups. That keeps pressure manageable while the guest still gets calm, reliable service.

I always explain the start from the guest’s view and the team’s view at the same time. The guest expects the order to be right and payment to feel simple, not confusing. The server does not need heroic improvisation to deliver that; they need orientation. In Bonzumo, the order, table, payment, and closing process stay connected to the same data basis. That matters because I do not want anyone jumping between memory, scraps of paper, and separate lists. If a dessert is added later or a group wants to pay separately, the connection remains visible. For training, that is crucial: it is better to handle one sale slowly and transparently than to close something in a rush that the guest, the shift lead, and the office can no longer understand afterward.

What you actually do at the till

At the till, you are not just tapping products on a screen. You are documenting a real guest situation. First you need to recognize the context: table service, counter service, or a fast direct sale. Then you enter the items, check quantity and selection, and, in table service, add an order note if needed. At the beginning, most mistakes do not happen because the system is too complicated. They happen because, under time pressure, someone opens the wrong table or picks a similar-looking item. That is why I train the sequence first: look, select, cross-check, then move on to sending or taking payment. Anyone who learns those four steps causes fewer follow-up problems than someone who only reacts quickly to the screen.

A simple first-shift example makes that clear: table 14 orders two spritzers and one daily special, then later adds an espresso. If the first order is entered on table 41 by mistake, not only is the bill wrong, but the work in the kitchen or service pass can get confused as well. That is why I set up table and area overviews so staff can orient themselves spatially, not just by number. I do not expect someone in a busy room to juggle table numbers in their head. I expect the screen to reflect the dining room in a way that makes sense. Someone who starts safely in one small section learns faster than someone thrown everywhere at once. I usually show this connection through Keep every sale connected to the service around it, so individual taps become one understandable workflow.

Why ordering and paying are two different steps

One of the most important lessons for beginners is this: an order is not yet a payment. First, you record what the guest ordered. Later, the guest pays for it, sometimes in full, sometimes partly, sometimes with a mix of cash and card. If you do not separate those two steps clearly, you are more likely to close something too early out of nervousness or lose track of what is still open. In Bonzumo, the remaining balance stays attached to the sale, and a table is only closed when nothing is outstanding anymore. In my training, that is the single most important safety rule. New staff should understand that an open table is not suspicious. Very often, it is simply the normal state of a table until the guests really want to settle.

In daily service, that can look like this: a group of four orders together. Later, one person wants to pay for their drinks in cash straight away, while the others stay seated and split the rest at the end. Then the task is not to quote some total quickly and hope it works out. The task is to record the intermediate state cleanly. Just as important is the separation between revenue and tip. If food and drinks worth 100 euros were sold and the guest pays 105 euros, then 5 euros are a tip, not additional sales revenue. Every server should understand that difference, even without a bookkeeping background. Anyone who learns it early runs into fewer explanations at the end of the shift and can answer questions clearly instead of relying on memory.

The tricky cases: split payments, tips, and invoice details

As soon as several people pay together, the most important thing at the till is calm. I teach my team to clarify the payment wish properly first and only then start entering it. Some groups want to split by items, meaning each person pays only for what they personally had. Other groups want the remaining amount divided into equal shares because everything was ordered jointly. Those are different situations, and a new server has to learn that difference. A common pitfall is starting the split before the group has even agreed among themselves. Then a simple payment turns into a messy back-and-forth. My rule is: ask first, confirm second, enter it third. That prevents rushed assumptions and saves everyone from correcting a half-built payment flow while guests are waiting.

I handle tips and invoice details with the same care. If the total is 46 euros and the guest says, “Make it 50,” it has to be clear that 4 euros are meant as a tip, not 50 euros of sales. That separation is part of clean till work. If someone needs an invoice with recipient details, those details go into the intended process, not onto a scrap of paper that can get lost before the end of service. Beginners especially need permission to take that extra moment. That is why I do not leave a new colleague alone with a large group that has complicated payment wishes in their first shifts. First come safe standard checkouts, then mixed payment methods, then split bills. We also practise the payment flow through Finish a good visit with a clear payment experience, so everyone knows which step belongs where.

What you should never do when something goes wrong

Mistakes at the till are normal at the start. They only become truly problematic when someone tries to smooth them over in secret. I make that point very clearly in training. No one should book the wrong item, estimate an amount, or close another table just to make an awkward moment disappear. If something was entered incorrectly, the correction has to happen on the real sale. In Bonzumo, receipts, cancellations, timestamps, and authorized actions remain traceable. For me, that is not a culture of distrust toward staff. It is protection for everyone involved. If someone corrects cleanly, the case can still be explained later. If someone improvises, a small tapping error often grows into a much bigger problem for the guest, the service team, and the end-of-day close.

An everyday example makes this easy to see: a dessert was accidentally entered twice even though it was served only once. The bad solution would be to delete something somewhere else or quietly offset the amount with another position. The right solution is to call the shift lead and check the actual sale directly. That is exactly why I organize one clear error rule: stop, show it, correct it together, explain it briefly. The biggest pitfall is often shame. New staff want to appear competent, so they ask too late. I normalize the opposite: questions are explicitly welcome. A fair till culture means nobody is humiliated for reporting an honest error in time. I would much rather praise that person than someone who stayed silent and left a confusing trail for the next colleague.

How I organize the first shifts so they are fair and learnable

Anyone who is new to hospitality is learning guest contact, walking routes, products, timing, and team communication all at once. It would be unfair to treat the till as a complete endurance test on top of that. I therefore stage responsibility deliberately. In the first phase, a new person handles only small, manageable cases: opening a small table, entering a few items, adding a reorder, and finishing a simple payment. In the second phase come tips, invoice details, and smaller split payments. Only after that do I put them into full evenings with many open tables, several payment methods, and spontaneous special requests. That order is not a luxury. It is risk control. If I demand everything too early, the uncertainty lands directly with the guest first and later shows up again in the daily closing.

Support matters just as much as task size. I do not only schedule enough people overall; I schedule real accessibility. For example, a new colleague on an early evening shift might serve only six tables in one clearly defined section, while the shift lead remains within sight and takes over complex group bills at first. That way, the colleague learns in real service without being abandoned in every special case. I also work with clear responsibilities. Not every person needs the same permissions for sensitive corrections from day one. That is not a demotion. It protects beginners from unnecessary pressure and protects the business from avoidable damage. An entry phase is fair when someone becomes more secure step by step instead of being judged in week one by exceptional situations that even experienced staff still handle with concentration.

How you can tell you are slowly becoming safe on the till

You are not becoming safe on the till because your tapping gets impressively fast. You are becoming safe because your sales remain coherent. Good signs are these: you find the right table without long searching, you check items and quantities before sending them, you keep ordering and payment separate, you ask when a payment wish is unclear, and you do not close a sale while a balance is still open. It also matters that you can explain a special case in one short sentence. If you can say, “One part has already been paid in cash, the rest is still open and will be split by card in a moment,” you are usually working more cleanly than someone who only looks quick but cannot reconstruct anything later.

That is why I do not judge a good start by showmanship. I judge it by traceability. If a question comes up after the shift, I want to be able to review the path from the first item to the payment. For me, that is the whole point of a shared data basis: order, part-payment, receipt, and closing belong together and should not exist only in the memory of individual employees. For you as a beginner, that is actually reassuringly simple. You do not have to know everything at the beginning, but you do have to record each step honestly and in line with the real sale. If you work slowly, attentively, and with the confidence to ask, you are on the right path at the till. In hospitality, that matters more in the long run than hectic fake certainty ever will.