Popular is not profitable
The item you sell most is often the one you earn least on. Volume flatters a dish that carries a thin contribution margin, and the kitchen keeps building the roster around it.
Menu intelligence for restaurants
Turn point-of-sale data into clearer pricing, stronger margins, and better menu decisions—while running orders, tables, KOT, QR menus, billing, and payments in one place.
Average check across live pilots
Pilot-observedOrder errors at the pass
Pilot-observedMenu questions your staff have to field
ModelledFrom registration to live service
Standard implementationThe margin leak
Most menus are written once, priced by instinct, and revised when a supplier raises a cost. Meanwhile the P&L moves every week. The gap between the two is where margin goes quiet.
The item you sell most is often the one you earn least on. Volume flatters a dish that carries a thin contribution margin, and the kitchen keeps building the roster around it.
High-margin dishes sit on page three, under a heading nobody reads, described in four words. They do not fail on quality. They fail on placement.
Raise it two dirhams and you might gain margin, or lose covers. Without an elasticity read you find out after the quarter closes, when the decision is no longer reversible.
The intelligence layer
that Korner applies the Kasavana-Smith menu engineering framework to your point-of-sale data — popularity on one axis, contribution margin on the other — and sorts your entire menu into four groups with a specific instruction attached to each.
High margin, high volume. These pay for the room. Never discount them, never move them off the first fold, never let a supplier change touch them without a re-cost.
Everyone orders them, nobody profits from them. Re-cost the recipe, adjust portion or price, and let elasticity tell you how far you can push before covers move.
Strong margin, weak sales. Rename, redescribe, move up the page, brief the servers. The fastest margin gain on any menu lives here.
Low on both. Cut them, or rebuild them from scratch. Each one costs you prep time, stock lines and a share of the guest's attention.
Pair-level analysis across every ticket, so you know which starter pulls which main, which dessert follows which wine, and where a bundle would earn more than a discount.
Demand response modelled per item from your own transaction history. You see the point where a price rise starts costing you covers — before you print the menu.
Move a price, swap a placement, retire a dish. The simulation returns the projected effect on revenue and contribution margin. Commit only to what the numbers support.
From registration to service
You do not stop trading to switch. We run alongside your current setup until the day your team decides to move across.
Two minutes, no card. Your workspace is provisioned immediately and your trial starts the moment you log in.
Day 0Upload a menu file and a point-of-sale export, or connect your POS directly. Our team maps categories, modifiers and taxes for you.
Days 1–3Your menu-engineering report lands: every dish classified, the four priority moves ranked, and the projected margin attached to each.
Days 4–7Floor plan, KOT routing, QR menus, payments and staff roles configured and tested. Your team trains on it in a single shift.
Day 14The operating layer
Everything a restaurant needs to trade, in one workspace — because analytics built on someone else's data export is always a step behind the service.
Dine-in, takeaway and delivery in one queue. Split orders, item modifiers and order history on every ticket.
Live floor status, custom floor plans, area zoning and reservation rules that hold your covers through peak service.
Categories, variations, modifier groups and options. Change a price once; it updates across every surface you sell on.
A mobile menu guests read in their own language, with allergen and dietary logic applied deterministically to every item.
Stripe and Razorpay built in, offline payment methods supported, multi-currency handled, taxes applied per venue rule.
Role-based access, waiter requests, delivery executives and a full audit log of who changed what, and when.
Kitchen tickets routed by station, receipt templates you control, and printing that keeps working when the internet does not.
Daily trade, item performance, staff productivity and margin movement — with the menu-engineering view sitting on top of all of it.
Integrations
that Korner connects to your existing POS through its API, or ingests a periodic export where no API exists. If your provider is not listed, send us a sample export and we will confirm the mapping before you commit to anything.
Pricing
Choose the plan that fits your operation. Your configured trial starts without a card.
Basic Package
Billed monthly. 30-day trial, no card.
This is a subscription package
Billed monthly. 30-day trial, no card.
This is a lifetime access package
One payment. 30-day trial, no card.
Test
Billed monthly. 30-day trial, no card.
Prices are shown in each plan's configured currency and exclude applicable taxes. Cancel at any time from your dashboard. Running a hotel or a group of five or more outlets? Talk to us about a group plan .
Security & data
Data encrypted in transit and at rest, with per-tenant storage separation. Your data is never pooled with another operator's for any purpose.
ISO 27001 in progress. SOC 2 Type II scheduled. We publish where we actually stand rather than a badge we have not yet earned.
Processed under GDPR and UAE PDPL principles, with a Data Processing Agreement available on request and a defined retention and deletion clock.
Questions
No. that Korner connects to your existing point-of-sale through its API, or ingests a periodic sales export where no API is available. Many operators run us alongside their POS for the intelligence alone. If you would rather consolidate, our operations layer can take over the floor entirely — that is your decision, not a condition of using us.
Three months of item-level sales history and a costed menu is enough to produce a reliable menu-engineering matrix. Twelve months lets us read seasonality and gives the elasticity model more to work with. If you have less than three months, we will tell you which parts of the analysis to treat as directional rather than decisive.
You get the full feature set of the plan you select for 30 days without a card. Founding-cohort registrations additionally receive the menu-engineering audit and white-glove onboarding at no cost.
You own it. Your menu, your transactions, your customer records. You can export at any time from the dashboard, and on cancellation we delete your data on a defined clock. A Data Processing Agreement is available before you upload anything.
The floor-facing surfaces are built to be learned in a single shift, and the interface is available in more than thirty languages. During onboarding we train your shift leads directly and leave you a short written protocol per station.
Order taking, kitchen tickets and bill printing continue on the local network during an outage and sync when the connection returns. Analytics and the intelligence layer are cloud-side and resume once you are back online.
Yes, from a multi-branch plan upward. Each branch keeps its own menu, taxes, floor plan and policies while reporting into a single view, so you can compare item performance across venues.
Email rs@thatkorner.com and you reach a person, not a queue. Recommended-plan accounts get a named success contact from day one.
The founding hundred
Register today and your menu-engineering audit is on us — along with the setup work, the POS mapping and a rate that does not move. 37 places remain in the founding cohort.
30-day trial · No card required · Live in fourteen days