{{ pageTitle }} {{ pageTag }}
{{ pageSub }}
{{ unread }}
VO
Vandan Office
{{ k.label }}
{{ k.value }}
{{ k.sub }}
×
{{ f.label }} {{ f.value }}
Export
{{ tb.label }} {{ tb.count }}
{{ c.label }}
{{ r.id }}
{{ r.puja }}
{{ r.place }}
 {{ r.date }} {{ r.dakshina }} {{ r.status }} {{ r.interest }} {{ r.pandit }}
{{ r.primaryLabel }}
{{ r.secondaryLabel }}
{{ r.cancelLabel }}
{{ emptyNote }}
Lifecycle stages this tab set follows
{{ sg.label }}
Dakshina must be set before a puja can be pushed. Push starts the 24-hour Preferred-Pandit window; after that it opens to every partner in the city. Cancelling at any point resets the booking to Pushed and re-opens interest.
{{ allocPuja }}
{{ allocBooking }}
{{ allocDakshina }}
Pandit dakshina
{{ m.label }}
{{ m.value }}
Pandits who showed interest · {{ candidateCount }}
Ranked by Best-Fit score, then interest time
{{ c.initials }}
{{ c.name }} Best suited Preferred
{{ c.meta }}
{{ cd.label }}
{{ c.btnLabel }}
{{ c.interestAt }}
Best suited = Preferred Pandit tag + puja sub-city within 10 km of residence + overall rating 4 or above. The ranking is advisory; assignment is always this manual approval.
On approval
·{{ e.text }}
Internal note
Why this pandit was chosen (visible to office staff only)
Back to Pandit Lifecycle
Claim against booking {{ claimBooking }}
{{ cr.label }} {{ cr.value }}
Evidence submitted by the pandit
3 of max 5 files
{{ ev.label }}
Invoice
Record the settlement
Amount paid
₹
{{ diffNote }}
Transaction ID
{{ txnError }}
Payment date
Note to the pandit {{ noteRequired }}
{{ settleLabel }}
Saving notifies the pandit and updates their dashboard total and income report.
Back to Pandit Lifecycle
Added to the existing Pandits page: a profile approval queue, the admin-only Vandan Preferred Pandit toggle, and per-puja rating entry. The pandit never sees the Preferred tag.
Profile approval queue
{{ queueCount }} awaiting review
{{ c.label }}
{{ p.initials }}
{{ p.name }}
{{ p.meta }}
 {{ p.city }}
{{ p.completeness }}
{{ p.rating }}
{{ p.prefLabel }}
{{ p.status }}
{{ p.approveLabel }}
{{ p.changesLabel }}
Rate the pandit for a completed puja
Admin rating is the primary input to a partner's overall average, pooled with Amantran mutual ratings.
VP-2026-04390 · Namkaran
★
{{ ratingBtnLabel }}
Read-only oversight. Amantran requests are raised and approved by pandits themselves — the office needs visibility for disputes and to see which partners work together, but has no approval role here.
{{ c.label }}
{{ a.principal }} {{ a.puja }} {{ a.when }} {{ a.dakshina }} {{ a.matched }} {{ a.associate }} {{ a.status }} {{ a.ratings }}
New Partner-App block on the existing Settings page. Every timing rule is configuration, so it can be tuned after launch without an app release. All changes are written to the audit log.
Timing rules
Tap a value to cycle through the allowed options.
{{ tr2.label }}
{{ tr2.value }}
{{ tr2.note }}
Earning milestones
Shown one at a time on the partner dashboard — the nearest unachieved one.
+ Add
{{ m.scope }} · change
₹
Remove
No milestones — the card is omitted from partner dashboards entirely
Vandan collection QR
Shown on the partner's Collect payment screen.
vandan-collections.png
Updated 2 Sep 2026
Replace
Office contact shown in the app
Used by the cancellation notice, help screen and bank-change flow.
Cancel {{ cancelTarget }}?
The assigned pandit loses customer details immediately, the booking resets to Pushed, and interest re-opens to every pandit in the city.
Route
{{ r.label }}
Reason shown to the pandit
Keep booking
Cancel booking
{{ drawerInitials }}
{{ drawerName }}
{{ drawerMeta }}
×
{{ d.label }} {{ d.value }}
Rating history by source
{{ rr.source }} {{ rr.value }}
{{ drawerPrefNote }}
{{ toast }}