🪔Puja & Bookings

Yes. Temple Hub runs on any iPad in a counter-top stand as a full front-desk point of sale — no proprietary hardware to buy. Staff can charge pujas, donations, memberships and facility bookings with cash, card, or split tender, reconcile the cash drawer at the end of each shift, and the same stand can flip to a devotee self-service mode for check-in and donations. A secure stand locks it to the counter and swivels for the devotee to sign or tap to pay. Contact us for a kiosk demo.

You can configure any puja type — archana, abhishekam, homam, sevas, and custom services — each with its own pricing, duration, priest requirements, and materials list. Devotees can browse and book these services directly from their portal.

The Bookings tile lets admins view, manage, and update all puja and facility reservations in one place. You can see upcoming bookings, check devotee details, and coordinate with priests — all without switching between systems.

Yes. Devotees can book pujas on behalf of any family member in their profile. All bookings appear in the devotee's order history and in the admin's Finance Dashboard tile for easy tracking and refund management.

The Finance Dashboard tile gives admins a full view of all devotee puja orders — including payment details, service records, and order status. Admins can issue refunds directly from this tile without needing to contact the payment provider separately. It opens as a full-screen three-frame console (like the Bookings POS): a left navigator rail with section jump-links — clicking Trends & Compare expands one-click Quick Range buttons (Today, Last 7 Days, This Month, This Quarter, This Year, All Time) below it, and clicking Revenue Analytics expands a Filter View and Revenue View picker right below it that drive the center breakdown and ledger, with a badge showing how many filter rules are active; the center holding all metrics, charts and the transaction ledger at full width, with the transaction search box in the ledger header; and a collapsible right-hand Finance Snapshot (slide it open or closed with its arrow button) showing what the center doesn't: a payment-mix bar, a Needs Attention list of anomaly flags (high refund rate, cash variance, drawer over/short, complimentary orders), Range Highlights (top service, top contributor, peak revenue day), and Export PDF/Excel buttons. On narrow screens the rails hide and the Filters & Tools card appears above the revenue breakdown instead. Key metrics for the selected date range include Gross Sales, Refunds, Net Revenue, Order Volume, Average Order, plus Donations (and their share of revenue), Tax-Exempt total, Refund Rate, and Cash vs Card collected. A Business Analytics row adds derived insight metrics for the finance/BI team: Net Margin (net ÷ gross), Daily Average run-rate, a linear Projected Month total, Median Order (outlier-robust vs the average), Unique Devotees and revenue per devotee, Repeat-Devotee Revenue Share, Online vs Front-Desk share, Complimentary and Tax-Exempt shares, and Cash Variance (drawer over/short as a percentage of cash handled). Every figure respects the active date range and filters and updates in real time.

The Finance Dashboard's Revenue Analytics section breaks collections down several ways: By Payment Channel (the tender — cash, card terminal, online card, split, cheque, complimentary), By Source (Temple Website self-service vs the admin Front Desk/POS), By Category, By Service, By Devotee, By Priest, By Collector / Cashier, and By Time of Day. The "By Devotee" view is a contributor leaderboard showing how much each devotee has paid, along with the number of unique devotees and the average given per devotee — handy for recognizing top supporters and for year-end acknowledgements. Click any row to instantly filter the transaction ledger. Cash-drawer reconciliation entries (shift over/short) are excluded from every breakdown and from Gross/Net revenue — they appear only in the dedicated "Drawer Over/Short" card and the ledger, since they are internal adjustments rather than sales. The one exception: extra cash converted to a general donation at shift close counts as real Cash + Donation revenue.

They answer different questions. By Source is a two-bucket split of where the sale originated: Temple Website (the devotee paid online themselves) vs Front Desk (POS) (a staff member collected it at the desk, whatever the tender). By Collector / Cashier breaks the front-desk bucket down to the individual person who collected each payment — useful for per-cashier accountability and matching each cashier's total against their shift reconciliation; website orders appear there as "Online / Self-Service". In short: Source tells you whether the temple or the devotee ran the transaction; Collector tells you which staff member's hands the money passed through — and Source's Front Desk total should equal the sum of all human collectors.

Every record carries up to three references. The Order ID (e.g. order-mr61iegvrm8w) is the permanent database ID of the order/booking itself — it exists even before payment and is what you use to look up or refund a specific order. The Transaction ID (e.g. TXN-LL7Q55) is the payment reference generated when money is collected. The Invoice No is intentionally the same number as the Transaction ID — the payment reference doubles as the receipt/invoice number so the devotee's receipt always matches the ledger; seeing them identical is expected, not an error. Card payments also store the processor's own identifiers (Square payment ID or Datacap Ref No/Auth Code) separately for settlement and refunds, and a cash-change donation is logged with a "-D" suffix (TXN-LL7Q55-D) so it traces to its parent transaction.

