School & Academic Management

ECOSIRE builds a proper Frappe application — installed onto your own site with bench get-app and bench install-app, versioned in its own git repo — that models your institution's real structure. We design the DocTypes for admission enquiry, admission application, student, guardian, program, course, batch/section, timetable slot, attendance, exam schedule, grade scale, report card, fee structure, and fee invoice, wiring them together with the ERPNext Education records you already have rather than replacing them. Business logic lives in hooks.py doc events (validate, on_submit, on_update) and server-side Python — for example, generating a term's fee invoices when a Program Enrollment is submitted, or recomputing a weighted grade when assessment marks change — never as brittle spreadsheet formulas.

The interface layer uses client scripts for in-form validation and dynamic fields (auto-filling section capacity, blocking double-booked timetable slots), and Frappe's print-format engine plus Jinja for report cards, fee receipts, and admission letters. Permissions are enforced through role profiles and user permissions: a Class Teacher role sees attendance for their assigned sections only, an Accounts role owns the fee ledger, and guardians get a scoped portal view of their child's attendance, results, and dues. Where you need an external mobile app, parent portal, or SIS-to-LMS sync, we expose whitelisted methods (@frappe.whitelist()) and the standard Frappe REST API, secured with API-key/token auth. Recurring work — daily attendance-reminder emails, overdue-fee escalation, term-rollover — runs on scheduler_events (cron and daily hooks) so nothing depends on someone remembering to click a button.

Because this is build-to-order, nothing is downloaded and left for you to figure out. After a short scoping call we confirm your academic calendar, grading policy, fee heads, and role matrix, then build against Frappe/ERPNext v15 (and v16-ready). Typical delivery is 2-4 weeks from confirmed scope. We install and configure on your staging site, run UAT with your registrar and accounts team, then deploy to production with a rollback plan and hand over the git repository, technical docs, and a training session — followed by a post-go-live support window.