Build Version 2.1.20 - Release Notes

Build Version 2.1.20 - Release Notes

Enhancements

Back Office 

  1. Detailed Sale Recap report
    1. A new report type ‘Detailed Report’ will be displayed. In this report the  
    2. To generate detailed sale recap report, select 'Detailed Report' in the Report Type 
    3. Click on 'Export as PDF' button.


  2. Reset points of Loyalty from back office. 
    1. Reference: Reset Loyalty points

  3. Parent/Child Inventory quantity 
    1. Currently, in the back office, the quantity and price of the parent item will be displayed in the Inventory Item screen. 
    2. Now, the user can view the split up for parent and child separately.
    3. Reference: Display of Parent & Child in Inventory Item in BO

  4. Weekly Report – Add Margin, Remove US$. 
    1. Gross Margin will be displayed in the Enterprise Weekly Report.
    2. Reference: Gross Margin in Enterprise Weekly Summary

iPad

  1. New till report with all the details- for Global till user wise
    1. Currently, in the POS, the cashier out report will be generated based on the selected cashier irrespective of the workstations. 
    2. Now, in the cashier out report, Till Detail option will be displayed. 
    3. Hence the report can be generated based on the sale created on the respective till for all the cashiers who have utilized the respective Global till.
    4. Reference: Global Till Report

  2. Sales refund
    1. Reference: Enhancement in Refund Process

  3. Tokenization of CC card in Phone order
    1. Currently, in the POS we are tokenizing the credit card in the “Customer Profile” screen. 
    2. Now we are tokenizing the cards while making payments.
    3. Reference: Credit Card Tokenization

  4. Conversational modifier 
    1. Currently in iPad, when the user selects the menu item the serving size will be selected in one screen and then the modifiers in another screen.
    2. Now the introduces a new feature where the user will be able to select the serving size & modifiers in a single screen based on the back-office configuration.
    3. Reference: Conversational Modifier

  5. Payment method sequence show in order
    1. Reference: Display of payment in sequence

  6. Dealer logo on IPAD:
    1. In UPOS Back office store settings  dealers can upload there logo (Image upload of size 400X70).
    2. After uploading the logo in UPOS backoffice , user can able to view the Dealer logo in CloudPOS Order screen on left hand side top corner. 

  7. Fire & Hold per check
    1. Reference: Fire& Hold per check

  8. Address Line 2 is displayed in the Phone Order tab
    1. Currently, only Address Line 1 will be displayed in the Address column in the Phone Order tab.
    2. Now, Address Line 2 will also be displayed along with Address Line 1.

Bug Fixes: 
  1. Following customer tickets are fixed : 
    1. 40307
    2. 47869 
    3. 47689
    4. 47491
    5. 45667
    6. 47123
  2. Sppax declined status should not show the in the failure payment 
  3. Clover Payment - After accepting the payment in clover device, confirmation message will not be displayed in iPad.
  4. iOS 13 version supported for magtek device.

Reset Loyalty points

Introduction

This document describes the ability to change the customer’s loyalty points of the customer(s) in the back office.

Changes in the back office

  1. Roles
    1. A new access Loyalty point Adjustment will be displayed in the Back Office section. [User Management >> Roles >> Select any role >> Back Office]
    2. By default, this option will be in disable mode. 
      1. Note: For existing Admin users, this option (Loyalty point Adjustment) will be in enable mode.
    3. The user can enable the option later.
    4. When the access ‘Loyalty point Adjustment’ is enabled for any role, then the respective user can edit the loyalty points of customer in the Customers screen.

  2. Customer screen
    1. Two new columns – Loyalty points and Reason will be displayed in the Customers screen.
    2. When the user who have proper access edits the loyalty points, a new pop-up will be displayed where the user can edit the loyalty points and reason.
    3. The user can increase/ decrease the loyalty points or can reset the loyalty points to zero.
    4. The field, Reason is mandatory.
    5. When the user submits the pop-up, the updated loyalty points and the reason will be displayed in the grid table.



  1. Reports
    1. Following columns will be displayed in the Loyalty report. [Loyalty >> Report]
      1. Adjusted Loyalty points
      2. Reason


    2. When the user clicks on the Customer's name, a pop-up will be displayed which has the following details:
      1. Customer's Name
      2. Date filter
      3. Grid Table having the columns:
        1. Date
        2. Check No
        3. Point Adjusted
        4. Adjusted by/Adjust Reason
        5. Check Amount
        6. Loyalty reward



