FIELD NOTES / BUYING GUIDE
Choose for the busiest meal window.
A polished demo is useful. Clear permissions, sensible exception handling and understandable records are what matter when everyone arrives for lunch.
Check the business fit first
A recurring student mess and a pay-per-item canteen have different needs. Ask whether the system supports your actual meal plans, breakfast rules and recurring enrollment rather than assuming every food-business product fits.
Ask who can change money and access
Request a demonstration of owner, worker and student permissions. A worker should not receive access to unrelated routes; a browser should not be able to invent a wallet balance. An attractive dashboard is not evidence of proper authorization.
Compare the complete cost
Separate meal prices, platform charges, applicable tax, payment-provider charges and hardware or support commitments. Do not compare only the largest number on a pricing card. Ask what is included and which claims are contractual.
Rehearse the busiest service
Run a pilot with the people who actually serve and deliver meals. Try a retry, a closure, a failed delivery and a support request. Record what each person sees, reconcile the outcomes, and expand based on evidence rather than a demo alone.