Custom Fields Without a Developer: Capture What Your Business Tracks, on the Records You Already Use
For admins and process owners who need one more field on a customer, employee or order and should not have to wait for a developer to add it.
Adding custom fields without a developer sounds minor until you need one. A pharma distributor needs a drug licence number on every customer. A school needs a blood group on every student. The standard form has neither.
When the field is missing, people type it into the notes, a spreadsheet or the address line. Then nobody can filter, validate or report on it.
This page covers what missing fields cost, an illustrative example, and how custom fields work in Apragya.
An example: a Guwahati medical distributor
Take an illustrative distributor supplying chemists across the north-east. Every customer must hold a valid drug licence, and the licence expiry matters before each dispatch.
The fields the admin added to customers
Customer, licence section
Validated against the state's format.
Cannot save a customer without it.
Retail or wholesale, from a set list.
The scanned certificate, on the record.
Who verified the licence.
Grouped together on the form.
Within a week every active customer had a licence number and expiry on the record. The dispatch team could filter customers with licences expiring this month and call them before the next order.
How to add custom fields in ERP records
Step 1 of 5
Choose the record
Pick the app and the record type, such as customers or employees.
- Choose the record: Pick the app and the record type, such as customers or employees.
- Pick a type: Text, number, decimal, date, select, multi-select, email, phone, file, currency, user and more.
- Set rules: Mark it required, give a default, and add limits or a pattern.
- Place it: Put it in a named section, in the order you want.
- Use it: The field appears on forms and can be used in lists, filters and agents.
Before and after custom fields
With a custom field
- A proper field on the customer form
- Checked against a pattern
- Available in filters and lists
- Everyone sees the same label and help text
Choosing custom fields software, and what to check
Some systems add custom fields as loose text, which cannot be validated. Others need a developer and an upgrade test. Typed fields with validation, set by an admin, give you clean data without code, and they survive upgrades.
Notes and workarounds against Apragya custom fields
| Feature | Notes and workarounds | Apragya custom fields |
|---|---|---|
| Type | Free text | Fifteen field types |
| Validation | None | Required, limits and patterns |
| Layout | Wherever it fits | Named sections and order |
| Reporting | Not possible | Usable in lists and filters |
| Change | Developer | Admin, without code |
Checked against public information on 16 September 2026.
What sets Apragya's configurable forms apart
Safe changes
A field's name and type are fixed once created, to protect data.
Across apps
Custom fields work on records in many apps.
Per company
Fields can be set for a company in a group.
Agents read them
AI agents can use custom field values on the record.
Role-based access
Who can add fields is controlled by role.
Retire, then remove
Fields can be switched off before being deleted.
See how custom fields compare in Apragya and Zoho and Apragya and Tally, or read about no-code ERP customisation.
Getting started
- Ask each team what they type into notes today.
- Turn each repeated item into a field with a type.
- Add validation where a format is known.
- Group related fields into a section.
- Tell the team, and clean up old notes over a month.
The notes field is the best list of missing custom fields you will find.
What it costs to start
Custom field questions
Can we change a field's type later?
Can a field be required?
Can we check a format such as PAN?
Will custom fields survive upgrades?
What does it cost to start?
Move one note into a proper field
Pick the item your team types into notes most often, and give it a field.