In this article

• The menu name and the kitchen name are not the same job

• What it costs when there is only one name

• A second name, written by you

• Why it has to reach the screen, the ticket and the label

• What to actually put in the field

• The setup nobody warns you about

• What a kitchen name will not do

• Where Peblla fits — and where it does not

• Frequently asked questions

The Menu Name and the Kitchen Name Are Not the Same Job

A menu name has to sell. It carries the description, the provenance, sometimes a bit of poetry — Grilled Branzino with Charred Lemon and Salsa Verde. It is written for someone deciding what to order.

A kitchen name has one job: tell the person cooking exactly what to make, in the fewest characters they can read at a glance from four feet away, in the language they think in. Those are different requirements, and in a lot of restaurants they are different languages.

This is not an edge case. Across the US, a very large share of independent restaurants are owned and staffed by people whose first language is not English while the menu facing guests is entirely in English. The kitchen has been quietly translating in its head for years, and everyone has agreed to call that normal.

It is the daily reality in dim sum kitchens, noodle houses, taquerias and sushi bars, and in plenty of full-service American rooms where the line speaks Spanish and the menu does not.

What It Costs When There Is Only One Name

The cost does not show up as one dramatic failure. It shows up as friction distributed across every shift.

A new cook takes three weeks to get fast, not because the cooking is hard but because reading the ticket is. During a rush, someone stops the line to ask what a dish is. A dish gets remade because two menu names look similar in a language the cook is scanning rather than reading.

In a quick-service room that is a thirty-second delay repeated forty times a shift. In a bakery packing morning orders, it is the wrong pastry in the box. The expediter becomes a human dictionary and cannot leave the pass.

It also quietly limits who you can hire. If reading the ticket requires English, you have narrowed your hiring pool in a labor market where that is an expensive thing to do. Kitchens end up paying a premium for language ability that has nothing to do with cooking skill.

None of this appears in a report. It appears as ticket times that are worse than they should be and a training period longer than it needs to be.

A Second Name, Written by You

The fix is small and old-fashioned: let every dish carry two names.

The first is the menu name, which is what the guest sees everywhere they encounter you — the printed menu, your website, a self-order kiosk, a server's handheld. Nothing about that changes.

The second is a kitchen name you type in yourself, per item, in whatever language and shorthand your cooks actually use. It is not a translation the software generates and it is not a language setting for your menu. It is a free-text field, and what goes in it is your decision.

Set it once, when the item is created. From then on, the guest sees one name and the kitchen sees the other, and nobody has to hold both in their head.

Why It Has to Reach the Screen, the Ticket and the Label

A kitchen name that only works in one place is worse than not having one, because the kitchen learns it cannot trust the name it is reading.

Most kitchens run more than one surface. The order appears on a kitchen display screen, it may also print as a kitchen ticket, and packaged or prepped items get a label. If the name is consistent on the screen but reverts to the menu name on the label, the person packing takeout is back to translating.

So the field has to be one field that all three read from. One place to set it, one place to change it, and no chance of the three surfaces disagreeing with each other during a rush.

What to Actually Put in the Field

Owners overthink this. A few rules from kitchens that have done it well.

Write what your cooks already say out loud. If the line calls a dish by a two-word shorthand, that shorthand is the correct kitchen name — not a formal translation of the menu name.

Keep it short. The value of this field is that it can be read at a glance across a hot line. A kitchen name longer than the menu name has defeated its own purpose.

Disambiguate the pairs that get confused. You do not need a kitchen name for every item on day one. You need one for the items that look alike, the ones that get remade, and the ones new hires always ask about. Start with those twenty and add the rest over time.

And handle modifiers deliberately. A dish name in the right language with modifiers in the wrong one still stops the line, so work through the add-ons that change how something is cooked before you call the setup finished.

The Setup Nobody Warns You About

The work is not technical. It is that somebody has to sit down with your menu and decide, item by item, what the kitchen calls each thing.

The person who should do this is your head cook, not your manager and not your vendor. They are the only one who knows which name the line actually uses. Budget an hour with them and the menu open, and treat the output as a working document you refine over the first month.

Do it while your menu is being loaded rather than after. Retrofitting a kitchen name onto three hundred existing items is a chore; setting it as part of creating each item costs nothing extra. If you are moving to a new system, this is the moment.

What a Kitchen Name Will Not Do

It will not train a cook. Someone still has to teach the dish; the name just stops the reading from being the obstacle.

It will not fix a chaotic order capture process. If the modifier was never recorded correctly, the ticket is wrong in every language.

And it is not a substitute for a kitchen that is organized. Station routing, timers and the whole-table view do their own jobs, and a good kitchen name makes each of them slightly easier to read rather than replacing any of them.

Where Peblla Fits — and Where It Does Not

In Peblla, every item can carry a kitchen name alongside its menu name. You set it once, per item, and it applies the same way to the kitchen display screen, the printed kitchen ticket and the label. Guests see the menu name in every place they order — counter, kiosk, web, app — and the kitchen sees the name it reads fastest. You set it once alongside the item in your Peblla POS menu, not once per device.

This is not a reason to switch systems on its own. If your whole kitchen reads your menu comfortably, the field will sit empty and you will not miss it. If your team is small enough that everyone already knows every dish by sight, it solves a problem you do not have.

Where it earns its keep is the kitchen that hires cooks faster than it can teach a menu, and the room where the front of house and the back of house do not read the same language. That is a very common restaurant in this country, including many of the grill-table and Asian dining rooms we work with. More on the approach at why restaurants choose Peblla.

Frequently Asked Questions

Can a restaurant POS print kitchen tickets in a different language than the menu?

Yes, if each item can carry a second name for the kitchen. The guest-facing menu name stays as written, and the kitchen name you enter is what appears on the kitchen ticket, the kitchen display screen and the label.

Is this the same as translating my menu?

No. Nothing is translated automatically. The kitchen name is a free-text field you fill in yourself, per item, so you control exactly what your cooks read — including shorthand that is not a translation of anything.

Do guests ever see the kitchen name?

No. Guests see the menu name wherever they order — the printed menu, your website, the app, a kiosk and the server's handheld. The kitchen name only appears on the surfaces your kitchen reads: the display screen, the printed kitchen ticket and the label. The two never cross.

Do I have to set a kitchen name for every item?

No, and you should not try to on day one. Start with the items that get confused, remade, or asked about, then add the rest as you go. Items with no kitchen name simply show their menu name.

Who should decide what the kitchen name is?

Your head cook. They know which name the line already says out loud, and that is almost always the right answer — better than a formal translation written by someone who does not work the station.

What about modifiers and add-ons?

Work through them separately. A dish name in the right language with modifiers in the wrong one still stops the line, so review the add-ons that change how something is cooked before you consider the setup done.

If you want to see what this looks like with your own menu loaded, book a walkthrough and we will set a few items up with you.