Perko
Platform

Counter, Orders & Kitchen

One live flow.

Counter, table QR, and pickup share one flow — from payment to the right station and final handoff.

Discuss your workflow
Orders · Live service Venue overview
Active orders 3 open
#1042
PreparingTable 7 · 5 items
04:18
#1045
NewTakeaway · 3 items
01:06
#1039
ReadyPickup · 12:30
Example order and kitchen flow

The handoff problem

The order is clear — until it leaves the counter. Verbal changes, paper tickets, and separate screens leave three questions: Is it paid? Who owns it? Is it ready?

The operating loop

One connected order flow

One source record follows the work. Each step keeps its context.

  1. 01 Order Counter, table QR, or pickup
  2. 02 Confirm Exact price and payment evidence
  3. 03 Route Each line to its station
  4. 04 Prepare Kitchen owns preparation
  5. 05 Ready Front sees the same status
  6. 06 Handoff One completed order record

No re-entry between steps. Corrections keep the original evidence.

Order where the customer is

Counter
A fast entry screen for staff. Full menu, table identity, modifiers, and tenders on one surface.
Table QR
Every table gets a venue‑branded page. Table identity travels with the order — no table number re‑entry at the counter.
Pickup
Guests order ahead. The counter sees arrival time and hands off when ready.

Payment

Exact price evidence
Every line, modifier, and tender is priced and recorded before the order leaves the counter.
Tender support
Cash, card, contactless, and country‑gated terminal adapters. Tender evidence survives shift and close.
No split‑brain totals
The counter total is the system total. No reconciliation between the POS, the kitchen, and the shift report.

Kitchen routing and stations

Station routing
Each order line routes to its correct station: hot line, cold prep, bar, or pastry. No verbal handoff.
Live tickets
A shared, synced ticket queue that every station sees. New, preparing, and ready states update in real time.
Multi‑station orders
One order can span three stations. Each station sees only its lines. The front counter sees the whole order.

Exceptions that don't get lost

Modifiers and notes
One without mustard, oat milk, extra hot — captured once, visible everywhere.
Void and refund
A reversed line creates a documented void, not a missing ticket. Refunds reference the original tender.
Allergens
Flagged on the recipe, surfaced at order entry, and printed on the kitchen ticket.

A clear boundary

Scope

Included

Counter order entry, table QR ordering, payment evidence, station routing, kitchen ticket queue, preparation states, and exception handling at one test venue.

Not claimed in this scope

Third‑party delivery provider integration, native mobile apps, and multi‑location counter orchestration.

Bring your venue onto Perko.

Tell us about your business and we will get back to you.

Join Perko