> ## Documentation Index
> Fetch the complete documentation index at: https://docs.now-os.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Tables & reservations

> Draw and publish your floor plan, connect a reservations provider, and track today's bookings from the backoffice.

<Note>
  This section applies to **restaurant mode** only. In retail mode, **Tables**
  does not appear in the backoffice menu. See [the two modes](/en/modes).
</Note>

## Building your floor plan

Open **Tables → Floor plan** in the location's menu to draw your rooms and
tables. This is the plan your registers show in the **Tables** tab.

<Steps>
  <Step title="Add a room">
    A floor plan is made of one or more rooms. Use the room controls to create
    rooms (for example *Dining room*, *Terrace*) and switch between them.
  </Step>

  <Step title="Place tables and decorations">
    Drag a shape from the palette at the bottom of the canvas onto the room:
    square, round, rectangle or bar tables, plus walls and columns to map the
    space. Drag a table to move it; use the rotation handle to turn it.
  </Step>

  <Step title="Set each table's details">
    Select a table to open the inspector on the right: its **label** (what staff
    see, e.g. *T12*), **shape**, number of **seats**, and position. The chairs
    are drawn automatically from the shape and seat count.
  </Step>

  <Step title="Publish the plan">
    Your changes stay a draft until you tap **Publish all changes** in the
    global header. Publishing includes the plan and the location's other saved
    changes. Confirm, then tap **Refresh** on the main register; until then, the
    registers keep the previous plan.
  </Step>
</Steps>

<Warning>
  Once a table has been published, you can no longer delete it — only
  **deactivate** it (from the inspector or the right-click menu). This keeps
  past orders and your provider's table mapping pointing at a table that still
  exists. A table you drew but never published can be deleted outright.
</Warning>

Deactivated tables are **hidden from the plan** by default to keep the editor
readable. The **Deactivated (n)** toolbar button shows them dimmed, and the
right-hand panel (when nothing is selected) lists every deactivated table in
the location with a **Reactivate** button — reactivating a table brings it
back on the registers at the next publish, history intact.

## Setting service timers

When a table has been seated for a while, its pill on the registers' floor plan
changes color to catch staff's eye: **azure** at first, **amber** after a first
delay, then **red**. It's a visual cue only — it never blocks anything.

Open **Tables → Service timers** to set these two delays per location.

<Steps>
  <Step title="Set the two delays">
    **Turn amber after**: minutes since the table was seated before its pill
    turns amber. **Turn red after**: minutes before it turns red. Red must come
    after amber.
  </Step>

  <Step title="Publish">
    Like the floor plan, the change stays a draft until you tap **Publish all
    changes**. Registers apply the new delays after their next refresh.
  </Step>
</Steps>

<Note>
  By default, amber appears at **60 minutes** and red at **90 minutes** — these
  are the factory settings until you change them. Your registers show these
  colors on the floor plan; see [Tables and reservations on the
  register](/en/pos/tables).
</Note>

## Connecting a reservations provider

NowOS does not keep its own reservation book — it connects to a reservations
provider (for example EatNow) that owns your bookings. Once connected, your
bookings flow to the registers, where staff can seat them.

Open **Integrations → Reservations** in the backoffice.

<Steps>
  <Step title="Connect the provider">
    Give the connection a name and confirm. NowOS shows an **API key** and a
    **webhook secret**.
  </Step>

  <Step title="Copy the credentials">
    They are shown **once**. Copy them and paste them into your provider's NowOS
    integration settings, along with the webhook URL the page gives you. If you
    lose them, rotate the key to get new ones.
  </Step>

  <Step title="Map your tables">
    Your provider matches its tables to the ones in your published floor plan.
    Publish the plan first so the tables exist to map against.
  </Step>
</Steps>

<Note>
  Connecting a provider is a one-time setup, usually done with your provider's
  support. The **Webhook deliveries** and **Provider activity** tabs on this
  page trace the events sent to the provider and the calls it has made — handy
  for troubleshooting. Day to day, you and your staff only deal with the
  bookings themselves — on the register and on the page below.
</Note>

## Tracking reservations

Open **Tables → Reservations** to browse bookings as the register sees them,
**one week at a time**: step between weeks with the arrows, jump back to
today with one button, filter by status (active, finished, no-shows,
cancelled) and search a name or phone number. The list is grouped by service
day.

Tap a booking to open its **detail panel**: guest contact details, allergies
and preferences, the provider's internal note, the prepayment and card
imprint breakdown, recent visits and technical references. Everything is
read-only — bookings are created and edited in your provider, and staff seat
them on the register.

For seating, prepayments and the day-to-day reservation gestures, see
[Tables & reservations on the register](/en/pos/tables).