LINGA — Feature Request Forum

Cash drawER OPEN
WOULD LIKE THE CASH DRAWER TO HAVE ABILITY TO OPEN ON ANY PAYMENT TYPE. EXAMPLE: SIDE CC ALLOW DRAWER TO OPEN TO ALLOW CLIENT TO PYT SLIPS IN DRAWER. WE ARE 90% PLASTIC SO HITTING NO SALE AFTER EVERY SALE IS NOT A VIABLE OPTION.

Add Payment Type details to Closed Check Data
Add Payment Type details to Closed Check Data such as cash, credit card, gift card, etc. If possible, even distinguishing the type of credit card (visa, MC, Discover, Amex).

Check/Screen Timeout Enhancements
Check/ Screen Timeout Enhancements
-Address delays caused when a check is left open on one terminal and accessed on another.
- Ensure faster allocation of checks between terminals.

Mix & Match Discount Restriction Working Backwards
When they are setting up a mix & match discount and it only has a restrict time and not the available time like the other discounts. This prevents them from setting a time frame that they need for the discount to work. Are we able to change this to available like the others? Or set up both? The merchant has combo discounts that they need this for and only during specific times.

Fix how Suggested Tips work and make Gratuities Calculation and suggested TIps match up
For Suggested tips.
1. Don't force how many suggested tips we can have. Most of my customers do not like 4 Suggestions they want 3 only.
2. Suggested tips are based off the total after Tax. It is suppose to be before tax.
3. Gratuities are based off Subtotal so why not Suggested tips?

Implementing Role-Based Access for the "Hold" Button
I would like to request the implementation of a role-based access system for the "Hold" button feature. The goal is to allow control over who can use this functionality by restricting it to specific user roles. Below are the key details for this request:
- Permission Level Control:
- Configure the "Hold" button as a feature tied to specific roles (e.g., Manager, Admin).
- Ensure that users without the assigned permission, such as servers, do not see or have access to the button.
- Backend Configuration:
- Add an option in the backend portal to enable or disable the "Hold" button for different roles.
- Provide a toggle or checkbox under role management settings for this purpose.
- Flexibility and Customization:
- Allow customization of role permissions to ensure only authorized personnel can access the "Hold" button.
- Include options for overrides or exceptions for specific users, if necessary.
This feature would provide precise control over the "Hold" button functionality, enhance security, and meet the operational requirements of clients who do not want this feature available to all users.

Customer Profile do not require Phone/Email
Do not require a phone or email in customer profile, these should be optional fields and not used an a UID in the customer database
Customer support service by UserEcho