Key takeaways
- Train by role. Cashiers, servers, kitchen staff and managers use different parts of the POS and need different sessions.
- Keep sessions short and hands-on, and practise real orders from your own menu.
- Give each role a one-page cheat sheet. Bilingual English and 中文 sheets help mixed teams.
- Spend extra time on voids, split bills and refunds, where most mistakes and losses happen.
- Check competence with a short practical test, and track void rates and ticket times after go-live.
A new POS can speed up service, or slow it down for weeks. The difference is usually training. Staff who have practised a busy lunch on the new system before opening day will cope. Staff who saw a single demo will call the manager every ten minutes.
This guide covers POS training for staff in Singapore restaurants, cafes, bars and shops: what each role needs to learn, how to run the sessions, how to check that people are ready and how to train new hires later. It focuses on the POS itself. For wider onboarding, such as food safety and service standards, see our restaurant staff training checklist. For the full rollout, see our POS implementation plan.
Why POS training needs its own plan
Most staff have used a POS before, so owners assume they will pick up a new one quickly. The basics usually are quick. The problems come from the less common tasks: a customer who wants to split a bill three ways, a dish sent to the kitchen by mistake, a refund on a card payment, a modifier the old system handled differently. These tasks are rare enough that staff do not practise them, and costly enough that mistakes show up in your reports.
A training plan also protects your controls. If staff do not understand why voids need approval, they will find workarounds. If managers do not know how to read the void report, nobody will spot a problem. Training is where you set the habits your cash controls depend on.
Role-based training: what each team needs
Cashiers and counter staff
- Signing in with their own account, never a colleague’s.
- Finding items fast, adding modifiers and notes.
- Taking every payment method you accept. ChaChaCha supports PayNow, PayLah!, NETS, Visa and Mastercard, and GrabPay.
- Split payments, for example part cash and part card.
- Applying discounts, vouchers, loyalty points or stored value, if you use loyalty.
- Handling a declined card and reprinting a receipt.
- Calling queue numbers, if you use the queue system with SMS notifications and a digital queue display.
Servers and floor staff
- Opening tables, moving guests and merging or transferring tables using table management.
- Running tabs, especially in bars. See our bar POS page.
- Splitting bills by item, by seat or by amount.
- Sending courses to the kitchen and adding items to an open order.
- Handling QR orders that arrive at their tables.
- If you plan to take orders on handheld devices, ask us to confirm which devices are supported and train on the device staff will use.
Kitchen and KDS users
- Reading tickets or the kitchen display, including modifiers and notes.
- How station routing works, so each station knows which items it will receive.
- Bumping orders when complete, and what order prioritisation and prep timers show.
- What to do when a ticket looks wrong: who to tell and how to avoid remaking dishes unnecessarily.
- Kitchen tickets can be printed in English or 中文, so confirm which language each station prefers before training.
Managers and supervisors
- Approving voids, refunds and discounts, and understanding why each needs approval.
- Opening and closing the day, counting cash and reading the end-of-day report.
- Changing prices, marking items as sold out and adjusting the menu.
- Setting staff permissions and adding or removing staff accounts.
- Checking reports for sales, voids and discounts by staff member.
- Following the outage procedure. ChaChaCha keeps taking orders if the internet drops and syncs later, but managers should know what to do and who to call.
A POS training plan you can copy
Short, focused sessions work better than one long demo. Run them in the week before go-live, with a refresher on the day before opening.
| Session | Who | Length | Content | Done when |
|---|---|---|---|---|
| 1. Basics | All staff | About 45 minutes | Signing in, menu layout, placing an order, where tickets go | Each person places and pays for a simple order |
| 2. Counter | Cashiers | About 1 hour | All payment methods, split payments, discounts, loyalty, receipts | Completes a payment on every method you accept |
| 3. Floor | Servers | About 1 hour | Tables, tabs, split bills, coursing, QR orders | Runs a four-table scenario without help |
| 4. Kitchen | Kitchen team | About 30 minutes | Reading tickets or KDS, routing, bumping, prep timers | Handles a burst of test orders at their station |
| 5. Managers | Managers and supervisors | About 2 hours | Approvals, voids, refunds, menu changes, end-of-day, reports, permissions | Closes a test day and explains the report |
| 6. Rush drill | Full team | About 1 hour | Simulated busy service using your real menu | No manager call-outs for routine tasks |
The lengths above are suggestions, not benchmarks. Adjust them for your menu complexity and your team’s experience. Every ChaChaCha package includes staff training; ask us to confirm how sessions are scheduled for your outlet and who should attend.
Practise safely: test mode and test transactions
Staff learn fastest by pressing buttons, so give them somewhere to practise without affecting real sales. Some POS systems offer a training or sandbox mode that keeps practice orders out of reports. Ask us to confirm whether a training mode is available for your ChaChaCha setup, and how to handle practice transactions.
If you practise on the live system before opening, agree with your vendor how test orders will be cleared or marked so they do not distort your first week’s figures. Never practise payments with real customer cards. Use a small real payment on a staff card if you need to test a card terminal, then refund it, and make sure a manager records it.
Cheat sheets in English and 中文
A one-page cheat sheet by each terminal saves more time than any refresher. Keep it to the tasks people forget, not the basics.
- Cashier sheet: split payments, applying a voucher, handling a declined card, reprinting a receipt.
- Server sheet: splitting a bill, transferring a table, adding items to a sent order.
- Kitchen sheet: what each station receives, how to bump, who to tell when a ticket is wrong.
- Manager sheet: approving voids and refunds, end-of-day steps, outage procedure, vendor support contact.
Many Singapore teams mix English and Chinese speakers. ChaChaCha has an English and 中文 interface and kitchen tickets, so write cheat sheets in both languages and use the same button names that appear on screen. Take screenshots from your own setup rather than generic images. Add the sheets to your SOPs so they stay current.
Common mistakes to train out early
Voids
The most common error is voiding an item that has already gone to the kitchen, which wastes food and can hide mistakes or misuse. Train staff to check the order before sending it, and to ask a manager for any void after sending. Explain that the void reason matters: “customer changed mind” and “kitchen error” lead to different fixes.
Split bills
Staff often split a bill the wrong way, for example by amount when the customers wanted to pay by item, then void and restart. Practise each type of split with realistic groups, including a table where one person pays for drinks and the rest is shared.
Refunds
Refunds should go back to the original payment method where possible. Train staff that a card payment should not be refunded in cash from the drawer, and that refunds need manager approval. Managers should know how to find the original transaction.
Other habits to watch
- Sharing logins, which makes every report meaningless.
- Using free-text notes instead of modifiers, which the kitchen may misread.
- Forgetting to mark items as sold out, which leads to QR and delivery orders the kitchen cannot fill.
- Opening the cash drawer without a sale.
How to check staff are ready
Do not rely on “Any questions?” at the end of a session. Give each person a short practical test at their terminal, based on real scenarios from your menu:
- Take a dine-in order for three people with two modifiers and one allergy note.
- Split the bill by item and take payment by card and PayNow.
- Process a refund on a previous sale with manager approval.
- For managers: close a test day and explain what each line of the report means.
Mark each task as done without help, done with help or not done. Anyone with “not done” gets a short one-to-one session and repeats the test before working a busy shift alone. Pair less confident staff with a stronger colleague for their first services.
Training new hires after go-live
The launch training is a one-off. Staff turnover is not. Build POS training into your normal onboarding so every new hire learns the same way:
- Nominate a POS champion per shift who knows the system well and trains others.
- Use the same cheat sheets and practical test for every new hire.
- Create the staff account with the right role and permissions on day one, and remove accounts promptly when people leave.
- Let new hires shadow for at least one full service before taking payments alone.
- Run a short refresher when you change the menu, add a payment method or launch a feature such as kiosks or delivery.
Local support is included in every ChaChaCha package, so managers can contact us when they are unsure how to do something rather than guessing.
Measuring whether training worked
Your POS reports tell you how well training has stuck. Review these in the weeks after go-live:
- Void rate. Value of voids divided by gross sales, by staff member and by reason. A high rate for one person usually points to a training gap before anything else.
- Discount and refund patterns. Check that approvals are being used as intended.
- Ticket times. Time from order to completion on the KDS. Slow times may come from order-taking errors as much as from the kitchen. See our guide to speeding up ticket times.
- Manager call-outs. Ask managers which tasks they are still called for. Those go on the next refresher.
- Cash variances. Differences between counted cash and the end-of-day report.
Our restaurant KPIs guide explains how to calculate and review these numbers. Set your own baseline in the first few weeks, then look for improvement rather than aiming for an outside benchmark.
ChaChaCha is powered by AppsPOS, a Singapore company working with F&B businesses since 2013. If you are planning a POS change and want to see how training would work for your team, contact us or read more about our restaurant POS.