One guest record
The allergy captured at booking is the allergy on the pass; the occasion the concierge noted is the card the server sees. Nothing re-typed on the floor.
On the floor
The moment they sit, the floor knows.
RAYN already holds the guest — who they are, their allergy, the occasion, the pre-order. The instant a table is seated it hands the right slice of that to the right person on the floor, and runs a live allergy-safety check underneath. Intelligence on your floor — not another tap-pad, and never your POS.
Just seatedTable 12
Amira Returning, VIP
Severe allergy
Sesame — anaphylaxis, carries an EpiPen.
Occasion
Anniversary Surprise dessert after the main.
Pre-ordered
2× Tasting menu
01
LiveThe seated card
The moment they sit, the floor knows.
As a table moves to seated, the guest’s card opens for the team — who they are, the occasion, any allergy with its severity, and the pre-order. It is role-trimmed: the host sees everything, the server the guest and the table, the kitchen only the allergy, pre-order and dietary notes.
- Opens on seatThe instant the table is seated the card appears in the host station — nothing to search for, nothing re-typed.
- Role-aware by designHost, server and kitchen each see only what their job needs. VIP is a computed score from the guest record — never a badge someone sets.
- Built on what RAYN already holdsIt reads the one guest record and the same pre-order prep sheet the kitchen works from — the allergy at booking is the allergy on the pass.
Just seatedTable 12
Amira Returning, VIP
Severe allergy
Sesame — anaphylaxis, carries an EpiPen.
Occasion
Anniversary Surprise dessert after the main.
Pre-ordered
2× Tasting menu
02
LiveAllergy safety
Safe by default — and it proves it.
Every declared allergy reaches the floor with its severity, and RAYN checks it against the pre-order now — and against what is actually ordered on the check the moment your POS is connected. A conflict is not just flagged: it runs a loop that ends in a sign-off you can audit.
- A loop, not just an alertFlag → a named acknowledgement (who signed off which dish) → an outcome: confirmed and told the kitchen, or not-applicable, with a reason.
- It re-alerts on the next dishAcknowledgement is item-scoped — a new conflicting dish ordered later raises a fresh flag, so a sign-off can’t go stale.
- Managers close the loopA false positive is suppressed for one dish-and-allergen by a manager — never silenced automatically — and any conflict left unacknowledged becomes the headline on the owner’s daily brief.
ConflictWagyu sliders contain sesame — guest flagged a severe sesame allergy.
- 1FlaggedOn the card, above everything else.
- 2AcknowledgedYusuf signed off — “told the kitchen”.
- 3OutcomeConfirmed · item-scoped, re-alerts on the next dish.
- 4Owner briefAnything left unacknowledged leads the daily brief.
A manager can suppress a false positive for one dish — never automatic.
03
LiveTable notes
The note that stays with the table.
A server jots a note from their phone — “holding the dessert until the main is cleared” — and it stays with that table for the night, timestamped and attributed. The kitchen sees only the dietary ones.
- In the moment, from the floorOne line, from the paired phone, without leaving the table — the floor’s shared memory for the night.
- Attributed and timestampedEvery note carries who wrote it and when; the card shows the latest under “Tonight”.
- Private to the venueAppend-only, venue-scoped, and erased when a guest asks for their data to be removed.
Table 12 · tonight
Hold the dessert until the main is cleared.
Yusuf · 20:44Prefers still water, no ice.
Lena · 20:31No sesame — severe. Kitchen aware.
Amir · 20:22 · dietary
Add a note for this table…Add
04
On with your POSSpend so far
Spend so far, at a glance.
Once your POS data is connected, each seated table shows spend-so-far on the floor view, and the allergy check widens from the pre-order to what has actually been ordered. RAYN reads the check — it never writes to your till.
- Reads, never writesRAYN sits on your POS; it does not re-price, re-order or replace it. Read-first, by design.
- Switches on with your POSThe moment your POS data is connected or imported, spend and ordered-vs-allergy light up — no rebuild, no new screen.
- One guest, one numberSpend joins the same guest record the concierge and host station already read, so the night adds up in one place.
Spend so far · Table 12from your POS
AED 320 · 2 items
- Pistachio parfaitAED 60
- Champagne, by the glassAED 110
Checked vs allergyNo conflict on what’s ordered
05
LiveThe staff console
On their phone. No app, no login.
Each server opens the floor from a single paired link — no app install, no password — and the pairing is revocable. The card is live in the browser today; when you switch on push, the seat alert reaches the phone too.
- A revocable paired linkPair a server’s device with one link; unpair it in a tap when the shift or the season ends.
- Nothing to installThe floor opens at /staff in any phone browser — no app store, no account, no shared password.
- Push when you want itWhen push is onThe in-app card is live now; phone push turns on once configured, and the alert it sends carries no guest detail.
Yusuf · Garden terrace
- T12 · AmiraSevere sesame · seated 20:15
- T9 · Walk-inParty of 2 · seated 20:22
- T14 · NadiaAnniversary · seated 20:31
Paired device · revoke anytime
One system underneath
It reads what RAYN already knows.
On your POS, not instead of it
RAYN reads the check to show spend and catch a conflict. It never re-prices, re-orders or replaces your till. Splitting and settling the bill live in Pay at Table.
Honest about what’s on
The card, the allergy loop, notes and the paired console are live now. Spend and live ordered-vs-allergy switch on with your POS; phone push when you configure it. Routing to a server needs your floor sections mapped.
Questions
On the floor, answered.
Is this live at venues today?
The seated card, the allergy-safety loop against the pre-order, table notes and the paired staff console are built and shipping. Spend-so-far and checking against what has actually been ordered switch on when your POS data is connected, and routing a card to the right server needs your floor sections mapped first.
Do we need our POS connected?
Only for spend-so-far and for checking a guest’s allergy against what has actually been ordered on the check. Everything else — the seated card, the allergy check against the pre-order, and table notes — works without it.
Does RAYN send orders to our POS?
No. It is read-first: it reads the check to show spend and catch conflicts, and it never writes to, re-prices or replaces your till.
Does the team need to install an app?
No. A paired link opens the floor in any phone browser, and the pairing is revocable per server. No app store, no password.
Is a guest’s data safe on a server’s phone?
The card is role-trimmed so each person sees only what their job needs, push alerts carry no guest detail, notes are venue-scoped, and everything is erased on a data request.
See it on your floor
Put the guest in your team’s hand.
A short walkthrough — we seat a table and show the card, the allergy loop and the note land where your team is standing.