“Northern food” or “Southern food” can help visitors place an unfamiliar dish, but a regional label does not identify the recipe or heat level of every serving. Use the region as context, then explain what your kitchen actually makes: the main ingredients, taste, side items and possible adjustments. The examples below come from Thailand Foundation's regional introductions, not a fixed rule for every cook in each area.
Northern Thailand: name the dish and accompaniments
Thailand Foundation's Northern Thai cuisine overview mentions khao soi, sai oua and nam phrik noom, as well as the role of sticky rice. For a khao soi menu entry, identify the noodles, protein, curry broth and sides served by this shop. “Northern curry” alone can suggest a rice curry rather than a bowl of noodles. See the khao soi explanation for a more specific template.
Isan: separate versions with different seasonings
The Isan cuisine overview gives som tum, larb and gai yang as examples and discusses fermented fish seasoning. Yet “som tum” does not tell a customer whether this shop's version includes fermented fish, crab, dried shrimp or peanuts. Give variations distinct names and descriptions based on the current recipe. The som tum guide shows how to ask those questions without assuming one standard plate.
Central Thailand: a regional list is not a dish description
Thailand Foundation's Central Thai cuisine article lists examples such as green curry, massaman curry and mango sticky rice. These foods differ greatly despite appearing under one regional heading. For a curry, say what protein and broth the shop serves; for a dessert, state the portion and ingredients. A regional page can introduce a category, but it cannot replace a specific menu item.
Southern Thailand: explain the actual dish's heat and ingredients
The Southern Thai cuisine overview includes examples such as khua kling, gaeng tai pla and Hat Yai fried chicken. Their methods and eating experiences are not interchangeable. If the menu says “Southern”, still describe each dish's current heat, curry paste, seafood ingredients and sides where relevant. Do not rank whole regions on a universal spice scale or promise that every dish from one region is suitable for a customer avoiding chili.
Turn regional context into a useful multilingual menu
Start with the Thai name used by the restaurant, then add one or two sentences identifying the dish type, important ingredients, sauce or broth, real spice level and accompaniments. Check allergens from recipes and supplier labels, not from a regional name. Have the cook verify the photo, price and text before translating to English and Chinese. The small restaurant menu-planning checklist helps organise these facts; the translation workflow helps keep all language versions aligned.