Custom Fields & Column Visibility
Okommerce has a global custom-field system: an "add a custom field" capability available on essentially every form across the platform — not just…
What is the global custom field system and where does it apply?
Okommerce has a global custom-field system: an "add a custom field" capability available on essentially every form across the platform — not just products, but customers, vendors, orders,…
How do you add a custom field to any form (product, customer, vendor, order, lead)?
On any form that supports it, there's an "Add custom field" option.
What field types are supported for custom fields?
Custom fields support the standard set of types — text, number, date, dropdown, checkbox, and similar — matching the attribute system so behavior is consistent.
Are newly added custom fields shown by default?
Yes — once a custom field is created, it is displayed by default on the relevant form.
How do custom fields participate in data, search, and templates?
Custom fields are treated like built-in fields: their values are stored as real data, they can participate in search, and they're available to templates.
How does per-user column visibility work on list/grid views?
Every list/grid view offers an option to choose which columns are shown and hidden, and this choice is saved per user.
How do custom fields appear as columns in the relevant lists?
Custom fields you've added become available as columns in the relevant list views, so they can be turned on through the same per-user column-visibility control as built-in columns.
What are Order Field Sets and how are custom fields captured at checkout?
Order Field Sets are named collections of custom fields attached to a product so that specific information is captured at order time.
Where are order-time custom field values stored?
The values a customer enters for an order-field-set at checkout are stored on the order line (in a custom-fields payload on the line, CustomFieldsJson), so each purchased line carries its…