Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Configuration

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.

A finance head sorting cards into five trays in a tea trading office

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

  1. Week 1

    Thirty-one customisations listed.
  2. Week 2

    Fourteen became custom fields and lists.
  3. Week 3

    Six became approval policies and numbering.
  4. Week 4

    Four became agents on records.
  5. Week 5

    Two became small built apps.
Five items were dropped; the rest were settings, agents or small 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.

Five trays of sorted cards with a small heap set aside
Most customisations became settings; the faded heap was simply dropped.

How ERP customization without coding works in Apragya

Step 1 of 5

Fields and lists

Add custom fields; configure statuses, categories and dropdown values.

  1. Fields and lists: Add custom fields; configure statuses, categories and dropdown values.
  2. Rules: Set approval policies, numbering series and email templates.
  3. Access: Define roles with permissions down to sub-features.
  4. AI: Bind agents to record events and adjust their behaviour.
  5. 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

FeaturePartner-written codeApragya configuration
Who makes changesA developerAn authorised admin
UpgradesRetest custom codeSettings carry over
Cost per changeA work orderAdmin time
Unusual needsMore codeA built app on the same platform
Record of changesCode historyAudit 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

  1. List every customisation in your current system.
  2. Mark each as field, list, rule, access, AI or new app.
  3. Drop the ones nobody uses.
  4. Configure the rest before go-live.
  5. 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

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

No-code customisation questions

Can we change dropdown values ourselves?
Yes. Statuses, categories and similar lists are configurable by admins.
How long does moving customisations to settings take?
It depends on how many you have. Listing and sorting them usually takes a few days; configuring them is done before go-live, alongside data migration and training.
Can AI agents replace some custom code?
Often. Checks and suggestions that were coded as custom logic can run as agents on record events, with human review where needed.
What if we need something no setting covers?
Build it as an app in Vibe Studio, on the same platform and records.
Do settings survive upgrades?
Yes. Configuration carries over; there is no custom code to retest.
Who can change settings?
Only roles given that permission, and changes are recorded.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

List your customisations, then sort them

Most become settings you own. The rest become small apps on the same platform.