# Configure tables and service terminals

**Console: Service → Tables.** Confirm the working location. Terminals are the
service points used for tables and supported counter, pickup, delivery, kiosk,
or shop flows. Creating a terminal is separate from placing it on a floor plan.

## Basic settings

Select **Add Terminal** or open the existing row. Set name and short name,
physical guest capacity, and maximum simultaneous sessions. Check **Session
Types** against the intended flow. Review description versus **Internal Notes**
before saving; internal instructions should not be put into guest-facing copy.
Use **Create Terminal** or **Save Changes**, then reopen and verify.

**Add Bulk** creates a numbered run: enter prefix and ascending From/To range,
select reservation availability, **Generate**, review the list, then **Create
terminals**. The current dialog limits a run to 30. Check generated names and
settings rather than assuming every created service point is identical.

## Reservation settings

**Automatic table use** has three modes:

| Mode                            | Operational meaning                                               |
| ------------------------------- | ----------------------------------------------------------------- |
| On its own or in combinations   | Eligible for individual automatic use and configured combinations |
| In configured combinations only | Automatic use requires a configured combination                   |
| Staff selection only            | Excluded from online and automatic selection                      |

These settings do not prohibit explicit staff selection of a conflict-free
table. Staff choices must include free tables regardless of online bookability,
automatic capacity fit, or a previously chosen seating area. Staff still need to
judge physical suitability and the restaurant's seating policy.

Choose **Seating area** and any **Limit reservation offerings** deliberately.
Configure actual [Table combinations](/tables-layout/table-combinations)
separately; changing the mode does not create a combination.

The list offers selected-row **Set area**, **Set reservable**, and **Set
capacity** actions. Check selected rows and the saved result before bulk
changes. An online eligibility change is not a request to move an existing
seated party.

## QR codes and links

Row actions include **QR Code**, **Order Link**, and **Copy NFC Link**. **Print
QR codes** previews selected terminals and offers paper-size choices. Check each
code or link against the intended location, terminal, and guest ordering flow
before placing it in the restaurant. Printing is not proof the linked menu or
order type is available.

Share only the intended guest-ordering links. Keep staff access links and
redemption credentials private. See [Order types](/orders/order-types) for
guest-flow configuration.

## Delete or recover carefully

**Delete terminal** removes it from active service setup, combinations, booking
blocks, future assignments, floor plans, and device/default references. The
confirmation requires moving active work first and preserves completed
booking/order history. Review affected future bookings and defaults before
confirming; this cannot be undone from the Console.

After an uncertain save/delete, inspect the original record and affected
bookings before repeating. Escalate with location, table, intended mode or
capacity, current booking/service state, and exact error.
