5.06 Release Notes

Client Release (POS, KDS, KIOSK)

POS

Custom Authorization Receipt

CONSR-1516 

Description

Users with the Punchh Integration enabled on POS will now have the ability to print both the Punchh trailer message and barcode on the authorization receipt when users select the "Print Receipt" button. This functionality allows customers to scan the printed Punchh barcode to earn reward points after paying.

Capture Name on Card in Freedom Pay Portal

STR-2926 

Description

We will now be displaying the ‘Name on Card’ for FreedomPay transactions in the Freedom Pay Portal. Displaying this information will help users identify a customer's name when revisiting the charges at a later date.

New Gift Card Flow

STR-2408 & STR-2850 

Description

We have modified the gift card flow to separate the operations (i.e. load/reload/wipe) from the gift card payment process. 

We have added the action and related description to the gift card dialog box so users are able to track the success or failure of the gift card operation. Once the operation is complete, the user will get a success message in the description section of the dialog box “i.e. Card Reloaded”;

In case that the gift card operation fails, it will be shown in the error dialog box: 

Once the gift card is reloaded, the customer will be able to proceed with payment. Should a gift card not be paid for, the check will not close. 

Olo Refund Permission

STR-2969 

Description

With this feature update, we have updated the Olo refund functionality for users to perform the Olo refunds. If both the site and the user have the Olo refund permission, the POS will display the refund button, and when the user taps on it, it will successfully allow the user to refund the Olo payment. 

Permission: OloRefund

According to this modification, users will now see a toast notification when attempting to perform an Olo refund for a site that does not have the necessary permissions.

HQ

Reorder Alphabetically Button for Reordering Modifiers 

ENT-1577

Description

We have created a "Reorder Alphabetically" button in the “Reorder Modifier” dialog box that, once selected, will automatically re-order modifiers in a modifier group alphabetically. This feature is available both at the node and the site level.

Auto-Populate Store Discounts from Enterprise Node

ENT-1296 

Description

This feature automatically populates the existing discounts from the Enterprise Node to the Store Level for each newly created site.

3 CTAs Added to Site Selector in Menu and Product Push

ENT-1672 

Description

We have added 3 CTA buttons on the top of the Site Selector in the Menu and Product Push UI. This functionality enables a user to copy products or menus directly from a node to a specific node or sites under sub-nodes without underlying the sites or vice-versa.

 

Bugs Fixes

Client Release (POS, KDS, KIOSK)

KIOSK

Incorrect discount application at Kiosk

CONSR-1515

Symptom

If discounted items are removed without removing the applicable discount first, all other items in the cart get discounted to $0.

Steps to reproduce

X for X discount --------------

1. Create x for x discount - buy one omelet and get a discount on 2 beverages (we can modify the discount type from Amount/Percentage/Free to check other scenarios in the same discount).
2. Add one omelet and add more than 2 beverages to cart, apply the newly created discount and verify it is applied correctly.
3. Now remove any one discounted item and verify at-least 2 eligible items in the cart gets discounted, if there is only one eligible item in the cart then discount should be applied to only one item.
4. Remove the last eligible discounted item and verify that promo code is also removed.

Now Similarly,  test negative scenarios where you do not add omelet instead add some other item and add beverages to cart, verify that discount does not apply.

Now Similarly, create another X for X discount where we do not include or exclude any item, perform the same steps mentioned above, this time the highest price item will be the required item and 2nd and 3rd highest price item will be treated as discounted ones.

Try removing discounted items one by one and the discount will shift to another item until we have only one item in the cart when the promo code will be removed automatically since we do not have any eligible items in the cart now.

Item Level Discount -----------

Same as X for X, you can create item level discount and perform the same steps to verify.

Order level discount ---------------

Same as X for X, you can create order level discounts and perform the same steps to verify.

Resolution

We have added the functionality that verifies if the remaining items in the cart are eligible for a discount when the discounted items are removed from the cart. Based on the status of the re-verification, the promo code is automatically removed if the eligible items are no longer in the cart.

Server

HQ

Switching Employee Status Doesn't Paginate Correctly

ENT-1698

Symptom

Staff numbers do not always appear correctly when selecting different quantities. Furthermore, when you apply the inactive filter, scroll to the next page, or change the items per page, the status filter is reset back to active.

Steps to reproduce

1. Log in to the HQ with valid credentials
2. Navigate to the Site_Pepole_In Store_Staff tab.
3. Try to fetch Active staff details
4. Try to select 25, 50, and All view links.
5. Here it is not showing the correct total data based on selected (25, 50, and All) links.
6. Here observed one more issue that is, Select In Active staff and select All links. Here In Active filter changes back to Active.

Resolution

For the default filter or status='active' filter it was pulling all the records(active + inactive) so 25 records of both active and inactive but it was showing only active records.

Fixed to fetch only active records for active filter and inactive records for inactive filter and fetch both active and inactive for both the filters.

Staff Summary Report does not include transactions outside of employee shift

STR-1782

Symptom

Staff Summary Report does not include the payments and tips taken for staff members outside of their shifts if the shifts are adjusted for that user. The missing transactions can be found in the TRAY Payments report but need to be included in SSR.

Steps to reproduce

