Menu Intelligence
Menu Engineering with Evidence: What Your Menu Is Actually Doing
“Which items actually drive our revenue and margin, and how should the menu change?”
Menu engineering answers three questions with data: what each item contributes, what role it plays in baskets and visits, and what would happen if you changed its price, placement, or existence. The classic popularity-versus-margin matrix answers only the first, and only partially. Quantiiv builds the full picture from item-level POS history: item and category performance with trend, basket pairings and attachment, substitution relationships, and price sensitivity, all normalized across locations and channels.
That turns menu decisions from debate into design. You see which categories are gaining or losing share and why, which items build tickets versus ride along, which price points have room, and where the menu's complexity is earning nothing. Every recommendation traces to transactions your own customers made.
Sound Familiar?
The menu matrix says what, never why or what next
Stars, plowhorses, puzzles, dogs: the labels describe last quarter. They do not tell you whether a dog is safe to cut, whether a star can carry a price increase, or why a category is quietly losing share to another.
POS naming chaos makes item truth hard to see
The same product lives under a dozen POS names across locations, sizes, and channels. Until that is normalized, item-level analysis produces confident numbers about fragments of products.
Menu decisions get made on anecdote and vendor pressure
A franchisee's feedback, a competitor's launch, an ops complaint: real signals, but unweighed ones. Without transaction evidence, the loudest voice sets the menu.
How Quantiiv Answers It
- 1
Normalize the menu so items have one identity
Every analysis starts from a governed menu mapping that merges POS naming variants into clean item and category structures across all locations and channels. This unglamorous step is why the numbers can be trusted.
- 2
Measure item and category performance with trend
Contribution, velocity, margin, and momentum by item, category, daypart, channel, and location. Not just a snapshot ranking, but which parts of the menu are gaining and losing, and where it is happening.
- 3
Map basket dynamics
What sells together, what builds checks, what attaches to what. Items reveal their real roles: anchors that bring the visit, builders that grow the ticket, and passengers that add complexity without carrying weight.
- 4
Layer on price sensitivity
Elasticity estimates show which items can carry price and which cannot, adding the forward-looking dimension the classic matrix lacks. A high-margin star with pricing room is a different opportunity than one already at its ceiling.
- 5
Translate into menu actions
The synthesis is a concrete agenda: price moves, promotion candidates, rationalization candidates, category bets, and LTO opportunities, each sized by the revenue at stake and backed by its evidence.
Why Quantiiv
Item-level POS truth, normalized first
Analysis runs on cleaned, governed, item-level transaction data across every location and channel. Most menu analytics fail at this step and never know it.
Roles, not just ranks
Basket analysis reveals what each item does for the visit, which is frequently different from what its sales rank implies. Ticket-builders and traffic-anchors get identified before someone cuts or reprices them by mistake.
Frequently Asked Questions
What is menu engineering?
Menu engineering is the practice of using sales and margin data to decide what belongs on a menu, how it should be priced, and how it should be presented. Traditional versions classify items on popularity and profitability. Modern menu engineering adds basket roles, substitution, trend, and price elasticity, which is what makes the classifications actionable rather than descriptive.
How is this different from the reports in our POS?
POS reporting ranks raw item records at single locations. Cross-location analysis requires normalizing naming inconsistencies so each product has one identity, then adding the layers POS reports do not have: basket pairings, substitution relationships, trend decomposition, and price sensitivity. The difference in conclusions is usually large.
What data do you need for menu engineering analysis?
Item-level transaction detail from your POS, ideally 12 to 24 months, including modifiers, check identifiers for basket analysis, and location and channel attributes. Margin inputs sharpen the profitability view but are not required to start. Loyalty or digital-order identity enriches it further with customer-level insight.
How often should menu performance be reviewed?
Category and item trend monthly, with a deeper structural review quarterly or ahead of each menu cycle. The monthly cadence catches mix shifts and emerging winners while they are actionable; the structural review is where pricing, rationalization, and category strategy decisions belong.
Related Problems We Solve
Menu Rationalization
“Our menu has gotten too big. Which items can we actually remove without losing the customers attached to them?”
Read morePrice Elasticity
“How much can we raise prices without losing traffic?”
Read moreLTO & New Item Analysis
“Our LTO sold well. But did it grow the business, or did it just cannibalize the core menu?”
Read moreStop Fighting Your Data.
Start Using It.
Transform fragmented restaurant data into actionable insights—with just an email to ROGER.
400+
Locations Served
15+
POS Integrations
10hrs
Saved Per Week
Powered by Quantiiv
Enterprise Restaurant Intelligence