Tables
Tables represent physical seating locations within a venue. Used for table service and reservations. Tables are organized into groups (see TableGroups).
Storage Location
{customer_id}-table.jsonNote: Not all customers use table management. This file may not exist for takeaway-only or quick-service locations.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Unique table identifier. |
customer_id | integer | Yes | Reference to Customer. |
name | string | Yes | Table name/number (e.g., "Table 5", "Bar 1"). |
capacity | integer | No | Seating capacity. |
table_group_id | integer | No | Reference to TableGroup. |
business_unit_id | integer | Yes | Reference to BusinessUnit. |
status | string | Yes | Status: active or inactive. |
Example
json
{
"id": 5,
"customer_id": 12345,
"name": "Table 5",
"capacity": 4,
"table_group_id": 1,
"business_unit_id": 10,
"status": "active"
}Example - Various Table Types
json
[
{
"id": 1,
"customer_id": 12345,
"name": "Table 1",
"capacity": 2,
"table_group_id": 1,
"business_unit_id": 10,
"status": "active"
},
{
"id": 10,
"customer_id": 12345,
"name": "Bar 1",
"capacity": 1,
"table_group_id": 2,
"business_unit_id": 10,
"status": "active"
},
{
"id": 20,
"customer_id": 12345,
"name": "Terrace 1",
"capacity": 6,
"table_group_id": 3,
"business_unit_id": 10,
"status": "active"
}
]Related Entities
- Customers - Parent customer/tenant
- BusinessUnits - Parent business unit/location
- TableGroups - Zone/area grouping
- Orders - Orders reference table via
table_id