Zones hide real differences
Two stores in the same zone can serve very different guests. One price leaves margin behind in one and turns guests away in the other.
Pricing Engine & Optimization
Restaurant price optimization. Your strongest lever, under control.
Price is the single most powerful lever a restaurant has, and the one most operators are afraid to pull. Pricing Engine turns it into an instrument: forecasts grounded in your sales history, guardrails that protect the brand, and discounts you can test before you run them.
Where it breaks today
Priced by zone. Paid for by the store.
Price changes are educated guesses
Increases follow gut feel or last year's plan, and the effect on traffic shows up weeks later, mixed in with everything else.
Guests notice before you do
An aggressive change can cost more in trust than it earns in margin, and franchisees carry that risk at their counters.
How it works
Recommend. Never overrule.
Understand demand
menuOS models how price changes affect orders for each item at each store, using your own sales history.
Set guardrails
Define floors, ceilings, maximum steps, price endings and items that must never move.
Compare scenarios
See projected revenue, margin and traffic for each option before choosing one.
Approve and publish
Accepted recommendations become proposed changes in Menu Management, where your normal approval applies.
What's in the module
Improve margins without burning trust.
Pricing Engine is where menuOS goes further than the incumbents: store-level evidence, clear guardrails and a human decision at every step.
Store-level recommendations
Prices tuned to each location's guests, not an average across a zone.
Elasticity forecasting
Estimates of how demand for each item responds to price, updated as new sales arrive.
Guardrails
Limits on the size, direction and frequency of changes, plus protected items and price endings.
Scenario planning
Side-by-side revenue, margin and traffic projections for alternative pricing plans.
Discount analysis
See how discounts and bundles affect margin and item mix before you run them.
Store clustering
Group stores by the characteristics of their trade areas to see where pricing should differ.
Where it sits in menuOS
Advisory by design. You keep the final say.
Pricing Engine reads store data from Store Management and the live menu from Menu Management. It never writes a price directly: every recommendation goes back to Menu Management as a proposal, so the approval process you already trust stays in charge.
Your pricing data is used only for your brand and is never shared with other brands on the platform.
What you'll see move
Margin you can see, guests you keep.
Margin per store
Gross margin movement at stores using recommendations.
Traffic retention
Order counts after a price change compared with forecast.
Recommendation acceptance
Share of recommendations your team approves.
Decision time
Time from spotting a pricing opportunity to a live price.
Common questions
Frequently asked.
What is restaurant price optimization?
It's setting menu prices from evidence about how guests respond, rather than by rule of thumb. menuOS does this for each store and item, within limits you define.
Does menuOS change our prices automatically?
No. Pricing Engine recommends and your team decides. Accepted recommendations go through the same approval process as any other menu change.
How is this different from zone pricing?
Zone pricing applies one price to a group of stores. menuOS still works with zones, but recommends store-level prices where the evidence supports them.
How does it work with franchisee pricing?
Recommendations can be shared with franchisees to adopt within brand guardrails, so owners get evidence rather than a mandate.
What data does Pricing Engine need?
Transaction history by store and item, your current menu and prices, and store attributes. menuOS reads these from the other modules and your existing systems.