Purpose:
Improve the discount engine in Cloud POS to support more advanced and predictable discount scenarios, including buy-one-get-one (BOGO) and item-specific discounts that handle modifiers correctly.

Current Behavior:

• When configuring a BOGO discount, the discount only applies correctly if the items are added to the check before the discount is applied.

• If the discount is added first, it may not attach properly or calculate the discount as expected.

• Additionally, when the “free” item has modifiers, there is no current method to make the item $0.00 while still allowing modifiers to be selected and priced appropriately.

• This behavior leads to confusion during setup, inconsistent application across transactions, and difficulty supporting merchants who offer bundled or promotional pricing.

Proposed Enhancement:

1. Discount Application Logic

   • Discounts should automatically identify qualifying items regardless of the order they’re added to the check.

   • Once all qualifying conditions are met, the system should retroactively apply the discount.

2. Modifier Handling for Free Items

   • Allow modifiers on discounted or “free” items while keeping the item’s base price at $0.00.

   • Option to include or exclude modifier pricing in the discount logic (e.g., “include modifiers in discount” checkbox).

3. Discount Type Expansion

   • Add preconfigured templates for Buy X Get Y, Mix & Match, and Item Pairing Discounts.

   • Ensure discounts are compatible with both item-level and category-level configurations.

4. Validation and Feedback

   • When discount logic fails to apply, the POS should display a clear, user-facing message (e.g., “Discount conditions not met: missing qualifying item”).

   • Include logging or audit data so partner support can verify which discounts were triggered and why.

Value & Impact:

• Reduced Merchant Frustration: Simplifies setup of common promotional discounts like BOGO or bundled offers.

• Consistent Behavior: Eliminates dependency on item entry order.

• Improved Partner Support: Easier for partners to troubleshoot discount-related issues without escalation.

• Competitive Parity: Aligns Cloud POS with modern retail and restaurant POS discount capabilities.

Example Scenario:

A merchant wants to run a “Buy one Budweiser, get one free” promotion. Currently, the discount only applies correctly if the second Budweiser is added after the discount, and fails if the discount is applied first. Furthermore, when the free Budweiser includes optional modifiers (e.g., “add lime” or “served cold”), the modifiers cannot be selected without breaking the discount.
This enhancement would ensure the promotion applies correctly regardless of item order and handles modifier logic gracefully.

We have an iPad POS. When the POS is not running in the foreground (e.g. Safari is open and we forgot to go back to the POS screen WITHOUT terminating the POS app). After 5 minutes, the POS assumes the store is closed and it shows on the OLO that it's closed. The BIGGEST problem is this scenario; 
1. a customer orders online when the OLO shows store open (meaning the POS is running in the foreground). 
2. For some reason, an employee opens safari (as an example) on the POS and forgets to return to the POS app (so the POS isn't in the foreground) and it is not terminated. 
3. Customer receives a cancellation email and we LOSE the customer and the order. 


It does NOT make sense to show store is closed and cancel customer's order just because the POS is not running in the foreground. This shouldn't happen and we should be able to still receive orders and also the order gets automatically printed. I have never seen this in any other POS system. This is just a common sense. No matter how we tell employees to keep the POS running in the foreground, sometimes they just forget (e.g. they want to print something from safari or whatever the case is)> 

on phone as an example, you don't stop receiving notifications if you texting app/FB/IG or whatever is not running in the foreground. This is just a common sense. 

It would be brilliant to have a module that offer customers paid membership for special offers and off menu items. The idea is that the business almost makes more from membership rather than general sales. I am in an area were there is a lot of competition and I am looking for a new business model.

Linga GO Device does not showcase modifiers under menu items, unlike a regular POS station and this is highly requested for servers to be able to read back orders to their customers.

Several of our merchants find it difficult to clearly separate menu items on the kitchen printer receipt. Some form of separator such as a break line or even an extra space would greatly help.

Account- Beto Hospitality

Customer Name- Scott

Customer mentioned that tip-outs should be calculated based on each server's net sales, but the deduction should occur from their individual tips equally. Currently, Linga does not support deducting calculated tip-outs from individual tips.

Requesting a feature that lets the system calculate tip-outs from net sales and deduct them from each server's tips.

The client would like the option to be able to have a short form option, on a menu item as we have it on modifiers. 

The client would like a longer character limit on menu items, modifiers, and secondary names to be longer than 50 characters.