Yes. In Confirm Payment Details, choose the "Other" mode (next to Cash / Card / Split) and pick the method — Check, Zelle, Venmo, PayPal, Cash App, Bank Transfer, or Other. Enter the reference or confirmation number and attach a required proof image (take a photo or upload a screenshot). The payment is recorded as a paid order, so it appears in the Finance Dashboard and the devotee's profile, and an acknowledgment is emailed to the devotee and can be printed. The proof image is viewable only by Finance, SuperAdmin, and the cashier who collected it. For checks, automatic scanning of the check number and amount is planned in a later update.

The Bookings tile opens a full-screen point-of-sale (POS) view built for the temple front desk. Staff pick puja or facility services from a category-organised store, attach the devotee (search, add new, or continue as guest), choose the date and time, and take payment — cash with change calculation, card, split cash+card, complimentary, or "Other" methods like check and Zelle. The same screen manages existing reservations (collect payment, reschedule, reassign priest, cancel, holds with expiry countdowns), shows order history with refunds, and runs the cashier shift: opening cash count, live cash/card totals, and end-of-shift reconciliation with a printable closing receipt. Records where money moved (paid, refunded, or complimentary) can never be deleted — they are retained permanently for financial reporting and audit; only never-paid rows such as expired holds or unpaid cancellations can be cleaned up.

Yes, if the temple turns it on — it is a per-temple setting. Under Temple Setup → Booking Rules → Holds, the "Allow reserve without payment" rule controls it: when it's on, a booking can be saved On Hold for a devotee with no payment collected — the date is blocked, a hold expiry counts down, and payment is taken later when the devotee confirms. When the rule is off, payment is required at booking time and the Save-on-Hold and Reserve options disappear from the POS entirely. A Reservation Policy panel in the same section fine-tunes it: which services may be reserved (all, only chosen categories, only chosen services, or none), whether a reservation needs admin approval before the devotee can pay (never, always, facilities only, or only above a set dollar amount), how long an unpaid reservation lasts, the maximum number of open reservations one devotee may hold, and whether reserving is members-only. When approval is required, a devotee's website reservation lands in Bookings → Active marked "Awaiting approval"; a SuperAdmin or Admin taps Approve (or Reject with a reason) — only after approval does the "Pay Now" button appear on the devotee's dashboard for that booking, and the devotee is emailed either way. Pair it with "Auto-expire on-hold bookings" so unpaid reservations cancel themselves after the window.

The reservation lands in the admin Bookings screen (Active tab) with an "⏳ Awaiting approval" badge. Admins and SuperAdmins see ✓ Approve and ✕ Reject buttons on the row — other roles don't. Approving emails the devotee and unlocks Pay Now on their website dashboard, and the row shows "✓ Approved · awaiting payment" until they pay. Rejecting requires a written reason, which is emailed to the devotee along with a push notification, and the booking is cancelled. Every decision — who approved or rejected, when, and why — is recorded in the audit log.

Yes. Shifts are per-admin: each cashier starts their own shift with their own opening cash count, and any number of shifts can be open at once. Every POS payment is tagged with the shift that collected it, so at End Shift the expected totals are derived directly from that shift's orders — one admin's drawer never mixes with another's. Cash drawers are configured under Settings → Add Setting → "Cash Drawer / Counter" (one row per physical box, e.g. "Front Desk 1", "Floor 2"); at Start Shift the cashier picks their drawer from a dropdown, a drawer already in use shows as taken and can't be claimed twice, and the drawer remembers its float — the closing count left in the box pre-fills the opening count for whoever runs that drawer next, whoever they are. The drawer name appears on the shift bar, printed labels, and the reconciliation record. Temples that configure no drawers can still type a free-text label. For counters where several cashiers genuinely work one box at once (e.g. a festival counter), mark the drawer "Shared" in its setting: it stays selectable while in use ("in use — join"), the first shift carries the opening float (joiners start at $0 unless they add cash), and the last shift to close counts the box against the whole group's collections — with the trade-off, stated plainly, that any over/short belongs to the group rather than one person. If an admin accidentally starts a shift on a second device, the POS adopts their existing open shift instead of creating a duplicate. The Finance Dashboard shows an "Open Shifts" panel listing every open drawer with its running totals and a combined expected-cash figure for the treasurer. Best practice: one login per person, one cash box per login — never share an admin account between two people.

