Different prices at the bar, terrace, and dining room — one QR
August 9, 2026

You already have two or three menus. You just pretend they are one.
The caña at the bar is not the caña on the terrace. The tapas list in the dining room is longer. Some dishes never leave the counter. Paper handles this badly: extra lists, handwritten surcharges, or a server who has to say “it’s more outside” and hope the guest does not feel tricked.
A restaurant QR with prices by location makes the difference explicit. The guest chooses where they are sitting. The digital menu shows the dishes and prices that belong there.
Guests are not angry about terrace prices. They are angry about surprises.
A terrace surcharge is normal. Finding it after the bill is not.
If the only way to know is to ask, you train people to distrust the carta. If you print three versions, you will have the wrong one on the wrong table by Thursday.
Location-based prices fix the conversation before it starts:
- Bar: faster list, bar prices, maybe dishes you only serve standing
- Terrace: the same drink with the outdoor price, clearly labeled
- Dining room: full groups, portions, the plates you do not send to the counter
One scan. They pick the zone. You stop narrating the price list.
One QR, several locations — not several reprints
In Ordenala you create locations (up to 2 on Basic, 4 on Standard, 8 on Premium). Each can have a name, an icon, and a short message. A dish can exist in one zone and not another. The same dish can have different prices and portions per zone.
You update that without reprinting. When you raise the terrace coffee in July, the QR on the table does not change. The number does.
Hide a tapa when it is gone at the bar; leave it on the dining-room list if the kitchen still plates it. That is the opposite of a Sharpie on laminated card.
Photos and allergens still belong on every zone
A guest at the bar is still a guest with an allergy. A tourist on the terrace still wants the dish in their language.
The digital menu keeps the rest of the product with the price:
- Photos per dish
- Official 14 allergen icons and filters
- Up to 10 languages, with the phone language detected
- No guest app
You are not choosing between “zone prices” and “a serious menu.” You get both on the same restaurant QR.
Staff stop mediating the surcharge
At peak, nobody wants to explain why table 4 paid less than table 18. When the menu states the location, the check matches what they saw.
That also cuts mistakes: a new waiter does not invent a price. The zone they confirmed is the zone the ticket should match.
Start without signup, publish when the zones are honest
Build the locations and the dishes on the create flow. See the preview. Register when you publish.
- Basic: internal path, two locations — enough for bar + terrace in a small venue
- Standard: subdomain, info site, four locations, more languages
- Premium: subdomain, info site, eight locations — hotel outlets, pool bar, room service style splits
The info site on Standard and Premium is useful when someone opens the link from Instagram and needs hours and a map before they care about the terrace price.
If you are still crossing out “barra / terraza” on paper, you are doing location logic by hand. Put it in the menu.
Create my QR menu and set bar, terrace, and dining room as they actually work. No account until you publish.