Every apology has to be made before the order is taken.

A kitchen with no dining room has no host at the door and no cashier to say the biryani is finished. So the answer is a setting rather than a sentence: an operating mode that adds minutes to every promised ready time, one channel paused while the rest keep selling, a portion count that runs out on its own, and a dish that switches itself off when the ingredient behind it is gone.

Book a demo Register your kitchen

Six operating modes, set per kitchen
Storefront, WhatsApp, phone-in and the road
One organisation, one storefront, one WhatsApp number

A room behind a shutter, with no board on it.

A first floor off the Palarivattom bypass, a converted garage in Kaloor, a unit in the Kakkanad lanes that feed Infopark at 12:45. Four to eight people work it: a head cook, two helpers, a packer at the bench, and whoever is holding the phone.

The packing bench is the counter.

Foil containers, lids, the paper carry bag, the bill stapled on. Nobody bills a walk-in, because there is no walk-in, and there is no wall a customer ever reads. The FSSAI licence on that wall is held against the premises rather than the business, which is the right way round for a kitchen with one room — it is that number that goes on the box sticker.

Orders arrive with no person attached.

A link in the Instagram bio, a WhatsApp chat, a phone call punched in at the POS, and, while the delivery system is on, the road. Two spikes: 12:30 to 14:00 for the office lunch, 19:30 to 22:30 for the night.

The hard part is not the cooking.

It is 13:10, when a ticket nobody accepted is eight minutes old and a rider is idling outside with the engine running. There is no queue to slow down and no host to stall with. The only two levers are what the kitchen will still accept, and what time it is willing to promise.

You provision as a restaurant.

There is no cloud-kitchen vertical in the platform and we would rather write that here than let you find it on the setup call. The business types are restaurant, distributor, bakery and caterer, so a kitchen with no dining room signs up as a restaurant — and its module list starts empty and is switched on one at a time. That is why the sections below name modules individually instead of selling you a preset.

Intake is a setting, not a sentence.

In a restaurant the cashier slows the door and says it out loud. Here nobody is standing there, so what changes is what the kitchen will accept and what time it is willing to promise. The customer meets that decision as an ordinary ready time and nothing else. It is all in Counter & Orders, which arrives with the base module.

Busy, and critical+15 and +30 minutes by default

Six modes per kitchen: normal, busy, critical, paused, closing and offline.

Busy and critical each add a fixed prep buffer — fifteen minutes and thirty out of the box, editable per kitchen — and that buffer is written onto the promised ready time the order carries, not painted onto the estimate for show. Neither mode tells the customer why. There is no kitchen-load wording anywhere on the storefront, only a later time. Critical also switches express pickup off, because a promise of minutes is the one thing a drowning kitchen cannot keep.

A paused channel, while the others keep sellingTyped reason, written to the audit log

Paused takes a list of channel names: delivery, pickup, express pickup.

Pause pickup and let delivery keep running, or the reverse; an empty list means the whole kitchen is shut. Paused, closing and offline each demand a typed reason, and the change is recorded with the value before it and the value after it. A pause with a time on it heals itself: once that time passes the kitchen counts as normal again rather than staying shut because the helper who paused it went home at four.

The fortieth biryani has to stop selling itself.

In a dining room somebody says it is finished to a face. Here it has to stop on the storefront, in the WhatsApp chat and on the phone order at the same instant, or somebody has paid for a dish that does not exist.

A limited portion countMenu & Catalog

A dish set to a portion count at this kitchen, counted down as orders land.

The count comes down under a guarded decrement, so a burst of simultaneous online orders cannot oversell it — two people confirming in the same second do not both take the last portion, and the one who missed is told exactly how many are left. One catalog sits behind the counter, the storefront and the chat, so all three stop offering it together.

The dish that switches itself offInventory & Recipes

Inventory can disable a menu item when a required ingredient reaches zero.

It sits on its own flag, separate from the on-off switch a person uses, so switching the dish back on by hand is never quietly overwritten — and it is off until you turn it on. With negative stock disallowed, an order is checked against its ingredients before it is written at all, and free deal or gift items are left out of that check so a short ingredient never blocks the paid order behind it.

The ingredient that limits the dishLow at ten portions

Servings you can still make of each dish, with the ingredient that caps them named.

Which is the figure a kitchen with no room reads at eleven in the morning and not at eleven at night. The same recipe carries a wastage percent per ingredient and can point at a sub-recipe, so a base gravy made once is consumed by the dishes built on it — and the plate cost behind your margin is the weighted average you actually paid for the stock, which matters here because you sell at a delivery price and pay for the container.

What you watch at 13:10.

Live Operations, per kitchen. Not a dashboard to admire — the short list of things that are about to cost you a customer nobody can see.

Orders awaiting acceptance, and the oldest unaccepted order in minutes
An order still unaccepted after five minutes, in a queue ranked by severity and then by age
Kitchen load in prep minutes, added up from the prep time on the items themselves rather than a score somebody types in
Pre-orders due in the next 45 minutes, and one push to the kitchen 30 minutes before a scheduled order is wanted
Print jobs pending, and the ones that failed

One thing it does not do: the utilisation percentage divides by a fixed sixty-point capacity that is not yet configurable per kitchen. The prep minutes are yours, the number they are measured against is not, and you would find that out in your second week anyway.

