Node Preferences - Customers - General
The following table lists the preferences available in the Customers - General area. There are also loyalty-related preferences available in Customers - Loyalty.
| Preference | Description |
|---|---|
| Allow duplicate customer IDs | Allow two or more customers to have the same Customer ID. |
| Append Installation ID to customer ID | If selected, when Retail Pro assigns a Customer ID to a new customer, the Installation ID is appended to the Cust ID (next available sequential number). If not selected, the next available sequential number is assigned as the Cust ID. If the preference is disabled, the installation ID will not be added to the custid. Instead 0's will be prepended to create a custid with a required length of 9 digits. The Installation ID can be viewed in the Store records in preferences in RIL |
| Default Customer Share Type |
Prompt: RP Prism will prompt the user to select a Customer Type if the user tries to save the record before entering a Customer Type. |
| Apply Customer Tax Areas for | Bill To Customer: If selected, when a Bill To Customer with an assigned tax area is entered on a transaction, a prompt is displayed asking if the tax area should be changed to the Bill To Customer's tax area. Ship To Customer: If selected, when a Ship To Customer with an assigned tax area is entered on a transaction, a prompt is displayed asking if the tax area should be changed to the Ship To Customer's tax area Bill To and Ship To Customer: If selected, whenever a Bill To Customer or a Ship To Customer with an assigned tax area is entered on a transaction, a prompt is displayed asking if the tax area should be changed to the customer's tax area. Example: Customer A and Customer B are each assigned a tax area in the customer record. Customer A is entered as the Bill To Customer on the transaction. A prompt will be displayed to change the tax area. Customer B is entered as the Ship To Customer. Another prompt will be displayed. |
| Customer Required Fields | IYou can require that new customer records include entries in specific fields before the user can save the record. For example, you might want new customer records to include address and phone information. In the Customer Required Fields area, click the check box for each field that will require an entry to save a new customer record. This is an inherited preference designed to be set at the Parent level. Once set at the parent level the configuration is maintained down to the child nodes. About Company and Name or Company required fields Company 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. Name or Company is dynamic. If First Name, Last Name, or Company are enabled, then Name or Company is disabled. If First Name, Last Name, and Company are all disabled, then Name or Company can be enabled. Enabling Name or Company 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, (First Name, Last Name when issuing an invoice to a person). In the Name or Company field, the Associate can enter First Name, Last Name, or Company name. |
Sample Customers > General Preferences
