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

This is one that popped up today.

There is no way to have a Cash Drawer Report to show how much is in the drawer with multiple employees using the drawer.

You have to pull a report and do a search by check number that corresponds to that terminal to see what was rung in that terminal.  Pull out a calculator to add up what's in the report, In this case its Terminal 3 which starts with a 2 (see below) (Terminal 1 starts with a 0).  If there's an issue (like what happen today) they have to tally up the amounts below and then count the drawer.  That is a lot of paperwork and prone to human error if they add a wrong number or a poorly placed decimal point.

We need to be able to pull a Cash Drawer Report and it have it say:

A-000 Bar Left (or Bar Left Receipt Printer)

* START BANK: +$300.00 

* CASH SALES: +$800.00

* PAY OUTS: -$150.00

* TOTAL CASH IN DRAWER: =$950.00

If you want to blow away what other POS companies have this section after "TOTAL CASH IN DRAWER"

Cash Sales by Employee

Billy - $200.00

Angela - $350.00

Joanne - $250.00

I was downloading each month for 2025, but when I go to review them, certain months are not clear and some parts are getting cut off and totals cannot be seen. Some show fine but on certain (Busy) months its messy
Can this be adjusted? Preferably it should print as it shows on the screen (See screen shot/video) just because this is how customers are viewing it.

attached is one of the PDF reports and video

ALT POS NYC - Google Chrome 2025-12-20 12-3....mp4

07-July-2025_SEH_Sale Recap Report201220251....pdf

"Back Office -> Transactions -> Report"

When showing the transactions, customer name doesn't show in the list of columns and it is not possible to search by customer name. It doesn't make sense to open each transaction to find the customer name. When opening an order, the customer name is already there, can't you just show it? 

When I contacted the support, they suggested sumbtting a feature request and also they shared this "There is another way to search for a transaction by customer name. From the home screen, navigate to Customers > Customer Info > Search the customers name > under Actions, select View Customer Metrics, and you will see the history of the customer transactions. This will only work if the customer's info was attached the the transaction at the time of sale."  
This won't work if a customer places an order as a guest without creating an account (which actually happens a lot). 

Purpose:
Allow partner support teams (e.g., EMS/Kurv) to access POS application logs directly within the Cloud POS platform. This visibility would enable faster triage of software-related issues and more detailed escalation reports to Linga’s development team, shortening resolution times.

Current Limitation:

Partner teams currently lack access to POS system logs. When issues occur—such as app instability, missing transactions, or synchronization failures—we must submit a ticket and wait for Linga’s developers to extract and interpret logs. This often delays resolution by several days, even when the symptoms could be quickly identified from POS-level data.

Proposed Enhancement:

Provide authorized partner support users with read-only access to Cloud POS system/application logs through the partner portal or an API endpoint.

Key Requirements:

1. Scoped Access Control:

   • Access limited to merchants managed by the partner organization.

   • Read-only permissions only—no modification, deletion, or system control.

2. Log Categories Requested:

   • POS application logs (service events, exceptions, app restarts).

   • Communication logs between POS, peripherals, and backend services (API requests/responses, timeouts, sync failures).

   • Configuration and sync logs (menu updates, local cache status, data push/pull activity).

   • Database-related errors or transaction anomalies (for identification, not correction).

3. Filter & Search Capabilities:

   • Date/time range selection.

   • Merchant or device identifier filtering.

   • Keyword search by module, error code, or event type.

4. Export Options:

   • Ability to export logs for documentation and inclusion with escalations.

Value & Impact:

• Faster Issue Identification: Partner support can immediately pinpoint probable causes—such as sync failures, timeout patterns, or database access errors—without developer intervention.

• Better Escalation Quality: Log details give Linga’s dev team clearer diagnostic data, improving accuracy and reducing back-and-forth communication.

• Reduced Resolution Time: Streamlines triage for both teams, leading to quicker fixes and less downtime for merchants.

• Enhanced Merchant Experience: Shorter wait times and more informed responses during support interactions.

Example Use Case:

A merchant reports delayed transactions and missing receipts. With access to POS logs, our support team could detect repeated sync timeouts or database write errors, confirm the issue scope, and escalate to Linga with specific timestamps and error references—allowing the dev team to resolve it faster.

Customer wants to be able to manually remove auto discounts from items on POS.

As of right now you can view an open check in the back office and view who ordered which item and at what time.  Once the check is closed you cannot see this info.  If this feature can be added to the TRANSACTION REPORT would go a long way for owners to police their staff.

It would be nice to have the option to view a closed check and see that information. along with a time stamps.  This will help identify "RED FLAGS, THEFT, FOUL PLAY etc..."