Childcare Management
Run a nursery, daycare or early-learning centre end to end — admissions, attendance, health, learning, billing, and the parent relationship — on one modular Odoo 19 suite that reuses Odoo's own accounting, CRM, HR and contacts rather than duplicating them.
Twelve modules, stacked in layers
Each module owns one slice of the centre and depends only downward. Nothing reaches sideways into a neighbour, so you can install the operational modules you need and leave the rest — and each one stays independently upgradable.
Read bottom to top. Install the whole suite, or only the layers you need.
One child, from first enquiry to invoice
The suite follows a child through the centre. Each step hands real data to the next, so nobody re-types a name, and every fee traces back to an enrolment.
Enquiries reuse Odoo CRM; invoices are real Odoo accounting entries. No parallel systems.
A day at the centre
The part staff touch every morning and evening — and the part parents judge you on.
Check-in and check-out are stored as append-only events, not editable rows. Changing one afterwards takes a correction request that a manager approves.
A kiosk you can leave in the lobby
A tablet pairs to your centre with a single-use code and holds a revocable device token — not a staff login. Parents identify themselves on every visit.
- Badge scan or personal PIN, with lockout after repeated wrong attempts
- Optional GPS geofence, so check-ins must happen at the centre
- A repeated tap cannot check the same child in twice
- Tablet lost? Revoke the token and it stops working immediately
Safe pickup, enforced by the server
Each child has approved collectors with validity dates and photo ID. At check-out the kiosk offers only that list, and the server refuses anyone who is not on it — the rule is not merely hidden in the interface.
Occupancy you can actually see
Graph and pivot reporting for classroom occupancy — enrolled against capacity, with over-capacity rooms flagged — and for revenue by month, centre and fee plan.
Nothing reaches a parent unreviewed
Sensitive actions are two-person by design: whoever writes it is never whoever releases it. Every screen names the role that owes the next decision, so work does not silently stall in someone's queue.
| What | Prepared by | Decided by |
|---|---|---|
| Admission application | Admission Officer reviews | Center Manager |
| Daily report to parents | Teacher | Communication Approver |
| Activity update to parents | Teacher | Communication Approver |
| Learning observation | Teacher | Academic Manager |
| Assessment and progress report | Teacher | Academic Manager |
| Incident report | Staff on the floor | Incident Manager |
| Fee discount | Accountant | Center Manager |
| Attendance correction | Teacher | Center Manager |
Approval buttons appear only for the role that owns them; everyone else sees a plain explanation of who must act next.
Module by module
Core
Companies, centres, classrooms with capacity and age ranges, academic years and terms, children, guardians and authorised collectors.
- Interactive family diagram: siblings, half- and step-siblings, cousins
- Optionally folds guardians in to show why two children are related
- Pan, zoom, and export the picture to SVG or PNG for a case file
Admissions
Turns Odoo CRM enquiries into applications and enrolments, with required-document checklists that must be received and verified before anyone can approve.
Attendance
Kiosk and manual check-in and check-out, append-only audit events, safe pickup, correction requests, and a kiosk device registry with geofencing.
Communication
Activity updates, daily reports, parent concerns with resolution tracking, staff conversations, and a scheduled notification outbox.
Health
The most tightly restricted module: health profiles, conditions, medication tied to effective consent, meal plans, incidents with escalation, and evidence retention with legal hold.
- Teachers can raise an incident without seeing any medical record
- Guardians can request and download their own child's health export
Learning
Curriculum catalogue and milestones, observations captured on the floor, assessments, learning journeys, and printable progress reports.
Billing
Fee plans with recurring and one-off components, discount rules that need approval, and billing periods that freeze into immutable per-child snapshots before becoming Odoo invoices.
Parent Portal
A guardian area under /my/childcare: children, attendance, invoices,
incident acknowledgement, consent decisions, and health record export.
Mobile API
A versioned JSON API under /api/childcare/v1 for parent and teacher apps,
with a persisted request audit trail and offline sync support.
Full Demo
A connected demonstration dataset spanning every module, so an evaluation database tells one coherent story instead of disjoint per-module fixtures.
Multi-centre, multi-company, least privilege
Scoping is enforced by server-side record rules, not by hiding menus.
Many centres, one database
Run several nurseries under one company, or several legal entities side by side. Staff are assigned to centres; records carry both company and centre and cannot straddle two.
An audit trail that holds up
Attendance events are append-only. Billing snapshots freeze once issued. Medication administration fields are immutable. Workflow steps post to the record's chatter with who did what and when.
Odoo-native, not bolted on
Contacts, CRM, HR, accounting, attachments and mail are standard Odoo. Custom models exist only for genuinely childcare-specific objects — so your accountant keeps the Odoo they already know.
What is included, and what is not
We would rather you know now than be disappointed afterwards.
Not included in this release
- Online card payments. Invoices are produced in Odoo accounting and can be paid through any payment provider you configure in Odoo itself. The suite adds no payment flow of its own to the parent portal.
- Automated tax-authority e-invoicing. The billing module checks and reports on Saudi/ZATCA configuration readiness before a period is invoiced, but does not itself submit or clear invoices with the authority.
- Push notification delivery. Notifications, devices and channels are modelled and queued, but connecting a provider such as Firebase or APNs is an integration step and is not shipped configured.
- Translations. The interface ships in English. Odoo's standard translation workflow applies if you need another language.
- Native mobile apps. The suite provides the server-side API for parent and teacher apps; the apps themselves are not part of this package.
| Requirement | Detail |
|---|---|
| Odoo version | 19.0, Community or Enterprise |
| Odoo apps used | contacts, crm, hr, account, product, portal, website, mail |
| Database | PostgreSQL, as required by Odoo |
| Licence | LGPL-3 |
| Installation | Install Childcare Management; it pulls in every module in the suite |
| Trying it out | Install os_childcare_demo for a connected sample centre |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) • Employees (hr) • CRM (crm) • Calendar (calendar) • Invoicing (account) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 17599 |
| Technical Name |
os_childcare_suite |
| License | LGPL-3 |
Please log in to comment on this module