POS

7/2024

Features

• DataCap* Cancel transaction from Tablet/Station -
  We are introducing a new feature that involves the DataCap Cancel integration for credit card transactions. This feature is primarily designed for tablet readers without screens but can be utilized for all types of readers. The new functionality will prompt a window during credit card transactions. Support documentation.

• Where’s my Food - SMS Feature - *This is NOT a live feature nor a GA feature yet*
  This feature’s goal is to enable consumers to receive updates via SMS on the status of their order and delivery. Sending consumers real-time SMS updates provides a quick way to communicate with consumers and improve their experience as they wait for the order. 

  • Order Confirmation -Stage event trigger for Order types -

  • Where's My Food - Replaceable Fields/Values -

  • Allow data sync with RM to work with new SMS message field on order stage events -

  • Where's My Food - Twilio integration -

  • Handle new order stage event for 3rd party, online & deferred orders -

• Integrate with delivery-api Dispatch Order endpoint - *Driver Track updates*

• Integrate Undispatch, Return Driver, Re-assign with delivery-api - *Driver Track updates*

• Item KDS - show deferred if items in order are deferred -

• Add new ThirdPartyTypes and OrdTags enumeration constants -
  Orders come into the POS with new ThirdPartyTypes and/or OrdTags values, so that these orders can be processed and tracked accurately.

• Cash drawer balancing: Make credit, gift, account, and other actuals read-only -
  With the changes made previously for cash drawers, there is no need to allow edits to credit, gift, account, or other actuals.

Bug Fixes

• KDS pending orders do not reflect correctly on the screen -

• Tax rate rounding to the hundredth decimal place when it is set to the thousandth after OrdTaxDataAccess Feature Flag Change -
  Taxes are saving to the OrdTax table after rounding the TaxRate to the hundredth when they are setup to the thousandth in the system.

• Refunds Done Through Manager Functions Don't Factor the Delivery Fee on Delivery Order Types -

• When the Feature Flag UseDatabaseCallPerformanceImprovement is True

  • Preselected modifiers linked to preferences are not showing up correctly when order is retrieved or printed -

  • POS fails to load excluded modifier objects on initial launch -

• Error message sprCustList_CellClick -

• vNext reports not sending in report packages -

• Monitor Item Display option is missing from the KDS Config UI of POS -

• KDS Config Filter By Order Type Breaks UI -

• KDS Deferred Order screen to update orders if items have been replaced/voided from the original order -

• Reports: Driver Mileage Report will only display the highest value of CC Tips instead of the sum when multiple orders are on one run -

• Show Rewards on Send/Collect configuration is being ignored by the POS -

• Hide field for “Qualifying Total” on non-Multiple Item Coupons -

• Cash drawer balancing: Gift card tip cannot be keyed in -

6/2024

Features

• vNext Reports refresh every 5 min through RM POS agent, and send a sync on close day -
  Whenever the Reports page in POS is open, the vNext report data in ADX is refreshed via the RM POS agent every 5 minutes. Closing the reports page stops the timer (the normal 15 minute refresh period triggered by the RM backend should remain in effect). vNext reporting data will now automatically refreshed as part of the close day report packages process, so that data I get for vNext reports in report packages (whether saving to file system or sending via email or ftp) contains updated data for the whole day.

• Implement new token process for Restaurant Management backend calls -
  This ticket will apply the decisions and patterns from previous Create proof of Concept feature to Restaurant Management back-end calls, effectively deprecating the old HMAC signature/IP verification process.

• vNext Reporting - Add Originator DataDog Metric -
  We wanted to show additional information on the vNext Reporting DataDog dashboard so that stakeholders can see what process and application triggered the report.

Bug Fixes

• UseDatabaseCallPerformanceImprovement Feature Flag causes Coupons with Order Type exclusions to ignore their configured exclusions -
  Exclude Order Type was not working correctly when 'UseDatabaseCallPerformanceImprovement' feature flag is enabled. Normally when using a coupon with this setting enabled the below message is triggered when attempting to utilize the coupon on an excluded order type. Now with the 'UseDatabaseCallPerformanceImprovement' feature flag enabled, it will allow you to apply the coupon regardless of what order type exclusion(s) have been configured.

