EdgeServPOS

We have a client that would like for bumped orders to alert the wait staff that orders are ready. This customer specifically called out the following functionality: When an order is bumped, an alert is sent to the server, indicating they have an order completed at table X. Additionally, the table itself changes color indicating the food is ready for pickup. There is another function they asked for which was the ability to hit a button on the KDS that sends an alert to the server that tells the server to talk to the kitchen about this order. I understand the EdgeServ KDS had this functionality, and if whatever was there, could be re-engineer so that it works with "texting service" that ChefTab already has built into their system.

When generating a cash drawer report, you are only able to select one specific drawer. Is it possible to select multiple cash drawer reports so that they generate on one report for the whole day?

I have had every merchant interested in integrating third party orders to EdgeServ that the revenue should be counted as non-revenue similar to gift card sales.

If a menu is disabled, it still shows up when you go to a menu item and scroll down, causing confusion for the customer. He completed a whole menu on the old menu because he was doing it item by item, rather than by using the price editor. Can we make it so that the menu item editors, "Price Section", correctly displays the active menus, and does not display inactive or disabled menus. Can we also make it so that Menu Priority dictates the order that they are shown in the Price Editor and in the Menu Item Editor "Pricing Section"?

We have a few clients that want the detailed void report to show all of the following information. When and on what ticket, By who, Name of the Void used, and if the Ask User Reason is enabled, the reason for using that specific Void. Currently the Void report only shows either the Name of the Void, or the Manually entered in reason. Ticket ID: What was Voided: Name of Void used: Reason: Example: Order ID Menu Item Name Reason Details Approval From Amount ______________________________________________________________________________________ . 11-2025 . 2025-11-19 . Sally .2025-11-5018/1 Fries "Server Error" . "Tammie opened the wrong ticket" 3.0000

We have a high volume customer that would like to have an easier way to enable/disable customer check out. They love to use their minis for customer checkout but find that with 6+ seats they have to babysit the table a little too much. It would be nice to add 2 buttons on the tender screen. 1 for the normal way to take payment and then another that takes you to the customer checkout screen.

Need to be able to add in Holidays where a site may be closed fully or partial day outside of the normal OLO hours for availability. This is most important when a site allows future orders, and will be closed for a holiday. Need to be able to black out those "dates" as OLO closed in a future scheduling sort of way. Currently sites have to change the number of days ahead # daily to accommodate a count down to a specific date they will be closed (Xmas eve & xmas). So that no orders can be put in for those dates in advance. Untill they get down to less than 7days in advance and can disable those "days" for that week. Then have to put it all back in place after the holiday to resume normal ordering capabilities. Site normally has orders coming in weeks in advance so this is very difficult to have a wall of sorts that ends it all, and have to turn it back on again afterwards.

I have had a few merchants ask if we can create a permission under roles for employee credit card tips to not show on server checkout reports and have another permission to "declare tips" similar to "declare cash tips". This would be simple solution for tip splitting for merchants. Is this possible to create another "Declare tips" permission and a permission to "not show credit card tips on server checkout"?

We'd like the ability to take deposits for reservations.

A couple of our sites have different payroll start days of the week, in which overtime and payroll reports need to be ran by, that are different from their business start day of week. We need to have a separate setting for payroll start day, that the system and reports/dashboard would use for calculating Labor related items differently.