Display of Parent & Child in Inventory Item in BO

Introduction

Currently, in the back office, the quantity and price of the parent item will be displayed in the Inventory Item screen. 
Now, the user can view the split up for parent and child separately. This document describes the changes in the Inventory Item screen

Changes in the Back Office

  1. Retail Item
    1. The field ‘Selling Unit’ will be renamed as Inventory Unit in the ‘Inventory Details’ screen. [Product/Items >> Product/Items >> Retail Item >> Inventory Details] 


    2. The field ‘Selling Unit’ will be renamed as Inventory Unit in the ‘Add Child’ screen. [Product/Items >> Product/Items >> Retail Item >> Childs] 


  2. Inventory Item
    1. There will be a modification in the display of the Inventory Item grid table.
    2. Newly added columns are
      1. Purchase unit
      2. Price per unit
      3. Parent & Child for Quantity on hand, Cost per unit



Gross Margin in Enterprise Weekly Summary

Introduction

This document describes the enhancement that needs to be implemented in the Enterprise Weekly Summary report.

Changes in the Back Office

  1. Enterprise Weekly Summary report
    1. A new column GM% will be displayed for each day adjacent to the Net Sales column in the Weekly Summary Report. [Enterprise Reports >> Sale >> Weekly Summary]
    2. Gross Margin percentage (GM%) will be calculated as ((Net Sales - COGS)/Net Sales) * 100
    3. Average of GM% will be displayed at the end of the week.


    4. Total Net Sales and the Average Net Sales for all the stores will be displayed at the bottom of the report.
    5. Average Net Sales = Total Net Sales / Total number of Stores.
    6. When the user clicks on the store name, drill down report will be displayed. The value of COGS will be displayed for each day.


Global Till Report

Introduction


Currently, in the Linga POS, the cashier out report will be generated based on the selected cashier irrespective of the work stations. Now, in the cashier out report, Till Detail option will be displayed. Hence the report can be generated based on the sale created on the respective till for all the cashiers who have utilized the respective Global till.

Changes in the Back Office


  1. Settings
    1. A new option Partial Payment not allowed in different tills will be displayed in the Settings screen. [Settings >> Store >> Settings]
    2. Help content for the option 'Partial Payment not allowed in different tills':
    3. On enabling this option, the partial payment cannot be allowed in different tills when Global Till is enabled.


Changes in the POS


  1. Cashier Out report
    1. A new option Till Detail will be displayed in the Cashier Out report screen when Global Till is enabled. [Operations >> Till Management >> Reports]
    2. By default, this option will be in disable mode.
    3. Hence the cashier out report will be generated for the selected cashier’s sales made in all the Global till.
    4. On enabling the option ‘Till Detail’, the report will be generated for all the cashiers sales made in the respective Global till.
    5. When the option ‘Till Detail’ is enabled,
      1. The Till Numbers will be listed in the drop down instead of Cashier’s name.
      2. The Till created date and time and the Till closed date and time will be displayed
      3. If Till closed time is not available, then the last sale created time will be displayed.
      4. All the details available in the Cashier Out report will be displayed in the UI and in the receipt. [Sales, Taxes, Payment Summary, Till Summary, and all Sale Summary]
    6. When the option ‘Till Detail’ is enabled and taken the print, the Till name/Device name will be displayed on the receipt. The Cashier’s name will not be displayed.
    7. The option Till Detail will not be displayed when the Global Till is disabled.
      1. Note: Hold and closed till details will not be show in Till reports. Only active till details will be shown. 
Screenshot:


Receipt:




Enhancement in Refund Process

Introduction

This document describes the changes that need to be done in the Refund process in the POS.