Yes. The Facility Services tile lets devotees and admins book the temple hall, kitchen, and other shared spaces. These reservations appear alongside puja bookings in the main Bookings tile so admins always have a unified view. When booking a facility at the front desk, staff pick the required duration/rate for the space and can optionally add In-Temple priest services to the same reservation — the calendar automatically blocks dates the chosen priest is already booked.

Yes. Admins add each item once under Temple Setup → Equipment & Add-ons with the quantity the temple owns (e.g., Wireless Mic × 2), a price, and whether it is a shared pool or fixed to one space. Devotees then add items with quantity steppers on the website or at the front desk; availability is counted per time slot, so a request that would go over what the temple owns is refused before payment. Equipment is taxed and itemised on receipts like any other part of the sale, and can carry a refundable deposit set in Booking Rules → Deposits & Fees.

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, mark items as sold out, and receive low-inventory alerts so popular items can be restocked in time. 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, 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.

Admins can assign priests to specific pujas, sevas, and events and manage their shifts. Each priest gets a personal schedule of their upcoming services, so they always know what they are assigned to and when. Priest assignments also flow into each priest's personal schedule, into the Temple Calendar's Bookings filter (visible to SuperAdmins and to any role granted the Bookings tile in Tile Access), and into finance reporting, where you can see revenue attributed to each priest.

Yes. Memberships are sold like any other service at the front-desk Bookings POS. Create a service with the category "Membership" and the subcategory "Yearly" (or "Annual") or "Lifetime", set its price, and it appears in the POS store. When the membership is paid — cash, card, or other methods — the devotee's profile is updated automatically: yearly memberships get an expiry date one year from purchase (renewing early extends from the current expiry, so no paid time is lost), and lifetime memberships never expire. A membership can only be sold to a devotee profile, never to a guest — the POS asks the cashier to select or create the devotee first.

Every service can carry two prices: a Member Price and a Non-Member Price. The Bookings POS checks the selected devotee's membership status automatically — active members (yearly not yet expired, or lifetime) are charged the Member Price, everyone else the Non-Member Price. If a service has no Non-Member Price configured, everyone pays the Member Price, so nothing changes until you fill in non-member prices. The devotee's status ("Member until …", "Lifetime member", or "Not a member") is shown right on the POS cart when they are selected.

Every devotee profile in Manage Devotees has a Membership tab showing their status: "Not a Member", the membership start date, and — for yearly members — the expiry date. The same status also appears as a column in the devotee list and on the POS cart when the devotee is selected for a booking. These fields are read-only: they are set automatically when a membership is purchased at the Bookings POS. Manual grants for legacy or complimentary members (with full audit logging) are planned for a later update.

Yes. Under Temple Setup → Booking Rules, the "Offers & Concessions" section lets admins create offers: a percentage or fixed-dollar discount, optionally with a minimum order value, a validity date range, a members-only or non-members-only restriction, specific service categories, or a repeat-visit condition (the devotee has a prior paid order within a chosen number of days — the classic "second visit within 2 days" concession). With multiple offers you decide exactly which ones may combine; when they do, each percentage is calculated on the original order value, never compounded. Discounts always apply to the original price, and sales tax and card fees are then calculated on the discounted amount. Offers never apply to Membership purchases or Donations. At the front desk, staff tap "Check Offers" in the POS order column: every offer appears as a tile showing the order cost with and without the offer — eligible offers apply to the total instantly, and offers the devotee doesn't qualify for yet still show the potential savings alongside the reason (a gentle nudge to qualify). Non-members see a "Become a Member" button right in the panel: choosing Yearly or Lifetime adds the membership to the same order and immediately unlocks member pricing and member-only offers for it. The receipt shows the original amount, the discount, and the amount charged.

Booking Rules → "Deposits & Fees" holds ONE list for both spaces and equipment — a hall can carry a $300 deposit and a wireless mic a $20 one, picked from the same dropdown. Deposits are never charged at booking: the devotee's card is kept on file (or they leave a check/cash deposit), and an admin charges or releases it after the event. The same section also holds the Priest Breakout Fee, which applies to facilities only.

That is the Booking Rules → "Order Records" setting. "One order for the whole booking" (the default) writes a single ledger row carrying every space, the equipment and the deposit. "One order per space" writes one row per space — the amounts always sum exactly to what was charged, and equipment rides the first row. Either way the devotee made one payment and gets one receipt.

Yes. Devotees can make general donations or give toward a specific purpose, and admins can create fundraising campaigns with public-facing pages so the community can contribute to temple causes. All contributions appear in the Finance Dashboard alongside puja orders, with donation totals and tax-exempt amounts tracked for reporting.