A server or bartender cannot view or access others checks without explicitly allowing this through a system setting.

In the case of a server looking at a table map they would certainly see tables that didn’t belong to them but they could not open the table. However for tabs one bartender would not be able to open or “See” other tabs.

Hello team
For the online orders, I can configure an email address to receive notifications for every order we receive from the OLO which is great.

Is there a way to apply the same thing for the orders that are placed from the POS itself (more specifically the delivery orders)?

The reason is we work with a third party company that manages all the delivery for us that makes it easy for us to handle delivery from all different sources. However, for delivery orders placed from the POS itself (e.g. phone delivery), we have to manually enter the delivery info (customer, address ....etc) on the system which makes it error prone and also not convenient when we're busy. For OLO, all the orders get sent to that third party delivery management company and it auto assigns in house drivers/third party drivers. We would love to have a setting to configure an email address to receive notifications for delivery orders placed from the POS itself. 

If not, can this be at least hardcoded? 

Much appreciated! 

We had a request to have the table layout be able set a default seat count based on each table so the server does not have to enter it. For example, if the table is a 4-top, the seat count would default to 4 seats and not prompt the server to enter the number of seats.

It would be a nice feature to be able to print a gift receipt when needed. For example, when selling a Gift Card, sometimes the customer wants a Gift Receipt to show the value added to the card. It would need to be able to be printed by item as it would only be needed for certain items. If a customer was having dinner and wanted to buy a gift card with as a gift for someone, we would only want the gift receipt for the gift card and not every item on the check.

Purpose:
Improve the discount engine in Cloud POS to support more advanced and predictable discount scenarios, including buy-one-get-one (BOGO) and item-specific discounts that handle modifiers correctly.

Current Behavior:

• When configuring a BOGO discount, the discount only applies correctly if the items are added to the check before the discount is applied.

• If the discount is added first, it may not attach properly or calculate the discount as expected.

• Additionally, when the “free” item has modifiers, there is no current method to make the item $0.00 while still allowing modifiers to be selected and priced appropriately.

• This behavior leads to confusion during setup, inconsistent application across transactions, and difficulty supporting merchants who offer bundled or promotional pricing.

Proposed Enhancement:

1. Discount Application Logic

   • Discounts should automatically identify qualifying items regardless of the order they’re added to the check.

   • Once all qualifying conditions are met, the system should retroactively apply the discount.

2. Modifier Handling for Free Items

   • Allow modifiers on discounted or “free” items while keeping the item’s base price at $0.00.

   • Option to include or exclude modifier pricing in the discount logic (e.g., “include modifiers in discount” checkbox).

3. Discount Type Expansion

   • Add preconfigured templates for Buy X Get Y, Mix & Match, and Item Pairing Discounts.

   • Ensure discounts are compatible with both item-level and category-level configurations.

4. Validation and Feedback

   • When discount logic fails to apply, the POS should display a clear, user-facing message (e.g., “Discount conditions not met: missing qualifying item”).

   • Include logging or audit data so partner support can verify which discounts were triggered and why.

Value & Impact:

• Reduced Merchant Frustration: Simplifies setup of common promotional discounts like BOGO or bundled offers.

• Consistent Behavior: Eliminates dependency on item entry order.

• Improved Partner Support: Easier for partners to troubleshoot discount-related issues without escalation.

• Competitive Parity: Aligns Cloud POS with modern retail and restaurant POS discount capabilities.

Example Scenario:

A merchant wants to run a “Buy one Budweiser, get one free” promotion. Currently, the discount only applies correctly if the second Budweiser is added after the discount, and fails if the discount is applied first. Furthermore, when the free Budweiser includes optional modifiers (e.g., “add lime” or “served cold”), the modifiers cannot be selected without breaking the discount.
This enhancement would ensure the promotion applies correctly regardless of item order and handles modifier logic gracefully.

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

We have an iPad POS. When the POS is not running in the foreground (e.g. Safari is open and we forgot to go back to the POS screen WITHOUT terminating the POS app). After 5 minutes, the POS assumes the store is closed and it shows on the OLO that it's closed. The BIGGEST problem is this scenario; 
1. a customer orders online when the OLO shows store open (meaning the POS is running in the foreground). 
2. For some reason, an employee opens safari (as an example) on the POS and forgets to return to the POS app (so the POS isn't in the foreground) and it is not terminated. 
3. Customer receives a cancellation email and we LOSE the customer and the order. 


It does NOT make sense to show store is closed and cancel customer's order just because the POS is not running in the foreground. This shouldn't happen and we should be able to still receive orders and also the order gets automatically printed. I have never seen this in any other POS system. This is just a common sense. No matter how we tell employees to keep the POS running in the foreground, sometimes they just forget (e.g. they want to print something from safari or whatever the case is)> 

on phone as an example, you don't stop receiving notifications if you texting app/FB/IG or whatever is not running in the foreground. This is just a common sense. 

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..."

It would be brilliant to have a module that offer customers paid membership for special offers and off menu items. The idea is that the business almost makes more from membership rather than general sales. I am in an area were there is a lot of competition and I am looking for a new business model.