October 2024 PrismPOS Release Notes

Application Updates from: July 11 - Sep 25, 2024

Release to Production: Oct 13, 2024

Application Version: 2.0.632

Please note: This release DOES include a back-office server update.

PrismPOS is the preferred point-of-sale solution for PrismCore and Mosaic. As additional functionality is added to Mosaic and PrismCore, application APIs are expanding to offer expected behavior regardless of a store’s inventory management system. Along with essential data exchange, there is an ongoing initiative to unify POS configuration, streamline content management, and enhance transaction processing quality.

A/R account with No Limit

When an A/R account with No Limit was used, the printed receipt was saying “No Limit” but when the receipt was downloaded from Thunder Admin > Transaction Inquiry > Download Receipt, the balance was displaying a dollar amount. The 1.9 functionality was printing the dollar amount so POS 2.0 code has been changed to print the dollar amount to stay consistent.

To accommodate all desired configurations, a new parameter has been added to Thunder Admin > POS Parameters > Receipts > Receipts tab called “Tender Account Limit”.

If checked, the text for that parameter will display under the balance.
Stores can add “No Limit” for the text, or any custom text, and that text will be displayed under the balance for accounts that are set for No Limit or Unlimited.
If the account has a balance set, the text for Tender Account Limit parameter will not print.

ID Required at Register

For PrismCore customers specifically, when an ID Required item is scanned at the register, the prompt will now display correctly. Previously, when an item that was marked for ID Required in PrismCore > Item Maintenance, scanning the item was not displaying the prompt, “This item (SKU) requires you validate the purchaser’s ID. Is this purchaser eligible?” as it did when the item was hand entered. This has been fixed.

Display Item Details Screen Configuration

To better facilitate adding products to a transaction in rapid succession, and to handle multiple transactions quickly, a parameter called “Display Item Details Screen After Selection” was added to Thunder Admin > POS Setup > Registers tab > Edit Register.

When checked the items details screen will be displayed after the item is added to the transaction.
If left unchecked, the items search screen will stay displayed allowing items to be quickly added to the transaction. The parameter will be checked by default for current stores.
Neither state will affect how items are scanned, only the screen behavior after scan.

Suggested Tender Button

When tendering with A/R, the suggested tender amount button was showing only the subtotal even though the default amount was correct. This has been fixed so the suggested tender button matches the default amount.

Register Login / Logout Behavior

Multiple enhancements have been made to login / logout behavior:

Cashiers can now swipe to login as well as use the automatic logoff feature and continue to run transactions correctly without error. Previously, issues were being reported when cashiers swiped to login after an automatic logoff, causing an increase of transaction upload failures from PrismPOS to PrismCore. This has been fixed.
When a cashier logs into the register, the logout timer (if set) starts upon login. Now, if a cashier logs in and then walks away from the register, the register no longer remains open to use. Previously, the Logout Time (Seconds) timer in Thunder Admin > POS Parameters > POS Setup > Registers > Edit Register was not starting when logging into the register, rather it would wait until a transaction was completed. This has been changed.

Report Hour Offset Fix

If sales are completed after midnight, and the Report Hour Offset is set, Register Reports and Cashier Reports now display as expected, showing the correct data, date and time per the Report Hour Offset settings. Previously, in PrismPOS, Prism 1.9 and Thunder Admin, Register Total reports were not showing current amounts after midnight as the Report Hour Offset setting in Thunder Admin was not being honored. This has been fixed.

Receipts: Total Items on Refunds

The Total Items on the refund receipt now show the number of items being refunded. When a sale is completed, the “Total Items” on the receipt displays the number of items. On refunds, the Total Items line was previously always displaying as zero. This has been fixed.

Transaction Fidelity

As a part of our commitment to ongoing monitoring and maintaining a high transaction fidelity between PrismPOS and connected systems, multiple edge-case issues with transactions and sale imports to corresponding backoffices have been addressed:

Specific authorization failures in Freedompay related to high item-count transactions have been addressed. Previously, POS data was formatted to exceed the size Freedompay accepted when the transactions contained more than 5 items, causing authorizations to occasionally fail. This has been fixed.
For Mosaic users specifically, if a transaction was taxed and then either the A/R account or A/R tender was changed to non-taxable after the sale took place, the refund for the transaction will include tax, matching the original sale and tax amount. Previously, for Mosaic stores, refunds were not calculating sales tax if the account or tender was changed to non-taxable after the sale was completed with tax.
When a transaction that was tax exempt was tendered with an A/R tender that had a DCC discount on the account and the transaction was split tendered, tax was being added back for the additional tenders. This has been fixed so that if an A/R tender is used that has a DCC discount to tender a tax exempt transaction, the transaction remains tax free for the additional tenders.
Multiple observed scenarios known to cause sale import and upload failures from POS to PrismCore have been addressed:
1. A digital text (Jumpbook) sale that was suspended/retrieved and then completed.
2. Using a guarantee tender (credit card or A/R) to split tender and using the same tender again to complete the transaction was allowing the guarantee tender flag to be used twice.