Changes in the POS

  1. Refund
    1. When the user navigates to the Refund screen, the screen displays three options:
      1. Refund with Receipt
      2. Refund without Receipt
      3. Refund Menu Items

  2. Refund with Receipt
    1. Navigate to Refund screen. [Operations >> Refund]
    2. When the user selects a check in the ‘Refund’ screen and click on the Refund option, the Refund pop-up will be displayed.


    3. The check amount will be displayed.
    4. The user can select any one of the payment options.
      1. Note: The Reason field is mandatory when the refund is made.
    5. On selecting the payment options, a message will be displayed saying, “Do you want to refund? Confirm” will be displayed with ‘Yes’ and ‘No’ option.
      1. When the user clicks on the ‘Yes’ option, the refund process will be completed, a success message will be displayed saying, “Refund done successfully” and the user will be navigated to the Order screen. 
      2. When the user clicks on the ‘No’ option, the refund process will not be done and retain in the same pop-up.
    6. The user can do partial refund.
    7. When the user refund for the same check next time, the application should validate the refund amount.
      1. For example,
      2. When a check amount is $100.00, the user refunds partially for $20.00.
    8. The next time the user will be allowed to refund up to $80.00.
    9. At any cost the user will not be allowed to refund more than the check amount.
    10. When a check is refunded completely, and the user selects the same check and click on the “Refund” option, then an alert message will be displayed, “The check has been refunded”.

  3. Refund without Receipt
    1. When the user clicks on the Refund without Receipt option in the ‘Refund’ screen, the Refund pop-up will be displayed.

    2. The user can select any one of the payment options.
      1. Note: The Reason field is mandatory when the refund is made.
    3. On selecting the payment options, a message will be displayed saying, “Do you want to refund? Confirm” will be displayed with ‘Yes’ and ‘No’ option.
      1. When the user clicks on the ‘Yes’ option, the refund process will be completed, a success message will be displayed saying, “Refund done successfully” and the user will be navigated to the Refund screen. [Operations >> Refund]
      2. When the user clicks on the ‘No’ option, the refund process will not be done and retain in the same pop-up.

  4. Refund Menu Items
    1. When the user clicks on the Refund Menu Items option in the Refund screen, the user will be navigated to the Order Summary screen.


    2. The screen displays 2 options at the bottom of the Menu screen.
      1. Refund Check
      2. Refund Item(s)
    3. When the user clicks on the Refund Item(s) option in the Order screen, without selecting any menu item, then a message saying, “Please select any menu item” will be displayed.
    4. The user can select multiple menu items.
    5. When the user clicks on the Refund Check option, the "Refund" pop-up will be displayed.
    6. When the user selects any menu item(s) and click on the Refund Item(s) option, the "Refund" pop-up displays as

      1. The price of the menu item(s) will be displayed.
      2. The user can select any one of the payment options.
        1. Note: The Reason field is mandatory when the refund is made.
      3. The user will not be allowed to edit the amount.
      4. On selecting the payment options, a message will be displayed saying, “Do you want to refund? Confirm” will be displayed with ‘Yes’ and ‘No’ option.
      5. When the user clicks on the ‘Yes’ option, the refund process will be completed, a success message will be displayed saying, “Refund done successfully” and the user will be navigated to the Order screen. 
      6. When the user clicks on the ‘No’ option, the refund process will not be done and retain in the same pop-up.
      7. The user cannot make partial refund.
      8. The user will not be allowed to select the same menu item(s) which has already been refunded.
      9. When the refund process is completed, a check will be created with the character (R) amended.
        1. For example,
        2. When a check (1-001) is created on 25th June and it is refunded on 27th June, then the check number will be R-1-001.
        3. The refund check (R-1-001) will have the menu item(s) that has been refunded.
        4. The original check (1-001) will have the refunded status for the menu items that has been refunded.
    7. Once the refund is completed, the user clicks on the Done button. On clicking the "Done" button, the details will be saved and the user will be navigated to the Refund screen. [Operations >> Refund]
    8. When the user navigates to Order Summary screen and decides to cancel the refund process, then the user can click on the Done button. 
      1. On clicking the Done button, the user will be navigated to the Refund screen. [Operations >> Refund]

Changes in the Back Office

  1. Sale Recap Report
    1. Refund Section
      1. The following data will be displayed in the Refund section:
        1. Cash Refunds
        2. Non-cash Refunds
        3. Refund Tax
      2. Refund Tax will be the sum of the tax amount for the menu item(s) that has been refunded in the POS.
      3. Hence the Total = (Cash Refunds) + (Non-cash Refunds) + (Refund Tax)


    2. Taxes Section
      1. Refund Tax will be displayed.
      2. The Total Tax Amount = Sum of all the tax amount – Refund Tax

        1. When the option Tax with Net sales is enabled in the back office


  2. Tax Report
    1. A new row Refund Tax will be displayed just above the “Total”.
    2. Hence the Total Tax Amount = Sum of all the tax amount – Refund Tax.


  3. Refund Report
    1. The column Amount will be split into three columns – Net Sale, Refund Tax, Total.



