ERP Custom Fields and Form Builder: Fit the System to Your Plant

An ERP form builder lets you add custom fields (often called user-defined fields) to the standard screens of your system, so information the vendor never anticipated has a proper home on the record itself. In Data, P-Soft’s manufacturing ERP, the form builder is part of the Elite plan and attaches your own fields to twenty core forms; the list covers, among others, inquiries, customers, suppliers, parts, payments and invoices.

Every factory has a handful of facts that matter enormously to it and to nobody else. A machining shop needs to know the heat treatment spec of each part. A fabricator wants the customer’s purchase order number printed on every invoice. A plant that switched systems last year still gets phone calls quoting legacy customer codes. Off-the-shelf software cannot predict all of this, and the usual workaround is a spreadsheet maintained by one person on one laptop. This guide looks at the alternative: when custom fields make sense, how to design them so forms stay usable, who should be allowed to create them, and exactly what Data’s form builder does and does not do.

What are custom fields in an ERP system, and when do you need them?

A custom field is an extra data slot that you attach to an existing form. It sits next to the built-in fields, is stored with the record and shows up whenever someone opens that customer, part or invoice. You do not need a developer, and you do not change the underlying software.

You probably need them if any of these sound familiar:

• The notes box is doing the work of five fields. People type “45 HRC, yellow zinc, ship in crates” into a comments area, and nobody can later find all zinc-plated parts.
• A shadow spreadsheet runs the department. Sales tracks trade-show leads or customer segments in a file that lives outside the system.
• Legacy references refuse to die. Old customer and part numbers still appear on drawings and in emails.
• The same question keeps coming up in meetings. “Does this supplier have a frame agreement?” and the answer lives in one buyer’s head.

What does the Data form builder actually do?

With Data’s form builder, twenty core forms can be extended with fields you define. Among them are the inquiry, customer, supplier, part, payment and invoice screens, which covers the places where most plant-specific information tends to collect.

It comes with the Elite plan, the tier designed for large and multi-site factories. Elite also includes the purchasing committee, automatic approval of in-tolerance inspection results, the machine-side operator panel and the oversight inbox for evaluating departments.

To set expectations honestly: the form builder adds fields to existing forms. It is not a report designer, a workflow editor or a scripting tool. If your requirement goes beyond extra fields, bring it to the demo so we can discuss the right approach rather than stretch a tool beyond its purpose.

Custom field examples for manufacturers (hypothetical)

The table below shows hypothetical fields a make-to-order plant might add. Use it as inspiration, not as a template to copy wholesale:

Notice that each field answers a question someone actually asks. A field that never drives a decision only makes the form longer.

How to design user-defined fields: a six-step method

Most form-builder regret comes from adding fields on impulse. Six months later the customer form has thirty extras, half of them empty and two of them meaning the same thing. Work through these steps before you click “add”:

1. Start with the question. Not “add a segment field”, but “we want to see which industries send us the most inquiries”. Sometimes the data already exists elsewhere in the system.
2. Pick the right form. Facts about the customer belong on the customer form, not repeated on every invoice. Duplicated data eventually contradicts itself.
3. Name it for a newcomer. Choose a label a new hire would understand on day one. Avoid department slang.
4. Decide the kind of value. Number, date, plain text or one of a fixed set of options? Where choices are limited, a fixed list beats typing.
5. Think carefully about “required”. If a value is usually unknown at first entry, making it mandatory just produces dashes and “TBD”.
6. Pilot with one team. Let real users work with the field for two weeks and check whether it actually gets filled.

How to keep ERP forms from getting cluttered

A form that needs three scrolls to complete will gradually be saved half-empty. A few habits keep things lean:

• Set an internal cap on custom fields per form and exceed it only with a clear reason.
• Every quarter or half-year, list the fields that are nearly always blank and decide whether they stay.
• Do not create permanent fields for short-lived initiatives such as a one-off campaign.
• Before creating a field, check whether a standard or existing custom field already covers it.

Who should be allowed to add fields? Light-touch governance

If every department adds fields whenever it likes, forms end up reflecting a dozen personal preferences. You do not need a committee, just three things:

• A data owner, usually someone in IT or production planning, who creates and maintains fields.
• A short request form stating the question to be answered, the target form and who will fill the field in.
• A field register: a simple list of every custom field with its name, form, meaning and requesting department.

Data gives every user a separate role and permissions, so each person sees only what they should. That foundation helps you formalise the process; ask during the demo how access to the form builder itself is assigned.

Form builder vs. a spreadsheet next to the ERP

Many plants have lived with a side spreadsheet for years and reasonably ask what changes. Mostly, the day-to-day details:

Data is installed on the factory’s own server, so your custom fields remain on your network and keep working during an internet outage, like everything else in the system. Updates run automatically with a backup taken before each one. If you are still weighing deployment models, see our comparison of cloud and on-premise ERP.

Migrating side spreadsheets into custom fields

1. Collect every side file and write down what each column means and who maintains it.
2. Drop columns nobody uses any more; migrating dead data only bloats forms.
3. For the rest, choose the target form and field name using the six steps above.
4. Clean the values, for instance by merging three spellings of the same supplier category.
5. Migrate, then archive the spreadsheet as read-only so nobody keeps editing it.

The P-Soft team can move your existing data from Excel or previous software into Data; the scope of that service is agreed in your contract and depends on the plan.

Is the Elite plan right for you? A quick checklist

• At least one permanent spreadsheet runs alongside your current system.
• Structured information keeps ending up in open comment boxes.
• Legacy codes from a previous system are still in daily use.
• Departments keep their own extra data on customers, parts or suppliers.
• You run a large plant or several sites and need full control.

If most boxes are ticked, Elite deserves a close look. If you are earlier on the journey and the priority is getting sales, purchasing and stock under control, the lower plans are a sensible place to begin.

Frequently Asked Questions

Which Data plan includes the form builder?

The form builder is part of Data Elite. It is not included in Start or Pro.

How many forms can take custom fields?

Twenty core forms, including inquiry, customer, supplier, part, payment and invoice.

Can the form builder create reports or workflows?

No. It adds fields to existing forms; custom reports and new workflows are outside its scope.

Where are custom fields stored?

On the factory’s own server, inside your network, together with the rest of your Data records.

Can you migrate our existing spreadsheets?

Yes. Our team moves data out of Excel files or a previous system into Data; how much is included depends on your contract and plan.

Want to see custom fields on forms modelled after your own plant? Request a demo of Data and we will suggest the plan that matches your factory.

Further reading

• What Is ERP? Complete Guide to Enterprise Resource Planning
• ERP Software Guide: Benefits and How to Choose the Right System
• How to Choose the Right ERP Software for Your Organization

Complete guide: ERP software