Repeat per check/not per seat

Currently in Linga you can send all the seat’s orders to the kitchen.

We need an option to repeat orders for all the seats.

Currently you can only repeat orders by one seat at a time.

Have the ability to have the bartenders automatically open up to the Bar Tab screen rather than the POS screen

A way where the POS shows a time entry each time something is added to the ticket. Ex: a bartender would like to know the last time they added the most recent drink. They can then look at this to see if there has been enough time in between drinks to serve another.

Places that do a high volume of Bar Tabs are dealing with the Bar Tab screen being really crowded.

We would need a role permission that can be toggled so employees only see their own tabs in the bar tabs screen.

Alternatively, there could be buttons on the Bar Tabs screen to see "All Tabs" or only "Your Tabs".

There is a feature request by Brittany CH about filtering bar tabs from 5 years ago marked as "Complete" but I don't see any filtering options?

We have an account where they pulled up a previous day transaction for $1356 and refunded it.

Now the owner is asking me where the money is because he doesn't believe it's a refund. I told him you can tell it's a refund because of the R in front of the check number that day, but that's not enough.

When I send myself a copy of the receipt, it doesn't say REFUND anywhere. This refund also does not show up on the back office Refund report, apparently only same-day refunds show up there?

Just need a way to more clearly show that this was a past day's check that was pulled up and refunded.

We need a way to retain a percentage of credit card tips for the house, to cover the cost of processing those tips.

Right now the closest you can get is with Service Charge on tips. This is no good for 2 reasons:
1. It makes you select what type of card you are running at time of payment, an additional step that will annoy most customers.
2. It doesn't work with Surcharge or Dual Pricing, so it's useless.

Ideally you could just put a % of credit card tips that is retained by the house without having to turn off any other settings or service charges.

The ability to turn off the hold and fire functionality in roles. I have a customer that doesn't want their servers to be able to do that.

I am requesting a way that we can delete old saved tokenized cards ourselves without having to contact support. Also many customers are requesting they can delete old credit cards that they have saved in the QuickPay in online ordering. Many programs offer this ability and I have no idea why Linga doesn't

Why not have Pre-Auth in Options for any service type?

Especially Table Service, since a lot of bars use the table layout instead of the bar tabs because they need to know where to run food.

Spinoff of this request:

https://requests.lingapos.com/communities/1/topics/643-ability-to-pre-authorize-on-table-service

During Close Day there is a function that lets users "Force Void" active checks. There are a few issues that come up with this function. 

1) There is no confirmation warning the user that they are about to instantly void ALL active checks.

2) The Force Void creates report discrepancies. It appears that the voided transactions are still included in the reports. In the case where a closer accidentally voided $200 worth of online transactions we see that they still got paid, even though now that payment history is gone in reports(I notice that some sales figures still accounted for the payments, just not any payments, or menu Item reports)

3) I think the application should force users to resolve ANY transactions that have payments within the transaction itself. The close day has a transaction list, this should guide the user straight to the transaction to resolve

4) Our stores typically close all cashiers before going through the close-day checklist. If there is an active check the close all cashiers button will bring up the mass void function before they can even see the active transaction list leading to an accidental mass void instance. That transaction list should show up here so it can be resolved otherwise we will run into issues again.