Credit Card Tokenization

Introduction

We can securely add and save the credit cards while making payments at the Linga POS so that the customer can use the same card for next purchases. Currently, in the Linga POS we are tokenizing the credit card in the “Customer Profile” screen. Now we are tokenizing the cards while making payments.

Changes in the Back Office

  1. Settings
    1. A new option Tokenize the credit card will be displayed in the Settings screen. [Settings >> Store >> Settings]
    2. The user can select the service types to which the credit cards need to be tokenized.
    3. By default, none of the options displayed.


Changes in the iPad

  1. Payment Screen
    1. If the option “Tokenize the credit card” is disabled in the back office and if the user taps on the credit card payment name, the credit cards will not be tokenized.
    2. If the option “Tokenize the credit card” is enabled in the back office and still no card is tokenized for the customer, then the user will be navigated to the “Credit Card screen”.
    3. If the option “Tokenize the credit card” is enabled in the back office and if the customer is having already tokenized cards, then the “Choose Card” pop-up will be displayed.
      1. Previously tokenized cards in the “Customer Profile” screen and the "Payment" screen will also be displayed.
      2. The user can select any one of the saved cards and complete the payment process.

    4. If the user taps on the “New Card” option, then the user will be navigated to the “Credit Card” screen. 

  2. Credit Card screen
    1. If the option “Tokenize the credit card” is enabled in the back office, and when the user taps on “Process” option and once the payment transaction is completed an alert message saying, “Do you want to tokenize your card?” will be displayed with Yes and No options.   
    2. When the user taps on “No”, the card details will not be tokenized. 
    3. When the user taps on “Yes”, the system will verify whether the customer has been attached to the respective check or not.
      1. If the customer has been attached to the check, then the given card details will be tokenized and saved. 
      2. If the customer has not been attached to the check, then a pop-up will be displayed with the following details:
        1. First Name
        2. Last Name
        3. Phone Number
        4. Email Address
        5. Save
        6. Cancel

        7. There will be a search option available to search customer.
        8. Note:
          1. The first name and last name will be populated when the card is processed through swiping or EMV. 
          2. The user has to provide either Phone Number or Email. 
          3. When the user has provided any one of the fields (Phone Number or Email), then the “Save” button will be enabled.
      3. On tapping the “Save” button, the following details – Card Number, First Name, Last Name, Phone Number/Email Address will be saved.
      4. On tapping the “Cancel” button, the pop-up will be closed, and the credit card will not be tokenized.
    4. During offline, the credit card will not be tokenized. Only the payment transaction will be saved and stored in "Process Offline".
    5. If the same credit card number is tokenized, a new token will be generated and this token will be updated for the respective card number.
    6. The card number will be tokenized and saved. It will be displayed as a masked number in the format “First 4 digits XXXXXXXXX Last 4 digits”. For example, 1234XXXXXXXXX3439

  3. Limitations:
    1. When the payment is through MPPG (TSYS), the saved card(s) will be displayed only for Sale process. During Authorize process, it will be navigated to the Card screen directly.
    2. For Pre-Auth transactions, the card number will not be tokenized.


Conversational Modifier

INTRODUCTION

Currently in the iPad, when the user selects the menu item the serving size will be selected in one screen and then the modifiers in another screen.
Now the Linga introduces a new feature where the user will be able to select the serving size & modifiers in a single screen based on the back-office configuration.

CHANGES IN THE BACK OFFICE

  1. A new option 'Conversational' is added to the following screen:
    1. Create/Update Category screen 
    2. Create/Update sub-Category  screen 
    3. Create/Update Menu Item screen
  2. By default, the option will be in disable mode.
  3. The user should be able to enable the option.
  4. When the user enables/ disables the 'Conversational' option and clicked on 'Save' or 'Update' button, the details should be stored.
    1. When the user has enabled the option 'Conversational' in a Category, the options in the respective Sub-category and Menu items should also be enabled. The user should be able to modify the option in Sub-category and Menu items screens.

