LINGA — Feature Request Forum
OLO Pickup Time Window
The Current OLO lets you select 5-minute intervals for a pickup time.
Rather than having this, it would be better to have pickup windows.
For example, If it is currently 12:05PM. When I select the "Future Order" section then it should show me the following times.
(based on 15-minute interval)
12:15PM - 12:30PM
12:30PM - 12:45PM
12:45PM - 1:00PM
Etc...
Capability of creating a combo at discounted pricing
Currently taking specific items and locking them down to a discounted price is not a feature.
Ex: Lg pizza, 20 wings, and soda for $35.00
Right now you can discount the items but they are not locked down to specifically just 1 of each item to get that combo
So same EX: If I ring in Lg Pizza, Lg Pizza I can still get the discount when it should be a Lg Pizza, 20 Wings and soda
Add more control for Kiosk
There is not a lot of functionality control for the Kiosk. I think the following would make great settings additions:
- Allowing stores to change the background for the kiosk to match the store.
- Option to disable the dine in/take away slide bar. This will not apply to many stores
- We need a space for customers to put in there name
New Kiosk is avaiable to download from Internal app stores having more options in BO.
Linga: https://app.lingaros.com/detail/linga-kiosk/ep6ga5wsdv
Show Weight Sold for Scale Items on Item Sales Report
Instead of showing the amount of times a scale item was shown, the item sales report should show the weight sold instead.
Urgent: Exchange Rate Decimal Precision Issue
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.
Add Customer Name and Phone Number in KDS
KDS should have customer phone number and name same as the kitchen receipts
confirmation email after order is placed online
We need to have an option to send gust automatic email after they place an online order to let them know when they can pick up their order
Web Order Charge Dispute
Currently we are having few issues of customers who placed orders on Web Ordering, then later on they dispute the charges which they have made, and without the protection of knowing who is actually using the credit card to place the Web Ordering, we need better protection shield to protect us as of business.
As to the Web Ordering:
Back Office Options:
1. Option to require customer to create an account:
We should have the option to require or not to require customers to first open an account before proceeding for Web Ordering.
2. Option to request for phone number and email:
There should be an option in the Back Office for Businesses to decide if they would like to mandate either or both the phone number and email to be the "REQUIRED" field to have Web Ordering customers entering those information.
Requirement displaying:
If Required, before customers entering to Payment, there should be a Pop Up screen to request customer to get a confirmation code to verify the phone number is a valid.
If Linga need to make a security check by sending a Verification Text Message to the customer phone, and have the customer key in that confirmation number to be able to proceed on placing orders, this will create an additional protection to all business owners from customer to claim of charging back on Web Ordering orders.
Customers side of how to:
1. Customer keyed in an order on Web Order
2. At the check out Before Payment, must enter phone number and email
3. Web Ordering check-out should have a button to send a Verification Code to the phone number that was entered by customer
4. Customer received Confirmation Number text message, then entered confirmation number before proceeding
5. Customer can now proceed to payment
This is a security process to protect the business owners and it will benefit your company and most of your customers who uses the Web Ordering feature.
Web Order: Disable Guest Ordering
We want to disable Guest ordering. We want every customers to have an account with info like Phone, Email and Order Info.
Customer support service by UserEcho