> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/new-guests/reserve/setting-up-reservations/tables-capacity-floor-plan.md). # Tables, Capacity & Floor Plan Your table setup is the foundation of how Oddle Reserve manages availability. Every reservation is tied to a specific table (or combination of tables), so getting this right ensures accurate availability for your guests and smooth operations for your team. You manage all of this in the Host App under **Settings > Tables and Floor Plan** (`host.oddle.me/settings/areas`). *** ## Areas Areas represent the different sections of your restaurant — for example, "Main Dining," "Outdoor Terrace," or "Private Room." You need at least one area before you can add tables. Each area has a **customer-facing name** that guests see on your booking page, and you can optionally set a **different internal name** for your team's reference. For example, you might call an area "Outdoor Terrace" for guests but use "OD" internally so it's quicker for staff to read on the floor plan and reservation board. Areas help you organise your tables logically, offer guests a choice of seating area (if you set this up in your tickets), and manage capacity by section. *** ## Tables Each table belongs to an area and has a few key properties: * **Table name/number** — How your team identifies the table (e.g., "T1", "Window 3", "Bar Seat A") * **Minimum covers** — The smallest party size this table can seat for online bookings * **Maximum covers** — The largest party size this table can seat for online bookings * **Online booking** — Whether this table is available for online reservations (toggle on/off). Tables that are toggled off can still be used for walk-ins or manual bookings by your staff. * **Priority** — When a guest books online, the system assigns a table based on availability and your priority settings. Higher-priority tables are assigned first. The min and max covers control what's offered to guests booking online — they set the boundaries for automatic availability. But your floor team always has full flexibility in the Host App. If you need to seat 5 at a 4-top because the restaurant is busy, you absolutely can. Your team can also seat a party across multiple tables without needing a predefined table combination — just assign the tables manually. The limits and combinations are there to guide online bookings, not to restrict your team. > **Important:** If no tables are set to "online," guests won't see any available time slots on your booking page. Make sure at least some tables are enabled for online bookings. *** ## Floor Plan (Optional) You can optionally lay out a visual floor plan in the Host App using the **Floor Plan Editor** (**Settings > Tables and Floor Plan > Floor Plan Editor**). This gives your team a spatial view of the restaurant when managing reservations and seating guests. The floor plan is **not required** for Oddle Reserve to work — you can manage everything through the list and timeline views. But if your team prefers a visual layout (especially useful for larger restaurants or venues with complex layouts), you can drag and position tables on a canvas to match your physical space. Your floor staff can then use the **Floor Plan view** on the reservation home page to see at a glance which tables are occupied, reserved, or available. *** ## Table Combinations Sometimes a party is too large for a single table but fits perfectly if you push two tables together. Table combinations let you define which tables can be merged to accommodate larger groups. You manage combinations under **Settings > Tables and Floor Plan > Combinations**. To create one, click **Create Combination**, select the tables you want to combine from your areas, and assign an allowed party size. That's it — the combination is ready to use. For example, if Tables 1 and 2 each seat 4, you could create a combination of those two tables with an allowed party size of 8. When a guest requests 8 diners online and no single table fits, the system automatically checks your defined combinations and offers this option. Combinations also have a **priority order** — you can reorder them to control which combination the system prefers when multiple options could work for the same party size. This is useful when you want to protect certain table arrangements and only use others as a fallback. > **Tip:** Table combinations are especially important for maximising online booking capacity. Without them, larger party sizes that don't match any single table will show as unavailable on your booking page — even if you'd happily push two tables together in practice. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.oddle.me/docs/new-guests/reserve/setting-up-reservations/tables-capacity-floor-plan.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.