Food Aggregators & The FSSAI Licence Mistake
FSSAI's e-commerce directions require platforms to ensure listed restaurants and sellers hold valid licences. That compliance duty is routinely misread as requiring every marketplace to itself obtain a full food business operator licence as though it manufactures or retails food. The distinction matters for Swiggy, Zomato, Blinkit-style marketplaces and pure listing aggregators.
What the Food Safety Act actually regulates
Section 3(o) defines "food business" as any undertaking carrying on any activity related to manufacture, processing, packaging, storage, transportation, distribution and sale of food. The regulatory trigger is participation in the food supply chain as an operator touching product safety, not merely displaying third-party offers on a software platform.
FSSAI's 2018 e-commerce guidance and subsequent licensing directions distinguish:
- Marketplace / listing models that connect licensed restaurants or retailers to consumers; and
- Inventory or fulfilment models where the platform stores, packs, or dispatches food under its own control.
Only the latter category unequivocally mirrors a traditional food business operator requiring comprehensive licensing across storage and distribution nodes. A pure aggregator that does not take title, does not prepare food, and does not operate central kitchens or cold-chain hubs is a different animal, closer to an intermediary with due-diligence obligations than to a manufacturer.
What aggregators must still do
Exemption from owning a manufacturer licence is not exemption from regulation. Platforms must:
- Verify and display seller FSSAI licence numbers;
- Delist non-compliant merchants;
- Operate grievance and recall coordination mechanisms;
- Ensure packaging and labelling information shown to consumers is accurate.
FSSAI has pursued "whole supply chain" licensing rhetoric aggressively, and certain hybrid models (dark stores, private labels, cloud kitchens owned by the platform) do trigger operator licences. Over-compliance by treating every aggregator as a manufacturer, however, creates unnecessary central licences, duplicate inspections and distorted liability maps.
Our position: Pure marketplace aggregators should be regulated as intermediaries with verification duties, analogous to IT Act due-diligence frameworks, while inventory-holding and brand-owned fulfilment nodes should carry FBO licences appropriate to their physical touchpoints. Counsel must map the data room: who holds title, who controls kitchen operations, whose GST invoice issues, and where cold chain custody transfers.
Commercial implication
Wrong licensing strategy increases cost of capital, slows expansion into new states, and confuses indemnity negotiations with restaurant partners. An architecture-first compliance memo prevents founders from applying for the wrong FSSAI category and defending the wrong business model before adjudicating officers.
Takeaway
Not every food tech platform is a food manufacturer. Aggregators need compliance programmes; they do not automatically need the same licence as the kitchen. The legal test is custody, title and control, not the colour of the app icon.