Doctrine deep-dive? Trace it across statutes and judgments with LITT.
Size
0%
Lex-O-Pedia

Can a Fungal-Protein Food Be Licensed as a Proprietary Food, or Does It Need Novel-Food Approval?

When a fungal or mycoprotein product can be licensed as an FSSAI proprietary food and when it falls into the non-specified/novel-food route, how downstream products using it are licensed, and what the non-disclosure of the source organism does to the licence.

0 / 0 · 0 min left
300 wpm

A company developing a protein ingredient from a fungal source in India faces a threshold regulatory question that determines its route to market: is the product a "proprietary food", which can be licensed on a simplified, ingredient-based footing, or does it fall into the non-specified/novel-food category, which requires a full safety dossier and scientific-panel review that can take one to two years? The answer is not fixed by the fact that the ingredient is fungal. It turns on whether the specific organism already has established permissibility under FSSAI regulations. This piece works through the proprietary-food definition, how downstream products built on a licensed proprietary food are themselves licensed, the consequences of not disclosing the source organism, the fast-track and self-declaration options for market entry, and where the regulatory framework simply runs out of published guidance.

What Counts as a Proprietary Food

Proprietary food occupies a deliberately narrow space in the FSSAI scheme. Regulation 2.12.1(1) of the Food Safety and Standards (Food Products Standards and Food Additives) Regulations, 2011 defines it as:

"an article of food that has not been standardised under these regulations, but does not include novel foods, foods for special dietary uses, foods for special medical purposes, functional foods, nutraceuticals, health supplements and such other food articles which the Central Government may notify in this behalf."

The defining feature is that a proprietary food does not require prior FSSAI product approval. It operates on ingredient permissibility instead, as FSSAI's own guidance puts it: "any food product prepared using those ingredients which are either standardised or permitted to be used in standardized products does not require any separate approval. However, safety requirements as prescribed under FSS Regulations shall be complied." What the product must satisfy is a set of composition and safety conditions. Regulation 2.12.1(2) requires that a proprietary food contain only ingredients (other than additives) that are standardised, permitted for use in food products, or listed in the Indian Food Composition Tables, 2017 — and it may add vitamins and minerals only up to one Recommended Dietary Allowance of each. Additives must sit within the limits for the relevant category under Appendix A; microbiological standards must meet Appendix B, and where none are specified, the food "shall not contain any pathogenic microorganism at a level that may render the food product unsafe." The label must declare the food category and sub-category with the generic name, nature and composition. No health claim may be made "unless it is substantiated by adequate and scientific evidence", and the food business operator bears full responsibility for the safety of the product.

Two limits are worth drawing out. A product that deviates from the specification of a standardised food cannot be re-badged as proprietary — the regulation contains a proviso that "any deviation in quality parameters of a standardised food… shall not qualify the resultant product as a proprietary food." And the FSSAI Licensing Guide indicates that a proprietary food manufacturer may require a Central Licence where FSSAI has issued a No Objection Certificate for the product, which suggests some proprietary foods pass through an NOC step before licensing.

Downstream Products Built on a Licensed Proprietary Food

A recurring practical question is whether a product that uses a licensed proprietary food as one of its ingredients must itself be approved as a proprietary food. It need not. The framework is ingredient-centric: if the downstream product is composed entirely of permitted ingredients — the licensed proprietary food among them — it can be licensed as an ordinary food product under its own applicable category. A protein bar incorporating a licensed fungal-protein proprietary food would be licensed as a manufacturer of a composite or processed food under the appropriate category on the FoSCoS portal, not re-approved as a proprietary food, unless the bar itself lacks any standard and independently qualifies as proprietary under Regulation 2.12.1.

There is no provision requiring a separate proprietary-food NOC for a downstream product that uses a licensed proprietary food as an ingredient. The downstream product must instead comply with its own standard if it is standardised; with the proprietary-food requirements if it has no standard; or with non-specified-food approval if it contains novel or non-permitted ingredients. In assessing the licence, the authority looks to whether every ingredient — including the proprietary-food ingredient — is individually permitted, whether the finished product meets applicable safety standards, and whether labelling is complete. On labelling, the Food Safety and Standards (Packaging and Labelling) Regulations, 2011 require all ingredients, including a proprietary food, to be declared by name, nature and composition; there is no requirement to mark the finished product as "proprietary food" where it does not meet that definition.

The memo underlying this analysis is careful not to over-state the position: while a licensed proprietary food enters FSSAI's regulatory scope as a recognised ingredient, the regulations do not expressly classify a licensed proprietary food as an automatically permitted ingredient for every downstream use. The practical safeguard is to verify ingredient permissibility independently rather than to assume that a licence on the upstream ingredient clears it for all applications.

The Non-Disclosure of the Source Organism

