Currently when ordering using the the Pizza Module it just list the toppings with a notation at the end of the Modifier indicating if its left (1/2 L) or right (1/2 R) and nothing if its the whole pizza. See Attached Pic

Can we have the module prompt 1st Half / 2nd Half / Whole Pie and list them together

EX: using the same options as the pic attached and if you set the Cut to 4 then it should use the word quarters (1st Quarter / 2nd Quarter etc…

-XL PIE PIZZA

    Thick Crust

— Whole Pie (< this should be in bold)

    Black Olives

        Pepperoni

        Sausage

— 1st Half

        Mushrooms

        Bacon

— 2nd Half

        Cheese

        Chicken Cutlet

        Eggplant

We have several merchants who want taxes broken out, not one rate, city state and sometimes county rates. When this is the desired configuration the open item or mods buttons do not automatically apply all the tax rates set. The default option esp in a restaurant setting should be to select all taxes and force the user to unselect if necessary because other wise an open mod or open item can result in taxes NOT being collected properly causing a financial loss to the merchant if the server forgets. 

The program should be able to save each customers preferred Payroll Columns- it used to-

PLEASE fix this for your customers.

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.

add more payment types as option on olo like House Account

LINGA reporting does not update the tip sharing values when an employee's hours are changed. For example, if a store has their tip sharing set up to share tips based on the hours worked and an employee had their hours adjusted in the back office (for example, an employee forgot to clock out), the reporting will not update the tip sharing amounts. 

Request to add an alert feature that notifies managers/owners when a employee is clocked in for too long. Some employees forget to clock out after the end of their shift, which can affect labor reports. Alert should be definable, a manager or owner should be able to set the threshold when they are notified (i.e., notify me if an employee has been clocked in for over 12 hours). 

Hello Request peeps.

In previous versions of the Software (Pre-Android) I was able to restrict a payment type by "ROLES" but that feature went away.  Can we have it back.  Client would like to create payment methods and restrict it to a specific Terminal OR Job Code.  

They would like to prevent certain ROLES or Terminals from access specific payment types

* SEE ATTACHED PIC FOR DETAIL IDEA