please allow mix and match and discounts to be applied in OLO.  Would be great for pizza places

If you are setting up an integration, such as UberEats, and would like to add 10% to the prices on your menu, the current method requires that you create a price level on every item. So the restaurant that I am doing this for has 463 items. We should be able to add 10% to the menu, automatically rounding the the nearest nickel or dime, all in one step. This is already how it is done for modifiers and it should be the same thing for menu items. This will happen very often in the new landscape. It will be a deal breaker for any merchant who knows this before choosing Linga. 

Have an option (or button) for a [VIEW CHECK].  

This will be beneficial for the Server/Bartender/Retailer to display the check on the screen, showing the ITEMS, TAX, DISCOUNTS, SERVICES CHARGES, GRAND TOTALS etc with options at the bottom [PAY CHECK] or [EDIT CHECK]

Problem

The current propagation model requires merchants to perform up to four sequential actions to push a single change end-to-end:

1. Make a change in the back office
2. Click Publish (red arrow)
3. Navigate to Online Ordering → Stores → Settings → Sync Data under Sync Data To Web Order
4. Sync each POS station with the back office

Step 3 is consistently misunderstood by merchants. Most assume Publish already pushes changes to the Online Ordering site.

Merchant feedback (paraphrased from a recent support thread)

A merchant who had been troubleshooting menu propagation issues — and who has a software product management background — observed that they had assumed the Publish button already pushed changes to the online ordering site, because that had appeared to be the behavior in the past. They suggested adding the "sync to online" functionality to the Publish action so that merchants running both POS and Online Ordering can make a change and have it propagate across all customer-facing interfaces with one action.

The suggestion aligns with the principle of least surprise: a single user-initiated "publish" action should propagate to all downstream consumers of that data.

Proposed behavior

When a merchant clicks Publish in the back office:

• If the location has Online Ordering enabled, the publish action also triggers the equivalent of the manual Sync Data → Web Order call.
• If Online Ordering is not enabled, behavior is unchanged.
• Sync runs asynchronously; Publish should not block on it.
• UI should reflect a third state in the publish confirmation: "Published to POS · Web sync queued."
• For web sync failures, surface a non-blocking notification with a manual retry option.

Requesting for an option to select and delete multiple product/ items or categories.

Requesting for an option to select and delete multiple product/ items or categories.

This is for the Retails POS - We would like to add Favorites button in the POS where we can add few categories we often use.

We generate employees attendance reports every two weeks. Every time, we need to go the report, select the dates, select the columns to be included, click apply, then download the report. Then repeat that for every single employee. This is really very time consuming and just repetitive unnecessary work. 
Can this be improved please? 

Still manual but less steps: for example, open the Employee Report -> Select the dates and the columns to be included -> then select all the employees to generate the report for -> this way it's just one time work that generates for ALL needed employees instead of doing that separately for every single employee. 

More Automated way: for us, we know we have a fixed pay schedule so we generate the reports every two weeks on a Monday. It's always the same columns and same employees and the report runs on the last two weeks. Can't this just be automated where it generates the reports by itself and then send it to an email address or manually go to the Employee report and just manually click generate report? 

In both solutions, it's just very minimal work instead of receptive time consuming work.