Tickets that fire in the right order
Starter goes when you tap 'send'. Main fires when you mark starter cleared. The chef gets a rhythm, not a flood.
Built for restaurants
Course-paced kitchen. Reservation-aware floor. English reports.
Tickets fire by course, not by tap order. Reservations show on the floor plan. Modifier groups handle 'no onion' without yelling across the pass.
Reservations on the floor plan, live
Table 6 is booked for 9pm. You see it on the floor view. No double-bookings, no awkward conversations.
Modifier groups that match real menus
Burger: well done, no onion, extra cheese. Builds the kitchen ticket exactly how the chef expects it.
Reports in English, receipts in Spanish
You read your weekly GP%, food cost, top sellers in English. The customer's receipt is fully Spanish, fully compliant.
Saturday lunch service
A typical restaurant workflow
- 1.Reservation arrival pings the floor view
- 2.Order taken on handheld at the table
- 3.Starters fire to kitchen immediately; mains held
- 4.Card split between two cards in 20 seconds
/kitchen
Kitchen ticket — Table 6
Starters · sent 19:42
Mains · holding
Dessert · queued
Compliance
Veri*Factu, sorted.
Every receipt goes through a tamper-evident audit trail. Default on. We've done the work so you don't have to.
Read the Veri*Factu guideMulti-language staff
A language per person, not per venue.
Staff pick EN, ES, DE, FR or NL at PIN login. The till speaks their language. Receipts stay in the customer's language. You read reports in yours.
FAQ
- Can we run multiple printers — bar vs kitchen?
- Yes — set destinations per product category. Cocktails to the bar printer, food to kitchen.
- Does it handle a tasting menu?
- Course-paced firing handles 7+ course menus cleanly. Each course goes when you mark the previous one cleared.
- What about allergens?
- Allergen notes attach to the product and show on the kitchen ticket. No screaming across the pass.