The Field Your Industry Needs
Every industry has one number a regulator, a donor or a buyer will ask for that no general system ships with. A custom field is how it gets a proper home — typed, validated, with an example in the empty box — instead of a line in the notes.
An agro-input distributor in Nakuru sells crop protection products, and every one of them carries a registration number from the Pest Control Products Board. A county inspector can ask for it on any shelf on any day. The item record has a name, a code, a unit and a price. It has nowhere for the registration number, so for three years it has lived in the description field, typed four different ways, and on about a fifth of the items not at all.
Every sector has a field like that. An NGO needs the donor grant code on every expense claim. A contractor tendering to government needs a supplier’s AGPO certificate number and when it expires. A transport company needs the insurance policy number on every truck. None of these belongs in a general product, and all of them belong in yours.
Where a field can go
The field builder in Settings offers 52 kinds of record. In inventory: items, adjustments, transfers, counts, warehouses and locations. In procurement: suppliers, supplier applications, requests, quotation requests, quotations, orders, bills and contracts. In sales and point of sale: customers, quotes, orders, invoices, credit notes, payments, contracts, leads, sales, tills and cash sessions. In finance: accounts, budgets, manual journals and payment runs. In people: employees, users, roles, departments, leave requests, expense claims, contracts, reviews and job applicants. And assets, work orders, projects, tasks, tickets, workflows, bills of materials and assembly orders.
A field is not a note. It has a type, and the type decides what can be typed into it: text, long text, whole numbers, decimals, money, percentages, dates, dates with times, yes or no, a single choice from a list, several choices, a file, a web address, an email address, a phone number or a barcode. Four types point at records you already have: a user, a department, a warehouse or a location, stored as a link to that record rather than as its name, so a renamed warehouse does not break the field.
Three fields, built properly
| Field | On | How it is set up |
|---|---|---|
| PCPB registration number | Items | Text, required, a pattern it must match, in a Compliance section, with an example in the empty box |
| Donor grant code | Expense claims | A single choice from the five live grants, required, retired options kept on old claims |
| AGPO certificate number | Suppliers | Text, required only when the supplier is marked as an AGPO supplier, with an expiry date beside it |
Each of those uses a rule the builder already has. Text can carry a minimum and maximum length and a pattern. Numbers can carry a minimum and maximum. Files can be limited to certain types. A field can be required always, or required only when another field holds a particular value: the certificate number is demanded from AGPO suppliers and from nobody else. Where the value must come from a list someone else publishes, a choice field fits better than text with a pattern, for the reasons in a catalogue is not a text field. Fields can be grouped into named sections in the order you choose, so the compliance fields sit together rather than scattered down a long form.
The example in the empty box
Every field can carry a placeholder: up to 120 characters shown inside the empty box as an example of what belongs there. It is the cheapest piece of data quality in the product; the item master’s heavier checks, duplicate detection among them, are in the duplicate check set to exact. A storekeeper who sees one real registration number, copied from a product label, in the empty box types the next one in that shape; one who sees an empty box types whatever they remember. Leave it blank and the form shows a plain hint instead, Type a value… for a required field and Optional for the rest. The same placeholder travels with the field to the API and to the phone app, so the example is the same wherever the number is entered.
A label says what the field is. A placeholder shows what the answer looks like, and that is the part people get wrong.
Where a field shows up
Each field can be switched on or off separately for the create form, the edit form, the record’s page, lists, reports, exports, the mobile app and portals. A field that only matters when goods are received can stay off the create form; one that is internal can stay out of a supplier’s portal. The phone app reads the same definitions as the web, so a field added on Tuesday appears in the app without an app update, and an offline edit that clashes with a change made on the web is shown for someone to resolve rather than silently overwritten.
Two more kinds of field do jobs a note never could. A formula field is calculated from other values on the record, to the number of decimal places you set, and cannot be typed over. A sensitive field is masked, fully or to its last four characters, for anyone without permission to see sensitive values, can be encrypted where it is stored, and each time someone does see it unmasked on a record, that is written to the activity log.
Changing a field once people depend on it
A new field starts as a draft, which no form, no API call and no phone sees until it is published. Once it is live, the risky changes are the ones that look small: making a field required, changing its type, retiring a choice, archiving it. Before any of those, the builder works out what the change would touch: how many records already hold a value, how many would fail their next save under a new required rule, how many duplicates a new uniqueness rule would trip on, which saved reports and workflows read the field, and which phones are reading the module.
A workspace can go one step further and switch on approval for field changes. Then publishing or archiving a field always waits for a different person’s approval, and an edit waits only when the impact check says it would break something. An archived field disappears from forms, but a record that holds a value in it still shows that value on its page. The registration numbers typed in 2026 are still there when the inspector asks in 2028. For how fields sit beside the rest of a record’s data, see the field customization overview.
Fields shaped to your sector
The builder, its 20 field types, the placeholder, the impact check and the approval switch are in place. These extensions come up most often, and we can add them to your workspace.
Fields for chosen roles
A field shown only to finance or only to HR, beyond the masking a sensitive field already gets.
Links to more record types
A field that points at a customer, a supplier, a project or an asset, as the four existing reference types point at users and warehouses.
A starter pack for your industry
The fields an agro-dealer, a clinic or an NGO usually needs, set up with their patterns and placeholders in one step.
What AWRA OpsHub does today
- A field builder on 52 kinds of record, across inventory, procurement, sales, point of sale, finance, people, assets, projects and helpdesk.
- Twenty field types, including money, percentages, files, barcodes and links to users, departments, warehouses and locations.
- Validation rules: length, number ranges, patterns, file types, and required-when-another-field-equals.
- A placeholder per field, shown on the web, through the API and in the phone app.
- Visibility per form, page, list, report, export, the app and portals, with formula fields and masked, optionally encrypted sensitive fields.
- Drafts, an impact check before risky changes, and an optional second-person approval for publishing, archiving and breaking edits.
More we can add to your workspace
- A field shown only to chosen roles, on top of the per-surface visibility and sensitive masking. Commission it
- The builder on customer contacts and customer addresses, which the wider field registry already describes. Commission it
- Links to customers, suppliers, projects and assets as reference field types. Commission it
- Industry starter packs of ready-made field definitions. Commission it
Where we point you to a specialist
- We do not decide what format a regulator’s number takes. You set the pattern from the authority’s own guidance, and the field enforces what you set.
Role-specific fields and links to more record types are the two extensions organizations ask for first.
The short version
If a number your sector depends on lives in a description or a note today, give it a field of its own: the right type, a pattern, a section, and a placeholder that shows the answer. Start it as a draft, publish it when it is right, and let the impact check tell you what a later change would break before you make it.
See field customization in AWRA
Custom fields across modules, the builder’s rules, and how fields reach reports, the API and the app.
Explore field customizationFrequently asked questions
Which records can carry custom fields?
The builder offers 52 kinds of record, including items, assets, warehouses, suppliers, purchase orders, customers, invoices, point of sale sales, accounts, budgets, employees, expense claims, leave requests, projects, tasks and tickets.
What does the placeholder setting do?
It puts an example of the answer inside the empty field, up to 120 characters, such as a registration number in the right shape. Left blank, the form shows a plain hint instead. The placeholder is also sent to the API and the phone app.
Can a field be required only some of the time?
Yes. A field can be required whenever another field on the record holds a particular value, such as a certificate number required only for suppliers marked as AGPO suppliers.
Do custom fields work in the mobile app and the API?
Yes. The API publishes each module’s field definitions, including type, rules, options and placeholder, and the phone app renders them. A field can also be hidden from the app if it only matters on the web.
What happens to old values if we archive a field?
Forms stop offering it, but any record that already holds a value still shows it on its page. Before archiving, the builder tells you how many records hold a value and which reports and workflows use the field.