EatNow
The book

One book, and the history that comes with it.

Bookings entered in EatNow are gathered in the same book. And a recorded change shows who made it, when, and what changed.

Front desk
Salma
Floor
Yassine
Automatic
EatNow system
Connected
Payments and till
Tonight's bookLive
  • 19:30Lefèvre4p
  • 20:00Bennani2p
  • 20:00MoreauDeposit6p
  • 20:30Sansone3p
  • 21:00Walk-in2p
Before / after

Two books that disagree, or one kept current.

The book at the front desk, a note scribbled on the pass, a change made from memory mid-service: everyone writes on their own side, and nobody knows which version counts.

Everyone on their own

Three versions of the evening

  • The book says one thing, the screen says another
  • A table sold twice on a busy Friday
  • Nobody knows who wrote what, or when
  • Service starts without an overall view
One book

A book updated during service

  • Recorded changes appear in the same book, with their time
  • Once a slot reaches capacity, EatNow stops offering it
  • Every recorded change keeps its origin and its timestamp
  • The team looks at the same book before service
The history

Every recorded change, with its origin.

Every booking keeps a record of what happened to it. Not just what the team did: the system and your providers write to the same log.

Booking historyBooking #4812 · Fri 8:30pm
  • 6:57 pmSalma · front deskBooking created for 4 covers at 8:30pm
  • 7:04 pmStripe€40 deposit captured
  • 7:05 pmSystemConfirmation sent once the deposit cleared
  • 8:11 pmYassine · floorCovers changed 4 → 6, table 12 → table 14
  • 10:48 pmPOSBill settled and attached to the booking
  • 11:02 pmSystemBooking closed after payment

Who changed what

The log shows who changed the covers, the table or the deposit, and at what time.

Your providers too

When they're connected to EatNow, payments and the till also leave a trace in the same log.

Useful when you're not there

The next day, you find the actions that were recorded on the booking.

Real time

A change during service, and the book follows.

  • When a cancellation is recorded, the slot can be offered again according to your availability rules, and the cancellation stays logged with its origin.
  • The floor plan and the book are synced. When a table assignment changes, the change shows up in the history.
  • A booking taken over the phone goes into the book like any other, with the name of the person who entered it.
EatNow floor plan synced with the reservation book
Table 12 · cancelled at 6pm
Slot freed
Book updatedAvailable
FAQ

On the book and its history

Who can see the history?

You decide. The history follows the rights you give each team member: some see the service book, others the full history of a booking.

Does a booking taken by phone appear too?

Yes, provided it is entered in EatNow. It then appears in the book like any other, with the name of the person who recorded it.

What if two people edit the same booking?

The history shows recorded changes, in the order they were recorded and with their time.

Is the history kept after service?

Yes. It stays attached to the booking, including once the evening is over and the bill has been attached.

Zero commission · No lock-in · Live in 24h

Bring your whole room onto EatNow.

Reservations, deposits, WhatsApp confirmations, CRM, reporting — one single system. Human support, in French and English, from people who've worked service.

0% commission
A clear subscription, never a cut of your covers
No lock-in
Export your data and history whenever you want
Live in 24h
Data import and team training included
FR & EN support
A team that answers — not a ticket into the void
Discuter via WhatsApp