Printing is honest in the same way: a printer is flagged for guest copies or for kitchen copies and nothing more, so an unrouted job may be picked up by any printer covering that copy type. There is no routing by dish, category or station.

How the food leaves a kitchen with no door.

The only block on this page that depends on the road. Everything above it is about what happens before anyone picks the bag up. Delivery Management needs Counter & Orders and Complaints & Reviews switched on with it, which is why the complaint ticket below is not optional for this operation.

The order offered to the RestoMama rider network, stage by stage back onto the order record
A tracking link for a guest who has never seen your building
A six-digit handover code at the door, minted by the delivery platform
Radius, base fee, per-km fee, free-above and minimum order set on the kitchen, with an ETA built from base minutes plus minutes per km
Delivery and pickup as separate switches, each with its own prep time in minutes

The guest is never standing there.

Customer WhatsApp and SMS are gated event by event, and the defaults are written for a counter: order ready arrives switched off, because at a counter the guest is already in front of you. This is the operation that turns it on.

Order ready, sent rather than called.

It goes out on WhatsApp, SMS, email and push. Organization Admin is where those per-event toggles live, alongside your own SMS sender ID, WhatsApp number and email domain.

The cart nobody came back to.

An unpaid order auto-cancels after sixty minutes by default, and a staff-created unpaid order raises one alert at a hundred and twenty. That window is what stops abandoned online carts sitting on the board through the lunch spike.

A complaint with no table to walk to.

A spilled biryani reaches you as a ticket against one order with a countdown running on it, and it escalates itself to refund-due if nobody answers. Complaints & Reviews is the only place that can land.

The badge is the whole of your reputation.

The star rating averages into the badge on your storefront. With no room to sit in and no board on the street, that badge and the page it sits on are the entire surface a stranger judges you by.

Which channel is actually paying.

The question a dine-in restaurant rarely has to ask, because it can see its room. Every order carries two things: what kind of fulfilment it is, and where it came in from.

Fulfilment is delivery, pickup or dine-in. The channel is walk-in, phone-in, your storefront, an in-store QR, WhatsApp or the marketplace. The daily figures count delivery, pickup and dine-in separately, so the split is countable over any range of dates you pick. That is Dashboard & Reports, and it is the report this operation opens first. Walk-in and dine-in never fire in a kitchen with no room, which is the point of reading it: the split that decides your week is the one between the storefront, the chat and the phone.

There is barely a drawer here. Almost everything is prepaid by UPI before the kitchen starts cooking, and the money settles into the wallet net of fees and is drawn to your bank from Payments & Wallet. Cash on delivery is the exception that has to be reconciled, not the norm.

There is no board on the street.

For every other outlet type the storefront is one channel among several. Here it is the shopfront — the only address a customer has, because there is no signage and nothing to walk past.

The storefront is the address.

Online Ordering & QR carries your own domain, your logo, guest checkout you can switch on per branch, and the pickup and delivery switches that decide what the kitchen is offering today. One organisation holds one subdomain and one custom domain, both unique, so this is one address and not a set of them.

The chat nobody has to install anything for.

A Kochi customer paying ₹180 for lunch will not install an app for it. WhatsApp Ordering files the order against the sender’s phone number with no login, and it lands on the same order list as a phone-in punched at the POS. One verified number per organisation, set by the platform.

The nearest thing to a sign.

Local SEO Pages builds a page per area you serve, each with the distance by road and a landmark. For a kitchen nobody can see from the street, that page is the signage. It needs the storefront switched on with it.

A repeat order has to be bought back.

Nobody walks past and remembers you. Rewards & Deals is coupon codes with date windows and usage caps, daily deals set on chosen weekdays and hours, and campaigns to a filtered audience — the whole retention surface a kitchen with no room has. A RestoMama marketplace listing is a separate thing again, and it needs both the storefront and delivery switched on.

Add-on

A page for every area you serve, generated per branch, for the searches nearby.

All modules

What this does not do for a cloud kitchen.

Every one of these is something a cloud kitchen gets sold somewhere, and the first is the thing you came to this page to check. We would rather lose the call than have you find out after you have moved your menu across.

No Zomato or Swiggy order sync, in either direction. Nothing arrives here from an aggregator, and no aggregator’s commission or payout can be reconciled in these reports, because none of it is in the data. It is on the list of what we do not connect to for the same reason.
No virtual-brand switch. There is no brand entity in the platform at all: one organisation holds one storefront domain, one verified WhatsApp number and one catalog. A second brand is a second RestoMama organisation with its own login, and there is no reporting across the two, because every report is scoped to one organisation.
No day-part menu. A dish has an on-off state and an optional portion count, not an opening hour — the weekday and hour windows belong to daily deals, and a late menu that switches itself on at eleven is not a thing you can set here.
No abandoned-cart nudge on WhatsApp. The flag is stored and the conversation carries the timestamp, and nothing sends anything. It reads like a shipped feature in the settings and it is not one.
No production run. Sub-recipes are real and a base gravy does deduct through the dishes built on it, but nothing schedules a batch, books its output or reconciles it afterwards.
No rider roster of your own. Running delivery yourself means only that nothing is pushed to the RestoMama delivery platform; there is no driver app and no screen to assign your own boys from.

If one of those is the reason this will not work for your kitchen, say so on the form below.

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.

Book a demo Explore the platform

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