Is SquareCampus a school ERP?

SquareCampus includes the record and workflow capabilities schools expect from ERP software, and is positioned as a School Operating System: the same capabilities, connected by one record and governed by ownership and audit trails.

Can school ERP software run alongside the tools we already use?

Yes. A bounded deployment can run next to an existing ERP, LMS, payment portal or identity provider, governing the workflow that crosses them. Consolidation is a later choice, never a precondition.

How is pricing structured?

One annual institutional licence calculated on student-volume bands, with the platform's modules and the standard parent and staff mobile apps included. The model is published on the pricing page; figures are issued in a written proposal after discovery, and migration, integrations and premium implementation are scoped as their own lines.

What does implementation involve?

A guided rollout sequenced around the academic calendar: institution blueprint, data migration, a parallel run on anything finance or academic teams must trust, role-based training, then go-live.

How does the platform handle security and data access?

Access is role-based and scoped by campus, department and workflow step; actions are logged with user and timestamp; data is designed to be encrypted in transit and at rest. Documentation is shared on request.

School management system · School ERP software

School ERP software that behaves like one system, not seven.

Most school ERP software is a set of modules sold together. SquareCampus is built the other way round: one institutional record, one workflow engine, one audit trail, and the modules a school expects sitting on top of it.

PrincipalsTrust administratorsIT coordinatorsFinance officers

Book a guided demo See the platform

Direct answer

What is school ERP software?

School ERP software is the system a school uses to run its recurring operations: admissions, student records, attendance, fees, examinations, timetables, transport and parent communication. The term comes from enterprise resource planning. In practice the useful question is not which modules exist but whether they share one record, so a change in one place is reflected everywhere else without re-entry.

SquareCampus includes these capabilities and is positioned as a School Operating System. Read the canonical definition.

How it runs in SquareCampus

Each step has an owner and leaves a record

A module list hides the real question: does the work connect? These are the workflows as they run in production.

Admissions to enrolment

An enquiry becomes an application, a verified document set, a fee plan and a section allocation, with each hand-off owned by a named person and visible to the parent.

Attendance to fees and alerts

Daily attendance feeds fee rules, transport billing and guardian alerts. Exceptions carry a reason and an approver rather than a note in a register.

Exams to results and promotion

Schedules, marks entry, moderation, publication and promotion run as one sequence with a record of who changed what and when.

Approvals with an audit trail

Leave, concessions, refunds, purchases and gate passes move through role-scoped approvals, so the trail exists before an auditor asks for it.

Communication tied to context

Messages to parents and staff attach to the class, term, fee state or incident they concern, with delivery status and escalation paths.

Leadership view

Trustees and principals see what requires attention across campuses today, with an owner against each item, instead of a monthly report pack.

Built for India

The realities Indian schools run on

Boards, fee structures, trusts and parent channels are configuration here, not customisation projects.

India-first specifics

Fee structures with term plans, sibling and staff concessions, transport slabs, late fees and GST-aware receipts.
CBSE, ICSE and state-board grading templates and report formats.
Ten Indian languages across the parent and student apps.
Multi-campus and trust-level structures as a first-class model, not a customisation.
Parent communication over the app and WhatsApp-style channels, with acknowledgements recorded.
An India-first data-residency posture, with the hosting region named in writing on the infrastructure page.

What to check in any vendor

Ask these of every vendor you evaluate, including us. The answers separate a connected system from a set of modules.

1Does a change in admissions, attendance or fees appear everywhere else without re-entry?
2Can you see who approved an exception and why, months later, without asking the vendor?
3Is pricing one institutional licence on student-volume bands with modules and the standard mobile apps included, or per-module with add-ons?
4What does the rollout involve: migration, parallel run, role-based training, and a rollback plan?
5Will the vendor answer an infrastructure and security questionnaire in writing?
6What happens to your data when you leave, in what format, and by when?

Questions

School ERP software: common questions

Short answers, the way a buyer asks them. The FAQ page covers evaluation, security and rollout in more depth.

More on evaluation, security and rollout in the FAQ.

Keep reading

The pages a buyer on this question usually reads next.

PlatformThe four layers every module sits on School management systemThe category page, modules as workflows SquareCampus vs FedenaManaged School OS against an open-source ERP How to choose a school management systemA vendor-neutral buyer's checklist PricingThe licensing model; figures by proposal

Next step

Bring one real bottleneck. We will show how it runs.

A guided demo on your own scenario, followed by a written scope, from a founder-led team. The licensing model is published; figures follow a written proposal.

Book a guided demo How pricing works