One menu for the table, Instagram, and WhatsApp

Someone DMs you on Instagram: “Can you send the menu?” You send a PDF from March. At the same time, table 7 is reading a laminated carta from June. The bar has a handwritten tapa list. Three menus. One restaurant.

Guests treat that as sloppiness even when the kitchen is excellent. They compared the bio, the story, and the table, and they did not match.

A single QR menu is not a marketing trick. It is one digital menu that is true in the dining room and true in the pocket of someone who has not sat down yet.

Social is already a menu. Treat it like one.

People decide before they walk in. They open Instagram, they ask on WhatsApp, they Google the name from the hotel.

If what you send is a photo of a paper sheet, you get:

Unreadable type on a phone
Prices you already changed
No allergens, or a legend nobody can zoom
One language, while the person asking is not a local

The restaurant QR you print for tables can be the same URL you put in the bio and paste into WhatsApp. When you update a dish, you update every channel. That is the whole argument.

What “one menu” has to include to work on a phone

A PDF is not one menu. It is a poster in a file.

Ordenala’s digital menu is built for the scan:

Groups and dishes with photos
Prices and portions, including different prices by location (bar, terrace, dining room)
Official 14 allergen icons and filters
Up to 10 languages, with automatic detection of the phone language
No app for the guest

Someone on the sofa at the hotel sees the same structure as someone already seated. They can filter gluten. They can switch to English. They can see whether the terrace exists as a zone with its own prices.

Print the QR once. Share the link forever.

The physical code on the table does not expire when you change the weekend special. Neither does the link in the bio.

You stop designing a “social version” of the carta. There is no social version. There is the menu.

Hours, map, and social icons live on the info site if you are on Standard or Premium (those plans use a subdomain). Basic still gives you a working internal path for the QR itself — enough if your only job is the table, not a mini website.

You do not sign up to try the idea

Build the menu on create. Put in the dishes you would be embarrassed to send as a blurry photo. Look at the preview. Publish when it is the carta you are willing to show a stranger in a DM.

Until publish, there is no public half-menu leaking into Google. After publish, the same object is table + Instagram + WhatsApp.

Inconsistent menus create extra work you cannot staff

Every time a guest says “online it was cheaper” or “the story had a dish we don’t see,” a server has to repair trust. That is unpaid customer service caused by files.

One current digital menu removes that repair. The answer is “scan this” or “here is the same link.”

If you are still exporting PDFs for social and printing a different list for the room, you are maintaining two products. Keep one: a QR menu guests open at the table, on Instagram, and on WhatsApp, with no app and no reprint every time a dish changes.