Nursery school ERP: what to look for in 2026

Nursery school ERP: what to look for in 2026

A nursery or early years setting has very specific operational needs: monthly or termly payment cycles, limited places with long waiting lists, a very high-frequency relationship with families, and a regulatory load that demands traceability in authorisations, allergy records and safeguarding protocols. The “nursery ERP” is, in essence, the tool that holds that daily operation together without the head, admin and key workers depending on spreadsheets, emails and filing cabinets. In 2026, the question is no longer “whether to go digital” but “how to choose the platform that covers billing, families, documents and enrolment without creating more bureaucracy than it solves”. Edena offers, according to contracted modules: base platform with digital pupil records, org chart, portal and app for families and staff, basic communication, onboarding, family self-service and analytics; electronic billing with Verifactu, invoices and arrears analysis; CRM with enrolment applications, pipeline and forms; extracurricular activities; automation; a school shop; and cloud documentation — all as listed in the public module catalogue, with nothing invented.

The nursery-specific needs that generic systems often ignore

Billing cycles in nursery settings are not the same as in a primary school: there are fixed monthly fees, additional services (meals, early drop-off, activities), variability by attendance days in some cases, and subsidies or discounts based on the setting’s criteria or public authority funding. A generic system without recurring billing logic, without integrated arrears management and without segmented due-date notifications turns those processes into manual work. The waiting list is another critical element: without an enrolment pipeline with statuses, lead sources and candidate follow-up, places are managed via an admin spreadsheet and unrecorded phone calls, which generates conflicts with families who “had been waiting longer”.

Non-negotiables: what cannot be missing

• Recurring billing with a cycle aligned to family reality: traceable invoices, per-child history and arrears analytics.
• Communication that actually arrives: basic if message volume is low; Pro with push notifications and read receipts when the frequency and importance of messages justify it.
• Place and extracurricular management with capacity limits and linked billing, to avoid a third informal circuit running on paper.
• Digital pupil records with authorisations, health data, ID photos and admission documents with controlled visibility.
• CRM if you have a waiting list or multiple intake channels, to avoid rebuilding the pipeline on new spreadsheets every season.
• Analytics that the head and admin team agree on, with the same definitions, so the monthly review closes with data, not impressions.

What to ask for in the demo, with your own data, not demo data

Ask to follow the complete flow from a place application through to the first payment and the upload of the collection authorisation. If you cannot trace those three points in ninety minutes without manually re-entering data, the system is not integrated. Also ask to see how an arrears case is managed: how many clicks to see which families have overdue invoices, when the last reminder was sent and what the current status is. That thirty-second flow in the demo reveals more than two hours of catalogue presentation.

Total cost of ownership over three years: do not be driven by licence price alone

The per-child or per-place price is just the first layer. Add: the cost of migrating data from the previous system, training hours (for the whole team, not just one person who “figured it out”), the cost of running the old system in parallel during transition, any third-party integrations you will now need to retire or connect, and the risk of re-migrating in two years if the system does not scale. A system that looks cheap but forces you to use a third party for billing and another for families will end up costing more than an integrated platform with modular pricing.

Common mistakes in nurseries

• Choosing on base price without calculating the full migration and training cost.
• Purchasing the Pro communication module without defining templates, responsible staff or frequency criteria: the channel remains empty of discipline.
• No process owner: the system does not set place policy or meal criteria; it only executes the rules you define.
• Starting with full functionality on day one without a prior pilot, overwhelming the team with change and technology simultaneously.

Frequently asked questions

Is Verifactu already mandatory for nursery settings?

The obligation and timeline is defined by tax regulation and the implementation calendar; check with your accountant or tax adviser. What you must ask the vendor is clear detail on how they support electronic billing, on what timeline, and what transition support they offer.

Can an ERP for nurseries manage children with special educational needs?

The digital pupil record can store information about adaptations, authorisations and protocols. The level of detail and structure of those records depends on how you configure the system; check what customisable fields the vendor offers for this profile before committing.

How do you handle the transition from a legacy system without losing critical data?

Require the vendor to provide a phased migration plan: master data first (pupils, families, groups), then billing history, then documents. Validate with real data before closing the old system and plan a coexistence period. Without that plan, the risk of losing arrears history or signed contracts is real.

How long until the platform is fully operational?

It depends on data volume, setting complexity and the level of personalisation needed. In settings with up to 150 places, a basic pilot can be live in four to six weeks including migration and training, if there is a dedicated internal lead.

Is the extracurricular module worth it if we only run a few activities?

If activities generate their own fees and have limited places, the module eliminates email-based management and the parallel paper sign-up circuit. If you only run one activity with open enrolment and no charge, assess whether the module cost justifies the benefit.

Conclusion

An ERP for nurseries in 2026 is not a technology novelty: it is the difference between a team that works with clear criteria and audit trails, and one that reconstructs reality every Monday from three separate sources. Choose with TCO, demo with your own data and an aligned team. With Edena you can start with the modules you will actually use from day one and add more when volume justifies it, with 24/7 support and no hidden catalogue surprises. Request a session and see the full flow with your own places, your billing cycle and your family communication.