HannaAI

A till that starts before they arrive.

Hanna POS is a restaurant point of sale that runs the whole guest journey rather than the transaction at the end of it. It begins with the briefing before service and doesn't finish when the card clears — because everything the guest does on the way through is worth keeping.

iPad, kitchen screen and staff phone Card payment reconciled to the till One close, one set of numbers

One service · six steps

Before service, the room is briefed in seconds.

Not a printout somebody skims. What matters tonight, written for the people working it.

Tonight · Friday · 96 covers booked

Busy from 19:00 — four tables land within ten minutes, so stagger the water and bread.

Table 12 is a coeliac and a wheelchair. Step-free route, gluten-free omakase, tamari not soy. Fourth visit — they had the Junmai last time.

Table 6 is an anniversary. Table 4 is a first visit from a review.

Two shortages: mackerel off after 20 covers, oysters are 86 already.

Allergies flagged tonight3
Returning guests with history on file11
Occasions anniversary, birthday2
Read on a phone, in the thirty seconds before doors

Replaces: a printout and a shouted handover

They arrive, and the floor is already ahead.

Check in with a tap. Walk-ins seated against real capacity, not a guess.

2
4
6
8
10
12
14
16
C1
C2
C3
C4

Table 12 · 4 covers · seated 19:02

Booked Tuesday · card held · step-free

Coeliac — gluten4th visitUsually omakaseJunmai

Table 14 is showing red — fifteen minutes past its booking and unconfirmed. One tap releases it to the waitlist, or holds it another ten.

Replaces: a paper book and a highlighter

The order can't get the allergy wrong.

Every item is checked against the guest record as it's rung in. Blocked at the till, not caught in the kitchen.

Table 12 · ordering

Omakase, 8 course£68.00 · GF route
Negima ×4£11.00 each
Tempura moriawaseBlocked · gluten
Grilled shiitake£9.50 · suggested swap
Junmai 720ml£68.00
Ponzu dressingBlocked · contains soy
Items checked against the recordEvery one
Blocked, with a swap offered2
Course timing set by the floor, held by the kitchen4 courses
The till knew before the kitchen did

Replaces: shouting the allergy down the pass

The kitchen sees it the moment it's sent.

No printer, no runner, no paper spike. Course by course, with the allergy on every ticket.

Table 12 · 4 covers19:14
1 × Omakase · GFCoeliac
4 × NegimaGrill
1 × Grilled shiitakeGF swap
1 × Junmai 720mlBar
Course 1 of 4Sent · 0:12 ago
Grill, bar and pass each see only their own items3 stations
86 an item from the kitchen screenInstant
Gone off the menu everywhere till, QR, booking chatInstant

86 the mackerel on the kitchen screen and it disappears from the till, the table QR menu and Hanna's answers to guests — in the same second.

Replaces: a spike of tickets and a bell

Split, paid and reconciled — at the table.

By item or by share, on the terminal, matched to the till without anybody keying a number.

Card 1 · settled£178.20Omakase ×2, Junmai, service
Card 2 · settled£134.40Omakase ×2, sides, service
Bill total including 12.5% service£312.60
Reconciled against the terminal automaticallyMatched
Session closed table freed, waitlist notified21:52
Time from tap to closed14 seconds
Nothing to key in, nothing to reconcile later

Replaces: a calculator and a split-bill argument

And what's left behind is the valuable part.

Every table writes back to the guest, the stock, the books and the forecast. That is what a till should be for.

£312.60Spend, on the guest record
11Stock movements, through recipes
£87.42What it cost to serve
Guest record 4th visit, £612 lifetime, coeliac carried forwardUpdated
Stock ingredients off the shelf, at costMoved
The books takings, tender, service, marginPosted
Next week's forecast covers, mix, spend per headFed

A conventional till would have recorded £312.60 and forgotten the rest. Everything above happened because one system held the booking, the guest, the menu and the money at the same time.

Replaces: typing yesterday into a spreadsheet

The basics

Every till does these. We're not going to pretend otherwise.

Seating, orders, floor, menu, billing. If a point of sale can't do all five properly it isn't a point of sale, and no amount of intelligence on top will rescue it. Hanna does them properly and quietly.

✓ 01

Seating

Floor plan, table states, combining and splitting, turn times, walk-ins against real capacity.

✓ 02

Orders

Coursing, modifiers, seat numbers, transfers between tables, voids with a reason and a name.

✓ 03

Floor

Sections, staff assignment, sales by server, handovers between shifts, live covers and pacing.

✓ 04

Menu

