Almost every college ERP vendor says their product is customizable. The word hides a wide range, from a settings page to a months-long development project. Before you rely on it, find out which one you are being offered.
What are the three kinds of customisation?
| Kind | What it is | Who does it | Typical cost and risk |
|---|---|---|---|
| Configuration | Using settings and builders in the product | Your staff, or the vendor on your behalf | Low. Survives upgrades |
| Customisation | Changing how the product behaves with extra code | The vendor’s developers | Higher. May need rework on upgrade |
| Custom build | A new module or integration made for you | The vendor, as a project | Highest. Scoped and priced separately |
Most colleges can get what they need from configuration. The more you can do there, the lower your cost and risk.
What should a college be able to configure?
- Application forms. Questions and sections for each programme.
- Document lists. The documents each programme asks for.
- Workflow steps. The stages an application or request passes through, and who handles each.
- Approval chains. Who approves leave, expenses and requests.
- Fee structures. Fee heads, instalments and due dates by programme.
- Policies. Leave rules, attendance rules and statutory settings.
- Roles and access. Who can see and do what.
- Branding and letterheads for receipts and documents.
If any of these needs a developer, ask what it costs each time.
What usually costs extra?
- A new module you do not already have
- A special integration with a system outside the product
- A bespoke report that goes beyond the reports and exports provided
- A change to core behaviour that no setting controls
None of these is unreasonable. They should simply be scoped and priced in writing before work starts.
What should you ask a vendor about customisation?
- Which of our processes can we set up ourselves, without code?
- What would a change cost, and who decides the price?
- Do our settings survive an upgrade?
- Is every change recorded, with who made it and why?
- Who owns the configuration and the data if we leave?
- Can you show one of our processes being configured live?
The last question is the most revealing. A product that is genuinely configurable can show you in minutes.
How does Tuling handle it?
In Tuling Admissions, application forms, document lists and workflow steps are set up to match your college and your programmes. In Tuling Financials, fee structures, discounts and waiver rules are policy settings with a reason and an approver recorded. In Tuling HCM, leave and statutory rules are settings you can read and update, with a history of changes. Anything beyond configuration, such as a new integration, is scoped separately.
Related reading: how to choose college ERP software in India and building a college ERP one module at a time.
The rule of thumb
Prefer a product where your own staff can change the common things. You pay less, you wait less, and your settings stay yours.
Frequently asked questions
What does customizable ERP mean?
It usually means the software can be adapted to your processes. The adaptation may be done through settings you control, or through changes the vendor makes to the code.
What is the difference between configuration and customisation?
Configuration uses settings and tools built into the product, with no new code. Customisation changes the product itself, which costs more and can complicate upgrades.
Can we change workflows and forms ourselves?
In a well-designed system, yes. Application forms, document lists, workflow steps and approval chains can be set up by authorised staff.
Do customisations break when the software is upgraded?
Configuration normally survives upgrades. Code-level customisation may need rework, so ask how the vendor handles it.
See what you can configure yourself
We set up one of your processes live, such as an application form or an approval chain, so you can judge the effort.
Book a demo- Customizable ERP
- College ERP
- Configuration
- Buyer's guide