Menu decisions are often made on item sales alone. That is not enough. A product can sell well and still do very little to grow basket size, while a modifier can look popular without adding much revenue.

That is where menu analytics becomes useful. For restaurant groups, the point is not just to know what sold. It is to understand how customers order, what combinations increase spend, and which parts of the menu are helping or limiting commercial performance.

Nomni Insights helps operators look past isolated item performance with the Basket Analysis, Sales by Modifier, Modifiers, Sales by Product, and Product Trend reports. Together, these reports show what customers buy together, which add-ons lift spend, which products are driving revenue, and when those products matter most throughout the day. So menu decisions are shaped by how customers actually order, not by how the business assumes they do.

See what customers actually buy together

Restaurant Basket Analysis shows how many items customers typically purchase per transaction and how often specific products appear within orders. Instead of guessing which products should work as a combo or which items should be promoted together, teams can look at what customers are already doing.

Basket Analysis shows how many items customers typically purchase per transaction and how often specific products appear within orders. That gives operators a stronger basis for bundles, cross-sell decisions, and combo design.

This is one of the clearest ways restaurant data analytics can improve menu decisions. The menu gets shaped around real purchasing behaviour rather than assumption.

Separate useful modifiers from menu clutter

Modifier lists tend to grow over time. Some genuinely lift spend. Others add complexity in the kitchen without creating much value.

Sales by Modifier shows how modifiers affect quantity and sales and which products they are tied to, while Modifiers shows how much revenue those add-ons generate by store. That helps teams see:

• which modifiers are worth promoting

• which ones are adding friction without enough return

• which customisations consistently improve spend

• where simplification may improve execution without hurting revenue

Understand which products matter, and when

A product that performs well overall may still matter most in a very specific trading window. That is why item sales in isolation do not tell the full story.

Sales by Product adds product-level revenue and quantity trends, while Product Trend shows when products sell most frequently throughout the day using a heatmap by hour and product variant. This matters because some high-performing items drive all-day volume while others are disproportionately important in specific dayparts. Better menu analytics helps teams see that difference and use it in promotion, placement, and daypart strategy.

Turn menu data into better decisions

This is where the reporting becomes the most useful. If Basket Analysis shows a hero product rarely travels with drinks or sides, that points to a bundling opportunity. If modifier reporting shows one add-on consistently lifts revenue while several others contribute very little, that points to menu simplification. If Product Trend shows a product is especially strong in a specific trading window, that can shape promotion, placement, or combo strategy

This is also where a menu engineering report can fit conceptually. A menu engineering view is useful when teams want to classify products by performance and contribution. But on its own, it is often too narrow. The stronger approach is to connect product performance with basket behaviour, modifiers, and daypart demand.

That is what makes this more than a static menu engineering exercise. It turns menu performance into a better decision system.

Move from item reporting to menu performance

A basic product report tells teams what sold. Better restaurant data analytics helps them understand how the menu is functioning as a commercial system.

• Are the right products carrying bundles?

• Are modifiers creating spend or clutter?

• Is the menu helping customers build larger orders?

• Are specific products stronger in specific windows?

• Is complexity growing faster than value?

Those are the questions that make restaurant menu analytics worth using.

Turn menu analytics into higher spend with less guesswork

Menu analytics is useful when it helps teams decide what to push, what to bundle, and what to simplify based on how customers actually order rather than how the business assumes they order.

Nomni Insights helps restaurant groups use basket, product, and modifier data to make those decisions with more confidence. That means less guesswork, better menu structure, and stronger opportunities to lift spend.

If you want to see how Nomni Insights helps operators use menu analytics and restaurant basket analysis to improve spend, book a walkthrough with our team.

Read more about Nomni Insights.