The ability to just choose the Time (not date) that an item is going to be available on the POS and OLO.

For example:  Lunch Items should only appear from 8:30am-5:00pm (doesn't matter what day of the week).

We would like to be able to set auto gratuity by item, not just by seat count. So for instance, we may have a beverage item that shouldn’t have auto gratuity, but apply auto gratuity on food items.

Currently, when looking through the report, the cash value only reflects the cash of purchases.  I'd like to request that the refund portion of the report be migrated within the cash portion to make it easier to see the true cash. 

Example:

cash 100

refunds 25

total cash 75

With the patch that auto-closes the error message, barcode scanning errors now do not interrupt scanning.  Before, if I scanned a barcode that was not recognized, the error would prevent all other scans.  Now, if I have 10 items, if the 3rd item doesn't scan, I may not notice that 1 or other items did not get added to the check.

Currently there is no way to swipe a manager card into the employee PIN section.  The issue is most manager cards to not have the card number written on them for security reasons, so there is no way for a card to be assigned.

Can we have the quantity for the per-item print at the beginning of the item name instead of at the last line?

Ex: 1 x  Grilled

            Chicken

            Sandwich

Instead of:

            Grilled

            Chicken

         1 Sandwich        

Gets confusing with multiple items on the printout.

The transaction report is good but lacks a filter on employee and time. It currently has dates but it is not specific enough all the time. For example  Jack is doing nights shift say from the 17th to the 18th so he has sales on the 17th at night and the 18th in the morning. His next shift is from the 18th at night to the 19 th. With the current filter only on date, you will always have transactions that are linked to two shifts (in our example the 18th). With time filter you can then have only the transactions of the relevant shift.

Right now, the way we have it set up, our modifiers have 4 pre-fixes ("Add", "No", "On the side" and "Sub"). When a customer wants to add a modifier (such as avocado) hitting the pre-fix "Add" is what charges them the cost of that item; we run into issues with our online ordering because customers are clicking on only the modifier (example avocado) but they are not being forced to click any of the prefixes, therefore they aren't being charged the cost of the modifier.
Once the customer has picked their modifier (avocado, bacon, cheese etc), we need to force them to pick a pre-fix so if adding, they get charged for that modifier. 

I have told the support staff about this since last year.  The way the the system has been programmed, what Linga calls Cash Discount is not Cash Discount it is actually Non Cash Adjust.  The name of the function throughout the system needs to be adjusted to alleviate any confusion.  Here are definitions for Cash Discounting, Non Cash Adjust and surcharging

At the most basic, a cash discount is when a customer pays less than the shelf or menu price because they pay with cash. For example, if the shelf price is $10 and a merchant offers a 3% cash discount, the customer will pay $9.70.

A surcharge is when a customer pays more than the shelf or menu price because they pay with a credit card. For that $10 item with a 3% surcharge, the customer will pay $10.30.

Any tinkering with these scenarios doesn’t change the end result. A program in which merchants add a “service fee” or a “non-cash adjustment” that is immediately removed for cash customers is not a discount, as the customer did not pay less than the shelf or menu price. That is, there was no actual discount.

For example, if the shelf price is $10 and the merchant adds a 3% “non-cash adjustment fee,” the price goes to $10.30. The customer chooses to pay with cash, so the merchant removes the fee, dropping the item back to the original $10. No discount on the shelf price occurred. Instead, the customer simply wasn’t surcharged. “Not being surcharged” is not the same thing as “receiving a discount.”

Before a new transaction is started, we should have an option to ask for customer phone number on the customer display. 

If the phone number is found it will bring up the account. If not the customer can enter in a name to create an account