LINGA — Feature Request Forum

+10
Completed

Ability to bump/clear individual items from the KDS ticket

Mike Warren 5 years ago updated by Product Engineering 9 months ago 2

Request is to be able clear an individual item or items from a KDS without bumping the entire order.  Given the small FONT size of the order the Completed check mark is very small and a color change doesn't necessarily help work flow.  

Use:  4 items fire back to the kitchen, 3 are long time cook and 1 is a quick item that needs to go right away.  Employee can clear that item off the screen leaving only the items still being needed and without tying up screen space.

Or at a minimum be able to strike through the item while leaving it on the KDS.  At least that is a stronger visual indicator.

Thank you

Answer
Hardy Singh 2 years ago

We do have this option available with KDS to KDS Broadcast feature, please call customer support to get more details. 

+10

Enable descriptions at the Category or Sub Category level, not just item level.

Mike Warren 5 years ago updated by Product Engineering 8 months ago 2

Need the ability to add group level descriptions.  Examples - "All Entree's include choice of soup or salad plus 1 side" or "

All tacos served with shredded cabbage, oaxca cheese, chopped onion, and cilantro", etc.  The goal is to give the customer as much information as possible without having to repeat for all items within that same group/category.  This would be applicable to both Kiosk and OLO where a picture and description can sell an item (or not).

+10
Completed

allow for same day future order but not next day

amendolachris 5 years ago updated by Product Engineering 9 months ago 1

I would like to be able to allow guest to order online for same day future ordering but not for the next day

+10
Completed

modifier kitchen print name

Brian Sharp 5 years ago updated by Product Engineering 9 months ago 5

Just like menu items, where you have the name of the menu item and then the Kitchen Print Name, the same thing needs to be available for Modifiers.  The Modifier Name and then the Modifier Kitchen Print Name.

+10
Completed

Auto Gratuity

Brittany CH 6 years ago updated by Product Engineering 9 months ago 5

The gratuity will automatically be added to the check if the check has more than (X) number of people.

- Create the gratuity and its settings

- Turn on the auto gratuity feature

+9
Under review

Customer wants to be able to 86 modifiers!

Megan McLewin, LINGA SALES rep 2 years ago updated by Product Engineering 7 months ago 4

This is very important for building a bowl. If they are out of " mango" or "cucumber" for Poke Bowls that day, they want to 86 the modifier in OLO & in POS.

+9
Completed

Option to Disable/Modify OLO Tip

Andrew Van Luven 5 years ago updated by Product Engineering 9 months ago 3

OLO Tip Settings


 

Image 134


We should have the ability to do the following from the Web Order admin page:

  • Disable the tip line from appearing if the store does not accept tips
  • Enabled/Disable tips based on order type. 
    • IE: Tip options present on Delivery, but not on Pickup.
  • Configure the pre-defined tip %. 

All of the above should be a store setting instead of an account setting. Allowing individual stores in a franchise to customize this information.

    +9
    Completed

    Bar Tab Screen Search Options

    Brittany CH 6 years ago updated by Product Engineering 9 months ago 4

    Bar Tab Screen:

    Searching options to add to this screen, such as:

    • Alphabet Letters (Customer can select a character and see only Tabs starting with that character)
    • Expand the Search Bar: (Makes the Search Bar longer and fills more of the screen)
    • Sort # - Z (Customer can select this button and it sorts the tab from #’s to Z)
    • Sort Z - # (Customer can select this button and it sorts the tab from Z to #’s)

    Original:

    Image 7

    Updated with Search Options:

    Image 8

    +8

    Urgent: Exchange Rate Decimal Precision Issue

    SEan Rowland 7 months ago updated by Jeff Massingill 3 months ago 1

    1. Objective

    To address and resolve the issue of insufficient decimal precision (currently limited to 4 decimals) in the exchange rate configuration between the FCFA and the US Dollar (USD). The goal is to allow for at least 8 decimal places to ensure accuracy in financial transactions and reporting.

    2. Background

    The FCFA (Central African Franc) has a relatively low value against the USD, resulting in exchange rates that are often represented as small decimal fractions. Due to this, even minor rounding or lack of decimal precision can lead to significant discrepancies in converted values.

    Currently:

    • The system restricts the exchange rate display and calculations to 4 decimal places.

    • For example, the actual rate of 0.00171141 USD per 1 FCFA is rounded to 0.0017, which introduces errors.

    • A change of 30 FCFA (from 585 to 625) results in only a 0.0001 shift in the displayed exchange rate (from 0.0017 to 0.0016), which is not granular enough for accurate representation.

    3. Problem Statement

    Limiting exchange rate precision to 4 decimal places causes:

    • Inaccurate currency conversions.

    • Misleading financial values in reports and transactions.

    • Large jumps in apparent exchange rates due to rounding.

    • Decreased reliability in systems handling multi-currency transactions.

    4. Requirements

    Functional Requirements

    • FR1: The exchange rate system must support a minimum of 8 decimal places for rate entries and calculations.

    • FR2: All interfaces displaying exchange rates (UI, reports, APIs) must reflect the enhanced precision.

    • FR3: Rounding logic, if any, should only apply at the display level, not at the storage or calculation level.

    Non-Functional Requirements

    • NFR1: The change should not degrade system performance during exchange rate calculations.

    • NFR2: Historical data must remain valid and accurate post-update.

    • NFR3: Adequate testing should be done to ensure backward compatibility.

    5. Priority

    High – Required to ensure the financial accuracy of transactions involving African currencies, especially FCFA.

    6. Stakeholders

    • Finance & Accounting Team

    • IT Systems/Development Team

    • Product Managers

    • External Partners (if APIs are affected)

    7. Proposed Solution

    Update the exchange rate module and database schema (if required) to:

    • Store and process exchange rates with at least 8 decimal precisions.

    • Ensure all modules consuming exchange rates (including 3rd party integrations) respect the updated format.

    8. Timeline

    To be determined based on development capacity, with a recommendation to prioritize the change in the next update cycle or patch release.

    9. Risks

    • Potential data inconsistency if decimal support is added inconsistently across subsystems.

    • Possible need for UI redesigns where space or formatting was based on 4 decimals.

    +8
    Planned

    86 List Modifiers

    Alyssa Schmitt 3 years ago updated by Hardy Singh 8 months ago 6

    To have the option to 86 modifiers would be a time saver! At the current time, we are only able to 86 menu items. 

    For example: We have a Family Deal with 2 pizzas, cheesy bread, and a 2 Liter. Because they get to choose the pizzas and the 2 liter it has to be set up as a combo, with modifiers. The modifiers being which pizza and which 2 Liter. If I run out of pepsi or sprite I have to go to the back office, find the modifiers, and turn off what 2 Liters we are out of from the back office and then sync, hopefully before someone orders it online. 

    It would be so much faster and convenient to be able to add the modifier count to the 86 List. 

    It would also come in handy for salads with certain dressings, say you run out of blue cheese or honey mustard.