Canteen management runs a prepaid balance per student, spent by card or by a code at the counter, with a daily limit the parent sets and an itemised statement they can read. It removes cash from the queue, which is the reason schools ask for it.
Dietary restrictions can be flagged against a student, but a flag is not a control. Enforcement is the person at the counter.
Cash in a school canteen produces three recurring problems: it gets lost, it gets taken, and nobody can tell a parent what their child actually bought. A prepaid balance solves all three and introduces one new question, which is who sets the limit.
A daily cap set by the parent rather than the school avoids the school arbitrating family decisions about pocket money, and it is the single feature parents ask about first. The balance is theirs; the limit is theirs.
A dietary or allergy note can be recorded against a student and shown at the counter. It is a prompt to a human being, not an interlock — the system cannot know what is in a dish prepared that morning, and a school that treats the flag as enforcement has misunderstood what it is buying.
Phrased the way they arrive, answered so each one stands on its own.
Yes, itemised, in the parent app. That transparency is most of the reason families accept a prepaid balance.
A card or an ID code works; existing RFID cards used for attendance can usually be reused.
It carries forward, and is refundable on leaving. Unclaimed balances appear on the student ledger rather than quietly lapsing.
Checked by the Implementations desk on 6 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.