• Moose's Tooth: dbo.OrdPayment line did not write in DB -
  Moose’s Tooth had an issue with a payment not writing in dbo.OrdPayment after the payment already was authorized and receipt was printed.

• Deferred orders not updating items on activation causing order items to not show up on order -
  Moose's tooth was having an issue with deferred orders where some of the order items were not showing up anywhere in the order screen after the order is activated.

• Pressing Send button twice with specific station configuration errors and sends POS into a screen loop -
  When a customer has the station configuration set to Logoff after each order as well as Caller ID after each order and they hit the Send button more than once on an order, they were getting an error and then were sent into a loop between the logon screen and the caller id screen.

• Cash > Account Payments are misbehaving -
  A dropdown for payment type is now available instead of the 3 buttons of Payment Type Categories.

• SaveAllOrderItemsCoupons - error when UseDatabasePerformanceImprovement FF is True -
  For Hungry Howie's, any order with a coupon gave an error, whether it was send order, retrieve order, or collect. Issue has been resolved.

• Weekly Sales for vNext reporting was not sending the correct date -
  Missed item in POC created - we only were sending dates if they had a date range, not a month/week.

• Print Button on reports for vNext in POS causing station to freeze. -

  If you select Enter on a keyboard it does select the OK, but does not if you don’t have a keyboard connected, the station becomes unusable. This has been remedied by using a standard print dialog.

5/2024

Features

• Increase Order Item Selection Color Contrast -
  Selecting an item on an order causes the background color to change to gray. The shade of gray was too light, making it difficult to tell which items are selected, given certain monitors, lighting conditions and viewing angles. The shade of gray has been changed to a darker gray so that it’s easier to tell which items are selected in a wider range of viewing conditions.

• vNext reports sending in POS report packages -
  Restaurant Management vNext reports replace POS reports in report packages when saving to file system or sending as email attachments, so that users see consistent reporting in POS report packages and Restaurant Management vNext reporting.

• vNext Reports Printing in POS Report Packages -

• Created option for automatically printing Restaurant Management vNext reports from POS and added the ability for report packages to automatically print those reports that are using Restaurant Management vNext reports.

• vNext reports fall back to Crystal Reports on failure in POS -
  If the Restaurant Management vNext Report fails to produce a report in the POS, system will now fall back to existing crystal reports-based POS reports, so customers can still access on-device reporting in case of network connectivity issues or Restaurant Management vNext Reporting outages.

Bug Fixes

• Account Payments Paid by Check Are Not Listed in Drawer Reconciliation -
  Customers can charge the balance of a Customer Account with 3 different payment types. (Cash, Check, and Credit Card). When they would collect that Account Payment to a drawer with a Check, the payment wasn’t showing in the “Other” section of drawer reconciliation, causing the drawer to be short without manual database manipulation by customer support.

• Add dbo.OrdCust to sync after any changes are made -
  OrdCust table was not syncing back to RM when changes are made to the customer address. POS DB updated but did not send that update to RM DB. This needed to be updated for Driver Track to show information correctly.

• Saving Employees in Master Schedule Creates Duplicate Schedule Entries -
  When Legacy Customers were using the Employee Scheduler in the POS, they could not use the Master Schedule feature to load due to this problem. This required then to manually create schedules, which is inefficient when the same schedule is created each week.

• Actual Cash changes do not take effect when UseCashDrawerBalancingFixes is enabled -
  When trying to improve Actual Cash parsing on UseCashDrawerBalancingFixes, it omitted a replacement of a dollar sign with an empty string and actually broke the parsing completely.

4/2024

Features

• Customer Facing Display (sign on screen) - Enhance the Total and amount due appearance to include Gratuity-
  Enhanced the sign on screen Amount Due to break down if gratuity is on the order. Employees using the tablets are not showing the customer the order that shows the gratuity being added causing the customer to double tip. Ask is to show the gratuity on the sign on screen along with any additional tips they select on the screen before they sign and submit.

