FIELD NOTES / MEAL ISSUANCE
A scan should mean one confirmed meal.
A QR code is the start of a check-in, not proof on its own. Enrollment, meal entitlement and the final server confirmation matter too.
The QR identifies a check-in opportunity
Scanning should start a request that checks the student, mess, service window and purchased entitlement. A readable code alone must not be treated as proof that a student can receive any meal.
Wait for the final confirmation
The serving team should issue a meal only after the supported flow confirms it. When connectivity fails, explain whether the request is still pending; do not show a successful meal merely because a button was tapped.
Retries must not mean extra meals
A double tap, a scan repeated after reconnecting, or competing QR and PIN submissions should not consume the same meal twice. Ask the software provider to demonstrate the duplicate-request behavior, not just the happy path.
Separate dine-in from delivery
Breakfast stays dine-in only in MessPass. Delivered meals use the delivery confirmation flow, and students should share their delivery PIN only after collection. An owner skip or failed delivery is not a successfully delivered meal.