Run a school tuck shop without the break-time crush

Anyone who has worked a school tuck shop knows the shape of the day. Nothing for two hours, then the bell goes and three hundred learners arrive at one window at once. The volunteers take cash, count change, shout across the counter and try to remember who asked for the toastie without tomato. By the time the queue clears, the next bell is ringing and the learners at the back have eaten nothing.

A market stall on a Saturday has the same problem, just spread over a longer day. That is the problem YesChef was built for, and it turns out a tuck shop needs most of the same answers.

Take the order away from the window

The window is slow because it does everything: choosing, asking, paying, change, handover. YesChef splits those apart. A learner scans the QR code on the wall, picks from the menu on their phone and pays with the method your tuck shop already uses. The order lands on your screen, you accept it, and they get a three-character collection code by SMS or WhatsApp when it is ready. The window only does the handover. There is no app to download either: the menu opens in the phone's browser, so a learner can order the first time they see the code.

Not every learner has a phone at break

Plenty of schools keep phones in bags until home time, and younger learners often do not have one at all. That is what the self-service kiosk is for. Put a tablet at the window in kiosk mode and learners tap through the same menu themselves, then pay in person at the counter with cash or your card machine. Kiosk orders paid in person carry no service charge, and the order still drops into the same queue as everything else.

Stop selling the last pie twice

Tuck shops bake or buy in a fixed number of everything. Set a daily stock count per item and YesChef counts down as orders come in. When the last chicken pie goes, it shows as sold out on every phone and the kiosk at the same moment, so nobody pays for something that is already gone and nobody has to be sent back to the queue.

Allergens on the menu, not on a volunteer's memory

Each menu item can carry badges for nuts, gluten and dairy, and learners can filter the menu to vegetarian, vegan, halal, kosher or gluten free. It is not a replacement for knowing which learners have allergies, but it means the information is on the screen every time, not dependent on who happens to be behind the counter that day.

Built for volunteers and a treasurer

Many tuck shops are run by a rota of parents and a committee that has to account for every rand. YesChef fits that:

• Volunteers sign in with a staff role. They see orders and the kitchen screen, not your settings, prices or reports.
• Online payments settle straight into the tuck shop's own Yoco, SnapScan, iKhokha, Zapper or Paystack account. There is no YesChef wallet in the middle.
• Cash up at the end of the day reconciles what the system says you sold against what is in the till, by payment method.
• Reports show what sold, what ran out and what each item cost you to make, so the committee can see which lines actually raise money.

Open when the school is open

Set your trading hours for the school week and add closed dates for public holidays and the school holidays. If you need to stop orders early, because the pies are finished or the hall is booked for exams, one switch pauses ordering until you turn it back on. Build a winter menu and a summer menu once, and swap which one is live when the term changes.

Getting started

• Sign up, connect your payment account and build the menu. It takes about as long as a staff meeting.
• Print the QR code for the wall by the window, and set up a tablet in kiosk mode if your learners will not have phones.
• Add daily stock for everything you make in batches.
• Give the volunteers a staff login and run one quiet day before the first busy one.

The goal is simple. The bell goes, the window hands out food instead of taking orders, and everyone has something to eat before the next lesson starts.