Custom fields
Capture the information your business actually needs on customers, jobs, quotes, and invoices.
What custom fields are#
Custom fields let you add extra data capture to your core records — customers, jobs, quotes, and invoices — without any coding. For example, an HVAC company might add “Equipment model” and “Refrigerant type” to jobs; a cleaning company might add “Access code” to customers.
You define the fields once in Settings; they appear on the create and edit forms for the relevant entity and are saved with the record.
Defining custom fields#
Open Settings → Custom fields. Choose the entity type (Customer, Job, Quote, or Invoice), then add a field. Each field has a label (what appears on the form), a type (text, number, date, yes/no, or a list of choices you define), and an optional placeholder or hint.
Fields you create appear on every new and existing record of that type — you don’t need to opt in per record.
Filling in custom fields#
When you create or edit a customer, job, quote, or invoice, a Custom fields section appears below the standard fields. Fill in the values that apply; fields you leave blank are saved as empty rather than blocking the form.
Custom field values are also visible on the record’s detail page so you can refer to them at a glance.
Custom fields from intake forms#
If a customer fills out your intake form and provides information that maps to a custom field on the resulting job, that answer is automatically carried into the job’s custom fields — nothing is dropped.
Data imported from a previous system#
If your records were migrated into Meridian from other software, anything the importer carried over that doesn’t map to one of your defined custom fields still shows up — jobs, quotes, invoices, and customers render it in an “Imported” section under Additional details on the record’s page. That includes things like marketplace channel details, route stops, truck rentals, deposits, reviews, attached documents, and your old system’s record numbers, formatted readably (money as money, dates as dates, files as links).
Where an imported value matches one of your defined fields but was stored under a slightly different key spelling, Meridian resolves it automatically — the defined field shows the imported value until you edit and save it, at which point your edit becomes the canonical value.
Related articles