Admissions season is where most schools and colleges lose their front office to spreadsheets and inboxes. Applications arrive by email, WhatsApp and paper form; supporting documents live in scattered folders; merit ranking is done by hand in a workbook no two people trust; and offer letters are copy-pasted one at a time. Odoo core gives you res.partner, account.move for fees and calendar.event for interviews, but it has no concept of an applicant pipeline, a program-specific application form, a ranked merit list with cutoffs, or a seat quota — so admissions teams either bolt a generic off-the-shelf apps.odoo.com module onto a workflow it was never shaped for, or run the whole cycle outside the ERP and re-key admitted students by hand.

This is a build-to-order module that ECOSIRE designs around your actual admission process and then installs on your Odoo. At its heart is an admission.application model with a proper stage pipeline (submitted → under review → shortlisted → offered → admitted → rejected) rendered as an Odoo statusbar, with mail.thread chatter and scheduled activities on every record so notes, calls and next actions stay in one timeline. Public applicants apply through a website-served form — one configurable form per program or course, built in QWeb/OWL with validated fields and document upload written straight to ir.attachment. Each program can define its own required-document checklist, and a verification tracker marks each uploaded file as pending, verified or rejected so front-office staff know exactly what is still outstanding per applicant.

Technically, the build wires the pieces Odoo already does well into an admissions spine. Application fees are raised as real account.move invoices and collected through your configured online payment acquirers, so finance sees admissions revenue in the same ledger as everything else. Merit lists are generated by a compute-driven ranking (@api.depends on score/marks fields) with configurable cutoffs per program, and seat quotas per batch are enforced with real-time store=True computed counters so a program can never over-offer against available seats. Entrance exams and interviews are scheduled against calendar.event and appear on staff calendars; stage transitions fire automated actions (base.automation) that send email/SMS notifications and dispatch the offer letter as a QWeb PDF report. Security is enforced with ir.model.access.csv plus record rules so website applicants only ever touch their own record, and everything is exposed over Odoo's XML-RPC/JSON-RPC API if you need to feed a legacy student-information system. When an applicant reaches admitted, one button converts them into a Core student record — no re-keying, full audit trail.

Because it is built to order, delivery follows a fixed path: a scoping call to map your programs, forms, fee rules, cutoff logic and student-record target; a written scope and quotation; then development on a staging copy of your Odoo, UAT with your admissions team, and go-live with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $349 (indicative, single-company base scope); multi-company or multi-campus rollouts, deeper localization, third-party integrations, and migrating a large backlog of historical applicant data increase the quoted scope.