IMPACT IN THE IPAD

  1. There is no change in the functionality when the ‘Conversational Modifier’ is disabled in the back office. 
  2. When the ‘Conversational Modifier’ is enabled in the back office, then the menu item should show the conversational modifiers.
  3. In the conversational modifier screen, when the user clicks on the menu item, the application should display serving size and modifiers in the same screen.
  4. ‘Conversational Modifier’ screen should be displayed with 
    1. Serving size
    2. Included Modifiers (if applicable)
    3. Mandatory Modifiers (if applicable)
    4. Optional Modifiers (if applicable)
  5. The user should be able to select the items in any order. Ie, the user can choose the serving size and then the modifiers or modifiers and then the serving size.
  6. When a menu item is selected the ‘included modifiers’ should be added in the ‘Order’ screen. The included modifiers should be highlighted in the ‘Menu’ screen.
  7. When the user does not want the included modifier, the user will  deselect the respective modifier in the ‘Menu’ screen, then
  8. The text ‘No’ will be appended before the respective modifier name in the ‘Order’ screen.
  9. The deselected modifier should be grayed out in the ‘Menu’ screen.
  10. Note: This action will be taken place only when the prefix 'No' is added for the menu item.
  11. On the selection of the modifier, the prefixes will be displayed in the right-hand side. The user should be able to select the prefixes.
  12. When the user wants extra include modifiers, the user will select the respective prefix and then the modifier.
  13. When an 'Alternate modifier group' is enabled for a menu item in the back office, a button 'Alternate Modifier' should be displayed below the 'Done' button for the respective menu item.
  14. When the toppings are selected, the user should be able to select the slices in the toppings diagram.
  15. There is no change in the functionality of mandatory & optional modifiers.
  16. The functionality of buttons - ‘Cancel’, ‘Start Over’, ‘Done’ and 'Alternate Modifier' remains the same.
  17. When the menu item has more modifiers, the application should display scroll down button. The user should be able to scroll up and down the screen.
  18. There is no change in the functionality of 'Modify' option.



Display of payment in sequence

Introduction

This document describes how the payment names will be displayed in the sequence order in the POS based on the back office settings.

Changes in the Back Office

  1. Settings
    1. A new option Sequence will be displayed in the Payment Methods in the Settings screen. [Settings >> Store >> Settings]
    2. By default, zero (0) will be displayed.
    3. The user can change the sequence(s) later. 
    4. Once the sequence has changed, and then again navigated to the ‘Settings’ screen, the payment types will be displayed in the sequence mentioned.

Changes in the POS

The payment names on the payment screen will be displayed as in the sequence given in the back office. 


Fire& Hold per check

Introduction

This document describes the functionality of holding and firing multiple menu items in the check level.

Changes in the POS

  1. The user will click on the Table and select one or multiple menu item(s) from any seat.
  2. On selecting any of the menu items, the Menu Option screen will be displayed.
  3. Currently, the user can select only the option Repeat.
  4. Now, the user can select Hold and Fire options.
  5. On selecting, the Hold option, multiple menu items will be in ‘Hold’ status and will not be send to the kitchen.
  6. On selecting the Fire option, the respective menu items will be sent to the kitchen in a single print.


    • Related Articles

    • Build Version 2.1.24 (1.1) - Release Notes

      Release Date: 07/09/2020 Release Version: 2.1.24 (1.1)   Enhancements: ·         Auto Update for POS -        Auto update will allow the system to prompt for each new software update automatically -        A Notification for update to latest version ...

    • Build Version 2.1.22 (1.3) - Release Notes

      Release Date: 4/28/2020 Release Version: 2.1.22 (1.3)   Enhancements: ·         Delivery Notes are Printed on the Receipt Print Out -        The delivery notes are now added to the receipt print as well as in the delivery print for driver ·         ...

    • Build Version 3.0.7 (1.3.1) - Release Notes

      Release Date:  29-Sept-2021 Release Notes: iPad Build version 3.0.7(1.3.1) Feature Back Office: Account Balance Codes and Report - Enhancement Provision to include new field “Comp Discount” in Back Office (My Store>> Settings>> Report Settings>> ...

    • Build Version 2.1.22 (1.2) - Release Notes

      Release Date: 4-20-2020 Release Version: 2.1.22(1.2)   Enhancement: ·         NMI Refund: -        There is now an option to delete the online order payments made via NMI gateway -        The User can delete the online order payment in the POS under ...

    • Build Version 2.1.18 (1.2) - Release Notes

      Release Date: 7-20-2019 Release Version: 2.1.18 (1.2)   ENHANCEMENT Enhancement: ·         86 List: -        The 86 List feature will allow the user to track the quantity of specific items in -        When the count of a menu item is properly set up, ...