> ## 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.

# The guest profile on the till

> Everything EatNow knows about your guests shows on the till the moment they're seated: VIP, allergies, visit history, average spend. Here's what travels and how to feed it.

This is the most visible benefit of the integration for your floor team: when seating a guest, the server sees **who they are**, without switching screens or asking reception.

<Info>
  **EatNow owns the customer file.** The till displays it **read-only** — it never modifies your customer data. Everything is corrected in EatNow.
</Info>

***

## What the floor sees

On the till, the reservation card shows **badges** that read at a glance:

| Badge         | Meaning                                        | Where it comes from in EatNow                  |
| ------------- | ---------------------------------------------- | ---------------------------------------------- |
| **VIP**       | Important guest                                | The `VIP` tag on the customer file             |
| **allergies** | An allergy or dietary preference to know about | The reservation's *Allergies & comments* field |
| **prepaid**   | An amount has already been collected           | The reservation's payments                     |
| **imprint**   | A card imprint guarantees the booking          | The pre-authorisation held by EatNow           |

Tapping the guest card opens the **full profile**.

***

## What travels to the till

| Information                 | Source in EatNow                                   |
| --------------------------- | -------------------------------------------------- |
| **Name**                    | The customer file's name                           |
| **Phone**                   | The customer file's phone number                   |
| **Email**                   | The customer file's email                          |
| **VIP**                     | The `VIP` tag (case-insensitive)                   |
| **Tags**                    | The customer file's tags (up to 20)                |
| **Allergies & preferences** | The **reservation's** *Allergies & comments* field |
| **Visit count**             | Counter on the customer file                       |
| **Average spend**           | Computed by EatNow from the guest's history        |
| **No-show count**           | Counter on the customer file                       |
| **Member since**            | The customer file's creation date                  |
| **Recent visits**           | Up to 20 visits, most recent first                 |

For each past visit, the till shows the **date**, the **table**, the **cover count**, the **amount spent** and the **outcome**: completed, in progress, or no-show.

<Note>
  All of this is **optional**. Anything EatNow doesn't know simply doesn't render on the till — no empty rows, no dashes.
</Note>

***

## Guests without a name

A reservation may well have no customer file: a walk-in seated quickly, a booking taken anonymously.

In that case:

* The till shows **Walk-in** instead of a name (in its own language).
* No customer statistics are sent — there's no file behind the party.
* **But the allergies still travel.** The *Allergies & comments* field lives on the **reservation**, not on the customer: an allergy reported by a walk-in does reach the floor.

<Tip>
  That's a deliberate choice: you can do without a name; you can't do without an allergy.
</Tip>

***

## Two notes, two purposes

This is the most important distinction to get across to your team.

<CardGroup cols={2}>
  <Card title="Allergies & comments" icon="alert-triangle">
    **The guest's note.** Allergies and preferences (*"nut allergy"*, *"quiet table"*).

    It shows on the till's guest profile, **read-only**. Editable in EatNow only.
  </Card>

  <Card title="Internal info (private)" icon="note">
    **Your team's note.** Never shown to the guest.

    It becomes the **order's note** as soon as the guest is seated, and **prints at the top of every kitchen ticket**. Editable on both sides.
  </Card>
</CardGroup>

### The internal note travels both ways

It's the only shared free-text field:

<Steps>
  <Step title="You write it in EatNow">
    The **Internal info (private)** field on the reservation form.
  </Step>

  <Step title="It lands on the order">
    As soon as the guest is seated, it becomes the order's note, visible under **Actions → Note** on the till.
  </Step>

  <Step title="It prints in the kitchen">
    At the top of every kitchen ticket for that table.
  </Step>

  <Step title="The server can edit it">
    If they rewrite it on the till, the new version comes back to EatNow, onto the reservation.
  </Step>
</Steps>

<Note>
  Last writer wins, on both sides. If the reservation is already **closed** (Done, No-show, Cancelled), EatNow refuses the change and the till reverts to EatNow's note.
</Note>

***

## Feeding the customer file

The richer your customer files, the better armed your floor is. The useful gestures, all in EatNow:

<Steps>
  <Step title="Tag your regulars">
    Add the `VIP` tag on the customer file to make the badge appear on the floor. All your other tags travel too (*Regular*, *Press*, *Group*…).
  </Step>

  <Step title="Record allergies in the right place">
    In the reservation's **Allergies & comments** field. Your guests can also fill it in themselves from the booking portal.
  </Step>

  <Step title="Use the internal note for tonight's context">
    *"Birthday, cake at 10pm"*, *"Chef's guest"*. That's what lands on the kitchen ticket.
  </Step>

  <Step title="Let the statistics build themselves">
    Visit count, average spend, no-shows: EatNow computes them automatically, including from bills cashed on NowOS. Nothing for you to type.
  </Step>
</Steps>

***

## When is the profile refreshed on the till?

On **every reservation push**, which means on every change. In practice:

* You add the `VIP` tag to a guest → the badge appears at the next change to their reservation.
* The guest dines with you → their average spend and history are recomputed, and reach the till on their **next** reservation.

<Tip>
  To force an immediate refresh, any harmless edit to the reservation is enough (for example reopening and saving the internal note).
</Tip>