How Heritage International ran CBSE and Cambridge tracks without two ERPs
Dual-board complexity was splitting the school into two admin cultures. One ScholarERP configuration served both pathways with shared masters and board-specific exams.
Challenges before ScholarERP
What made day-to-day operations fragile — and why a patchwork of tools stopped scaling.
Two boards meant two admin dialects
Assessment schemes, report formats, and term calendars disagreed — staff maintained parallel trackers.
Sibling fee logic broke across tracks
Families with children on different boards needed one invoice story, not two portals.
Room and teacher clashes
Shared labs and specialists were double-booked because timetables lived in separate tools.
How ScholarERP solved it
ScholarERP modeled board pathways as configuration — not as separate products — while keeping people, fees, and rooms shared.
-
One student, many program tags
Board pathway became a structured attribute driving exam templates and report cards.
-
Shared fee wallet, board-aware heads
Parents saw one account; academics still billed pathway-specific charges correctly.
-
Unified timetable constraints
Rooms and teachers were scarce resources the whole school negotiated in one planner.
What they say after go-live
“We stopped pretending we were two schools sharing a gate. ScholarERP let CBSE and Cambridge coexist without doubling our admin burden.”