ChurmuriYour Menu Should
Sell Itself.
A recommendation engine built into every menu. It reads the cart, the weather and the kitchen, starts working on the first table, and gets sharper with your own orders.
Change the moment. Watch the suggestion change.
Pick what the table ordered, then change the weather, the time of day or the kitchen, and see what a guest would be offered and why.
Veg Pizza₹299
Cheese Garlic Bread
Cheesy FriesSample menu, no real orders. The pairings here are hand-set for these dishes; a new outlet starts from category pairings plus the same weather, time and kitchen rules, then learns from what its own guests order together.
Once, at the right moment, in the right place.
Timing is most of it. A suggestion shown while the guest is still deciding converts; the same one shown as a correction does not.
A single strip above the cart bar, shown right after an item goes in. Never a pop-up, never more than one at a time.
If the meal has an obvious gap, like a curry with no bread or a main with no drink, a bottom sheet offers it once. Closing it still places the order.
Staff taking an order at the POS see the same suggestion, so phone orders and walk-ins are part of it too.
A hesitating diner gets a short list of three dishes, not a ninety-first one.
Useful on day one. Sharper with your own orders.
We would rather be exact about what it does than impressive about what it might do.
Pairings by dish type, the weather, the hour and how busy the kitchen is. No order history needed, so a new outlet gets useful suggestions on the first table.
As orders come in, what your guests really order together starts to outweigh the starting rules, dish by dish.
A small share of tables never see a suggestion, so you can compare them with the rest instead of taking our word for it.
A readout you can check, not a promise.
Cart strip, checkout sheet and register, each with its own add rate.
The dishes guests accepted, and the ones they dismissed.
Tables that saw no suggestion, next to the ones that did.
Cost a dish and suggestions can lean toward what earns more. Dish costs stay staff-only.
Ordering and billing got you in the door. They won’t grow the business.
Ordering, a kitchen board and billing are the baseline now. Churmuri ships all of it, then adds the layer that moves revenue.
What every POS already does
- QR ordering, a kitchen board, billing and basic reports
- Runs the floor, doesn’t change what a guest orders
- The same menu, shown the same way, to everyone
What Churmuri adds
- Suggestions that read the cart, the weather and the moment
- Timing and limits so guests are not nagged
- A per-surface readout with a control group
- Standard on every plan, not an enterprise add-on
Questions owners ask first
Is this AI?
It is a set of explicit rules plus statistics from your own orders. It reads the cart, the weather, the hour and kitchen load. We don't call it AI, and we don't pretend it knows more than it does.
Will it pester my guests?
No. A dish is shown at most three times, a table sees at most three nudges a visit with a gap between them, and a dismissal is remembered across every place a suggestion can appear.
What lift should I expect?
We won't quote a number. It depends on your menu and your guests, which is why part of your tables are held back as a comparison. Your own readout is the proof.
Does a new restaurant have to wait?
No. It starts on the defaults above from the first order and gets sharper as your own orders accumulate.
Let the menu start
working for you.
Set up a menu and print a QR code. Ordering, kitchen and billing work together straight away, and suggestions start from the first guest. Fourteen days, no card required.