How to run a school on Odoo.

Walk into most private schools across the UAE, GCC, and Pakistan and two institutions are running in the same building. One is academic — timetables, teachers, exam schedules — and it usually works, because education is what the school actually cares about. The other is a business: enquiries, enrolment, fees, transport, payroll — and it survives on a WhatsApp group, a walk-in register at reception, and a spreadsheet only the finance officer really understands. The business side is not the smaller half. On a school's own books, it is most of the story, and it is the half quietly drowning.

Fee collection is where it hurts most. Instalment plans live in a spreadsheet rebuilt every term. Reminders go out by phone call, whenever someone remembers to make one. Sibling and staff discounts get applied however the person answering the phone decides that day — a different rate for the same family depending on who picked up. Nobody, not the principal, not the owner, not a group's finance director, can say with confidence what the school is actually owed until the year closes and an auditor forces the question. None of this gets fixed by hiring another accounts clerk. It gets fixed by putting admissions, fees, and the classroom on one system that agrees with itself. Here is how that looks on Odoo.

What standard Odoo gives you — and where it needs shaping

Odoo's Invoicing, CRM, and HR are not built for schools specifically, but they are exactly the raw material a school administration needs: a CRM that tracks a lead from first enquiry through to a decision, an invoicing engine that can generate thousands of recurring charges without a human touching each one, and HR and payroll that runs a staff base of teachers and support staff properly. None of that arrives configured for a school. Standard Odoo does not know, out of the box, that a customer is really a student attached to a parent, that a charge recurs every term against an academic year rather than a calendar month, or that a discount depends on whether a sibling is already enrolled. That is the shaping: academic-year structure, grade-linked fee plans, and parent-facing communication and payment flows built on top of the standard apps — the same layer we configure for every school we work with.

The workflow: from enquiry to collected fees

• 1. Enquiry becomes a tracked pipeline, not a walk-in register. Every enquiry — website form, phone call, walk-in — lands in one pipeline with a stage: enquiry, assessment, offer, enrolled. Follow-up stops depending on whoever answered the phone remembering to make the next call.
• 2. Enrolment creates one student master, not a folder. A confirmed enrolment creates the student record — grade, section, sibling links, guardian contacts — the single master that every fee, timetable, and message references from that point on.
• 3. Fee structures are built per grade, with rules, not memory. Tuition, books, and activity fees are set per grade and campus, with sibling and staff discount rules configured once, centrally, so the third child in a family gets the same discount whoever takes the call.
• 4. Instalment plans and post-dated cheques run on a schedule. Each family's fee splits into termly or monthly instalments against the academic year, with post-dated cheques — still the norm across much of the UAE and GCC — logged against each instalment and tracked to deposit date.
• 5. Invoices and reminders go out on their own. Instalment invoices generate automatically on schedule, with WhatsApp and email reminders firing ahead of the due date and again after it, so chasing a fee stops depending on somebody picking up a phone.
• 6. Arrears are visible the day they happen, not at year-end. Overdue instalments surface immediately by student, grade, and campus, with an ageing view showing exactly who owes what and for how long, instead of a reconciliation exercise every summer.
• 7. Transport and activity fees land on the same invoice. Bus routes, after-school clubs, and exam fees bill to the same student account as tuition — one invoice, one balance, instead of a separate transport ledger nobody ever reconciles against fees.
• 8. School groups see every campus on one number. For a group running several campuses or branches, fees, discounts, and collections consolidate centrally, so the group finance director sees one true receivables figure, not a spreadsheet stitched together from each campus's own system.

What management finally sees

Because admissions, fees, and enrolment sit on one system, management finally sees receivables by grade and by campus, not one lump number that hides where the problem actually sits. The collection rate becomes a tracked figure, term over term, instead of a feeling. Enquiry-to-enrolment conversion shows which enquiries turn into enrolled students and which quietly go nowhere. And with our AI Connector, a principal or group finance director can just ask: "which grades have the highest outstanding fees?" — and get the answer from live data, not a spreadsheet built the night before the board meeting.

How we implement it

We implement around your academic calendar, not against it, ideally over a school holiday or the summer break, so admissions and fee collection are never disrupted mid-term. A single school typically goes live in six to ten weeks, covering admissions, fees, and student records; a school group follows the same proven pattern, campus by campus. It comes with our guarantee: you see the system running on your own students and your own fee structure before you pay, and if we miss the date we agreed, you walk away.