What RestoMama talks to.

Where money, messages, tickets and orders leave the building — and the list of things we do not connect to.

  • UPI checkout, or collection into your own UPI ID
  • Your own WhatsApp number and sender ID, or ours
  • Any printer that speaks ESC/POS, at 58 mm or 80 mm

Taking the money.

PhonePe checkout, or collection into your own UPI ID

PhonePeOn by default

Hosted UPI checkout — the only hosted gateway that ships switched on.

The guest is handed a checkout, pays with whichever UPI app is already on their phone, and the payment confirms itself against the order. It runs on PhonePe’s own SDK, the only payment vendor’s SDK in the backend. Of the four gateways in the catalogue it is the only hosted one an organisation gets by default; the others stay off until somebody turns them on. Where a hosted gateway collects, it collects into RestoMama’s merchant account rather than yours — which is what the next row is for.

Your own UPI IDYours, if you have one

The rail that collects into an account you already own.

You store your own UPI ID and payee name, the guest scans, and your staff enter the payment reference afterwards. This is the collection mode an organisation starts in, not an escape hatch bolted on the side: guests pay straight into the UPI account you select, and RestoMama’s hosted gateways and card payments are not used in that mode at all. No wallet, no platform fee, no merchant account of ours in the middle.

Reaching the guest.

SMS, WhatsApp and email through MSG91 — ours or yours

MSG91Yours, if you have one

SMS, WhatsApp and email on one account, which can be yours.

Order updates, one-time codes and receipts leave through MSG91. It is the only messaging vendor in the product and the data model has no room for a second one. SMS is the channel that ships as the default. WhatsApp and email are built and can be switched on per platform and per restaurant, and WhatsApp additionally waits on Meta approving each template before the first one sends. The account can be ours or yours: a restaurant with its own sender ID, DLT template, verified WhatsApp number and email sending domain enters them once, its auth key is held encrypted, and each channel stays off until you mark it provisioned. All three run on one MSG91 auth key, so bringing your own is a single account to arrange rather than three.

Browser pushSwitched on when you want it

Notifications to a browser that has been given permission.

Push runs on the browser’s own Web Push standard with VAPID keys. There is no Firebase, no FCM and no APNs anywhere in the product, so what arrives is a notification in a browser that has agreed to receive one — not an app-store app asking for a badge. The four channels the product can reach a person on are WhatsApp, push, email and SMS, and that list is the whole list.

Paper and screens.

Any ESC/POS thermal printer, and the TV boards

Any ESC/POS thermal printerYours, if you have one

Raw ESC/POS bytes, no vendor driver and no certified-model list.

The receipt builder is ours and writes ESC/POS directly — its first line says there is no native-dependency printer library — so what a printer has to speak is the standard, not a driver we bless. Two paper widths are supported, 58 mm and 80 mm, set per printer, and each printer is flagged for the guest copy, the kitchen copy or both. The printer is paired over Bluetooth in Android settings first, and the RestoMama Admin Android app claims print jobs from a queue and acknowledges them, which is what lets printing keep working at the counter regardless of where the rest of the system runs. That app is the path that ships: there is no browser printing, and no USB or network printer setup.

Android TV menu boardsSwitched on when you want it

A TV runs a native Android player and pairs to a location with a code.

Boards are built from the menu you already maintain and shown by a native Android TV app. A screen is paired to a location with a code, and the screen list tells you which TVs have actually checked in — which is the part that matters on the evening one has quietly gone dark.

Signing in, files, and the map.

Google Sign-In, spreadsheets in, reports out

Google Sign-InSwitched on when you want it

Sign in with a Google account instead of a password.

A Google sign-in token is verified on our side against Google’s own tokeninfo endpoint, with the client id checked before anything is trusted. It is another way into the same account, not a separate account and not a data connection.

Spreadsheets in, files outOn by default

Stock arrives as a spreadsheet; reports leave as CSV, XLSX or a PDF.

Inventory can be loaded from a spreadsheet, and long reports are built in the background and written out as CSV, XLSX or a PDF summary with a download link that expires on its own. This is the honest answer to whether RestoMama works with your accountant’s software: you get a file, and somebody loads it. There is no accounting connector at either end.

AnthropicSwitched on when you want it

One capability, and only when it is configured: reading a stock document.

A photographed stock list or a supplier invoice can be turned into inventory rows by a language model, and Anthropic is the vendor behind that. It is the only place in the product where a model runs. It is switched on by configuration rather than by default — the service reports itself disabled without an API key and without file storage — and the forecasting the site talks about elsewhere is arithmetic on your own numbers, not a model.

OpenStreetMapSwitched on when you want it

Nearby place names, once, while a branch is being set up.

When a branch is placed on the map, the named settlements near its coordinates come from OpenStreetMap’s Overpass service. The distance is worked out here rather than taken from the provider, and the data is ODbL, which is why the admin screen carries the attribution. Nothing about a guest or an order goes to it.

Down the road.

Handed to RestoMama’s own delivery service

The RestoMama delivery platformOn by default

The other end of the delivery hand-off is ours, not a courier marketplace.

When an order goes out for delivery it is handed to RestoMama’s own delivery service — a separate system of ours, not a third party, and not an aggregator. Both directions are signed, an inbound message that carries a timestamp is only usable for five minutes, and an operator can read whether the connection is healthy. Your own riders are the other supported arrangement: an organisation set to deliver with its own riders sends nothing to that platform at all.

What we do not connect to.

Every competitor page in this market is a list of what a product plugs into. This is the other list, because it is the one you actually came to check.

  • No Zomato, no Swiggy, no third-party aggregator order sync of any kind. Your storefront runs on your own domain; RestoMama’s own marketplace is a separate listing, switched on per organisation and carrying its own commission.
  • No Tally, Zoho Books, QuickBooks or Xero connector. Reports come out as CSV, XLSX or a PDF and go into your accountant’s software by hand.
  • No third-party courier fleet. Delivery is RestoMama’s riders or your own.
  • No GST e-invoicing and no IRP filing. A supplier’s GSTIN is a field we store, and nothing more.
  • No Google Business Profile connection. The rating and the review link on your page are typed in by hand.
  • No public API and no API keys to hand out. Nothing here is built against by a third party yet.

If the thing you need is on that list, say so — it is how we decide what to build next.

Book a RestoMama demo

Tell us about your restaurant and the workflows you want to launch first.

  • One replyA person from the team, not an autoresponder sequence.
  • One serviceWe walk your own dinner rush end to end — bill, KOT, payment, dispatch, day close.
  • No hardwareIt runs in the browser on the machines and printers you already have.

See a real service, end to end.

We will take one dinner rush the whole way — ring a bill, print the KOT, call the token, mark the payment, dispatch the order, pay the agent and read the day close. On your menu, with your zones, in about thirty minutes.

  1. Billing and the counterOrder, modifiers, receipt, token
  2. The kitchen screenKOT routing, stations, prep state
  3. Payments and closingUPI, card, cash, wallet, day-end
  4. Dispatch and payoutsZones, assignment, tracking, settlement