Custom Fields
Capture any business-specific data that doesn't fit the standard fields, from lightweight notes to fully reportable columns, without a development project.
- Capture what matters to your business
B-BBEE level on customers, batch codes on movements, project refs on orders: Floware holds anything that doesn't fit the built-in fields.
- Four tiers, lightest option wins
From quick display-only notes to fully searchable columns with reports: Floware picks the lightest option that fits, and you can promote fields as needs grow.
- Filter, export, report on anything
Elevate custom fields to first-class columns and they become filter options, CSV export columns, and report dimensions, not just decorative labels.
- Extends without drifting
Custom fields ride alongside the core model, so they stay consistent with the audit trail, permissions, and state machines instead of drifting as standalone concepts.
What it does
Every business captures information that doesn't fit the standard fields: a B-BBEE level on a customer, a batch code on a stock movement, a project reference on a sales order. Vertex supports four levels of custom fields, from lightweight notes stuck onto any record through to fully searchable columns with their own reports. The data model is built to accept custom fields everywhere; Floware surfaces them on the screens and reports the customer cares about, picking the lightest option that fits each field.
What it replaces
The alternative in most ERPs is "talk to us in six months and we'll raise a change request". The alternative without an ERP is a spreadsheet tab called extra info that nobody trusts. Vertex is built so that extending the data model is a normal part of the product, not an exception, and the lightest tier is a quick configuration change, not a development project.
Who it's for
- Every business. No two businesses have the exact same data. The question is how much of your custom data you want to treat as first-class (searchable, reportable) versus display-only.
- Regulated industries: food & beverage (lot numbers, best-before dates), pharmaceuticals (GMP batch records), chemicals (SDS references), electronics (serial numbers), where specific fields are non-negotiable.
- Businesses with compliance or reporting requirements specific to their country or industry: B-BBEE in South Africa, country-of-origin for customs, tariff codes, CE marking references.
- Distributors selling into mixed channels where each channel needs its own reference codes (retailer SKUs, marketplace IDs, EAN codes, customer-specific part numbers).
What problems it solves
- "We need to track B-BBEE level against every customer." A display-only field Floware can surface on the customer overview in a short turnaround: no new column or database change needed.
- "We need to filter the customer list by region." Turn that into a first-class field: it becomes a column on the list, a filter option, a CSV export column, and a dimension you can report on.
- "Our auditor wants to see the purchase reason on every PO." Add it as a field that rides along with the purchase order and lands in the audit trail automatically, without adding a new database column.
- "We have two more customer types our competitors don't: trade and wholesale." Extend the built-in Type list rather than inventing a parallel concept that drifts out of sync with everything else.
- "Our approval workflow is different from the default." Extend the Status state machine with your own transitions ("pending approval", "awaiting signature") without losing the built-in guard rails.