Orders stay in this browser. Not uploaded.
What is Restaurant Orders, POS & KOT?
Dine-in, takeaway and delivery carts with tax/service, cash or partial payment, dues, void, kitchen tickets and thermal/A4 receipts. Place the order once (idempotent). KOT moves pending → preparing → ready → served; additions get a new batch, not a silent duplicate. Checkout does not wait on dish stock by default. Printing is browser print/PDF to 58/80 mm — no fake printer API. This is one browser profile, not a real-time kitchen display network.
Key features
- Dine-in / takeaway / delivery with table or type
- Idempotent place-order
- KOT batches with status flow
- Partial payment, dues, void
- Thermal or A4 receipt and KOT layouts
Popular uses
- Run a small dining room from one phone or tablet
- Pass a kitchen ticket without claiming Wi-Fi KDS sync
- Collect a remaining due after the guest leaves
Supported formats
Browser print / PDF 58 mm or 80 mm. No native printer driver.
Troubleshooting
- Kitchen did not update on another phone Expected — there is no live multi-device sync in this release.
Also known as: Restaurant POS, Kitchen order ticket, Dine-in billing.
How it works
- Tap menu items into a cart, set table/type, place the order once (idempotent).
- Advance kitchen tickets: pending → preparing → ready → served; additions get a new KOT batch.
- Collect dues, void orders, print receipt or KOT. No silent upload.
FAQ
Does checkout block on dish stock?
No by default — dishes are not finite prepared stock unless you mark them unavailable. Optional ingredient tracking is separate.
Can KOT duplicate on retry?
No. Each KOT batch uses a client operation id.
Native printer drivers?
Browser print / PDF to 58mm or 80mm layouts. No fake printer APIs.