Field configurations let you hide unused fields and mark others as required on the main data-entry forms, and reorder or hide the columns on the sale and receiving item grids.

The item form has a lot of fields, and so do customers, suppliers and expenses. Most stores use a fraction of them. Field configurations let you take the rest off the screen, and make the ones you care about impossible to skip — without any customization.

This is different from custom fields, which add fields of your own. Field configurations govern the fields that ship with the product.

Where to find it

Each module's list screen has a Field Configurations link (a wrench icon) alongside its other tools. Open the module from the left navigation menu and look for it on the list screen:

• Items
• Item Kits
• Customers
• Suppliers
• Employees
• Expenses
• Appointments
• Invoices (configured separately per invoice type)

You need permission for the module itself to change its field configurations — an employee who cannot open Suppliers cannot change what the supplier form shows.

Hide and require

The configuration screen is a table with one row per field and two checkboxes:

• Hide — the field disappears from the form. Existing data is kept; you simply stop seeing and editing that field.
• Required — the form refuses to save until the field is filled in.

Forms with tabs are configured tab by tab. The item form, for example, splits into Item Info, Pricing, Inventory and Locations; item kits into Item Kit Info, Pricing and Locations. Customers, suppliers, employees, expenses, appointments and invoices are a single list.

Click Save and the change takes effect immediately for everyone.

The settings are store-wide, not per employee. If some staff should see less than others, that is a job for permissions rather than field configurations.

Sensible uses

• A store that does not track suppliers per item can hide the supplier fields on the item form.
• A store that always wants a phone number can mark Phone Number required on the customer form, so nobody saves a customer you cannot call back.
• A service business that never sells by weight can hide weight and unit fields.
• A shop with one location can hide the per-location pricing fields.

Do not hide a field you still populate through import or the API — hiding it only removes it from the form, so the value is still there and still used, but nobody can see or correct it on screen.

Sale and receiving grid columns

The columns of the item grids on the sale and receiving screens are configured separately, in Store Config → Sales:

• Sale Items Details — the columns of the item queue on the sale screen.
• Receiving Items Details — the same for the receiving screen.

Each is a small table with three columns: Sort, Title and Hide. Drag a row by its handle to change the order columns appear in, and tick Hide to leave a column out. Click Save at the bottom of Store Config.

This is how you get a register that shows exactly what your cashiers need — price, quantity, total — and nothing that just makes the line wrap. The item identifier column follows Store Config → Sales → Item ID to Show on Sales Interface, so it reads as the item number, product ID or item ID according to that setting.

Common questions

I hid a field and now I cannot enter data I need. Untick Hide for it. Nothing was deleted — the field and its data come straight back.

Can I make a field required for one location only? No. Field configurations are store-wide.

Required is ticked but old records do not have the field filled in. Required is enforced when a record is saved, not retroactively. Existing records are untouched until someone edits and saves one, at which point the field has to be filled in.

A field I want to hide is not in the list. Only the built-in fields of the supported forms appear. Fields you added yourself are managed under custom fields, which have their own show/hide settings.