Customer Required Fields

You can configure Prism to require that customer records have entries in certain fields before a customer record can be saved or before the customer can use a certain tender. Two different preference areas are used to define these settings:

• To define required fields for new customer records, navigate to Admin Console > Node Preferences > Customers > General and select the desired required fields. When a user creates a new customer record, required fields are highlighted and if any required fields lack an entry, the user is prevented from saving the record.
• To define required customer fields for specific tenders, navigate to Admin Console > Node Preferences > Transactions > Tenders > Tender Requirements and select the desired required fields for individual tenders. If the selected tender has any customer fields marked as required, Prism checks the customer record to confirm those fields have an entry. If any required fields are missing an entry in the customer record, a prompt is displayed at POS. This enables the Associate to capture the information (updating the customer record) and complete the transaction.

Customer Required Fields for New Customer Records
Navigate to Admin Console > Node Preferences > Customers > General. In the Customer Required Fields area, click the check box for each field that will require an entry to save a new customer record. 
Important! The Customer Required Fields are designed to be set at the Parent level. This is an inherited preference, so once set at the parent level, the configuration is maintained down to the child nodes. 
Sample Node Preferences > Customers > General:
  
When adding a new record, the required fields are highlighted in red. The Save button (or OK button in the case of Address/Phone/Email modals) remains disabled until all required fields have an entry. 
Sample New Address modal on new Customer record with required fields highlighted in red:

 
About "Company" and "Name or Company" required fields
The "Company" checkbox in customer required fields preferences works the same as the other required fields. If it is selected, then when creating a new customer record, the Company field requires an entry. The "Name or Company" checkbox is dynamic. If First Name, Last Name, or Company are selected in preferences, then "Name or Company" is disabled. If First Name, Last Name, and Company are all disabled in preferences, then "Name or Company" can be selected in preferences. Selecting "Name or Company" in preferences disables First Name, Last Name and Company. The "Name or Company" selection helps retailers in some countries (e.g., Spain) comply with fiscal laws that require the company name when issuing an invoice to a legal entity, and First Name, Last Name when issuing an invoice to a person. In the "Name or Company" field on customer records, the Associate can enter First Name, Last Name in the case of a person, or Company name in the case of a legal entity.
Customer Required Fields for Tenders
In Admin Console > Node Preferences > Transactions > Tenders > Requirements, you can configure Prism to require that certain customer fields have an entry before the Associate can update the transaction. For example, you can require that when taking the check tender, the customer entered on the transaction must have an entry in the Phone 1 field.
In Tender Requirements preferences, each tender has a dropdown button that when clicked displays the list of customer fields that can be marked as required. Select each field that will be required for the tender. You can define separate settings for Take and Give operations.  
Sample Node Preferences > Transactions > Tenders > Requirements:
 
At POS, when the Associate selects a Tender Type, if the Bill To Customer on the transaction has any required fields for that tender type missing in the customer record, a prompt is displayed. Enter the required information and click Save.
Note: The customer record is NOT updated with the information entered at POS.
Sample Customer Required Fields prompt: