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.

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. 

The client would like an error message to be displayed to the user if an import fails, indicating that the import was unsuccessful.

On the linga go app there is the ability to the customer to tip adjust on a preauthorized bar tab. However, on the customer facing screen at the cloud POS this options does not exist. This is huge hindrance for breweries and wineries.