Node Preferences - Transactions - Tenders - Requirements
The Tender Requirement preferences give retailers control over the tenders available to users at POS, including:
- Tenders you take as payment
- Tenders you give as change
- Tenders that cause the Change Window to display
- Tenders that cause the cash drawer to open
- Default take tender
- Default give tender
- Maximum overtender amount
- Required fields for EFT tenders
Controlling the tenders that can be used for POS activities has important security benefits. In addition, limiting the UI to only those tenders actually used by your business results in a UI that is easier for employees to navigate.
| Preference | Description |
|---|---|
| Take | If selected, the tender can be taken as payment. |
| Give | If selected, the tender can be given as change. |
| Return | If selected, the tender can be used on a return (when the transaction total is less than 0.00. |
| Deposit Return | If selected, the tender can be used to return the deposit for a closed (cancelled) order. |
| Change Window | If selected, when the user touches or clicks the Print Update (or Update Only) button, the Change window will be displayed, listing the tender amount(s) taken and given in change. This serves as a visual reminder to Associates to prevent mistakes when giving change. |
| Open Drawer | If this checkbox is selected, the drawer will open when taken the tender. This is typically only needed for tenders such as Cash and Foreign Currency but may also be necessary for other tenders such as Gift Cards, Gift Certificates and Credit Cards. |
| Default Take | If selected, indicates the tender will be selected by default when a user is taking payment. Default = Cash |
| Default Give | If selected, indicates the tender will be selected by default when a user is giving change. Default = Cash |
| Max Take Amount | If selected, limits the total amount allowed for a particular tender type on a single transaction. For example, you can restrict an individual store to not take more than $1,000 in cash on a single transaction. At POS, Prism adds the Give amounts for a tender type and subtracts the Take amounts for that tender type. If the resulting amount exceeds the Max Over Tender and the Max Take Amount, a message displays, showing the Take amount error. If the amount is under the Max Take Amount but over the Max Over Tender amount, then an overtender error is shown. This ability to set the maximum take amount for individual tenders is a legal requirement in certain countries. You can configure the setting at the store level as some countries do not have such restrictions. |
| Max Over Tender | Enter the maximum amount by which the transaction can be over tendered (with the difference between the transaction total and the over tendered amount being returned as change to the customer). |
| Enable Tender Rounding | To round tenders, click the Enable Tender Rounding Checkbox. When you select the checkbox, options for selecting a Rounding Method (None, Up, Down, Normal) and a Rounding Multiple (e.g. 0.10) become available. |
Required Customer Fields for Specific Tenders
You can require certain customer information be included on a transaction when using specific non-eft tenders. 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. When tendering a transaction, Prism checks Admin Console > Node Preferences > Transactions > Tenders > Tender Requirements. 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 for the tender 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.
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 Tender Requirement Preferences
Permissions for Individual Tenders
A full suite of permissions are available for individual tenders, enabling you to control which employee groups can use individual tenders for payment, giving change, or returns. The Tender permissions will only be applied if the tender is already selected in Tender Requirements for that specific action (give/take/return).