Where a fungal protein is produced by a particular species, the licence application may not name the source organism — and FSSAI's proprietary-food framework does not, on its face, require it to. The regulations focus on ingredient permissibility, not organism identification, as the control point. Non-disclosure of the source organism therefore creates a regulatory gap rather than an automatic defect: the licence is granted on the finished product meeting safety and ingredient requirements, the operator carries the safety responsibility under Regulation 2.12.1(6), and there is no specific regulation making organism disclosure a pre-condition of proprietary-food licensing.

That gap is not costless. Several regulatory contexts pull the organism's identity back into relevance. If the source is a microorganism, fungus or alga not previously established as safe under FSSAI regulations, the product may fall outside the proprietary category and into non-specified food under the Food Safety and Standards (Approval for Non-Specified Food and Food Ingredients) Regulations, 2017, which demand a full dossier — formulation and ingredient specifications, a Certificate of Analysis covering chemical, nutritional, microbiological, heavy-metal, pesticide-residue and toxicant testing, and a global history of consumption. Microbiological safety is another pressure point: some Fusarium species produce mycotoxins, and an undisclosed organism leaves no documented assurance that the right controls are in place, even though the Appendix B standards still apply to the finished product. And there is an allergen dimension — cross-reactivity between certain fungi and mould allergens is documented, and the labelling regulations require allergen information to be displayed prominently, so a source organism material to allergen status is information that should reach downstream manufacturers and consumers.

The consequences run in two directions. For the licence itself, non-disclosure does not automatically invalidate it, but if the organism is later found to be novel or non-permitted, FSSAI may issue a compliance notice requiring non-specified-food approval, suspend or cancel the licence, or require fresh documentation. For downstream products, a proprietary food with an undisclosed organism is not automatically unlawful, but it carries a compliance risk (if the organism is later held non-permitted, the ingredient — and any product using it — becomes non-compliant), a label-accuracy risk where the organism bears on the product's nature or allergen profile, and a traceability risk in any food-safety incident. The sensible mitigations are to obtain independent confirmation of the organism's identity and FSSAI permissibility rather than treating the licence as validating it, to collect and hold the organism's safety data regardless of what the licence records, to consider seeking non-specified-food approval or a licence amendment to close the gap, and to pass organism and allergen information to downstream customers.

Fast-Track and Self-Declaration Routes to Market

FSSAI provides no "provisional licence" or "interim permit" for a business awaiting approval, but three faster pathways exist for eligible operators. The first is the Tatkal (instant) licensing scheme, launched under FSSAI's 2024 "Ease of Doing Business" advisory, which allows instant issuance for defined categories — importers, merchant-exporters, wholesalers, distributors, retailers, transporters and storage without atmospheric control — sidestepping the standard 60-day processing period. The trade-off is validity: a Tatkal licence "is valid for only 1 year." The second is self-declaration for petty food businesses, where under Regulation 2.1.1(3) the registering authority must consider an application within seven days, and the applicant provides a self-attested declaration of adherence to the hygiene and sanitary requirements in Schedule 4. The third, from the Food Safety and Standards (Licensing and Registration of Food Businesses) Amendment Regulations, 2026 (notified 10 March 2026), is perpetual validity: "Any License/Registration issued on or after 01.04.2026 will have perpetual validity", which removes the renewal burden entirely, alongside deemed registration for street vendors already registered under the Street Vendors Act, 2014.

None of these, however, authorises manufacture of a product still pending novel/non-specified-food approval. For a genuinely novel proprietary or fungal food, the route is to engage FSSAI's scientific panels early on documentation and timelines and to hold off manufacture until the licence or approval is granted. The Tatkal and petty-business mechanisms accelerate market entry for the business categories they cover; they do not shortcut the scientific assessment of a novel ingredient.

Where a Fungal or Mycoprotein Product Actually Lands

Fungal and mycoprotein products are not automatically novel foods. Their status depends on the specific organism, and two pathways follow. Under Pathway 1 (proprietary food), if the fungal organism is not prohibited or listed as novel, contains only permitted ingredients, does not fall into an excluded category (health supplements, nutraceuticals, or the special-dietary uses discussed below), and meets the Appendix B safety standards, the product can be licensed as proprietary food under Regulation 2.12.1 with the usual additive, microbiological, hygiene and labelling compliance. Under Pathway 2 (non-specified food), if the organism is novel or not established in Indian food use, approval is required under the 2017 Non-Specified Food Regulations, with a dossier covering formulation, a full Certificate of Analysis, global history of use and, where available, human clinical safety data — reviewed by FSSAI's scientific panels over a timeline typically of 12 to 24 months.

The distinction is squarely one of established use. Industry guidance frames it as: a proprietary food is a composite product with no FSS standard but where "every individual ingredient it contains is already on FSSAI's permitted lists", whereas an ingredient "derived from microorganisms, fungi, or algae not covered under existing FSSAI regulations" qualifies as non-specified food requiring approval. The Novel Food Regulations of 2016 treat as novel any food with "no history of safe use within the [Indian] food supply", and specifically flag ingredients "consisting of or isolated from microorganisms, bacteria, yeast, fungi, or algae" as potentially requiring novel-food approval where not established in Indian use. The most documented fungal protein, mycoprotein from Fusarium venenatum, illustrates the international variance: it has been treated as Generally Recognized as Safe by the US FDA since 2002, and in the EU the pre-1997 strain sits outside the novel-food category, while other strains may require assessment. India, by contrast, does not appear to publish a comprehensive list of approved fungal organisms for food use — which is precisely what leaves the classification uncertain for a new fungal protein.

