How Garud Zep runs 17 branches with ₹2–3 Cr monthly collections per branch
A high-velocity coaching network needed HQ control without slowing center cashiers. ScholarERP delivered multi-branch ledgers and deep collection visibility since 2021.
Challenges before ScholarERP
What made day-to-day operations fragile — and why a patchwork of tools stopped scaling.
Collections velocity outpaced tools
Cashiers handled high daily volumes while HQ needed same-day visibility. Spreadsheets could not keep pace with peak counseling weeks.
Branch autonomy vs HQ control
Centers needed speed at the counter; leadership needed policy locks on discounts, refunds, and batch transfers.
Counselor follow-ups fell through cracks
Hot leads went cold when batch seat maps and fee status lived in different notebooks.
How ScholarERP solved it
ScholarERP gave each branch a fast counter workflow while HQ retained ledger control, discount governance, and network MIS.
-
Configure branch ledgers with HQ locks
Fee heads, offers, and refund rules were policy-driven — branches executed, HQ governed.
-
Tie admissions to batch capacity
Counselors saw live seats and fee stages so conversion did not overbook classrooms.
-
Pulse collections every day
Network dashboards showed branch-wise recovery so underperforming centers got coaching the same week.
What they say after go-live
“ScholarERP is the admin panel our branches actually use under pressure. Collections stay visible, policies stay enforced, and HQ finally manages a network — not seventeen islands.”