POS and QR Menu Basics: A 60-Minute Compact Training Plan

A small cafe in Kadikoy has exactly sixty minutes before a new server hits the floor on Friday night. Inside that hour the trainer has to cover both the POS and the QR menu — which means every block of minutes must earn its place.

15 minutes: interface walkthrough

The first 15 minutes are pure orientation. Walk the new hire through the POS layout: table map on the left, category tabs across the top, quick-access buttons on the right, and the payment strip at the bottom. Name zones aloud — "this is tables, this is categories, this is payment" — so the map sticks.

End the block with a fast drill: trainer calls out a random table number, server taps it within three seconds. Three or four repetitions and the navigation becomes muscle memory rather than a slow visual hunt.

20 minutes: order entry and table transfers

Block two — 20 minutes — is live scenarios. Two teas, one coffee, a toast with a modifier ("no butter"), then transfer the open ticket from table 4 to table 7 because guests moved. Every scenario should mirror what actually happens on the floor, not a sanitized demo.

• Adding items and increasing quantity from the same screen
• Where modifier notes go and how the kitchen sees them
• Transfer and merge flows for shifting parties

15 minutes payments + voids, 10 minutes QR menu

Block three takes 15 minutes on payments and corrections: cash, card, split check, and a void with the right reason code. Voids deserve attention — wrong-reason voids skew nightly reports more than people expect. The final 10 minutes introduce the QR menu: what guests see when they scan, where in-seat orders land on the POS, and how the server confirms them.

Close the hour with a 10-question mini-test: 5 POS, 3 payment, 2 QR. Eight correct unlocks floor authorization; gaps get a five-minute reinforcement next shift instead of being ignored.

FAQ

Is one hour really enough? For core flows yes; stock counts and deep reporting need a second session within the first week.

Is the mini-test mandatory? Not strictly, but cafes that use it report fewer wrong-item tickets in the new server's first weekend.

Why put QR menu last? Once the server understands ticket flow, QR-borne orders make sense in two minutes instead of fifteen.

Found this helpful? Share it.