What an ERP for nursery schools should have in 2026

A nursery school or daycare has very specific needs: monthly or quarterly payment cycles, limited places with long waiting lists, a very high frequency relationship with families, and a regulatory burden that requires traceability in authorizations, allergies and protocols. The "ERP for nursery schools" is, in essence, the tool that sustains this day-to-day life without management, administration and tutors depending on spreadsheets, emails and closets with folders. In 2026, the question is no longer "whether to digitize" but "how to choose the platform that covers collection, families, documents and deposits without creating more bureaucracy." Edena offers, according to contracted modules, a base platform with digital file, organizational chart, portal and app for families and team, basic communication, onboarding, family self-management and analytics; electronic billing with Verifactu, receipts and analysis of non-payments; CRM with enrollment requests, pipeline and forms; extracurriculars; automation; store; and cloud documentation, all according to the public catalog, without inventing capabilities.

The specific needs of children that many generic systems ignore

The billing cycles in nursery schools are not the same as those of a primary school: there are fixed monthly fees, additional services (dining room, early risers, activities), variability by days of attendance in some cases, and bonuses according to the criteria of the center or the public administration. A generic system without recurrence logic, without integrated default management and without segmented due notification turns these processes into manual work. The waiting list is another critical element: if there is no recruitment pipeline with statuses, origins and tracking of candidates, places are managed with secretarial Excel and calls without registration, which generates conflicts with families who "have been waiting longer."

Hard requirements: what cannot be missing

Recurring collection with a calendar aligned to the families' reality, with traceable receipts, history per student and late payment analysis.
Communication that arrives: basic if the volume of messages is low, Pro with push and confirmation when the frequency and importance of the message justify it.
Management of places and extracurricular activities with capacity limits and linked charges, so as not to create a third informal circuit on paper.
Digital file with authorizations, health data, ID photographs and admission documents with controlled visibility.
CRM if you have a waiting list or several entry routes, so as not to rewrite the funnel every season on new sheets.
Analysis that management and administration agree upon, with the same definitions, to close the monthly committee with data, not with impressions.

What to ask in the demo, with your data and not with toy data

It asks you to go through the entire flow from a place request to the first payment and the loading of the collection authorization. If in ninety minutes you do not see traceability between those three points without manual re-writing of data, the system is not integrated. Also ask to see how a non-payment is managed: how many clicks to see which families have overdue bills, when the last notice was issued and what the current status is. That thirty-second flow in the demo reveals more than two hours of catalog presentation.

Three-year TCO: don't get carried away by the license price alone

The price per student or per place is only the first layer. Add: cost of migrating data from the old system, hours of training (from the team, not just from "someone who learned alone"), cost of keeping the old system in parallel during the transition, possible integrations with external applications that you will now have to throw away or connect, and the risk of re-migrating in two years if the system does not scale. An ERP that seems cheap but forces you to a third party for billing and another for families ends up costing more than an integrated one with a modular price.

Frequent errors in nursery schools

Choose by base price without calculating the total cost of migration and training.
Hire the Pro communication module and do not define templates, managers or frequency criteria: the channel is left empty of discipline.
Without a process manager: the system does not set the places policy or the dining room criteria; it only executes the rules you define.
Start with all the functionality on day one without a prior pilot, saturating the team with change and technology at the same time.

Child-specific ERP requirements

Places and ratios: Control of occupancy per classroom and regulatory compliance.
Menus and allergies: Integrated into the file and daily communication with families.
Collection authorizations: Authorized persons updatable without paper at reception.
Billing per day: Half day, dining room, early risers with differentiated rates.
Daily communication: Food, nap or incident reports with traceability.

Context in Spain: what a school ERP requires in 2026

Beyond grades and attendance, school management software in Spain must cover billing (including Verifactu preparation), family portal or app, file with minor data under GDPR and LOPDGDD, and communications traceability. Buying an isolated SIS when the real pain is in secretarial, collections and families usually ends in duplicating data between three tools.

In nursery schools they weigh places, ratios, menus and allergies; in academies, bonuses, seasons and multiple venues; in private schools, differentiated fees, internal scholarships and commercial recruitment. An ERP that works in language academies may fall short if you manage child, NEAE or dining room ratios with billing per day.

Evaluates three-year TCO: license, migration, training, internal coordination hours and cost of bridge integrations. Request a demo with your real data (five families, one cycle of receipts) before deciding. Software that seems cheaper at the beginning can become more expensive if it forces you to add CRM, billing or communication separately.

Case study (Spain)

An 85-place nursery school in Girona evaluated three providers with the same checklist: enrollment, menus, billing and family app. The 10-week pilot with real data revealed that only one closed the application-enrollment-payment cycle without Excel. The change cost them 40 hours of migration, but they eliminated duplicate data in three tools.

Conclusion

An ERP for nursery schools in 2026 is not a technological whim: it is the difference between a team that works with criteria and traces, and one that reconstructs reality every Monday from three different sources. Choose with TCO, demo with your data and aligned committee. In Edena you can start with the modules that you are really going to power and add when the volume justifies it, with 24/7 support and no catalog surprises. Request a session and see the complete flow with your places, your collection cycle and your communication.

What an ERP for nursery schools should have in 2026