> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt
> Use this file to discover all available pages before exploring further.
# What syncs
> The complete reference table: which information travels between EatNow and NowOS, in which direction, when, and what the precedence rules are.
This page is the **exhaustive reference** for the integration. Use it to answer "does X come back?" and "why did my change disappear?".
***
## 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
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.
Status, covers, tables, internal note, guest, time. Including changes the guest makes themselves from their confirmation link.
A deposit or prepayment collected, a card imprint captured or released.
Automatic table assignment, automatic no-show at the end of service, automatic close-out.
A reservation deleted in EatNow is first pushed to the till as **cancelled**, so it disappears from the panel too.
### What each push contains
| Information | Detail |
| ------------------------ | ---------------------------------------------------------------------------- |
| **Status** | See the mapping table below. |
| **Party name** | The guest's name. Empty for an anonymous booking → the till shows *Walk-in*. |
| **Covers** | The number of people. |
| **Time** | Exact date and time, in your restaurant's timezone. |
| **Tables** | The assigned tables, up to 20, **if they are paired**. |
| **Internal note** | The *Internal info (private)* field, up to 500 characters. |
| **Guest profile** | See [The guest profile on the till](/nowos/guest-profile). |
| **Allergies & comments** | The reservation's *Allergies & comments* field, up to 500 characters. |
| **Prepayment** | Amount already collected, and its breakdown (deposit / prepayment). |
| **Card imprint** | Amount and state (active, released, charged). |
### Status mapping
| EatNow status | Becomes on the till |
| --------------------------------------------- | ------------------- |
| Pending / Pending payment | **Not sent** |
| Confirmed | Confirmed |
| Confirmed pend. payment | Confirmed |
| Manually confirmed | Confirmed |
| Double confirmed | Confirmed |
| Arrived | Arrived |
| Seated / Partially seated / Seated for drinks | Seated |
| Done | Finished |
| No-show | No-show |
| Cancelled by user | Cancelled |
| Cancelled by restaurant | Cancelled |
| Rejected | Cancelled |
**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.
| What happens on the floor | Effect in EatNow |
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A guest is seated** at a table | The reservation flips to **Seated**, with the tables and the sit-down time. A reservation ticket prints if you've set that up. |
| **A walk-in is seated** | A **Walk-in** reservation is created, already **Seated**, on the right tables. |
| **The bill grows** | The running total is recorded on the reservation (visible in the Floor plan view). |
| **A check is paid** | The amount paid is attached to the reservation and the customer. Any deposit consumed is identified separately. The card imprint is **released** automatically. |
| **A table is freed after payment** | The reservation flips to **Done**, with the leave time. The imprint is **released**. |
| **An order is voided after the meal started** | The reservation flips to **Done** (the guest did come). The imprint is left as-is: that call is yours. |
| **An order is voided before anything was fired** | The reservation goes **back to Confirmed**, its tables are freed, the link to the order is cut. The guest is still expected. |
| **A table is moved** | Nothing immediately: the new seating follows right away and updates the tables. |
| **The guest is marked arrived** | The reservation flips to **Arrived**. |
| **The guest is marked no-show** | The reservation flips to **No-show**, its tables are freed on the plan and the card imprint is **charged** automatically. |
| **The reservation is cancelled on the till** | The reservation flips to **Cancelled by restaurant** and its tables are freed on the plan. The order itself stays open on the till: the guest can stay and pay as a walk-in. |
| **A reservation's tables are changed** (before seating) | Tables are updated and marked **definitive**. |
| **Covers are corrected at the table** | The cover count is updated. |
| **The order's note is rewritten** | The reservation's **internal note** is updated. |
| **A seating requested by EatNow is refused** | The reservation is flagged as rejected by the till; the trace appears in the **History** tab. |
| **A new floor plan is published** | EatNow re-reads the plan and checks that your table pairings still point at existing tables. |
A gesture made on the till updates the **status** in EatNow, but **never** triggers your guest communications (email, WhatsApp) or refunds. To notify or refund a guest, make the gesture **from EatNow**.
The one exception is the **card imprint**, which is released or charged automatically — see [Deposits, prepayments and imprints](/nowos/payments).
***
## The precedence rules
Understanding these four rules explains 99% of the behaviour.
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.
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.
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.
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.
***
## What does not sync
For completeness, here's what deliberately stays on one side:
| Item | Where it lives |
| ------------------------------------------- | --------------------------------------------------- |
| The order's contents (items, prices) | NowOS only. EatNow only receives the totals. |
| Discounts, detailed tender breakdown | NowOS only. |
| The customer file (contact, tags, history) | EatNow only. The till displays it read-only. |
| Emails and WhatsApp messages sent to guests | EatNow only. |
| Card imprints (charge / release) | EatNow only. The till shows an informational badge. |
| Shifts, capacity, booking rules | EatNow only. |
| Menu, prices, kitchen | NowOS only. |