> For the complete documentation index, see [llms.txt](https://appfront.gitbook.io/portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appfront.gitbook.io/portal/online-ordering/dine-in-and-table-number.md).

# Dine In & Table number

## Setup

In order to set up a dining option that will force a user to enter their table number you need to first mark "Ask for table code" in the setup section under Configure > Menu > Setup > Serving options:

![](/files/-M8A9QzBxQ459z978Agz)

Now, in the location settings, scroll down to "Dine in table code ranges" and enter the range which you want to enable a customer to select a table.

![](/files/-M8AA7W8WEUU6y_VuQjE)

If you have more than one range you can enter them with commas, for example if you have 101-118 on the main floor, and 201-207 on the second floor, you can enter in that field:

```
101-118,201-207
```

## Customer view

When a customer will select to dine in at that restaurant, they will have to enter the table number they are sitted at:

![](/files/-M8AAsbR9ksEY-J6G89W)

## Printing on the receipt

The table number will be printed on the receipt:

![](/files/-M8ACAmf_znaGbZ0yyxY)

## Creating a deep link to print on each table

Your URL template will consist of the following fields:

* [ ] Your website URL (for this example we will **YOUR.RESTAURANT.COM**
* [ ] Location id (**branchId**) - the location of this table - can be found in the online ordering site as a URL parameter: "branchId=LOCATION\_ID" \
  please read more here: [Create Link To Order From Specific Branch](/portal/online-ordering/create-link-to-order-from-specific-branch.md#getting-your-branch-id)
* [ ] Table number (**tableCode**) - the table code you want to open.

This is the URL template you'll need to use:&#x20;

```
https://YOUR.RESTAURANT.COM/order/?branchId=LOCATION_ID&servingOptionType=sitdown&tableCode=TABLE_CODE
```

For each link, please change:

1. **YOUR.RESTAURANT.COM**
2. **LOCATION\_ID**
3. **TABLE\_CODE**

to the correct values

In order to set this up, you'll need to create a QR code for each table (using <https://www.qrcode-monkey.com/>)

For example, if we are building the qr code for Bierstadtlager, with the following values:

1. **YOUR.RESTAURANT.COM** = bierstadtlager.appfront.ai
2. **LOCATION\_ID =** 5e77579e2f5d250e142de64a
3. **TABLE\_CODE** = 32

Switching these values will give us:

<https://bierstadtlager.appfront.ai/order/?branchId=5e77579e2f5d250e142de64a&servingOptionType=sitdown&tableCode=32>

![](/files/-McBZ4aO40jqGTD1czfc)

You will be able to see the online ordering / app open directly in the dine in menu, with the table already chosen


---

# 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://appfront.gitbook.io/portal/online-ordering/dine-in-and-table-number.md?ask=<question>&goal=<endgoal>
```

`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.
