Skip to main content
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.
EatNow owns the customer file. The till displays it read-only — it never modifies your customer data. Everything is corrected in EatNow.

​
What the floor sees

On the till, the reservation card shows badges that read at a glance: Tapping the guest card opens the full profile.

​
What travels to the till

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.
All of this is optional. Anything EatNow doesn’t know simply doesn’t render on the till — no empty rows, no dashes.

​
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.
That’s a deliberate choice: you can do without a name; you can’t do without an allergy.

​
Two notes, two purposes

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

Allergies & comments

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.

Internal info (private)

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.

​
The internal note travels both ways

It’s the only shared free-text field:
1

You write it in EatNow

The Internal info (private) field on the reservation form.
2

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

It prints in the kitchen

At the top of every kitchen ticket for that table.
4

The server can edit it

If they rewrite it on the till, the new version comes back to EatNow, onto the reservation.
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.

​
Feeding the customer file

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

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…).
2

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

Use the internal note for tonight's context

“Birthday, cake at 10pm”, “Chef’s guest”. That’s what lands on the kitchen ticket.
4

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.

​
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.
To force an immediate refresh, any harmless edit to the reservation is enough (for example reopening and saving the internal note).