Have the ability to integrate with employee scheduling software, such as, 7Shift

The option to remove seat print should be available for ALL service types. 

Not all table service restaurants like to use the seat option. 

They will often split by seat at the end of the transaction but many do not enter the order by seat and many do not want the seats printed in the kitchen.

Ability to change Quantity in Inventory Menu item beyond 2 Units after decimal point

Ability to create custom Payment types that each on its own is summarized and used at Close Day and used in the financial back office reports

Add a reason/description (optionally forced or not) when applying discounts

-Toggle this feature on and off

In California if you order something for take out or delivery, they DON'T CHARGE tax.

If they get that same item and eat in, it CHARGES  tax.

Update the ticket in the cloud as items are added. Right now the way tickets are created is that it creates the ticket and nothing saves to the ticket or the cloud until finish is tapped. What happens in this case is that when the device freezes and has to be restart it brings back up a blank ticket and they have to start over entering items again. 

have it ask:

Are you a loyalty member or would you like to join?" and have a yes/no option. 

If a customer selects yes, she would like the system to open the keypad for customers to enter phone number for Loyalty to either sign in, or create a loyalty account. If the customer selects no, the system closes the prompt on the CDS and the cashier would ask for and enter a customers name.

I am writing to request a change in how the system handles tax calculations when Loyalty points or Deposits are applied. Currently, the system calculates these payments after taxes and fees have been applied to the full subtotal. This logic results in a "tax on tax" effect or a discrepancy that overcharges the customer compared to the actual remaining balance.

The Problem: When a deposit or loyalty credit is treated as a post-tax payment rather than a pre-tax deduction, the customer ends up paying taxes and fees on a value they have already partially cleared.

Mathematical Proof of Discrepancy:

• Transaction Total: $100.00
• Applied Taxes & Fees: 8.88% Tax + 3.12% Card Fee.
• True Gross Total: $112.28

1. The Deposit: The customer makes a $10.00 deposit. Including tax and fees, they pay $11.23.
2. The Math: Total ($112.28) - Paid ($11.23) = $101.05 (Expected Balance).
3. The System Issue: Currently, Linga shows a balance due of $101.97.
4. The Discrepancy: This creates a $0.92 – $0.97 error on a small $100 order.

Scalability Concern: This error scales significantly with larger transactions. For a $10,000 banquet with a $5,000 deposit, the calculation error grows to $457.85. This is a significant financial discrepancy that is difficult to explain to a merchant or a guest.

Proposed Solution: Update the calculation logic so that all Deposit and Loyalty operations are deducted from the subtotal before taxes, additional fees, and card charges are calculated. This ensures that taxes are only applied to the remaining taxable liability, maintaining accounting integrity and preventing double-charging of fees.