Manage Tables

In this article

Before you start

• You are signed in to Harbor Demo Group and Harbor Soho is the active location.
• You have `layout:view` to open layouts and `layout:manage` to create, edit, move, resize, duplicate, delete or save tables.
• An editable layout is open as an existing layout, a new layout or a copied layout. Historical and read-only layouts can be viewed but not changed.
• At least one zone exists before creating a table; the Create table control is disabled when the layout has no zones.
• A table type must already exist in the same layout before it can be assigned to a table.

Instructions

1. 1.

   Open the layout editor

   Open Floor plans for Harbor Soho and choose an existing layout, create a new one or copy an existing layout. The editor shows the canvas, zones, tables, toolbar and side panel.

2. 2.

   Create a table

   Choose `Crear mesa`, select a round or square shape, then drag inside an existing zone. The editor creates a table with a generated name such as `Mesa N`, default capacity 2 to 4, the selected shape and no table type.

3. 3.

   Edit table details

   Select a table such as `B1` on the canvas. In `Selección`, update the name, `Mesa supletoria`, capacity, shape, table type, position and size. Use `Mesa supletoria` only for a table that should save capacity as 0 to 0.

4. 4.

   Move, resize or duplicate

   Drag the selected table to reposition it, or use resize handles to change its size. Round tables keep a single diameter. `Duplicar mesa` creates a copy with a new ID, incremented name and offset position.

5. 5.

   Delete a table

   Select the table, choose `Eliminar` and confirm `Eliminar mesa`. The deletion stays local until the full layout is saved, and local combinations that included that table are removed.

6. 6.

   Save or discard

   Choose `Guardar` to validate and persist the whole layout. Existing layouts use `PUT /api/app/{orgId}/{locationId}/layouts/{layoutId}`; new and copied layouts use `POST /api/app/{orgId}/{locationId}/layouts`. Closing or cancelling discards unsaved table changes.

Validations and limits

• The layout must have a name, at least one zone and at least one table before it can be saved.
• Every table needs a non-empty name, and table names must be unique without relying on letter case.
• Normal table capacity must be positive with minimum capacity no greater than maximum capacity; `Mesa supletoria` is the supported 0 to 0 capacity case.
• Each table needs a `layout_zone_id` that belongs to a zone in the same payload, and each zone must keep at least one table.
• If `table_type_id` is present, it must point to a table type in the same layout payload.
• Drawn or resized tables must be at least 48 by 48 canvas units.
• Remaining combinations must reference tables from the same zone and have valid positive capacity ranges.
• There is no independent application API for a single table. Saving an existing layout replaces the layout collections through the full layout payload.
• Do not document table-overlap prevention as a guaranteed validation; the verified layout save path does not prove that rule.

Expected result

After Save, the layout owns the updated tables and downstream reservations, optimisation and TPV table views use the same floor-plan data. Unsaved local table changes are discarded when the editor is closed or cancelled.