Indian restaurant menu design: regions, spice levels and long lists

The classic Indian restaurant menu in Europe is a booklet: eight pages, 120 dishes, every curry available with chicken, lamb, prawn or paneer, and a numbering system that runs past 200. It works for regulars who order by number and fails everyone else. Guests who do not know the cuisine order the two dishes they recognise, and the kitchen carries an inventory it cannot cook well. Here is how to shorten without losing the regulars, structure by region or by cooking method, make spice levels honest, and fit the result into a format that can be printed properly.

The list is the problem, and it is fixable

Start with your sales data. In most Indian restaurants, twenty dishes make 80 percent of the food revenue. Everything outside that list is either a regular's favourite that must stay or an item nobody would miss. Cut the second group. Then collapse the protein matrix: instead of listing korma four times, list it once with the protein options and prices on one line: "Korma, chicken 14 €, lamb 16 €, prawn 17 €, paneer 13 €". A card of 120 lines becomes a card of 45 without removing a single combination.

Keep the numbers if your regulars use them, but move them to the margin in a light grey 8 pt so they stop dominating the page. A menu that leads with 47 and 48 rather than with the food is telling the guest to look elsewhere for appetite.

Structure: region or method, not protein

Two structures work and one does not. Organising by protein (chicken dishes, lamb dishes) forces the guest to read every section to find a korma. Organising by region (Punjab, Goa, Kerala, Hyderabad) tells a story and suits a restaurant with a real regional identity. Organising by cooking method (tandoor, curries, dry dishes, biryani) is the clearest for guests who do not know the geography. For most restaurants, method is the safer choice, with a one-line note on origin in each descriptor where it adds interest.

1. Starters and street food, six to ten items, including at least two vegetarian.
2. Tandoor: kebabs and grills, with weight or piece count.
3. Curries, listed by the sauce with protein options on the line, ordered from mild to hot.
4. Vegetarian dishes as a full section of equal weight, not an afterthought: dal, sabzi, paneer.
5. Biryani and rice, breads, sides and chutneys in compact two-column blocks.
6. Desserts and drinks, including lassi and Indian beers.

A spice scale guests actually trust

Chilli icons fail for two reasons: nobody agrees what two chillies means, and they are illegible at 9 pt. Use words, and calibrate them once at the top of the curry section: "Mild: no fresh chilli. Medium: warm, balanced heat. Hot: made with green chillies, ask us if unsure." Then place the single word after each dish name in a lighter weight. If a dish can be made at any heat, say "to your taste" and leave the choice to the table.

Do not try to score heat from 1 to 5. Three levels are all a kitchen can reproduce consistently across a busy service, and three levels are all a guest can remember.

Descriptors that teach without lecturing

Each curry gets one line: the base (tomato, onion, coconut, yoghurt), the defining spice, the texture. "Rogan josh: slow-cooked lamb, Kashmiri chilli, fennel and yoghurt, deep red and aromatic" is enough. Skip the history of the dish and the word authentic, which no card has ever made true by printing it.

Breads, rice and the sharing logic

Indian food is eaten with breads and rice that are ordered separately, and guests unfamiliar with this under-order both. Put a short line under the curries heading: "Curries are served without rice; we suggest one rice or two breads between two people." Then set breads and rice in a tight two-column block right after the curries, prices at 3 to 5 €, so the eye lands on them at the moment of decision rather than three pages later.

Allergens on a long card

Regulation 1169/2011 applies to the whole card, and Indian cooking touches most of the 14 allergens: gluten in naan and in many marinades, milk in paneer, ghee and korma, nuts in korma and pasanda, mustard in pickles, sesame, celery in some spice mixes. On a card of 45 lines, the workable system is a numbered key after each price, with one legend on the back. Because sauces are shared across dishes, be honest in the key: if the base gravy contains cashew, every dish on that gravy carries the nut number.

A format for 45 to 60 dishes

Once the list is cut to 45 or 60 lines, the eight-page booklet becomes unnecessary. An A4 bifold gives four faces: a cover with the restaurant name and a paragraph about the kitchen, two inner faces for the whole food list in two columns at 10 pt, and a back face for drinks, desserts and the allergen legend. Print on 350 g matte board; laminated booklets with plastic sleeves date a restaurant faster than any dish on the list.

Typographically, resist the ornamental faces and the paisley borders. A clean serif for dish names, with Hindi or Urdu terms in the same face and a two-word gloss the first time they appear, reads as confident. Colour can carry the warmth: a deep saffron or a dark green accent on a cream page does more than any border.

Shorten first, then design

Every improvement on an Indian menu starts with the list. Cut it with your sales data, collapse the protein matrix, calibrate three heat words, put breads and rice where they are decided. Then the layout becomes straightforward, and a design that once needed eight pages fits comfortably on four faces.

In Menu Atelier you can paste the shortened list, let the layout handle the two-column curry section with protein options on the line, switch between A4 and A5 bifold in one click to see whether the card breathes, check it in 3D, and export a 300 dpi PDF with bleed and crop marks or order it printed on 350 g matte board.