Training providers, ed-tech startups, and corporate L&D teams outgrow spreadsheets and disconnected video tools fast: they need to author structured courses, gate progression on graded assessments, issue verifiable certificates, and prove completion to auditors or clients — all tied to the same contacts, invoices, and reporting they already run in ERPNext. ERPNext core has no learning surface at all (the community frappe/lms app is a separate product with its own opinions), so teams end up stitching together an external LMS that never shares a customer record, a payment, or a report with their operational system. That integration gap is exactly where this build lives.

ECOSIRE builds a proper Frappe app — a versioned, bench get-app-installable module with its own DocTypes rather than customizations bolted onto stock forms. The data model is modeled as first-class DocTypes: Course, Course Lesson (child ordering by idx), Quiz and Quiz Question, Course Enrollment, Lesson Progress, Assessment Result, and Course Certificate. Business logic runs where Frappe expects it: hooks.py doc_events (for example Assessment Result.on_submit) recompute a learner's weighted grade and, when the pass threshold is met, insert the Course Certificate and fire a notification. Server-side scoring and eligibility checks live in whitelisted methods (@frappe.whitelist()) so a browser can never award itself a pass; client scripts handle the in-form UX like revealing the next lesson only after the current one is marked complete.

Access and multi-audience separation are handled with Frappe's permission engine — Role Profiles and role_profile-driven permissions for Student, Instructor, and Program Admin, plus User Permissions to scope instructors to their own batches. The learner-facing experience is delivered either as a Frappe Web Portal (Jinja www/ pages and Web Forms) or as a headless front end consuming the Frappe REST API (/api/resource/Course, /api/method/...) and your whitelisted enrollment and quiz-submission endpoints — you choose during scoping. Scheduled jobs (scheduler_events — hourly/daily) drive cohort lifecycle automation: opening and closing batch enrollment windows, sending drip-lesson and deadline reminders via the Notification framework, and expiring or renewing time-boxed certifications. Certificates render from a Print Format to PDF with a QR/verification link backed by a public whitelisted verifier.

Because this is build-to-order, you are not downloading a fixed marketplace app and hoping it fits. We start with a scoping call to map your course structure, assessment rules, certification logic, and who needs to see what. We then build and configure the app against Frappe/ERPNext v15 or v16, validate it with you on a staging bench through UAT, and cut over to production with a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full source in a Git repository you own, so nothing about the system is locked away from your own engineers.