One login on a sticky note
The owner's password is taped under the counter. Whoever is on shift can refund, change prices and open payment settings, and nobody can say afterwards who did what.
Two roles, Admin and Teammate, with access per outlet. Counter staff see live orders and dispatch, the kitchen gets its KOT, your riders get the Rider app, and refunds, payments and POS keys stay with the owner. A counter login can't empty the till.
Last updated
Owncart has two login roles. Teammates run service: live orders, accepting tickets, the KOT and dispatch. Admins hold the money and the settings: refunds, payments, POS keys, the domain and bulk uploads. Access is granted per outlet, and API keys and webhooks let your other systems read orders. Guests never see roles; tickets still move.
The owner's password is taped under the counter. Whoever is on shift can refund, change prices and open payment settings, and nobody can say afterwards who did what.
A guest insists at 10:40 pm. The counter has the full login, so ₹2,000 goes back without a question, and the owner finds out the next morning.
The kitchen needs the ticket, the floor needs the board, the rider needs the address and the owner needs the money. Today they all get the same everything, or they get nothing.
Two roles, one rule: the floor runs the board, the money stays with Admin. See the live order board →
The owner's login is the Admin. It holds payments, refunds, POS keys, the domain and bulk uploads.
Counter and floor staff get Teammate logins. They see live orders and dispatch, accept tickets, print the KOT and create phone orders. They cannot refund.
Refunds are for managers only. The manager you trust with money gets an Admin login; everyone else stays a Teammate.
Each outlet keeps its own hours, POS, payments, delivery and order prefix such as CHN- or TRY-. Access is granted per outlet, and the owner sees every branch from one login.
Create API keys and webhooks so accounting or another POS can read orders and receive order, delivery, cancel and return events.
A prepaid order cancelled before cooking is refunded automatically, so most refunds never need a login at all. See cancellation and refund rules.
Payments, refunds, POS keys, the domain and bulk uploads. The only login that can move money or change how you get paid.
Refunds are for managers only. The manager who handles them gets an Admin login; a Teammate login never sees the refund button.
See live orders and dispatch, accept tickets, create a phone order and attach a table. No refunds, no payment settings.
Cooks don't need the dashboard. The KOT prints in Petpooja or Positeasy, with the table number on dine-in orders, as soon as a paid ticket is accepted.
Your own riders are assigned from the ticket and run each drop on the Owncart Rider app. The guest shares an OTP at the door.
Order, delivery, cancel, return, abandoned-cart and restaurant-closed events, plus cart, customer and order APIs, for the systems you already run.
The evening shift logs in as a Teammate. Nothing about service gets slower; only the money is out of reach.
The shift is logged in as a Teammate. They accepted the order, printed the KOT and assigned the rider. The refund request waits for the owner's Admin login, so the counter never has to say yes under pressure.
Teammate runs the board; only Admin refunds · CHN-2041 · refund · Admin only
Guest never sees roles — tickets still move
Access is per outlet. Each branch keeps its own hours, POS, payments, delivery and order prefix, and the owner sees all of them from one Admin login.
Chennai · CHN-2042 · Trichy · TRY-0913 · one Admin view
Sees the nearest outlet and its menu; no sign of roles
An API key and a webhook send order, delivery, cancel and return events to the software you already run. Nobody exports a spreadsheet at midnight.
API keys for the other stack · webhook sent on every new order
Nothing changes for the guest: Hi, menu, pay, KOT

POS keys stay with Admin; the kitchen gets its KOT without a dashboard login.
Two-way sync with the POS keys held by Admin; Teammates only run the board.
Payment settings and manual refunds are Admin only; automatic refunds need nobody.
Teammates book on-demand riders from the ticket when the board is full.
Guests get the same status messages whoever moved the ticket.
Two: Admin and Teammate. Teammates see live orders and dispatch, accept tickets, print the KOT and create phone orders. Admins hold refunds, payments, POS keys, the domain and bulk uploads. Access is granted per outlet.
No. A Teammate login cannot refund. A prepaid order cancelled before cooking is refunded automatically; anything manual needs an Admin login, which is why refunds are for managers and owners only. See cancellations and refunds.
Not to cook. The KOT prints in Petpooja or Positeasy, with the table number on dine-in orders, as soon as a paid ticket is accepted. Give logins to the people who run the board. See POS and KOT sync.
Assign a rider from the ticket on the live order board. They run the drop on the Owncart Rider app, the guest gets an ETA and shares an OTP at the door. Adloggs, Shadowfax or Porter can be booked from the same ticket. See delivery and pickup.
Yes. Access is per outlet. Each outlet keeps its own hours with force open or close, menu availability, POS connection, payments, delivery settings and order ID prefix such as CHN- or TRY-, all managed from one Admin. See multi-outlet restaurants.
Webhooks send order, delivery, cancel, return, abandoned-cart and restaurant-closed events to your other systems, and there are cart, customer and order APIs. Any other POS can connect the same way. See all integrations.
No. It is a feature area inside Owncart, on the same Restaurant plan as WhatsApp ordering and the live order board: ₹10,000 per outlet per year, 0% commission.
Start free with a photo of your menu, or book a 15-minute demo and we'll walk through Admin and Teammate access with your team.