← Back to support

Daily ops

DeepL translations for menu items

Updated: 2026-05-25

DeepL translations for menu items

Also known as: traducciones del menú, menú bilingüe, ES/EN, English menu, menú turista, DeepL.

brasio uses DeepL to translate product descriptions between Spanish (ES) and English (EN) automatically. Write your menu in your working language; brasio fills the other one at sync time. Customers reading the public menu PDF on their phone get it in their language; staff on the till switch between locales without losing context.

What gets translated

  • descriptionEs / descriptionEn on each product (the tasting notes, ingredient list, the marketing copy).
  • Beer descriptions imported from Untappd (Untappd descriptions are typically EN; brasio fills ES).
  • Wine notes (when notes are imported from your supplier sheet in one language).

What's not translated:

  • Product names. Names are short, brand-y, and any literal translation would be worse than just leaving them. Write the name once; it appears the same in both locales.
  • Category and subcategory names (same reason).
  • Modifier option labels (these are too short to translate reliably; we ask you to provide both ES and EN labels manually).

When translation happens

  • At Untappd sync time: every beer description coming from UTFB is translated as it lands.
  • At wine import time: the bundled wine import script translates supplier notes once.
  • Not on every save: editing a product in Admin → Catálogo doesn't automatically translate; the descripción (ES) and description (EN) fields are both shown side by side for you to edit either or both. Use this if you'd rather hand-write a translation than rely on DeepL.

Override a translation

If DeepL's output is wrong (a slang term, a brewery-specific expression):

  1. Admin → Catálogo, open the product.
  2. Edit descripción (ES) or description (EN) directly.
  3. Save.

The override sticks. Future syncs do not clobber a hand-written description; brasio only fills empty fields.

Where the translation shows

  • Public menu PDF: the PDF is generated per locale. The Spanish PDF uses descriptionEs; the English PDF uses descriptionEn. See Public menu PDFs.
  • Till product description modal: uses the locale of the logged-in employee (each employee picks ES or EN as their working language).
  • Customer receipts: today receipts only use the venue's primary locale.

Quota and cost

brasio uses the DeepL Free tier today — 500,000 characters per month, shared across all tenants. For most small bars and restaurants this is never hit. Heavy menu changes (re-translating a 300-item catalog) can blip the meter. If a sync fails with a quota error, we get a notification and reach out.

If you'd like dedicated DeepL Pro for guaranteed throughput, talk to us.

Not working?

  • A description didn't translate: check the source field — DeepL only translates from a non-empty field into an empty one. If both descriptionEs and descriptionEn are filled (even with the same text), no translation runs.
  • The translation is wrong / awkward: hand-edit it. DeepL is good but not perfect; for brand-critical text, treat it as a first draft.
  • DeepL quota error: wait for the monthly reset or contact us to upgrade.
  • Special characters / HTML in the description: DeepL handles markdown reasonably. HTML tags and entities (<, >, &) can cause translation failures — keep descriptions in plain text.

More in Daily ops

Still stuck?

Talk to our 24/7 agent in your language. If it can't answer, we'll pass you to a human.