Restaurant OS

The regulars you think you have, measured

Most restaurants know their regulars by face and nothing else. A customer record built automatically from orders turns that instinct into something you can actually act on — who has stopped coming, who spends the most, what they order.

The record builds itself

A phone number given at ordering ties the visit to a customer. Order history, frequency and spend accumulate without anyone maintaining a list.

  • Customer history tied to the number they order with
  • Visit frequency and spend per customer
  • What each customer actually orders
  • Analytics across the whole base, not just today's till

Why this beats a loyalty card

A punch card measures nothing and is forgotten at home. An order-derived record works whether or not the customer opts into anything, and tells you the thing that actually matters: who used to come weekly and has not been in for a month.

Reaching them

TableOS pairs with WAVE, Kriyava's WhatsApp platform, for order alerts and customer messaging. Sending offers to people who did not ask for them is how a number gets blocked, so treat the list as something to use sparingly.

Common questions

Is customer data mine?
Yes. It is your customer list, exportable, with no fee for taking it with you.
Do guests have to give a phone number?
It is what ties a visit to a record. An order without one still works — it just does not build history.

Built for

The rest of the system

Put this in your restaurant this week.

₹999 a month. No setup fee, no per-terminal licence, no annual contract.