TRAY 7.07 Release Notes

TRAY Product Release Notes 

Version 7.07

7.07 New Features & Enhancements 

Client Enhancements (POS & KDS) 

POS

​​Remove the Options under the ‘About’ Button - POS & Kiosk

STR-11328

Description

We have removed the following options under the ‘About’ Button on the POS and Kiosk. Please note, we will reintroduce these in a future version once updated: 

• Learn More
• Privacy Policy
• Terms of Service 

Indicator When There is an Open Check on a Destination 

STR-11132

Description

In the new transfer UI, if there is not a table map configured, we have added an indicator that there is an open check on the destination. This change will reflect accordingly when using the ‘Start New Check’ option as well as the ‘Other Destination' option, as shown below: 

POS Cart Item Icon Status Changes - Phase 1 

STR-11562

Description

We have made changes to the following POS Cart Item Status Icons: 

1. New, Accepted, Ready and Done Order Status UI Changes

As part of these changes: 

• The item will now show the time when the order was fired.
• The time will display on the POS based on the device configured timezone.
• All times will display in 00:00 format for HH:MM with the indicator for AM and PM

• To the left of all times, there will be an icon to indicate the order status and the contents of the cell will be highlighted to correspond to the color codes for NEW, ACCEPTED, READY and DONE.

The UI for the button changes are as follows: 

NEW:  Arrow Symbol - Green - 006400 → White Text

 

ACCEPTED: Hourglass Symbol → Yellow - FFA500 → White Text

READY: Single Checkmark → Blue -  3355CF → White Text

 

DONE: Double Checkmark → Black - 000000 → White Text

KDS

Item Level Routing

STR-8586

Description

Please see Item Level Routing documentation. 

Server Enhancements (HQ, API, DataAPI)

HQ 

Replace DB ID with PLU in 'Select Product' Dropdown of Discount

ENT-6157

Description

The current interface in TRAY HQ displays the internal Database ID of products when users create or edit a Discount and attempt to include or exclude products. This ID is not meaningful to most users, especially those in operational roles who rely on the PLU code for identifying products. This change aims to improve usability by displaying the PLU instead of the DB ID, making the process more intuitive and reducing the chance of human error.

Pay Class Permissions

ENT-6152

Description

Currently in TRAY HQ, permissions related to Pay Classes are handled in a general way, meaning that if a user has access, they can typically perform all actions — viewing, adding, editing, and deleting — without any specific control over each function. This becomes a challenge in enterprise environments where roles and responsibilities vary greatly across teams and locations.

By introducing granular permissions for each action (Add, Edit, View, Delete), TRAY HQ will provide enterprise managers with the flexibility to assign permissions based on real job roles, reduce human errors, and improve overall system governance. The new permissions we have introduced are as follows: 

Permissions

• View Pay Class - ability to view existing pay classes
• Add Pay Class - ability to add a new pay class
• Edit Pay Class - ability to edit an existing pay class
• Delete Pay Class - ability to delete an existing pay class

Enterprise Features Push Permission

ENT-5702

Description

Prior to this change, the ‘Push’ permission was bundled with the Add/Edit permission for all enterprise-managed features, including:

• Cash Management (Reasons, Actions, Reason Codes)
• Categories
• Pricing Schedules
• Revenue Centers, Service Templates
• Discounts
• Tax Categories
• Roles
• Pay Classes
• Tender Types
• Products

To alleviate operational concerns, we have added a separate ‘Push’ permission or the following Enterprise-managed features:

• Cash Management (Reasons, Actions, Reason Codes) - Push Cash Management
• Categories - Push Category
• Pricing Schedules - Push Pricing Schedule
• Revenue Centers, Service Templates - Push Revenue Center/Service Template
• Discounts - Push Discount
• Tax Categories - Push Tax Category
• Roles - Push Role
• Pay Classes - Push Pay Class
• Tender Types - Push Tender Type
• Products - Push Product

This ensures that node-level admins/users can propagate enterprise-managed entities to stores without modifying them at the node level.

Bug Fixes

Server & API

When leaving the Menu tab in HQ, navigating back should return the user back to the default screen

ENT-6355

Description

Prior to this change, the menu tab was artifacting the page to whichever tab was previously loaded. Going forward, if the user leaves the Menu tab, or clicks on Menu tab again, HQ will now reload back to the default screen. 

 

Olo Payments with AP and GP Tenders Reporting Incorrect Names on DSR

INFRAP-8362

Description

If there is an Olo Payment with AmazonPay Visa, it is showing as “OLO APOLO AP-VS” on DSR instead of “OLO AP - OLO AP-VS”. Going forward, the DSR will reflect the accurate tender name. 

 

Push Reason Codes, the “Select Reason Code” option does NOT note the Reason “Type” field

ENT-5868

Description

Going forward, when a user goes to push reason codes, In the ‘Select Reason Code’ dropdown, the reason name along with the type is displayed.

 

Check details report is showing incorrect open and close time for offline synced checks

INFRAP-8080

Description

We have resolved an issue where checks created and closed while the device was offline displayed incorrect open/close timestamps in the Check Details Report after syncing. The Orders and Payments Reports reflected the correct times, but the Check Details Report did not. This has been fixed to ensure that the Check Details Report now accurately reflects the POS time the tab was opened and closed.

 

Bulk Adding Items is not selecting the correct Menu / Section / Subsection

ENT-6352

Description

We have resolved an issue where, in some cases, the menu or subsection was not properly assigned when bulk adding products, resulting in a NULL value. This caused products to be improperly categorized or not appear as expected. The system now correctly assigns the appropriate menu and subsection during bulk operations.