Two further constraints matter. Some fungal-derived ingredients — certain edible-mushroom products — have their own FSS standards, and a product derived from a standardised fungus must comply with that standard rather than the proprietary route. And FSSAI has excluded Category 13 (foods for specific nutritional purposes, including infant food and foods for special dietary uses) from proprietary-food classification, so a fungal protein intended for infant nutrition, medical purposes or special dietary use cannot use the proprietary pathway at all and must seek the applicable category or non-specified-food approval.

The Gaps in the Framework

Several of the questions a fungal-protein developer most needs answered are ones the published framework does not resolve, and it is worth being candid about them. FSSAI does not expressly mandate organism-origin disclosure as a condition of proprietary-food licensing, and no public guidance was located on the documentation required or on the consequences of non-disclosure in an already-issued licence. There is no explicit interim or provisional licence for operation during regulatory review — Tatkal offers only a one-year licence, not a temporary status. FSSAI has not published a list of approved fungal organisms comparable to the EU's species list, leaving developers to determine for themselves whether their organism needs approval. Specific guidance on fungal-protein allergen testing, cross-reactivity thresholds and labelling format is not prominently available. And research located no significant Indian court judgments interpreting proprietary-food licensing disputes, so the analysis rests on the regulatory text and FSSAI guidance rather than on judicial precedent. These are genuine interpretive gaps, not settled positions, and a developer should treat them as points to clarify with FSSAI rather than assume in its own favour.

Practical Takeaways

  • Establish the source organism's status first: if it is already permitted or has established Indian food use, the proprietary-food pathway is open; if it is novel or not established, budget 12 to 24 months for non-specified-food approval and a full safety dossier.
  • On the proprietary route, obtain FSSAI confirmation that every ingredient (including any microbial source) is permitted rather than inferring permissibility from the absence of prohibition; declare the food category and sub-category precisely; hold Appendix B microbiological test records; and make no health claim without published scientific evidence.
  • For a downstream product using a licensed proprietary food, license it under its own applicable food category — not as a fresh proprietary food — but verify ingredient permissibility independently and declare the proprietary-food ingredient by name, nature and composition.
  • Do not treat a proprietary-food licence as validating an undisclosed source organism: obtain independent confirmation of identity and permissibility, retain the organism's safety data, and disclose organism and allergen information to downstream purchasers; consider a licence amendment or non-specified-food approval to close the gap.
  • For faster entry, check Tatkal eligibility (one-year licence) or petty-business self-declaration (approval in 7–30 days); and note that licences issued on or after 1 April 2026 carry perpetual validity — but neither route permits manufacture of a product still pending novel-food approval.
  • Products for infants, medical purposes or special dietary uses cannot use the proprietary pathway (Category 13 exclusion) and must take a dedicated category or non-specified-food approval.

Key Authorities

  1. Food Safety and Standards (Food Products Standards and Food Additives) Regulations, 2011, Chapter 2, Regulation 2.12.1(1)–(6) — definition, composition, additive, microbiological, labelling and health-claim conditions for proprietary food. Source
  2. Food Safety and Standards (Approval for Non-Specified Food and Food Ingredients) Regulations, 2017 — approval route and dossier requirements for novel/non-specified ingredients.
  3. Food Safety and Standards (Health Supplements, Nutraceuticals… and Novel Food) Regulations, 2016, and Direction dated 30 March 2022 — novel-food definition and treatment of microorganism/fungus/algae-derived ingredients. Source
  4. Food Safety and Standards (Licensing and Registration of Food Businesses) Regulations, 2011, Regulations 2.1.1(3) and 2.1.2, and the 2026 Amendment Regulations (perpetual validity) — petty-business self-declaration and licence validity. Source
  5. FSSAI advisory, "Launch of Provision for Instant (Tatkal) Issuance of License/Registration" (2024) — Tatkal categories and one-year validity. Source
  6. FSSAI Licensing Guide for Food Businesses, 2024 (GFI India) — licensing categorisation and the proprietary-food NOC position. Source

This analysis reflects the law as at July 2026. It is published for general information and does not constitute legal advice.

Written by Sushant Shukla
Follow the thread

Questions about this piece

AI-powered, citation-anchored. Pick a question to see the answer.

  1. 01
  2. 02
  3. 03
Powered by LITT AI · Educational explainer, not legal advice. Verify before relying.
1.5×

More in

Legal Wires

Legal Wires

Stay ahead of the legal curve. Get expert analysis and regulatory updates natively delivered to your inbox.

Success! Please check your inbox and click the link to confirm your subscription.