The platform, in full.
Five subsystems, one managed service. Each is documented below the way it is built: plainly, and in order.
Order in a minute. Collect on time.
Students and staff browse the live menu for their campus, filter in three stages (campus, dietary preference, allergen), build a basket and order ahead or schedule for later. Order status tracks live from placement to collection.
Allergen transparency is a safety commitment, not a feature. Every item carries its full allergen declaration in line with UK food information law, including Natasha's Law. Filters exclude; they never merely warn.
ALLOWANCE RULES SET BY THE INSTITUTION.
Settlement without friction, or card data.
Payment is taken on collection, at the point of handover. Where an institution manages daily allowances, the entitlement is applied to the order total before any balance is requested, and settled at the till on collection. The platform records the outcome; it never holds the balance.
The platform holds no card details. Allowance policy (who, how much, when) belongs to the institution and is administered from the management dashboard.
The kitchen sees demand before it arrives.
Each campus kitchen runs a live order queue, sequenced by collection slot. Hold windows keep food at its best; collection and no-show management keep the counter moving; settlement happens at handover.
Leadership sees the estate, not a spreadsheet.
Demand analytics by site, service period and menu line. Menu and campus administration in one place. Production planned against orders, not habit.
Engagement insight can serve attendance and welfare oversight where the institution chooses to use it. It is opt-in, privacy-first and aggregate by design; the platform reports patterns, never plates.
Their name on the door. Ours underneath.
The platform re-brands per institution: their colours, their name, their identity provider. Students see their college, not a vendor.
Each client runs as an isolated instance. No shared tenancy, no co-mingled data, no neighbour effects.