Four screens, one cook
WhatsApp on a phone, website orders in an inbox, table 6 waving, a regular on the landline. The counter retypes each one into the POS and the kitchen cooks in whatever order someone remembered.
WhatsApp, website, table QR and pickup QR orders land on the same screen with a sound. Accept, print the KOT, assign a rider and mark it ready. The guest is told on WhatsApp at every step, and nobody copies a chat into the POS.
Last updated
The live order board is the screen a restaurant runs service from. Every paid order from the website, WhatsApp, table QR and pickup QR lands on it with a beep. Staff accept it, the KOT prints in Petpooja or Positeasy, a rider is assigned from the same ticket and the guest is updated on WhatsApp at every step.
WhatsApp on a phone, website orders in an inbox, table 6 waving, a regular on the landline. The counter retypes each one into the POS and the kitchen cooks in whatever order someone remembered.
A paid order sits unaccepted while the phone is in a pocket. No sound, no flag, and the guest finds out when they call to ask.
Every status question means finding the chat, checking the kitchen and typing a reply, in the middle of the rush, while the next three tickets wait.
One board, every channel, and the guest is told without anyone typing. See a WhatsApp order from Hi to KOT →
The board moves the ticket. WhatsApp tells the guest. Nobody types a status.
A paid order lands from WhatsApp, the website, a table QR or a pickup QR. Unpaid payment links expire, so a ghost ticket never reaches the kitchen.
Staff accept the ticket, or online-paid orders auto-accept in the rush while cash on delivery waits for a tap. With Petpooja or Positeasy connected, the KOT prints now and the guest's chat says preparing.
Mark it ready. Pickup guests get a “Ready for pickup” message and an OTP for the counter. Dine-in tickets carry the table number, so the runner knows where it goes.
Assign your own rider, who runs the drop on the Owncart Rider app, or create an Adloggs, Shadowfax or Porter task without leaving the board. The guest gets “out for delivery”.
OTP confirms the handover and the ticket closes with its GST invoice PDF attached. Pickup orders close automatically a set time after they are ready.
Website, WhatsApp, table QR, pickup QR and staff-created orders land on the same screen and sound the same alert. With more than one outlet, each ticket carries its prefix, such as CHN- or TRY-.
Received → Accepted → Ready → Dispatched → Delivered. Cancel requests auto-approve before you accept and are refused once cooking starts; wrong-item claims need a photo.
Find tickets by status, payment, order type, pre-booking and date. Pull up tonight's cash orders or Sunday's pre-booked thalis in one view.
A regular calls instead of tapping? Staff create the order on the board. For dine-in, attach the table so the KOT and the runner know where it goes.
Stuck orders and payment errors are flagged on the board, so a ticket never sits forgotten behind the rush.
Print or share the invoice from the ticket. Restaurants without a POS run service on the board and the GST PDF alone.
The board is the back half of every WhatsApp order. This 16-second reel is the front half.
The kitchen hears the board beep for both. The cook doesn't care which channel it came from; the KOT prints the same way.
Kitchen hears the board beep as a WhatsApp biryani lands beside a table-QR dosa
Priya sees Received → Accepted → Ready on the same ticket she just paid
Online-paid pickup orders auto-accept, so the counter stays on the coffee machine. Cash orders wait for a tap. Ready orders close automatically a set time after they're done.
Pickup QR · CHN-1844 · auto-accepted · OTP at counter
“Ready for pickup — show OTP 4821 at the counter”
Mark the next ticket ready and create a Shadowfax or Adloggs task from the same ticket. Status flows back to the board and on to the guest.
Website · CHN-1845 · Shadowfax task created · Dispatched
“Out for delivery — share OTP 7731 with the rider”

Paid board tickets are created in the POS and the KOT prints; status comes back to the guest.
Two-way sync: orders in, KOT printed, status out to WhatsApp.
Hire riders on demand; the delivery task is created from the ticket.
Create a partner task from the board for rain and rush; status flows back.
Every state change becomes the status message the guest is already waiting for.
UPI and cards on every channel; unpaid links expire before they reach the board.
No. The board is part of Owncart, on the same Restaurant plan as WhatsApp ordering, table QR and the ordering website: ₹10,000 per outlet per year with 0% commission. Orders from every channel, including phone orders your staff create, land on it.
Yes. Restaurants without a POS take orders on the board, print or share the GST invoice PDF and manage menu availability in Owncart. With Petpooja or Positeasy connected, the same ticket also prints as a KOT. See POS and KOT sync.
No. Online-paid orders can auto-accept during the rush. Cash-on-delivery orders wait for a tap, so you decide before the kitchen starts. See payments.
WhatsApp updates at each step: order confirmation, preparing, ready for pickup or out for delivery, and delivered. With a POS connected, the updates follow the POS status, so nobody types a reply.
Assign your own rider from the ticket; they run the drop on the Owncart Rider app and the guest gets an ETA. Or create an Adloggs, Shadowfax or Porter task from the same ticket. See delivery and pickup.
Before you accept, the cancellation is auto-approved and an online payment is refunded automatically. Once cooking starts, cancel is refused. Wrong-item claims need a photo. See returns and cancellations.
Yes. Add staff as Teammates: they run the board and the KOT but cannot refund. Admins keep refunds, POS keys and the domain. See staff and roles.
Start free with a photo of your menu, or book a 15-minute demo and we'll walk through the board with your team.