Turn more tables.
The contactless QR dining platform built for the rhythm of a real restaurant floor — from the first scan to the last split-bill.
Walkouts during the rush.
Guests who scanned a menu and a 12-minute wait still got their drink order taken by hand. Half left.
Tickets lost between stations.
The same item printed in two places, or in none. Someone heard medium-rare. Someone heard medium. Both are wrong.
Twenty minutes for the check.
Eight covers, one card, three splits, two zeroed-out tips. The table sat for half an hour longer than it should have.
The arc of one table
Four moments. Zero friction.
The guest sits, opens the camera, and they're in your menu.
Each table has a unique QR — no app to install, no wait.
They build a cart with photos, modifiers, and dietary tags.
Carts survive refreshes. Nested modifiers, allergens, instructions — all there.
The kitchen sees only what their station owns.
Grill gets grill. Pantry gets pantry. Tickets age green → yellow → red.
Bill splits clean. Money lands in your account.
Apple Pay, Google Pay, evenly, by item. Stripe routes it directly to you.
What's inside
One platform.
Six moving parts of your restaurant.
Front of house
A menu your guests can move through faster than a server can pour water.
Every table gets a unique QR. Scan, browse, build the cart — no app to install, no wait, no menu hand-off. Lazy-loaded photography and nested modifiers keep it crisp on every phone.
- Under 150kB initial payload — instant on bad LTE
- Nested modifiers with force-multipliers and add-ons
- Carts persist through accidental refreshes
Back of house
A kitchen display that thinks in stations, not orders.
One order, atomically routed to grill, pantry, bar, fry — only the items that station owns. Tickets age green → yellow → red so nothing dies under the heat lamps.
- Per-station ticket streams over WebSockets
- SLA color states at 10 and 15 minutes
- Consolidation view: 'Total active beef patties: 14'
- 2× branzino
- 1× toast
- 1× steak mr
- 4× burger ms
- side fries
On the floor
A staff PWA that vibrates when food is up.
Servers know the moment a ticket is bumped, the moment a guest hits 'Call Waiter,' and the moment a table requests the check. POS-fallback built in for the guests who hand you their phone.
- Push notifications via WebSockets + service workers
- Manual order entry & cart edit override
- Reset table state from your phone
The check
Bill splitting that won't strand the table at the end.
Two paths: split evenly across N people, or let each guest claim line items in real time. Paid items update across every device at the table — no double-charges, no awkward math.
- Stripe Connect — money lands in the restaurant's account
- Apple Pay and Google Pay native sheets
- Partial-payment ledger until the invoice clears
Inventory
86'd means 86'd everywhere. Instantly.
Out of avocado? Tap once. Every active phone at the restaurant freezes the avocado addition and renders 'Sold Out' without a reload. Day-parting hides the breakfast menu at 11:00 sharp, with a grace window for carts already in motion.
- Instant WebSocket-driven UI mutations
- Atomic stock counters with row-level locking
- Day-parted categories with configurable grace
Owner dashboard
The floor, rendered in real time.
Every table is a colored node — empty, scanning, drafting, ordered, served, dirty. Tap any node to see what's happening, who placed what, and where the bottleneck is.
- Six table states pulled from real events
- Historical reporting: turn times, prep latency, peak windows
- CSV / XLSX / PDF exports — offloaded to background workers
Built by people who lived through the rush
“If your software can't handle the pass on a Saturday at 8 PM, it can't handle your restaurant. We built TurnFloor for the moments when covers, turns, and tempers are all on the line.”
Founding restaurants
Lifetime pricing. Locked the day you sign.
The first cohort of restaurants on TurnFloor gets a price that never goes up — for as long as you keep the lights on. We'd rather build with operators who'll tell us the truth than chase short-term margin.
- Lifetime locked pricing
- Direct line to the team building it
- Menu & QR setup on us
- Stripe Connect onboarding hands-on
- Your feedback shapes the roadmap
Questions we hear at the bar
The honest answers.
No. Guests use their own phones. Your kitchen runs on any 10-inch tablet. Servers install a PWA on their existing phones. The only physical thing you need to print is the table QRs.
Carts persist locally on each guest's browser, so a dropped connection doesn't lose an order. The kitchen display caches active tickets. We reconnect automatically when service comes back.
You do. TurnFloor uses Stripe Connect to route every charge directly into your restaurant's bank account. We extract our platform fee per transaction. You never wait for a payout from us.
Yes. TurnFloor runs alongside an existing POS during your transition, then replaces the parts that hurt: ordering, kitchen routing, and bill splitting. We help you migrate menus on day one.
Yes. Multi-tenant isolation is enforced at the database layer. Each location has its own menu, staff roster, station map, and reporting — rolled up under a single owner login.
You do. Menus, orders, guest emails, sales reports — all yours, exportable any time as CSV, XLSX, or PDF.
Be on the floor when we launch.
We're onboarding a small cohort of founding restaurants. Get on the list — we'll be in touch before anyone else.