I was auditing a three-brand cloud kitchen in Ahmedabad when I found a chat that made my stomach drop. A customer had messaged the brand’s WhatsApp number, before ordering paneer butter masala, asking whether it contained nuts. Her son was allergic. The shift manager checked the menu, found no mention of nuts, and replied no. But the shared makhani base used cashew paste in every batch. That single message is restaurant allergen labelling failing in real time.
Nobody in that kitchen lied. Each person answered from the document in front of them, and no document mentioned cashew. The supplier invoice listed cashew paste clearly. Their recipe card only said “makhani base, 400 ml.” On Swiggy and Zomato, the listing read “rich tomato gravy with butter.” So the manager trusted the listing, and the listing was wrong.
I have seen versions of this across the 18 restaurants I managed in Gujarat and the kitchens I consult for today. The allergen information exists somewhere in the business. However, it never travels to the person answering the customer. Fixing that gap needs a system, so here is the one I use.
Why Does Restaurant Allergen Labelling Break Down in Most Kitchens?
Restaurant allergen labelling breaks down because allergen information lives in four places that never sync. Those are the supplier pack, the recipe card, the menu and your staff’s memory. Most kitchens get one or two right. The gap between them is where customers get hurt and food safety officers find misbranding.
Indian kitchens make this harder than most because allergens hide inside base preparations. Cashew paste thickens most makhani and korma gravies. Peanuts show up in Gujarati dal, poha and plenty of chutneys. Many compounded hing brands cut it with wheat flour, so a “gluten-free” dal tadka often is not.
Scale multiplies the risk. According to the NRAI India Food Services Report 2024, the organised segment is growing at 13.2% CAGR. CAGR means compound annual growth rate, the average yearly growth across a period. That growth brings more multi-brand kitchens running shared bases. When one base gravy feeds six dishes across three brands, one undeclared allergen spreads six ways.
What Do FSSAI Rules Require for Restaurant Allergen Labelling?
FSSAI’s Food Safety and Standards (Labelling and Display) Regulations, 2020 set the rules. Chains with a central licence or 10+ outlets must display calories and allergen information against menu items. Any packaged item you sell needs a full label with ingredients and allergens. Smaller restaurants are still liable if a menu description misleads a customer.
An allergen declaration means a clear statement of which listed allergens a food contains. FSSAI’s list covers cereals containing gluten, crustaceans, milk, eggs, fish, peanuts, tree nuts and soy. Sulphites also count once they cross 10 mg/kg. You can read the current text on the FSSAI food safety and standards regulations page.
FSSAI has amended these regulations and pushed some enforcement dates more than once. Check the latest notification before you reprint a menu. Meanwhile, the Food Safety and Standards Act, 2006 allows a penalty of up to Rs 3 lakh for misbranded food. The fine is the smaller cost, though. A hospital visit and a screenshot on Instagram cost far more.
What Do Other Markets Already Require?
Other markets are further ahead. When I worked in restaurant operations in Germany, our menus carried small letter codes beside each dish. Those codes mapped to the 14 allergens that EU Regulation 1169/2011 on food information to consumers requires restaurants to disclose. Servers answered allergen questions in seconds because the menu answered them first. The UK also tightened rules on prepacked food through Natasha’s Law in 2021.
Packaged items follow stricter rules than plated food. If you sell bottled green chutney or sealed tins of gulab jamun, those are prepackaged food. They need ingredients, an allergen declaration, the FSSAI logo, your licence number and date marking. This matters more as operators chase quick commerce and 10-minute delivery with retail-style products.
The Recipe-to-Label Chain: Four Links Every Allergen Passes Through
The Recipe-to-Label Chain is a four-link system that traces every allergen from the supplier pack to the answer your staff gives a customer. The links are Supplier Spec, Recipe Card, Menu Declaration and Staff Answer. If any link holds different information from the one before it, the chain is broken.
Treat each link as a handover. Information passes from supplier to recipe, recipe to menu, and menu to staff. Every handover is a chance to lose an allergen, so every handover needs a check.
Link 1: Supplier Spec
Supplier Spec means the ingredient and allergen list printed on every packaged product you buy. You do not control what goes into readymade gravy pastes, mayonnaise or soy sauce. Mayonnaise carries egg. Soy sauce usually carries both soy and wheat. Photograph the back label of every packaged input and store it in one shared folder. When a supplier switches brands, replace that photo the same day.
Link 2: Recipe Card
The recipe card must carry allergens forward from every sub-recipe. A sub-recipe means any preparation used inside other dishes, like a makhani base, green chutney or tadka. Most recipe cards I audit list “base gravy” as one line and stop there. If you already map recipes in Petpooja or Posist for inventory, you have done half the work. Add allergen columns to that mapping, even in a simple spreadsheet, so they flow upward.
Link 3: Menu Declaration
Menu Declaration covers every place a customer reads about your food. That includes the printed menu, the QR menu, your aggregator descriptions and delivery stickers. These drift apart because different people update them at different times. The fix is an allergen matrix. An allergen matrix means one grid with dishes in rows and allergens in columns. Every customer-facing menu pulls from that grid. So when you next revise prices using the psychology and math of menu pricing, update allergens too.
Link 4: Staff Answer
Staff Answer is the weakest link because the people holding it keep changing. With the restaurant staff turnover crisis hitting kitchens hard in 2026, allergen knowledge walks out with every resignation. So the rule is simple. Nobody answers from memory. Staff say “let me check the allergen chart” and point to the laminated matrix at the pass.
Your team also needs to understand cross-contact. Cross-contact means an allergen reaching a dish through shared oil, equipment or hands. If your onion pakoras and fish fry share a kadhai, staff must say so. An honest “we share the fryer” protects the customer and protects you.
How Does the Recipe-to-Label Chain Work in a Real Cloud Kitchen?
In a multi-brand cloud kitchen, run the chain backwards from each shared base. Tag the allergens in every base first. Then trace each dish that uses that base across every brand. In the Ahmedabad kitchen, the cashew gravy sat under dishes on all three brand menus, and none declared it.
Here is the sequence I run with clients. Follow it in order, because each step feeds the next one.
- List every base and sub-recipe: gravies, marinades, chutneys and batters.
- Pull the supplier label for every packaged input used in those bases.
- Tag each base against the FSSAI allergen list.
- Map every finished dish to its bases, then add its direct allergens.
- Update the master matrix, then every menu, listing and sticker from it.
- Brief every shift and laminate the matrix at the pass.
For a kitchen with a few dozen dishes, steps 1 to 4 usually take a couple of working days. Updating the aggregator listings is the quickest part. Shared bases are a big part of why cloud kitchen profitability often beats dine-in. They are also where one mistake multiplies fastest. Laminating the final matrix costs a few hundred rupees.
Which Decision Does the Chain Help You Make?
The chain tells you, dish by dish, whether to declare, separate or remove an allergen. Declare it when the allergen defines the dish. Separate it when only some customers want it. Remove it when it adds little flavour but real risk.
Cashew in shahi paneer or korma gets declared, because removing it changes the dish. Peanuts sprinkled on poha can go in a small side cup instead. Compounded hing in a dish you call gluten-free should switch to pure hing, or the claim should go.
The chain also settles growth decisions. Before you launch a new brand on an existing base, run that base through all four links. Crossing 10 outlets or moving to a central licence triggers calorie and allergen display duties. Build that into any plan for restaurant scaling with discipline.
Compliance gaps rarely sink a restaurant alone. But they stack on top of the cash and staffing problems behind why 70% of restaurants fail in their first year.
Five Facts to Pin on Your Kitchen Wall
Print these and stick them near the pass. They are the shortest version of everything above.
- Allergens hide in bases: cashew in makhani, peanut in chutneys, wheat in compounded hing.
- FSSAI’s 2020 Labelling and Display Regulations put calorie and allergen display duties on chains with a central licence or 10+ outlets.
- Packaged items you sell need full labels, including an allergen declaration and your FSSAI licence number.
- The Recipe-to-Label Chain has four links: Supplier Spec, Recipe Card, Menu Declaration and Staff Answer.
- Staff answer allergen questions from the written matrix, never from memory.
Can Your Restaurant Allergen Labelling Survive a Two-Minute Test?
Here is the diagnostic. Pick any dish from your Swiggy listing and ask whoever is on shift which allergens it contains. When they answer within two minutes, from a written source, and the answer matches the recipe card, your chain holds. Anything less means you have found your broken link.
This week, pick your five best-selling dishes. Pull the supplier label for every packaged input inside them, including the bases. Build the matrix for those five dishes only. Then compare it line by line with your aggregator descriptions and fix every mismatch before Sunday.
Stop guessing. Start building. Get Design Dine Dominate, the complete restaurant business playbook from someone who has actually done it.
Leave a comment