Prism Administration Console Guide
Node Preferences > Transactions > General
In Node Preferences > Transactions > General, define key point of sale preferences. Refer to the following table for information about the available settings. Please be aware that the Lookup Item By preference applies to ALL DOCUMENTS.
| Option | Description |
|---|---|
| Lookup Item By | In this area, select the fields that will be available to look up items on a document. (Note: This preference applies to all documents; not transactions only.) Here's an example of how the preference works: If only UPC is selected, then when a user scans (or enters) a value in the Lookup field, RP Prism will check to see if any items have a matching value in the UPC field. If both ALU and UPC are selected, then when a user scans (or types) a Lookup value, RP Prism will search for an item with a matching entry in either the UPC or ALU field. Available Lookup Fields: ALU, Description 1, Description 2, Item Number, UPC (default) |
| Search Alternate Vendor ALU/UPC | Prism enables retailers to assign one or more "alternate vendors" to items. Each alternate vendor has its own UPC or ALU for the item. If the Search Alternate Vendor UPC/ALU checkbox is selected, then Prism will include alternate vendor UPC or ALU in the search. |
| Default Item Type for New Transaction | Select the item type that will be the default item type for new transactions: Sale, Order, or Return. This is useful when a location is primarily used for the selected transaction type. For example, a store might be dedicated to orders or returns. This preference only determines the default item type. Users with the required security permission can change item type on transactions. |
| Bring Original Price from Price Level |
This preference enables you to set the price level to use as the "original price" on a document. |
| Default Status Filter for Pending Transactions |
When using Pending Transactions, users can filter the list of results by transaction type: All, Held, Pending or Discard. This preference enables you to control which option is selected by default when a user goes into Pending Transaction Lookup. |
| Force logout after creating transaction | If this option is enabled, Prism will automatically log out the current user immediately when a transaction is updated. This feature is especially useful for businesses where multiple employees share the same workstation. This feature helps ensure the correct Associate is entered on each transaction. Using this feature helps prevent situations in which User A logs in, walks away from the workstation, and user B then finishes the transaction or creates a new transaction while still logged in as User A. This creates inaccuracies in Associate information with the potential to impact commissions. Now, using the Auto Logout feature, the current user will be logged out when a user updates, cancels, or holds a transaction, or when a document is automatically generated (e.g. when using the "Purchase Store Credit" feature for customers) (Default = disabled) |
| Require Customer for Returns | If selected, a customer must be entered on the transaction to return an item. |
| Require Customer for Sales | If selected, a customer must be entered on sales transactions. |
| Require Customer for Manual Discount | If selected, a customer must be entered for a user to enter a manual discount. (Note: Permissions are still applied) |
| Consolidate like items on documents | If selected, when the same item is scanned multiple times, the item quantities are consolidated on a single line item. If not selected, when the same item is scanned multiple times, a separate line item will be created for each scan. |
| Restrict transactions to a single item type |
This preference is useful for keeping strict separation of document types for accounting purposes. When the preference is enabled, any single transaction will only have items of a single type, whether that is sale, order, return or send sale. When the preference is disabled, a single transaction can have items of multiple types and this may have unexpected results when the documents are sent to the accounting system. For example, a transaction with a mixture of sale and order items is sent to the accounting system (via Accounting Link) as a sales document. When the preference is enabled, if a user clicks the Item Type button, the "Apply to all Items" check box will be selected and set to read-only. If the preference is disabled, the "Apply to all items" check box is cleared by default and can be selected, if needed. This is important for retailers who operate in environments where regulations prohibit the mixing of sale and return items on a single transaction. When the preference is enabled, any single transaction will only have items of a single type, whether that is sale, order, return or send sale. When the preference is disabled, a single transaction can have items of multiple types. Mixing sale and order items on transactions may have unexpected results when the documents are sent to the accounting system. For example, when a transaction with a mixture of sale and order items is sent to the accounting system (via Accounting Link), the Cost of Goods, merchandise sales and all other ledger accounts reflect the entire document totals rather than only the sale items. |
| Restrict Order Item Rows to Single Quantities | (Prism 2.3 and later) The "Restrict Order Item Rows to Single Quantities" preference, when enabled, does just what the name implies. When a user lists an order item on a transaction, that order item can only have a quantity of one (1). This preference is a child setting to "Restrict transactions to a single item type" and is only available when "Restrict transactions to a single item type" is enabled. By default, the preference is disabled. A common use case is to avoid having partially fulfilled orders that could result mismatches in the tax rate on the original order and an item return. For example, an order is created that has one or more items and a full deposit is taken. After the order is finalized, the customer wants to increase or decrease the quantity. However, in the interim, the tax rate has changed. If the existing order item has been partially fulfilled and the tax rate has changed since the order was created, we cannot change the tax rate on the order item. |
| Restrict return tenders to original sale tenders | (Prism 2.3 and later) The "Restrict Return Tenders to original Sale Tenders" preference, when enabled, restricts both the tender types and the amounts on an item return to what was taken on the original sale. This setting can be configured at the Subsidiary and Store level. This setting gives retailers greater control over returns and aligns with what customers typically want (i.e., to be refunded in the same tender as the original sale). |
| Always allow store credit tender for returns. | (Prism 2.3 and later) This is a child preference to "Restrict return tenders to original sale tenders." If enabled, store credit can be used as the return tender (assuming it is allowed in Tender Requirements preferences). |
| Apply original transaction discount to return items | A key concern for merchants is how discounts will be handled on returns, especially the return of a single item from a multi-item transaction that has a transaction discount applied. This preference helps ensure that any discount amount on the original transaction is correctly applied to return items - so the merchant doesn't lose on the transaction (e.g., by refunding the full price on an item sold at a discount). If enabled, and the original document has some unspread transaction discount, the server will calculate an EXTRA item discount (in addition to item discounts brought from the original sale) by using the formula: ExtraItemDiscAmt = OrigItemSalePrice * (OrigSaleTransDiscAmt / OrigSaleSubtotal). This is similar to [virtual] spreading of the original global discount to each original item proportionally to their prices (e.g. two items $10 and $90 dollars each with $20 global discount will take $2 and $18 extra item discount during return respectively). Note that the SaleSubtotal is NOT the same as transaction subtotal - it includes only sale items (not order or return) from original sale document. |
| Activate Gift Card for Original Amount |
This preference controls whether gift cards can be activated for an amount other than the original amount. |
| Open Tender screen in pop-up window | If selected, the tender screen opens in a child window of the current browser page. If not selected, the tender screen displays in the current browser page. Default = Not selected. |
| Prompt for decimal qty items |
If selected, when a decimal quantity item is listed, a prompt is displayed so the user can edit the decimal quantity for the transaction. |
| Automatically Print/Updated balanced document |
If selected, when a user takes payment and the transaction is balanced (i.e. no Amount Due), then the print/update process starts automatically. |
| Open cash drawer prevents new receipt |
If selected, users will be prevented from starting a new transaction unless the cash drawer is closed. This preference requires that you also select the Cash Drawer Status Enabled check box (Node Preferences > Hardware > General). |
| Count Package as a single sale | If selected, when printing a transaction with a package item, the package item is treated as a single sale item (Qty = 1) rather than multiple component items. If not selected, when printing a transaction with a package item, the quantity listed represents the quantity of the component items that comprise the package. |
| Print Package Items | If selected, when printing a receipt that has a package item, both the package header item and the component items are printed. If not selected, only the package header item is printed. |
| Print Package Item Prices | If selected, when printing a receipt that has a package item, both the package header item price and the component item prices are printed. If not selected, only the package header item price is printed. |
| Print Broke Kits | If selected, when breaking a kit at POS, both the Kit header item and the individual component items are printed. |
| Print Kit Item Prices | If selected, when breaking a kit at POS, both the Kit header item price and the Kit component item prices are printed. |
| Print Zero Quantity Items | If selected, the printed receipt will include any items that have a quantity of zero (e.g. voided items). If not selected, the printed receipt will not include items that have a quantity of zero. |
Prism 2.5 Transactions > General Preferences:
