> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt
> Use this file to discover all available pages before exploring further.

# QR codes & sharing

> Print a QR code for your tables, share the link, and see exactly what your guests get — filters, languages, and how Google reads your menu.

Every menu — PDF or interactive — has a **permanent public link** and a **QR code**. They never change, so a QR code you printed last year still works today.

## Get the link and the QR code

From **Digital menus**, click the **QR code** icon on the menu's row.

<Frame caption="The link to share, and the QR code to print.">
  <img src="https://mintcdn.com/eatnow/Ui0ES7GP5Mmu1gDB/images/screenshots/menus-qr-en.png?fit=max&auto=format&n=Ui0ES7GP5Mmu1gDB&q=85&s=8118b3117c6632116979283df8218d22" alt="The QR code modal with the direct link and a downloadable QR code" width="2880" height="1800" data-path="images/screenshots/menus-qr-en.png" />
</Frame>

* **Direct link** — copy it with the button next to it. Put it on your website, in your Instagram bio, in an email or a WhatsApp reply.
* **QR code** — click **Download QR Code** to get a PNG. Print it on table tents, on your window, at the bottom of the bill.

<Note>
  The QR code and the link are deliberately slightly different. A QR code is normally scanned **at the table**, so the page it opens hides the *Book a table* button — your guest is already seated. The copied link keeps the booking button, because it's meant for people who are not there yet.
</Note>

## Where guests find it on your portal

As soon as one menu is visible, a **Menus** link appears in the header of your booking portal. If you have several, it opens a small dropdown listing them.

<Frame caption="The Menus link in your portal header, listing every visible menu.">
  <img src="https://mintcdn.com/eatnow/Ui0ES7GP5Mmu1gDB/images/screenshots/menus-portal-header-link-en.png?fit=max&auto=format&n=Ui0ES7GP5Mmu1gDB&q=85&s=2d3abd97bd49bfb23eec97e6587d20ae" alt="The Menus dropdown in the booking portal header" width="780" height="1688" data-path="images/screenshots/menus-portal-header-link-en.png" />
</Frame>

<Tip>
  You can rename or reorder that link — and the other portal links — in **Settings → Portal → Links**.
</Tip>

## What your guests see

A PDF menu simply opens your file. An **interactive menu** opens a page like this one:

<Frame caption="An interactive menu on a phone, in your restaurant's colors.">
  <img src="https://mintcdn.com/eatnow/Ui0ES7GP5Mmu1gDB/images/screenshots/menus-portal-mobile-en.png?fit=max&auto=format&n=Ui0ES7GP5Mmu1gDB&q=85&s=acf193f75aa786b8967384cc130e0f32" alt="An interactive menu on mobile" width="780" height="1688" data-path="images/screenshots/menus-portal-mobile-en.png" />
</Frame>

* **Category tabs** stick to the top while they scroll, and follow the section they're reading.
* **Prices, photos, dietary chips and allergens** on every dish; tapping a dish opens its full details and photo.
* **Badges and chili levels** stand out — a good reason to use them sparingly.
* A dish you marked out of stock stays visible, greyed out, labelled **Unavailable today**.

<Frame caption="Badges, dietary chips, and a dish marked unavailable for the day.">
  <img src="https://mintcdn.com/eatnow/Ui0ES7GP5Mmu1gDB/images/screenshots/menus-portal-unavailable-en.png?fit=max&auto=format&n=Ui0ES7GP5Mmu1gDB&q=85&s=0a0ca8ebf49943a9634d6fcc082eac3c" alt="A menu section showing a chef's pick badge and an unavailable dish" width="780" height="1688" data-path="images/screenshots/menus-portal-unavailable-en.png" />
</Frame>

### Filters

Behind the **Filters** button, guests can pick dietary preferences and exclude allergens.

<Frame caption="Dietary preferences and allergen exclusion, guest side.">
  <img src="https://mintcdn.com/eatnow/Ui0ES7GP5Mmu1gDB/images/screenshots/menus-portal-filters-en.png?fit=max&auto=format&n=Ui0ES7GP5Mmu1gDB&q=85&s=a897faf0db0ff789afca43b7d8faebef" alt="The guest-side filter drawer with diets and allergens" width="780" height="1688" data-path="images/screenshots/menus-portal-filters-en.png" />
</Frame>

* **Dietary preferences** keep only the dishes that carry *all* the selected tags.
* **Exclude allergens** hides the dishes that **declare** the excluded allergen.

<Warning>
  The allergen filter can only work with what you entered. A dish with no allergen filled in is never hidden — it simply declares nothing. The page carries a disclaimer inviting guests to tell your team about any allergy, but that does not replace an accurate menu.
</Warning>

### Languages

The page follows the guest's language, and they can switch it from the flag at the top right. Six languages are available: English, French, Spanish, German, Portuguese, Italian — filled automatically when your PDF is imported.

A dish no translation covers — a recent addition, say — shows in the language you wrote it in rather than leaving a blank on the page.

## Google and AI assistants

An interactive menu is a real web page, rendered on the server, so:

* **Google can index it** — your dishes and prices become searchable, which a PDF never allows.
* It embeds **schema.org structured data** (`Restaurant → hasMenu → MenuSection → MenuItem`, with prices and diets), the format search engines and AI assistants read to answer questions like *"vegan pizza near me"*.

Nothing to configure — it happens as soon as the menu is published.