• DoorDash marketplace orders with in-house delivery should keep the preauth tip in the paid amt-
  Temporary solution in Sites that use in-house drivers to deliver DDM orders are experiencing issue with assigning orders to drivers to the issue in until we can determine the longer-term solution.

• vNext reports showing in POS - PoC Option 1 (Part of Roadmap item - Reporting Data Integrity)-
  (This requires a feature flag to be enabled and ONLY available for RM customers.)
  POS users, were seeing vNext reports in POS rather than corresponding POS reports, so that I get consistent reporting between RM and POS.

• Include preauth tip in paid amt for in-house delivery with Menufy-
  Same change as in DoorDash marketplace orders with in-house delivery should keep the preauth tip in the paid amt but for Menufy instead of DDM, pending investigation in Sites that use in-house drivers to deliver DDM orders are experiencing issue with assigning orders to drivers.

• QR Code for KB Link in POS Close Day Form-
  Support asked for the ability to show links to knowledge base articles from within the POS, so that POS users can self-serve with documentation to resolve common problems, specifically for this item, the close-day process. This item exists to show the support team some ways in which we can do this from the POS so that they can be informed about what options are available.

Bug Fixes

• Performance updates for V3 (tablets and stations)*- Jira Ticket
  Tablet testing on V3 is showing performance issues when loading specific screens, such as Initial Startup, Login Screen to Main Form, Sending of Order, Time Clock screen.

• Item Countdown .Net error when no entries are in Menu86 table- JIRA Ticket
  When there are no items marked OOS (the Menu86 table is clear) and you attempt to set an item countdown value, then the system will throw a .NET error and block you from being able to set the item countdown.

• .Net Framework error on reports in POS- JIRA Ticket
  "DragDrop registration did not succeed" message when accessing reports.

• Customer search by account freezing screen- JIRA Ticket
  Changes for POS: Customer search missing guardrails, forces user to initiate system crash to move forward
  accidentally broke search by account. There should have been no change in behavior when searching by account for POS: Customer search missing guardrails, forces user to initiate system crash to move forward.

• Reports: Sales by Category on DPR is showing #### when running for multiple days- JIRA Ticket
  Moose’s Tooth reported another issue with the #### showing up on sales by category on the DPR.

• Split tickets not assigning a split number causing order items to not show up on order- JIRA Ticket
  Moose's tooth was having this issue with split tickets where some of the order items are not showing up anywhere in the order screen after the split is done - under the split it shows split number of 0.

• Replace r-enterprise.com URLs with hub.hungerrush.com in code & config**- JIRA Ticket
  Every year in December, we have to renew our r-enterprise.com certificates or risk outages connecting to RM from POS. To avoid this, the POS team should replace references to r-enterprise.com with hub.hungerrush.com. Functionality will be unchanged as a result, and we will not need to renew the r-enterprise.com certificate any longer.

• Tickets with Preauth tips that are being printed by stage events are showing incorrect totals- JIRA Ticket
  This requires a feature flag to be enabled and ONLY available for RM customers.
  Tickets that have a PreAuth Tip applied on an order are printing incorrect totals when printing from a stage. The total amount on the payment is including twice the value of the preauth tip causing it to be incorrect. This applies to Preauth Tips on ANY order type when printing by stages. This was likely a result of changes made on this item that did not include stage printing in the scope.

• Grat on Credit Card report is not being calculated correctly- JIRA Ticket
  Grat was not calculated correctly on Credit card report, when there were splits in the orders. This was noticed at Moose’s Tooth, but affecting all customers.

• Sequence in which you reconcile the payments should not change the calculations of the drawer when it is being balanced- JIRA Ticket
  Customers reported that when balancing a drawer that has values in the "Other" section of the details screen, when it does not get reconciled in a specific sequence the Tips and Totals will be incorrect. When closing a cash drawer that accepts payment types from the Other category as we are seeing with OrderAI customers (Text Prepaid), when reconciling the payments with tips if you add them starting from the Other section and moving towards the right one by one, then the CC Tips and Cash Total amounts seem to be adding up correctly.

