Chinese Menu Guide

Chinese Food Allergy Phrase Sheet

A practical Chinese food allergy phrase sheet for diners, covering major allergens, cross-contact, shared fryer questions, sauces, broths, and emergency wording.

What this page is for

A phrase sheet should help a diner communicate risk clearly, not negotiate with the kitchen. The best wording is direct, specific, and oriented toward whether the restaurant can prepare the food safely.

This guide is deliberately specific. It is meant to help a diner, restaurant owner, writer, or menu designer make better decisions at the level where confusion usually appears: dish category, ingredient signal, kitchen workflow, service format, and customer expectation. The right answer is different for a Cantonese barbecue shop, Sichuan restaurant, dumpling house, bakery, hot pot room, noodle counter, or suburban takeout kitchen.

Cross-contact can happen through shared fryers, prep surfaces, tongs, and ladles even when the ingredient list looks safe. Packaged foods follow formal allergen-label rules, but restaurant dishes often depend on staff knowledge and recipe consistency instead of standardized labels. Sauces, broths, marinades, and garnish blends are some of the easiest places for allergens to stay undeclared on restaurant menus.

Specific signals to look for

Use the following signals as a working checklist rather than as a rigid rule. A good menu or restaurant system will make several of these visible without requiring a long conversation.

  • Opening statement: I have a severe food allergy. Can you check with the kitchen before I order?
  • Ingredient question: Does this dish contain peanut, tree nut, sesame, egg, milk, wheat, soy, fish, or shellfish?
  • Equipment question: Is this cooked in the same wok, fryer, steamer, pot, or pan as my allergen?
  • Sauce question: Does the sauce contain soy sauce, oyster sauce, sesame oil, peanut sauce, hoisin, chili crisp, or fish sauce?
  • Broth question: Is the soup or noodle broth made with pork, chicken, seafood, shrimp, dried seafood, or wheat-based seasoning?
  • Garnish question: Are peanuts, sesame seeds, fried shallots, chili oil, or crushed nuts added at the end?
  • Refusal wording: If you cannot prepare it safely, please tell me. I would rather not order it.
  • Emergency wording: If I eat this allergen, I can have a serious reaction and may need emergency medicine.

Common mistakes

Most problems come from treating Chinese food as one undifferentiated category or from separating the written menu from the kitchen that has to execute it. These are the failure points to check first.

  • Using vague phrases such as sensitive, cannot eat, or do not like may sound like preference rather than medical risk
  • Listing too many unrelated restrictions can make the highest-risk allergy less visible
  • Depending only on machine translation can create dangerous ambiguity around nuts, peanuts, shellfish, wheat, soy, and sesame
  • Showing the allergy note after the order is placed is too late for kitchens that batch sauces or use shared prep

How to use this information

The practical use depends on who is reading. Diners should use the page to ask sharper questions and build more balanced orders. Operators should use it to reduce menu friction, clarify staff training, and align the website, printed menu, delivery platform, and kitchen workflow. Writers and content editors should use it to avoid vague generalizations.

  • Write the allergen list in large print and show it before discussing dishes
  • Ask one operational question at a time: ingredient, oil, wok, broth, garnish, and sauce
  • Carry a card in English and Chinese characters if dining where English fluency may vary
  • Choose simpler dishes after the discussion rather than forcing a complex dish into a special-prep process

When the page is applied correctly, the result should be less guesswork. The diner should understand what to order, the operator should know what to highlight or simplify, and the menu should communicate the restaurant's actual strengths rather than hiding them behind generic category names.

Related guides