1. Day starts at 10 am.
2. Clocked in on 22 March at 10 am.
3. Completed 8 hrs of shift+Overtime.
4. Clocked out with declared tips on 23 March at 11 am.
5. Made some transactions(between clock-in & clock-out duration).
6. Total hrs worked= 25 hrs( including overtime).
7. Generated Time entries & Staff summary report for the particular date & staff.
8. Validated the "Sales" & "Tips" data in Staff summary report.
9. Then in the "Time entries" report, edit the working hours of staff from 25 hrs to 12 hrs and save the entry.
10. Validated the "Sales" & "Tips" data in Staff summary report.
11. Observed that the checks that started after the shift time are still in his shift that started the previous day.
12. Clocked in again on 23 March at 12 pm.
13. Made some transactions.
14. Validated the "Sales" & "Tips" data in Staff summary report.
15. Observed that the checks which started after a new shift begin are in the new shift record  (current shift) only.

Resolution

1. Previously, we only considered payments and tips for a staff member between their clock-in/clock out time in the Staff Summary Report .
2. As part of this ticket, we now include the payments and tips taken outside of their shift duration. (i.e. till next clock-in) This applies to both the Staff Summary Report in HQ and Printed Staff Summary Report on the POS. Payments outside of a shift can occur due to shift editing or payments taken by a manager for that user.

Inconsistency of the total hours of an employee across different reports

STR-2870

Symptom

The total hours worked for an employee differ by 0.01 for Time Card, Labour, and Staff summary reports.

Steps to reproduce

1. Clock in with a staff role.
2. After some time , Click on the Break button.
3. Select unpaid break.
4. End the Break.
5. Now clock out for the staff role.
6. On HQ , check Timecard, Labor, and Staff Summary reports.
7. Observe the discrepancy of .01 in the Staff summary Report. 

Resolution

Previously we didn't use "seconds" to calculate total hours/break time hrs, which resulted in discrepancies across reports like Time Card, Labour, and Staff summary reports.

We have now fixed the issue by considering "Seconds" for calculating total hours/break time hrs.

 

The DSR's Check/Guest Count is Incorrect

STR-2845

Symptom

The ‘guest count total’ and the ‘check count total’ differ by a count of 1 if the filter checks are voided as false. 

Steps to reproduce

1. Place some orders on POS using comp/discount /void.
2. Pay for some checks , via cash/Gift Card.
3. Send and hold some orders.
4. Complete orders.
5. On HQ go to DSR reports.
6. Observe count of Checks begun and Checks.
7. Verify API response for each check.

Resolution

Previously, checks with the gift card items were not included in ‘total checks’ count in the ‘Order Types’ section of the Daily Sales Report. The checks with GIFT CARD items are now counted as part of the overall checks in the DSR.

SVS Gift Card Cashout Records Positive & Negative ‘No Sale’ Simultaneously

STR-2578

Symptom

Positive & Negative No Sale Values appear simultaneously for SVS Gift Card Cashout transactions.

Steps to reproduce

1. Login to POS > Functions.
2. Perform Cash out in POS.
3. Validate in no sale reports.

Resolution

We fixed the issue by calling “NoSale API” again on the client side, which was already handled by the server when we used to call the gift card/wipeCard API.

FM Report does not format properly if "Week Starts On" is not set to Monday

ENT-1624

Symptom

When entering the date manually in the Financial Management Report, the FM Report does not display the correct data for the selected dates.

Steps to reproduce

1. On the HQ home page Reports Menu select Sales -> Financial Management report.
2. From the Period drop-down list choose the Week Starting From option.
3. Choose the Site.
4. The start date will be changed, according to the Site Settings (Site Settings -> Operations: Week Starts On).
5. Run the report.
6. The first column of the report will be the day of the week set on the Site Settings.

Resolution

We have fixed the issue by configuring the start date of the week per the week’s start date for the selected site, leading to the report displaying the correct dates.

For example

  Site A - week starts on monday (20th march)

  Site B - week starts on Friday (17th march)

  Consider Current date is 23rd march

  When Site A is selected, start date will default to 20th march

  When Site B is selected, the start date will default to 17th march.

 

DSR discrepancies

STR-2434

Symptom

Discrepancy between Checks Begun count and amount as compared with Checks Paid on DSR report.

Steps to reproduce

1. Login to POS.
2. Add some items in the cart.
3. Place an order.
4. Make a full payment for 2 or 3 orders.
5. Again place an order.
6. Do not make payment for 2-3 orders.
7. Go to HQ.
8. Run DSR report.
9. Observe the Checks Begun and Checks Paid.

Note: Checks that are completely paid will be calculate & displayed in Checks Paid and the checks which are not paid will be calculated in Checks Begun along with the checks paid

For eg: Make 6 transactions with 3 fully paid and the remaining non-paid.

Calculation:

checks begun=6

checks paid= 3

Resolution

Checks that are added but have a zero sum are counted in the Checks Paid section.

Tax exempt tenders from OLO do not remove tax from checks

STR-2583

Symptom

It appears that tax-exempt tenders (uber, door dash, etc.) are not removing tax from the orders on the check; for orders placed via Olo.

In the check report, checks were not balanced and had a discrepancy equal to the tax amount.

Steps to reproduce

1. Place an Olo order which has external tender in it and the tender is tax-exempt.
2. Check the Payments and Orders report. The payments report shows the correct data (tax = 0) but in the Orders report orders had tax in them even though tender is tax-exempt.

Resolution

Whenever new taxation is enabled :

For the orders placed via Olo with tax-exempt tenders, then we will consider the tax amount as 0$ and zero sales tax in validateApi.