From EatNow to NowOS
EatNow sends a reservation to the till as soon as it is confirmed, then on every change. Sending is automatic and immediate.When a push happens
On creation
On creation
Reservation taken on the portal, by phone, by the WhatsApp AI agent, by a prescriber, through Reserve with Google, or typed in by your team.
On every change
On every change
Status, covers, tables, internal note, guest, time. Including changes the guest makes themselves from their confirmation link.
On money movements
On money movements
A deposit or prepayment collected, a card imprint captured or released.
On automatic gestures
On automatic gestures
Automatic table assignment, automatic no-show at the end of service, automatic close-out.
Before a deletion
Before a deletion
A reservation deleted in EatNow is first pushed to the till as cancelled, so it disappears from the panel too.
What each push contains
Status mapping
Pending reservations are never sent to the till. That’s deliberate: until a request is accepted, it shouldn’t clutter the floor plan or hold a table hostage for the floor.
From NowOS to EatNow
The till tells EatNow about everything happening on the floor. Every message is cryptographically verified (thanks to the signing secret) and processed exactly once, even if it’s redelivered.The precedence rules
Understanding these four rules explains 99% of the behaviour.1. The latest gesture wins
1. The latest gesture wins
On shared fields (covers, internal note, tables, status), the most recent change wins, regardless of which system it was made in. There is no “priority side”: there is a chronological order.
2. EatNow stays the book of record for bookings
2. EatNow stays the book of record for bookings
When the floor changes covers, tables or the note on the till, EatNow applies the change then sends it back to the till for confirmation. That’s what guarantees the two systems never drift apart, even on fields both sides can edit.It also explains a behaviour that can surprise: if EatNow refuses a change (see rule 3), the till visibly reverts to EatNow’s value. That’s not a bug — that’s the refusal showing.
3. A closed reservation can no longer be changed
3. A closed reservation can no longer be changed
A Done, No-show, Cancelled or Rejected reservation is frozen. A late event from the till (a bill that lingered, a redelivered message) can no longer resurrect or modify it.If the floor corrects covers or the note on an already-closed reservation, EatNow refuses and the till reverts to EatNow’s value.
4. An unpaired table blocks the gesture — entirely
4. An unpaired table blocks the gesture — entirely
If the floor assigns three tables to a reservation and just one of the three isn’t paired in EatNow, the change is refused as a whole. EatNow never seats a party on “the tables it happened to recognise”: that would silently contradict the floor.