How to choose a school ERP in India: a buyer's checklist checklist
Every vendor's feature list is long. This is the short list of questions that decide whether the ERP you sign for actually runs your school — covering daily workflows, hidden costs, support, and the demo tests that separate a real option from a polished pitch.

Most school-software regret doesn't show up in the demo. It shows up in October, eight months after the contract is signed, when the office discovers the "fully integrated" ERP can't generate the board-format report card without an export to Excel, the parent app the salesperson swiped through so smoothly is a separate paid add-on, and the support number rings to a queue. The brochure was honest about everything the school never asked about. A good buyer's checklist is just the list of questions that turn that October surprise into a March decision.
Choosing a school ERP isn't about finding the longest feature list — every vendor's list is long. It's about confirming, before you sign, that the handful of things your school does every single day work end to end, that the price you were quoted is the price you'll actually pay, and that someone answers the phone in week six. This checklist is built around exactly those three.
What a school ERP must actually do
Before comparing vendors, write down what your school actually runs on. Most Indian schools share the same non-negotiable core — and a surprising number of products are thin on one or two of these while polished everywhere else. Score every shortlisted product against this list first, then let the nice-to-haves break ties.
The non-negotiable core
- Admissions and a clean student master record that every other module reads from.
- Fees: flexible structures, concessions, fines, online collection, instant receipts, and a clear dues report.
- Attendance: daily and period-wise, with absentee alerts to parents.
- Exams and board-format report cards for your board — CBSE, ICSE, or your state board — without re-keying marks.
- Parent communication over the channels parents actually use: WhatsApp, SMS, and a mobile app.
- Payroll for teaching and non-teaching staff with TDS, EPF, and ESI.
- Timetable, transport, and library if you run them — sharing the same student record.
- Role-based access so a class teacher, accountant, and principal each see only what they should.
- Compliance exports — UDISE+, APAAR — assembled from existing data, not a fresh data drive.
The India bar
A feature list that would pass in any country still misses what separates a workable ERP in India from a frustrating one. The differences are mundane, and they are exactly where products fail: the language the office and parents speak, the way Indian fees actually work, and whether the thing runs on a ₹8,000 Android phone on a patchy 4G connection in a Tier-3 town.
What separates a workable ERP in India
- Hindi and English (and ideally your state language) across the parent app and office screens — not just a translated brochure.
- Indian fee reality: term and monthly plans, sibling and staff concessions, RTE students, late fines, and partial payments.
- UPI-first online collection, because that's how parents pay — with the gateway charge (MDR) made explicit.
- A genuinely mobile-first parent and teacher experience, tested on a budget Android phone, not just an iPad demo.
- Data stored in India and a clear answer on the DPDP Act and parental consent.
- Onboarding that imports your existing student and fee data, plus training for non-technical office staff.
The buyer's checklist: eight tests in order
Run every shortlisted product through this, in order. The ones that survive are your real options.
- Write your requirements before the first demo. List your daily must-haves and your board's report-card format. Walk in with the list, not a blank mind that a polished demo can fill for you.
- Demo with your own data. Ask the vendor to load 10 of your real students and one real fee structure. A demo on the vendor's clean sample data hides every gap.
- Run your hardest workflow live. Collect a fee, generate a receipt, then produce your board's report card — in the demo, without a "we'll customise that later".
- Confirm what's included vs paid extra. Get the parent app, online payments, SMS, and report cards in writing as included or add-on, with per-unit costs.
- Ask the price for your exact student count, all-in. One annual number, with implementation, training, and support named — not a per-module teaser.
- Check the channel charges. Ask the MDR on UPI vs cards and who pays it, and the per-SMS cost if SMS isn't bundled.
- Call two reference schools yourself. Same board, similar size. Ask what broke and how fast support fixed it.
- Read the exit clause. Confirm you can export all your data, in a usable format, the day you decide to leave.
The products you'll shortlist
You'll build your shortlist from a familiar set of names. The options you'll run into in India include Teachmint, Vidyalaya, Fedena, Entab, MyClassboard, Campus 365, and Edunext, alongside newer entrants and your current vendor's renewal pitch. Some are strong on academics, some on fees and administration, some on a particular board. The checklist above matters precisely because no two are strong everywhere — the right choice is the one that clears your non-negotiable core and your India bar, not the one with the most logos on its website or the loudest sales rep. Treat every "all-in-one" claim as a question to test, not a fact to trust.
What it really costs
Indian school ERPs are almost always priced per student per year. Broad cloud products commonly land between ₹40 and ₹150 per student annually, so a 600-student school sees roughly ₹60,000 to ₹2 lakh a year depending on modules, board complexity, and support level. The traps are predictable. "Starting at ₹X" usually means a stripped base plan, with the parent app, online payments, SMS, and report cards as paid modules that quietly double the quote. Online fee collection carries a gateway charge (MDR) of roughly 1.8–2% on cards and often near-zero on UPI — ask whether the school or the parent absorbs it. SMS is frequently per-message on top. Get one all-in annual figure for your real student count, including implementation and training, and compare those — not the headline.
Where Inkwelly fits
Inkwelly is built to clear this checklist, not dodge it. The fee engine handles Indian fee reality — term plans, sibling and RTE concessions, fines, UPI-first online collection — and the parent app, attendance alerts, and board-format report cards are part of the platform, not surprise add-ons. It runs in Hindi and English on a budget Android phone, stores data in India, and imports your existing students and fees during onboarding. Pricing is per student, all-in, so the number you compare is the number you pay. To see the wider market first, start with our guide to the best school management software in India, or learn how to read a quote in our school software price breakdown.
“The best school ERP isn't the one with the longest feature list. It's the one that still answers the phone in week six — and does the three things your office does every day without an asterisk.”
Decide it in three weeks
Decide it in three weeks, not three months. Week one, write your requirements and shortlist three products. Week two, demo each on your own data and run your hardest workflow live. Week three, call references, get all-in prices in writing, and read the exit clause. The school that buys this way pays for what it uses and isn't surprised in October. The school that buys on a feature list and a friendly rep spends the year working around the gaps it never tested for. The checklist is boring. The October it saves you is not.
Bring your checklist to the demo
Book a 30-minute demo, load your own students, and run every test on this list — fees, report cards, parent app, all-in price.
Frequently asked
7 questionsHow do I choose the right school ERP for my school?
Write your daily must-haves and your board's report-card format first, shortlist three products, then demo each on your own real data and run your hardest workflow live. Confirm what's included vs paid, get one all-in annual price in writing, and call two reference schools before signing.
What features should a school ERP have in India?
A non-negotiable core of admissions, fees with concessions and online collection, attendance with parent alerts, board-format report cards, parent communication over WhatsApp and SMS, and payroll with TDS, EPF, and ESI — plus UDISE+ and APAAR exports and a Hindi-English mobile experience.
What questions should I ask a school ERP vendor before buying?
Ask for an all-in annual price for your exact student count, what's included vs paid add-on, the UPI and card gateway charges and who pays them, two reference schools of similar size and board, and the data-export clause if you leave.
How long does it take to choose and set up a school ERP?
A disciplined evaluation takes about three weeks — requirements, demos on your own data, then references and pricing. Implementation and data import typically run a few weeks more, depending on how much existing student and fee data needs migrating.
What are common mistakes when buying a school ERP?
Buying on a feature list instead of testing daily workflows, comparing 'starting at' prices that exclude the parent app and report cards, skipping reference calls, and not checking the data-export clause. Each one shows up months after the contract is signed.
Should a small school buy a full ERP or start with one module?
Most small schools should start with the module that hurts most — usually fees — on a platform that can grow into the full ERP later, so they're not migrating data twice. Confirm the same student record powers every module before you commit.
How much should a school ERP cost per student in India?
Commonly ₹40–₹150 per student per year for a broad cloud product, so a 600-student school sees roughly ₹60,000–₹2 lakh annually. Always price the all-in figure including the parent app, online payments, SMS, and support — not the headline base plan.
You might also like
3 readsSee Inkwelly on your school
30-minute demo. We open your current ERP with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.