7:00 AMReceive the menu
A morning phone notification brings the breakfast menu to the student. Lunch and dinner updates follow your schedule.

Connect daily meals, attendance and campus cafeteria delivery—with planning information for your teams and simpler food choices for students.
7:00 AMA morning phone notification brings the breakfast menu to the student. Lunch and dinner updates follow your schedule.

“Dinner party tonight. I’ll skip the mess.”
Students voluntarily opt out when they do not plan to eat. Your team sees the expected participation before preparation.

Connect meal access and attendance through the configured QR or face-device process.
Review separate breakfast, lunch and dinner attendance totals against the number expected.
University-controlled setting
Define the students, schedules and meal access rules for each mess.
Set participation cutoffs and how your team uses the information.
Where multiple vendors exist, enable students to choose, book and pay for their preferred mess.
Campus cafeteria · hostel delivery

Students browse the campus cafeteria menu and place a food order through FretBox.

The university’s cafeteria team receives the order and prepares the food.

Campus staff deliver to the hostel room within the university’s configured service rules.
Your university defines cafeteria availability, ordering hours and the hostel rooms served.
In the university’s view

Compare eligible students, voluntary opt-outs, expected diners and actual attendance for each meal. Use the numbers to prepare the service and review participation afterwards.
Explore reporting & governance| Meal | Eligible | Opted out | Expected | Attended |
|---|---|---|---|---|
| Breakfast | 1,200 | 120 | 1,080 | 1,042 |
| Lunch | 1,200 | 180 | 1,020 | 986 |
| Dinner | 1,200 | 90 | 1,110 | 1,075 |

Explore the student experience, the connected teams and your university’s rules.