Categories, prices, availability, timed menus, set menus and experiences, 86 in one tap.

✓ 05

Billing

Split by item or share, discounts with a reason, service charge, cash and card, refunds, receipts.

So the question isn't whether a till can take an order. It's what happens to everything else that occurs at that table — the allergy, the occasion, the pace, the preference, the cost of what was served, and whether they come back. That's the part almost every system throws away.

The difference

It starts with a person and ends with a number. Everything between is kept.

A table generates far more than a total. Hanna's till writes all of it into one record, and that record is what makes every other part of the platform work.

What a single table produces

Who they areName, visit number, lifetime spend, party
What they can't eatAllergies and preferences, carried forward
What they orderedEvery item, course, modifier and swap
What it cost youIngredients off the shelf, priced by recipe
How it wentSeated, coursed, paid — with timings
What was saidRequests, occasions, the things worth remembering
Hanna One record. One definition of every figure. Nothing reconciled, because nothing was ever separate.

What it becomes

Business InsightCovers, spend per head, mix, which nights carry you
Menu & InventoryStock moved, cost of goods, what to order next week
FinanceTakings, tender, margin — the day closed and reconciled
MarketingWho returns, who lapsed, who to write to and when
The next bookingThey ask for a table and Hanna already knows them

On the floor

Four screens, one system.

Not four products with an integration between them. The same record, shown differently to the people who need it.

01 · iPad

The till

The main screen. Floor plan, orders, bills and payment. Designed for a wet thumb in a dark room, not a mouse.

02 · Kitchen screen

The pass

Tickets by station, course timing, allergies in red, 86 an item and it's gone everywhere at once.

03 · Phone

The staff app

Take an order at the table, check a guest, read tonight's briefing, clock in and out. In a pocket, not on a stand.

04 · Guest phone

Order at the table

A QR code opens your live menu with the same prices and allergens. Orders land on the same kitchen screen.

In detail

The things you only notice when they're missing.

All included. There is no service-charge module and no payments upgrade.

Payment at the table

Card terminals talk to the till directly, so the amount is never typed twice and the takings reconcile themselves at close.

Allergy enforcement

Items containing a flagged allergen are blocked at the point of ordering, with a swap suggested from your own menu.

Combining tables

Push two tables together for a party of six and the system treats it as one session — one bill, one record, no maths.

Service charge, handled

Set the rate, apply or remove it with a reason and a name against it, and see exactly what was collected at close.

Voids and discounts, on the record

Every one carries a reason and the staff member who authorised it. Not to catch people out — so the numbers mean something.

Live dashboard

Covers, spend per head and takings as they happen, on any screen, without leaving the floor.

Shift handover

Sections reassign cleanly between services, and sales by server survive the change.

Clock in and out

Staff clock in on the same system that records what they sold — so hours and takings sit in one place.

One close

Z-report, tender breakdown, service charge and staff hours in a single action at the end of the night.

In service

Running services tonight, in three London rooms.

A yakitori counter, a Chinese barbecue and a cocktail bar — three very different services on the same till. Each name here will take your call.

Hotori Yakitori & Edomae sushi · London EC4ALive since 2024
Charcoal Champ Chinese barbecue · London N1Live since 2026
Brass Bar Cocktail bar · LondonLive since 2026

Before you ask

The questions operators actually ask.

What happens if the internet drops mid-service?

Orders and payments keep working. The iPad holds the session locally and syncs when the connection returns, and the card terminals have their own path to the acquirer. What you lose temporarily is the live dashboard and anything that needs the cloud — not the ability to take money.

Do I have to buy your hardware?

No. It runs on standard iPads and any modern screen for the kitchen. Card payment runs on Dojo terminals, which most venues already have or can get quickly. There is no proprietary box, no five-year hardware lease, and nothing that stops working if you leave.

How long does the team take to learn it?

A shift. The floor layout is deliberately conventional because service is not the place for novelty — the difference is in what the system knows, not in where the buttons are. Managers take longer, mostly on menu and reporting.

Can it handle a bar as well as a restaurant?

Yes, and one of the three live venues is a cocktail bar. Fast tabs, no bookings, split payments and open sessions behave differently from a booked dining room, and both are configuration rather than a different product.

What about my existing menu and staff?

The menu can be imported from a PDF or photographed, then checked by us with you before you go live. Staff are set up with a role and a four-digit PIN, which takes minutes.

Book a demo

Put your hands on it.

We'll run a real service on it with you — your menu, your floor plan, your awkward table — and be straight about what it doesn't yet do.

Book a demo