Overview
The following release notes contain updated versions of the following files:
- Genius Classic POS
- Admin Console
If you have questions regarding the updates described in this document, please contact the Support Department by email at geniusrestaurantsupport@globalpay.com or phone at 800-4genius.
What's New?
The following release notes detail the enhancements we have included in this release.
HR-53320 KDS now displays item special instructions when running in real time
We have modified the KDS to include special instructions with items when running in real time. In the Display Formats screen, if you select Real-time in the On the Fly KDS list, the POS sends new items to the KDS as soon as you add them to a ticket. In previous versions, when displaying menu items in the KDS screen, the app listed each item with its modifiers, but not special instructions. We have modified this, and now when you order an item and add special instructions to it, the KDS will display the item with those instructions, even when running in real time.
HR-56377 New subtotals for non-revenue items added to Daily Summary Report
We have added various new subtotals for non-revenue items in the Daily Summary Report. Under Net Sales, we have removed the Non-Revenue Items subtotal and replaced it with separate subtotals for Non-Revenue Items (Gross) and Non-Revenue Items (Net). Under Discounts, we have added subtotals for Non-Revenue Discounts and Non-Revenue Adjustments. In the Daily Summary Report, the total for Non-Revenue Items (Net) is calculated by subtracting all non-revenue discounts and non-revenue adjustments from the total for Non-Revenue Item Gross.
Updates
The following release notes detail the fixes we have included in this release.
HR-50102 POS no longer "moves" Pay-at-the-Table payments to other tickets
In previous versions, if your location uses the Pay-at-the-Table service, you may have encountered a problem. In certain circumstances, after applying a payment to a ticket with a PAX device, the POS may have "moved" the payment to a different ticket. For instance, a customer may have used a credit card to pay a ticket with a total of $26.37. But after making the payment, if you then tried to close the ticket, the POS may not have closed it because the $26.37 payment was no longer on the ticket. However, if you then reviewed all other tickets currently open, you may have found the $26.37 payment on a different ticket. We have corrected this, and now when you add a card payment to a ticket with a Pay-at-the-Table device, the POS no longer moves the payment to a different ticket.
HR-58354 When using Como credit, POS no longer deducts taxes from Online Order tickets
In previous versions, if your location uses the Como loyalty service, you may have encountered a problem. Specifically, if a customer placed an order in the Online Ordering website and applied Como credit to the ticket, the POS may have deducted taxes along with the credit amount. For instance, if a customer ordered an item for $5.00, the total with tax may have been $5.30. If the customer then applied a $5 Como credit to the ticket, the remaining total should be the tax on the original total ($0.30). However, in these cases, the POS displayed a total of "0.00", because it recalculated the tax based on the total after the credit was applied. We have corrected this, and now when customers apply como credit to online orders, the POS does not deduct or recalculate tax totals after the credit is applied.
This problem only occurred in locations configured to use loyalty credit as discounts. In the Admin Portal's Main Menu, click Loyalty. In the Loyalty screen, in the Loyalty list, select Como. (The program will display additional configuration settings for the Como service.) In the POS Configuration area, if you select the Points/Credit as Discount check box, the POS will treat reward points and credit as discounts rather than a receipt type. If you enable this setting, the POS will not include Como reward credit when calculating sales tax for its ticket.
HR-60037 POS Order History no longer lists all gift card purchases as "Pending"
In previous versions, if your location uses a third-party loyalty service (such as MobileBytes, Como, or Paytronix), the POS may have displayed gift card purchases with inaccurate statuses in the customer's order history. For instance, in the POS, you may have opened a new ticket, accessed the ticket's Info screen, and entered the customer's loyalty account number. After associating the ticket with the loyalty account, if you then tapped the Order History button (in the top banner of the Ticket panel), the POS may have listed any previous gift card purchases with a status of "Pending", even if the gift cards were valid.
In such cases, the POS erroneously displayed the "Pending" status for all gift items, regardless of their actual statuses. We have corrected this, and the POS now displays gift card purchases with accurate statuses in the Order History screen.
HR-60190 POS now reverses partially approved payments for bar tabs
In previous versions, if your location uses bar tabs, you may have encountered a problem with the Partial Approval POS prompt. In the Admin Console's Main Menu, click Location Setup, then click Settings. In the Location Settings screen, click the App Settings tab. In the App Settings tab, the Partial Approval POS Prompt check box enables you to set the POS to display an alert prompt when partial payments are received for a ticket. If you select the check box, the POS displays a prompt stating that a partial payment was received, along with the amount paid and the remaining amount due. This prompt is intended to alert servers that a partial payment has occurred and that additional payment is pending.
However, in previous versions, if you preauthorized a credit card for a ticket and it was only partially approved, the POS did not display the Partial Approval POS Prompt, even when configured to do so. We have addressed this by modifying how the POS handles partial approvals for bar tabs. Now, in locations configured to use bar tabs, if you preauthorize a card and receive a partial approval, the POS reverses the partial payment and displays the "Declined" message for the entire amount.
HR-61590 POS uploads DoorDash item data with accurate prices to Avero service
In previous versions, if your location uses the Avero and DoorDash services, you may have encountered a problem with pricing rules. In certain circumstances, if you ordered an item associated with a pricing rule in DoorDash, the POS may have later uploaded the transaction's data with inaccurate prices to the Avero service. Normally, when you order an item with a pricing rule within DoorDash, the POS applies the rule immediately when the item is ordered. However, in certain circumstances, the POS may have applied the pricing rule to the item a second time, specifically when uploading the transaction's data to the Avero service. Consequently, sales reports within Avero may have included inaccurate prices for menu items associated with pricing rules. We have corrected this, and the POS no longer applies pricing rules a second time to menu items when it uploads transaction data to the Avero server.
HR-61871 POS accepts manually entered amounts for cash payments
In previous versions, if your location uses cash discounting, you may have encountered a problem. In certain circumstances, when paying a ticket with cash, if you manually entered a base total (rather than a cash discount total) in the Checkout screen, the POS may have still prompted you for an amount, as if you had tapped the Cash button without first entering an amount. We have corrected this, and now when you pay a ticket with cash and enter a base total manually, the POS accepts the amount you enter and processes the payment without prompting for an amount.
HR-63350 POS applies Como discounts properly at checkout
In previous versions, if your location uses the Como loyalty service, you may have encountered a problem. In certain circumstances, the POS may have generated an error when you applied a Como coupon code to a ticket and then tried to check out. For instance, in an open ticket with a total of $10.95, the customer may have asked you to add a Como coupon that takes $2.00 off any order that costs greater than $10. If you accessed the customer's Info screen and applied that code, the POS would have verified that the ticket met the coupon's requirements and then added the discount to the ticket. However, if you then tapped Checkout (to pay the ticket), the POS may have displayed an error and removed the coupon code.
In such cases, when you tapped Checkout, the POS again tried to verify that the ticket met the coupon's requirements, but it did so by examining the ticket's total after the discount ($8.95) instead of before the discount ($10.95). We have corrected this, and now when you apply a Como discount to a ticket, the POS applies the discount properly at checkout.
HR-63591 POS now prints updated or edited future order tickets properly
In previous versions, if your location uses future orders and has set the POS to print them at the start of each day, you may have encountered a problem. Specifically, if you created a ticket for a future order, then sent it, then reopened and edited it, the POS may not have printed the updated ticket the following day.
You can enable the future orders feature in the Location Setup screen. In the Admin Console's Main Menu, click Location Setup, then click Settings. In the Locations Settings screen, click the App Settings tab. In the App Settings tab, you can enable the location to place future orders (prepared for a specific time and date in the future) by selecting the Future Orders check box. Then, in the Future Orders Send Behavior list, if you select Send future orders at start of day, the POS will hold each future order it receives until the date of its prep time, then it will send all future orders for the current day to the kitchen printers at the start of that business day.
However, in previous versions, if you set the system to print future orders at the start of each day, you may have encountered a problem. For instance, you might have created a future order set to print the following day. Later, you may have accessed that ticket and made changes to the ticket. Normally, the POS should print the future order ticket the following day with the changes. However, in previous versions, the POS may have printed only the original version of the ticket, before changes were made later. We have corrected this, and now if you create a ticket for a future order, send it, then open it again and make changes, the POS will print the updated ticket, not the original (outdated) ticket.
HR-63755 POS no longer applies reward credit twice to Como tickets
In previous versions, if your location uses the Como loyalty service, you may have encountered a problem. In certain circumstances, if you applied a customer's Como reward credit to a ticket, the POS may have applied it to the ticket twice. For instance, if you applied a Como credit of $11.00 to a ticket, the POS may have applied a credit of $22.00 to the ticket. We have corrected this, and now when you apply a Como reward credit to a ticket, the POS only applies it once.
HR-64110 POS prints accurate credit sale statuses on printed receipts
In previous versions, the POS may have printed inaccurate credit sales statuses on printed receipts. In certain circumstances, if you tried to process a credit card transaction multiple times, the POS may have printed a receipt for the transaction with a Credit Sale Status listed as "Unknown", even if the transaction was never processed. We have corrected this, and the POS no longer prints "Unknown" as the Credit Sale Status of failed transactions when printing receipts.
HR-64778 POS deducts Como credit from ticket total properly
In previous versions, if your location uses the Como loyalty service, you may have encountered a problem. In certain circumstances, if you added a Como credit to a customer's ticket, the POS may not have deducted the credit amount from the ticket's total. The credit appeared on the ticket, but the app did not include it when recalculating the ticket's total. We have corrected this, and now when you apply Como credit to a ticket, the POS deducts the credit amount from the ticket's total properly.