🍲Canteen, Kitchen & Store

Yes. The Canteen & Store module lets you run a temple canteen, kitchen, or prasadam/gift counter. You can build and manage the menu (with portions and pricing), take and track orders, and run the kitchen itself under Canteen → Kitchen — logging what was cooked each day, seeing what is left after sales, tracking raw materials like rice, dal and oil, and receiving low-stock alerts so popular items can be restocked in time. Dishes mark themselves sold out once a tracked batch runs out. Every dish can carry a photo — upload your own, paste an image URL, or generate one from the dish name with a single click, so a new menu does not need a photographer. Those photos appear on the menu cards and beside each dish in the Top Performing Menu Items ranking under Canteen → Analytics. You also control when orders may be taken: set per-day business hours in Canteen → Settings, or turn on "Open 24/7" to accept orders at any time — and pause ordering instantly with the "Accept New Orders" switch. It also includes promotions, reviews, and basic sales analytics — keeping food and store operations in the same platform as the rest of your temple.

Yes, under Canteen → Kitchen, and the difference from a restaurant BOM is deliberate. Generic restaurant software models a per-portion bill of materials: grams of dal per idli, millilitres of oil per vada. A temple kitchen does not work that way. Nobody weighs dal per idli — cooks make a vessel of sambar, a tray of pongal, a batch of poori — so per-portion figures have to be invented, and an invented number that nobody maintains quietly becomes confidently wrong, which is worse for a kitchen than having no number at all. Temple Hub therefore uses a BATCH RECIPE: one entry per dish that says what a single batch yields and what it consumes ("one batch yields about 120 portions and uses 5 kg idli rice and 1.5 kg urad dal"). The cook logs the batch once per cook session — not once per plate — and raw-material consumption follows automatically, scaled to the portions actually made, so a half vessel counts as half. You get real consumption figures with a fraction of the data entry, and the figures stay true because they match how the kitchen actually behaves. Tracking works in two tiers so nothing is blocked on data entry: every dish gets portions made, sold and left over for free (counter sales and food bought through a temple event both count against the same tray), while only the dishes worth it — usually the ten or fifteen that are most of your volume — need a batch recipe. Stock on hand is always calculated from batches and orders rather than stored as a running total, so it cannot drift out of step when an order is refunded or edited. Low-stock alerts fire against each ingredient's reorder level, and dishes mark themselves sold out once a tracked batch runs out — never dishes you have not started tracking, so adopting this does not make your menu disappear. The number that actually reduces wastage is the variance: what the batches should have consumed, compared against a physical shelf count. That gap is your over-portioning, spoilage or loss, and raw totals on their own never show it.

Yes, when the canteen order is placed for a selected devotee at the counter. Each such order links to that devotee's profile, so their canteen spend appears in two places for admins: a "Canteen Spend" section on the devotee's profile in Manage Devotees (lifetime and this-year totals and order count, broken down by branch when you run more than one), and a "Top Customers" panel in Canteen → Analytics that ranks devotees by attributed spend net of refunds. Orders taken without picking a devotee stay as walk-ins and are grouped into a single "Walk-in / unattributed" line rather than guessed at. To keep history unified, when a cashier types a phone or email that matches an existing devotee the counter offers that profile with one tap instead of creating a duplicate. Canteen spend is a purchase, so it is always kept out of giving totals and never appears on tax letters. Temples can also show each devotee their own canteen history on the temple website's My Profile — turn "Canteen spend on the website" on or off under Booking Rules → Canteen Spend, and choose how much detail to show (itemized dishes, per-order summary, or totals only).

Yes, an optional one — off by default. Configure it under Booking Rules → Canteen Spend: choose a punch card (every Nth qualifying order earns a reward, with an optional minimum order value), points ($1 spent earns points redeemable in whole hundreds), or spend tiers (annual-spend recognition bands with no redemption). The "Loyalty Program" quick action in Canteen → Settings is the same on/off switch, so either page controls the one program. Once on, the canteen's New Order screen shows the selected devotee's live progress under their name — punch count, points balance, or current tier — and flags a punch-card order that completes the card before payment so the counter can honor the reward. Balances are always calculated from the devotee's actual order history (net of refunds), never stored, so changing settings can never strand points. Only orders placed for a selected devotee earn loyalty — walk-ins earn nothing — and automatic redemption at the counter arrives in a later release.