How prices are displayed

Fenómenus stores exactly what you type and shows it with an indication of the serving format. Understanding that division — your text, the product's presentation — explains what you control and what you do not.

What the product adds

Each price is presented alongside the format it belongs to, with its own icon: a full portion, a half portion, a unit, a glass, a shot, a bottle, a Magnum, a Benjamin, a menu price, a pairing price. Cocktails and beverages use drink-specific icons for their glass and bottle prices.

That is how a guest knows that 12,00€ is a full portion and 7,00€ is a half of the same dish, without either line saying so.

What you control

Everything inside the value:

• the number;
• the decimal separator;
• the currency symbol and its position;
• any qualifier, such as (6 unidades) or mínimo 2.

Because the field is text, it accepts all of that. Because it is text, nothing enforces consistency — that is an editorial job.

Decide the convention once

Write it down and apply it to every menu type on the site:

Guests compare prices down a column. Two conventions in the same column reads as an error even when both numbers are right.

Empty, zero, and free

• Empty — the format is not offered. Nothing is shown.
• 0 — a real price of zero, and it is displayed.
• A genuinely free item is better expressed in words in the description than as a zero in a price column.

Prices in a PDF design

Each PDF price is a dynamic layer inside the reusable loop-item component. Bind the layer to the required stored price field, then position it freely. A layer can have its own short Prefix or Suffix, and any text or dynamic text layer can enable Fill remaining width with dots to connect an item name to a right-aligned price.

Do not use a layer prefix to hide inconsistent stored values: the public digital menu would still be wrong. Put long tax wording in a fixed feed, header, or footer text layer instead of repeating it beside every price.

What Fenómenus does not do

• No tax calculation. If prices include VAT, say so in the item description, a menu footer note, or a fixed PDF text layer.
• No currency conversion, and no second currency column.
• No automatic rounding, no discounts, no happy-hour pricing.
• No price history. A changed price replaces the old one, and menu items keep no revision history.

For a record of what prices were, keep the Excel export taken before each change.

Where the same values appear

The public archive, the category navigation rows and the generated PDF all read the same stored values. A correction made once is correct everywhere — except in a PDF generated earlier, which is a snapshot and must be rebuilt.

Checking the display

1. Read one section on a phone, signed out, and compare the price column line by line.
2. Confirm every format shown corresponds to something the house serves.
3. Confirm the currency convention is identical across every menu type.
4. Confirm each PDF price layer's prefix and suffix do not duplicate a symbol already stored in the value.