Checks before and after service
What to check in EduMeal before the first service, before every service day and after it, and what to do when something fails.
When you need this
Before the first service in a new school and before every ordinary day. This is the list for the admin; the list for the kiosk operator is on the page Prepare the tablet for service.
Before the first service
- School details: the name, time zone and status are correct.
- Every active student has a class and a category (Students).
- Every meal type is active on the right days and at the right time (Meal types).
- For every "category - meal type" pair that is served there is a valid rule with a tariff (Meal rules). The counter Without a current price on the Tariffs page is zero.
- The repeat-scan guard is set the way the school wants (School details).
- Every student who is served has an active QR code or card, and the printed sheets are current (QR codes).
- Kiosks are active, registration requests are approved, rejected or cancelled, and stale tablets are switched off (Kiosks). The counter Pending requests is zero.
- Before the first monthly documents are printed: the school calendar holds the holidays and vacations of the month, and the report settings hold the approver, the signers and the act groups.
Before every day
- If you changed anything (classes, students, categories, meal types, rules, codes), press Refresh Session on every kiosk while it is online and do one controlled scan before the line opens. Do not consider the settings ready while a kiosk still refuses.
- Look at new kiosk registration requests (Kiosks).
After service
- Make sure the kiosks sent everything: Offline and sync, Close the service.
- Look at flagged servings in reports (the Flagged servings tab, see Reports).
- If a serving was missed, enter it (Manual servings).
- If something changed unexpectedly, look at the audit log.
What you will see
When all items are done, a kiosk passes the controlled scan and students get meals without refusals.
If something goes wrong
When you ask for help, give the exact text of the message from the screen. Most refusals are empty required fields, records from another school, wrong dates or meal windows, or missing access. If it is a validation message, fix the data and try again. If it is about access or the school, stop and check which account you are in, which school and which record is chosen before you change anything. When access is missing, the page shows No access, the reason and the Home button. It opens in the language chosen in your account.
What the kiosk said, and where to go:
| The kiosk says | Where to go |
|---|---|
| No active meal rule for this student. | Meal rules |
| Meal type is inactive., Meal is outside the service window., Meal is not served today. | Meal types |
| Token is not recognized on this kiosk., Token is inactive. Request a new QR code. | QR codes |
| Student is inactive. | Students |
| Kiosk deactivated | Kiosks |
The full list of refusals is on the page Why a student was not served.