Ask any PG resident what the single most common source of low-grade friction is, and it won't be rent. It's food — specifically, not knowing what's coming, and having no way to say in advance whether they'll be there for it.
Quick answer (for the impatient)
A PG can now publish what the kitchen serves — by day and by meal slot, as a real record rather than a whiteboard.
Menu slots carry options with a veg marking, so residents can see what's actually available to them.
Residents can indicate whether they're taking a meal, which is what turns the menu from information into planning.
The whiteboard problem
Most PGs run their mess on a weekly cycle that lives in the cook's head, a laminated chart from 2022, or a whiteboard nobody has updated since the last cook left. The result is a small daily uncertainty for every resident and a large weekly guessing game for the kitchen.
The kitchen's version of the problem is more expensive. Cooking for forty when twenty-eight are eating is waste every single day, and the only defence most PGs have is cooking slightly less and hoping.
What the menu record actually holds
The mess menu is structured rather than a note: the days, the meal slots within each day, and the options within each slot. Each option carries a veg marking, which matters more in an Indian PG than almost any other attribute — a resident who doesn't eat non-veg needs to know what's in the slot before they arrive at it.
That structure is what makes the menu publishable rather than just recorded. A resident can see the week ahead instead of finding out at 8pm.
The part that changes the economics
Residents indicating whether they're taking a given meal is the feature that pays for itself. A PG that knows on Tuesday morning that eleven of its forty residents are out for dinner can cook for twenty-nine.
Compounded daily across a year, that's a serious number for a business whose margins are thin and whose largest variable cost is food. It also removes the standing argument about residents who paid for meals they didn't eat, because the record of who opted in exists.
Where AXOIX is honest about its limits
This is menu publication and meal indication, not inventory. A PG mess still has no ingredient stock tracking — that gap was confirmed absent in the batch-2 audit and hasn't changed. Nothing here deducts dal from a store.
It doesn't cost your food. Recipe-level costing exists in the restaurant module, not the PG one. Don't expect a per-plate cost figure.
Residents indicating a meal is not a binding commitment unless you make it one operationally. The system records the intent; enforcing it is a house-rules decision.
No vendor or purchase management. What you buy and from whom is still outside the system.
FAQ
Can residents see the menu themselves?
Publishing the menu is the point of structuring it. Confirm what's visible on your tenant portal for your setup — the portal post covers what residents can see generally.
Does this connect to what residents are billed?
Meal plans are the billing side — see meal plans and billing. The menu is what's served; the plan is what's charged.
Can I run different menus for different floors or blocks?
Confirm scope for your property configuration before promising it to residents.
The bottom line
A mess menu that exists as a record rather than a rumour fixes a daily annoyance for residents and a daily waste for the kitchen. Neither is dramatic. Both happen 365 times a year.
See how meal plans get billed, how tenant complaints are handled, or pricing.
Say what's for dinner, in advance. Start free →
Comments