Several restaurants, one account: QR menus without duplicate logins

A second venue should not demand a second email, a second dashboard, and a second forgotten password. It should not mean copying the first carta into a PDF and hoping terrace prices match.

If you already run more than one outlet — two bars, a restaurant and a café, a hotel with dining room and rooftop — the pain is not “making a QR”. It is keeping several live menus without going mad.

One login. Several menus. Each with its own skin.

On Ordenala you can have more than one QR menu under the same account (each with its own subscription). Logo, colors, locations, languages, and subdomain or path belong to the venue, not the account. The dashboard lists what you have published and what is still a draft.

You change the rooftop special without touching the breakfast menu. You hide a sold-out dish at the harbour bar and leave the city-centre one alone.

What you do not want to copy by hand between venues

• Official allergens: marked per dish, not invented in each PDF
• Zone prices: hotel terrace ≠ beach-bar terrace
• Translations: the same “starters” group in six languages, different dishes per site
• Instagram link: each bio points to its own menu, not a shared Drive

Basic per venue if you only need the table. Standard / Premium per venue if you want a subdomain and info site. You pick a plan at each publish, not an opaque bundle for the whole group.

Start with one. Add the second when the first is live.

Design the first menu without an account. Publish it. Open the dashboard and create the next when the first is no longer being reprinted. That way you do not build two theoretical cartas: you build two that guests already scan.

If today you keep three spreadsheets and a freelance designer for every change, the cost is not the subscription. It is the lag between venues.

Create my QR menu — the first without signup. The second from the same account when you publish.