Tapas, portions, and prices: a QR menu that matches how you serve

In many rooms a dish does not have one price. It has several: tapa, half, ración. Sometimes bar and terrace too. On paper that becomes an unreadable paragraph or a footnote nobody reads.

The guest orders “the calamari” and service has to ask the size. Time is lost. The ticket is wrong. The terrace surcharge becomes an argument.

Paper flattens what the kitchen distinguishes

One line cannot hold tapa and ración with different pours. A PDF is worse: guests pinch-zoom and still mix columns. Instagram shows one price and the table another.

A QR digital menu can list portions of the same dish with their own prices — and, if needed, different prices by location.

How you set it up in Ordenala

You create the dish once. You add portions. You assign locations (bar, terrace, dining room) and hide the ones that do not apply. The optional location message can explain the terrace surcharge without a speech.

Different photos per dish help show that a ración is not “a big tapa”. Allergens and languages travel with the dish; you do not copy them into three PDFs.

Basic gives two locations: enough for bar and terrace in many bars. Standard and Premium go to 4 and 8 if the hotel or group has more zones.

Fewer questions, cleaner tickets

• Guests pick size on the phone before they raise a hand
• Terrace is not a surprise at payment
• The same dish is not duplicated across three groups just to change the price
• WhatsApp and the table show the same portions

You still recommend. You stop reciting the menu from memory.

Design without an account and publish when the prices are true

The preview is the test: if a stranger understands tapa vs ración without asking, the carta works. You pay when you publish. The table QR is printed once.

Create my QR menu — portions and zones as they actually work. No signup until you publish.