• OrdTax records are removed after a split and OrdSplitTax.SplitNumber is not always correct- JIRA Ticket
  The legacy behavior to save order taxes/order split taxes worked like this:

  1. Add two items, split, send → no OrdTax records, only OrdSplitTax records are created

  2. Add two items, send, look up, split, send → both OrdTax and OrdSplitTax records are created

• Send & Stay button not working after the customer name entry splash screen prompts- JIRA Ticket
  When a customer had an order type that was configured to require “Name Only” and they were using the Send&Stay button on the Order screen, the button did not function properly and sent the order but did not keep it on the screen.

• When a Cash Drawer is configured to Tipped Employee and set as Server Cashout Drawer, Payroll Reports show CC Tip discrepancies- JIRA Ticket
  A customer reported seeing negative values in their POS Payroll Reports under the Employee CC Tips field. It was found that the cause of the negative values showing was due to cash drawer configurations that set conditions causing the system to subtract the CCTipsFromOthers field from the CCTips field in the CashDrawer table and use that value as the CC Tips value in the payroll report. The cash drawer configurations that cause this are having a cash drawer that is a Tipped Drawer and also making that cash drawer the default drawer for employees to cash out to. While looking into this issue I also found that when rebalancing the cash drawer and server drawers for a day, the issue would no longer be present. This is due to a separate bug that clears the CCTipsFromOthers value when rebalancing a drawer. The system should not do this.

• vNext reports not fully gated by feature flag- JIRA Ticket
  vNext reports showing in POS - PoC Option 1 introduced new behavior when a new feature flag was enabled. However, some of the behavior introduced was not gated by a feature flag:

  1. Changes to the phone list report that should never have been checked into main made there way into production without a feature flag

  2. One of the print buttons does not use the feature flag but always assumes if a vNext-supported is running to use the vNext code path

• • Removing Order Notes were not removing them from screen- JIRA Ticket
    When removing an order note, despite the POS user not getting any error message and despite there being no Sentry log, the order note is not removed from the order and is recalled upon reopening the order.

3/2024

Features

• Dynamic Coupon Codes (RM is required)*-
  POS will support authorizing Dynamic Codes from Restaurant Management and apply corresponding coupon.
  *Dynamic Codes currently requires a manual set up in order for them to work - for any customer inquiries reach out to Shay in Product or the Ops Eng team.

Bug Fixes

• OOS is ignored when using the last order feature-
  When configured to Ask to Use Last Order feature on an order type, system should bypass the Out Of Stock setup rules.

• POS Build 20240216.1 prompts an error when removing an order note.-
  Removing Order note prompts an OrdSave error

• Out of stock does not refresh when changing sizes-
  When switching between sizes, the out of stock X of the item button was not refreshing. When switching between groups with no sizes, the out of stock X of the item button was not refreshing. Also, when paging up and down on mods, the OOS items were not updating.

• Payroll Detail Report double space removed-
  Due to recent changes to the reports to resolve the ##### signs, some extra vertical space was added. This additional space has now been removed.

• 2nd item pricing on splits, leaving an amount due on paid orders depending on which split is collected or sent first- JIRA Ticket
  This pricing bug caused incorrect/inconsistent pricing in the system if they have 2nd Item Pricing configured in their menu and are using split orders. After running a query on the local dbs in the field it was seen that around 300 stores (11%) of our customer base is using this configuration along with allow splits. This issue directly leads to customer problems as they are charged incorrectly. 2nd item pricing was breaking the pricing engine when orders were split, leaving an amount due on paid orders depending on which split is collected or sent first.

• Customer search missing guardrails, forces user to initiate system crash to move forward- JIRA Ticket
  When using the customer screen to search for customers, if you select Find without entering any information on the Name, Location, ID, and Email field the system will attempt to load a list of all customers that have any of that data. On an average size db this search can take over 30 minutes. If the order taker accidentally does this action they are forced to crash the system in order to reload it and continue taking orders.