Every business is different. For example, a workshop wants to know the
car registration; a clinic, the date of birth; a fashion store, the
size or favorite color. With custom fields, you define what appears on the registration form — both in physical stores and online. The fields are automatically added to the program enrollment form, just before the customer accepts the terms. No code, no complications.
2 types of fields
Fields visible only to your team: not everything has to be asked from the customer. You can create internal-use fields that only your administrators see — to add notes, segment by your own variables, or enrich the profile from the back office without the customer seeing it.
Data visible to the customer: those that the customer will fill out in their registration process, or through a subsequent survey, for example in exchange for a certain number of gift points. These fields will be available for the user to consult or modify.
Data always well formatted
Each field can have its own rules: minimum and maximum length, mandatory value, custom format using regular expressions. If you need the NIF to have the correct format or for the registration to follow a specific pattern, you can define it without code.
Each extra field has a unique technical identifier (slug) that is returned directly in the Omniwallet API. This means you can read and write them from any external tool — just like custom fields work in Salesforce, HubSpot, Klaviyo, or any CRM you use. Your CRM can send data to Omniwallet and receive it back. If you update a field from the back office, your CRM will see it in the next synchronization. If you update it from the CRM, it will be reflected in the customer record in Omniwallet.