No-Code ERP Customisation: Fit the System to Your Business With Settings, Not Code
For owners and IT leads who have been told every change needs a partner and a custom module, and want to know what can be done by settings instead.
No-code ERP customisation means fitting the system to your business through settings an admin controls, rather than code a partner writes. Most requests are not unusual: another field, a different list, a new approval rule, your own document numbers.
When those changes are code, each one costs money and has to be retested at every upgrade. Over a few years the custom code becomes the thing nobody dares touch.
This page covers what code customisation costs, an illustrative example, and the layers of configuration in Apragya.
What ERP customisation cost looks like over time
Partner fees
Each small change becomes a paid work order.
Upgrade risk
Custom code is retested, or the upgrade is skipped.
Waiting
Business changes wait for a developer's calendar.
Dependence
Only one partner understands the changes.
An example: a Kolkata tea trading company
Take an illustrative tea trader moving from an older system with many custom modules. The finance head listed every customisation and asked which could become settings.
Customisations moved to settings
Week 1
Thirty-one customisations listed.Week 2
Fourteen became custom fields and lists.Week 3
Six became approval policies and numbering.Week 4
Four became agents on records.Week 5
Two became small built apps.
Of thirty-one customisations, twenty-four became settings or agents, two became small built apps, and five were dropped as no longer needed. The finance head now owns the changes that used to need a partner.
How ERP customization without coding works in Apragya
Step 1 of 5
Fields and lists
Add custom fields; configure statuses, categories and dropdown values.
- Fields and lists: Add custom fields; configure statuses, categories and dropdown values.
- Rules: Set approval policies, numbering series and email templates.
- Access: Define roles with permissions down to sub-features.
- AI: Bind agents to record events and adjust their behaviour.
- New apps: Build what the apps do not cover in Vibe Studio.
A configurable ERP in India, against custom code
Custom code gives an exact fit on the day it is written. Configuration gives a slightly less exact fit that you control and that carries through upgrades. For most SMEs, control and upgrades are worth more than the last few per cent of fit.
Code customisation against Apragya configuration
| Feature | Partner-written code | Apragya configuration |
|---|---|---|
| Who makes changes | A developer | An authorised admin |
| Upgrades | Retest custom code | Settings carry over |
| Cost per change | A work order | Admin time |
| Unusual needs | More code | A built app on the same platform |
| Record of changes | Code history | Audit log |
Checked against public information on 16 September 2026.
What sets Apragya's configuration apart
One record
Configuration applies across apps that share the record.
Multi-company
Settings can differ by company where needed.
Audit log
Changes are recorded with user and time.
Human review
Agent output can wait for a person.
Employee self-service
Configured processes reach staff on their phones.
No lock-in
Built apps can be exported with their data.
Details: custom fields without a developer, approval workflows without code, and how workflow automation compares with Odoo.
Getting started
- List every customisation in your current system.
- Mark each as field, list, rule, access, AI or new app.
- Drop the ones nobody uses.
- Configure the rest before go-live.
- Keep a short change log owned by one admin.
The list of customisations nobody uses is usually longer than expected.
What it costs to start
No-code customisation questions
Can we change dropdown values ourselves?
How long does moving customisations to settings take?
Can AI agents replace some custom code?
What if we need something no setting covers?
Do settings survive upgrades?
Who can change settings?
What does it cost to start?
List your customisations, then sort them
Most become settings you own. The rest become small apps on the same platform.