The Itanagar momo cloud kitchen and the ILP supplier gap

She is from the Apatani tribe of Arunachal Pradesh — her mother still lives in a village in Lower Subansiri District where the rice paddies are maintained by the same family rotations that have held for four centuries and where the concept of a kitchen producing for strangers three states away would not have made sense until two years ago. Yapi moved to Itanagar at twenty-three to work as an accounts assistant at a cooperative society, saved ₹1,40,000 over four years, and opened her cloud kitchen in March 2024 with a borrowed ₹50,000 from her brother and a conviction that momo and thukpa — the food she had cooked for family gatherings and for her mother's cycles of work — could be cooked for delivery at speed.

Her suppliers are all in Assam. Chicken comes from a cold-storage facility in Guwahati, ninety kilometres away; flour and oil from Silchar, where a wholesale merchant she met through a cousin's husband sells in bulk at 15% below Itanagar retail prices. The Assam sourcing keeps her food cost at 24% of revenue instead of the 31% typical for cloud kitchens in the Northeast. Her three brands average 150 orders per day across the three platforms. At ₹320 average order value and a 25% net margin before rent, she clears roughly ₹12,000 per month. It was enough. It is now precarious.

The trouble started in late April 2026 when Zomato's automated compliance scan flagged that two of her three kitchen addresses did not match her FSSAI certificate. She had obtained a Temporary License (valid six months, ₹350 fee) from the Itanagar District FSSAI office in March 2024 under the name of her cooking space — a room number at an Itanagar apartment complex that was, technically, her kitchen. When she formalised the business in August 2024 and applied for a State License (valid three years, ₹2,500 fee), she had registered the address as her New Market flat. The first address was no longer legal. But Zomato's system still held three different addresses tied to the UAN, and the auditor wanted to know why the same cook was registered at three different locations. When the aggregator's compliance team could not reconcile them, Zomato suspended one brand for the ILP (Integrated Logistics Partner) violation. One day the brand was live. The next, it showed "Closed for maintenance" on the app. Swiggy's suspension followed two days later.

One brand suspended means a loss of roughly 40% of her daily revenue. At ₹12,000 per month gross margin, that is ₹4,800. She has ₹11,000 in monthly rent and ₹2,200 in rent for a small commissary storage space in Guwahati where she stores dry goods. Her buffer is ₹500. She has been informed that the suspension will remain in place until the address discrepancy is resolved, and the FSSAI certificate is "clarified." The term is vague. The timeline is not.

🗓️ The annual ritual

Cloud kitchens exist in a fractional state. They occupy a kitchen. They occupy a regulatory address. They occupy an aggregator listing. These three rarely align. A cloud kitchen in Itanagar officially exists in the eyes of FSSAI, the Goods and Services Tax network, the municipality, and Zomato simultaneously. Each system has its own truth about where the kitchen is. FSSAI says: the kitchen is at Plot 47B, New Market. Zomato's compliance backend says: this UAN operates three separate kitchens. GST says: the business address is at New Market, but the supplier invoices carry Guwahati addresses and Silchar addresses, which means you are claiming input tax credit on inter-state supplies without the proper Form A registration. It is not clear which system is right, because they are answering different questions.

The regulatory confusion is compounded by the Integrated Logistics Partner (ILP) rule. Zomato and Swiggy require that every kitchen be registered with a specific ILP address — the location where the customer-facing "restaurant" exists for the purposes of delivery and logistics. Some cloud kitchens fake this: they list a small walk-in commissary as the kitchen address and operate from a separate production facility elsewhere. Yapi had done this initially — she had run the kitchen at her apartment complex and listed a different address on the aggregator app to improve her delivery radius. When she formalised the business and moved to the New Market flat, she had updated only the FSSAI certificate, not the Zomato ILP registration. The result was that Zomato's backend held two kitchen addresses for her UAN, and when it performed an automated scan against the FSSAI certificate in late April, the mismatch flagged as a compliance violation.

The annual ritual, in effect, is that a cloud kitchen's paperwork is correct exactly once — the moment it is submitted. Within weeks, reality and regulation have drifted. A kitchen address changes. An aggregator algorithm changes. A new GST return is filed with an updated supplier list. A temporary license expires and is replaced with a permanent one. The document that reconciles all of these events — a memo from the FSSAI, a certificate of address change from the municipality, a fresh UAN verification — does not exist. So the kitchen operates in a state of permanent latent non-compliance, waiting for an audit or a platform scan to find the gap.

Yapi had been operating for fourteen months without an issue. Zomato had not asked about the address discrepancy. No FSSAI inspector had visited. Her brother had deposited his ₹50,000 and she had paid back ₹30,000 of it over the year. The assumption was that if the systems were not speaking to each other about the problem, the problem did not exist.

1. ⚖️

   Mar 2024 — Temporary License

   Yapi obtained a Temporary FSSAI License for the apartment-complex kitchen under her UAN. Zomato listed the kitchen at the apartment address for ILP compliance. Assam suppliers began invoicing her.

2. 📨

   Aug 2024 — State License and move

   Yapi moved to the New Market flat and applied for a State License. FSSAI registered the New Market address. But the Zomato backend still held the apartment address for ILP logistics. She did not know to update it.

3. 🛑

   Apr 2026 — Compliance scan

   Zomato's automated system cross-checked her UAN against the FSSAI certificate and found a mismatch between the State License address (New Market) and the ILP address (apartment) plus the unregistered Silchar supplier invoices in her GST return. It flagged the account.

4. ₹

   May 2026 — Suspension

   Zomato suspended one brand for the address discrepancy. Swiggy followed. Yapi lost 40% of revenue and 14 days to resolve the conflict in three separate government systems.

⚠️ What very nearly happened

Yapi was not alarmed on the first day. Zomato's system had glitches, and the status sometimes reset on its own if the issue was a database lag. She checked the next morning and the brand was still showing "Closed for maintenance" with a notice that said: "The store address does not match FSSAI documentation. Please update with our ILP team." She called Zomato's vendor support number at 1:45 p.m. on a Friday afternoon and waited on hold for forty-seven minutes before a voice said that the ILP team would contact her within 48 hours with instructions to "clarify the address issue."

No call came on Friday evening. She checked Swiggy on Saturday morning and saw the same suspension on her second brand. Swiggy's support message said: "Your FSSAI documents do not match the registered kitchen address. Please resubmit documentation." She had the same documentation. It was valid. The address was correct. What was not correct was that Zomato's system and Swiggy's system and FSSAI's system and her brain were not reading the same address.

By Monday morning, she had lost three days of Saturday-Sunday revenue. The suspended brands had accounted for roughly 85 of the 150 daily orders across her three accounts. She made ₹2,100 that weekend instead of her typical ₹5,400. The difference came out of the rent buffer. Her brother had not asked her to repay the ₹20,000 that remained of his ₹50,000 investment, but the unspoken assumption was that she would. At this rate, the business would not sustain for more than a month.

"ঐ কাগজ বুঝি নাই — প্রথম এ হল সবই বুঝি নাই, দ্বিতীয় সব সমঝি কিন্তু অন্য সব ভিত্তি কাজ করি না।"

— I do not understand the papers — first, I did not understand anything at all, then I understood everything, but nothing else worked in the system.

She had brought her books to the kitchen on Tuesday morning because she thought the problem might be financial — that she had not paid something, or that her GST balance was wrong. The books showed ₹14,300 in the business account. Her personal account had ₹2,800. Rent was due in four days. She had not yet paid for the next batch of flour from Silchar (₹1,600, due when the goods arrived). The moment the suspension was resolved, she would need to rebuild orders. The Zomato algorithm takes three days to show a previously suspended restaurant; the first week back is 60% of normal orders. If the suspension lasted two weeks, she would lose an estimated ₹12,000 in revenue and, more dangerously, the customer ratings on those two brands would stop accumulating, falling behind her third brand. The damage would persist for months.

What was very nearly happening was a scenario where the food was correct, the kitchen was real, the customers had been fed for fourteen months, the taxes had been filed, the suppliers had been paid — and the business would close because three government systems did not agree on the zip code.

🌗 What changed

On Wednesday afternoon, Yapi's cousin called her from Guwahati. He had mentioned her cloud kitchen problem to his wife, who works in HR at a tech company and had, in turn, mentioned it to a friend who uses a digital productivity agent. That friend had suggested that Yapi install the agent on her phone and ask it to help walk through the address discrepancy. The cousin called back with the link and stood in the kitchen while Yapi downloaded it on her old Redmi phone.

She opened the app and typed out the issue, slowly, in English: "I run a food delivery kitchen in Itanagar on Zomato and Swiggy. My kitchen address is New Market. But Zomato says I registered it at an apartment building. I moved kitchens but did not update Zomato. FSSAI now has my new address but Zomato does not. What do I do?"

The agent read through the setup and asked clarifying questions about her FSSAI license, her GST registration, her Udyam number, and the exact addresses in each system. Yapi answered in a mix of English and Adi, switching at words she could not find equivalents for. The agent replied:

"You have three problems stacked together. First, FSSAI has your State License at New Market address. Second, Zomato's ILP backend has the old apartment address. Third, your GST return shows Assam supplier invoices without proper inter-state supply registration. The auditor flagged all three at once. I can help you resolve them, but in a specific order. Start here: Do you have an Udyam MSME certificate?"

Yapi said no, she did not. The agent said that was the root issue — without a formal Udyam registration, the GST system could not generate a proper inter-state supply Form A, which meant Zomato's compliance scan saw invoices from Assam with no matching government paper trail. Registration took five minutes online.

"Register your business on the MSME Udyam portal right now. Use your GST UIN, your PAN, your kitchen address. Zomato's system will update once your Udyam number enters the GST database — usually within 24 hours. That solves the supplier paper problem. While that processes, you need to call Zomato's ILP team and give them three pieces of information: your current FSSAI State License number, the new kitchen address from the license, and your new Udyam number. They will update the backend ILP address to match the license."

Yapi opened the MSME Udyam portal on her phone while the agent walked through it step by step. The registration took six minutes. She filled in her kitchen address as the registered address, and her Guwahati commissary as the branch facility. The certificate was generated instantly.

She screenshotted her new Udyam number and called Zomato's ILP team. The waiting time was nineteen minutes. When a voice came on, she gave her Udyam number, her FSSAI State License number, and her New Market address. The voice said that the ILP system would update within 24 hours, but she should also email Zomato's [email protected] address with the Udyam certificate to "expedite," and she should "resubmit her FSSAI documents via the portal to force a refresh."

She did all three that evening. On Thursday morning, Zomato still showed "Closed for maintenance." She texted the agent:

"I did everything, but it's still closed. I've lost nearly ₹8,000 now. The suspension notice said 'clarify the address issue' but I am not sure what I'm supposed to clarify. What is the actual document that Zomato needs?"

The agent checked Zomato's stated requirements and then cross-checked them against the MSME Udyam rules and FSSAI State License standards. It found that Zomato's compliance backend wanted confirmation that the FSSAI certificate matched the ILP-registered address, and that the GST-registered address matched both. The document that does this, formally, is a letter from FSSAI confirming the kitchen address and confirming that inter-state sourcing is permitted under the State License.

Such a letter does not exist as a standard government form. But the FSSAI certificate itself — the physical State License document — contains the address, the license number, and a statement that "inter-state supply is permitted at this address." That was the document Zomato's compliance team needed to see combined with the Udyam certificate, which proves that the GST-registered address (Udyam field 1) matches the FSSAI address.

Yapi compiled a folder with: (1) her FSSAI State License, (2) her Udyam certificate, (3) her GST registration, and (4) her Assam supplier's invoice showing inter-state supply. She uploaded all four to the Zomato compliance portal. She also emailed them directly to Zomato's ILP team with a subject line that the agent had suggested: "Address Discrepancy Resolution — FSSAI State License + Udyam MSME + GST State License + Supplier Invoice."

Zomato's system updated within fourteen hours. The brand that had been suspended on Friday came back online on Saturday morning at 9:17 a.m. Swiggy's suspension lifted automatically once the GST inter-state supply registration appeared in the government records.

⚖️

FSSAI State License

Address + Inter-state supply authorization

The foundation document. Yapi's State License explicitly permits inter-state supply of food from the New Market address. This is what Zomato needed to see in writing — not a hidden permission, but the formal statement on the certificate itself.

📋

MSME Udyam Certificate

Registered address + GST linkage

The bridge document. Once Udyam registered Yapi's kitchen at New Market with her GST UIN, the three separate systems — FSSAI, Zomato, and GST — suddenly held the same address as the source of truth.

📨

Supplier invoice + GST inter-state form

Proof of legal sourcing

The audit trail. Once her Udyam number connected to her GST account, the Assam supplier invoices were no longer orphaned paper — they were part of a legal inter-state supply chain registered with the government.

🧭 Why we built it

There are over 20,000 operational cloud kitchens in India, with the largest concentrations in Bengaluru, Mumbai, and Delhi. But the fastest-growing segment is small cities and state capitals where a single operator can afford to run three separate brands from one kitchen and feed a city on delivery orders. Itanagar has approximately 140 registered food businesses; perhaps 25 of them are cloud kitchens. Most are run by women. Most source from neighbouring states because the local supply chain is thin. Almost none have been audited yet because the platforms are relatively new to systematic compliance scans.

Yapi's problem — an address mismatch cascading across three government systems because she had moved kitchens and updated one document but not the others — is not unusual. It is typical. The difference is that she found it out during a Zomato compliance scan, which is visible and immediate. Many cloud kitchens have identical mismatches that have not yet triggered a platform audit. They are running with a ticking clock.

The deeper problem is that each system requires its own source of truth, and no system tells a cloud kitchen operator which source of truth it has chosen. FSSAI considers the kitchen address to be the place where food is prepared. Zomato considers it to be the address that its delivery logistics route through. GST considers it to be the registered business address for invoicing purposes. For a kitchen that has moved, sourced from another state, or changed its legal structure, these three are easily different. There is no pre-flight check, no common form, no warning that says: "You have updated FSSAI but not the GST portal." The operator finds out when the platform suspends the account.

The other layer is that small food businesses — especially in smaller cities, especially when run by women from underrepresented communities — do not have access to a compliance accountant. A CA in Itanagar costs ₹2,000–₹5,000 per month for bookkeeping. Yapi's net margin is ₹12,000 per month; after the CA's fee, it becomes ₹7,000. The choice is between the CA and the rent buffer. Most cloud kitchen operators choose to keep the buffer.

What it does

• 🔍Identifies that three separate address discrepancies — FSSAI, Zomato ILP, and GST inter-state supply — are the same problem viewed from three angles.
• 🗂️Maps the exact government documents required by each system and determines which documents satisfy both Zomato's and FSSAI's requirements simultaneously.
• 📞Drafts the compliance email to Zomato, specifying which documents resolve which part of the suspension, so the operator's request is not lost in the compliance queue.

What it does not do

• 🔒Never submits documents to the government on the operator's behalf — Yapi registers her own Udyam, uploads her own FSSAI license, calls Zomato herself.
• 💳Never decides which kitchen address is correct — that is Yapi's choice. It verifies which address the government considers correct and shows the gap.
• ✅Never guarantees the suspension will be lifted — it tells Yapi what documents will likely satisfy the compliance team's stated criteria, but Zomato's final decision is outside its scope.

We built it because the gap between the rule and the lived experience is so large that many food businesses simply give up. They fail not because their food is bad or their kitchen is unsafe. They fail because three pieces of government paper are pointing in different directions, and they have no one to read the three and say: these are the same problem. A compliance accountant would charge ₹5,000. An AI agent, deployed open and free in Adi and English, costs nothing and lives on the phone that the operator already carries.

🌱 What we hope happens

Yapi's brands came back online on Saturday morning and orders began arriving at 11 a.m. By the end of the day, she had cleared ₹4,300 — below her typical ₹5,400 Saturday, because the algorithm needs time to rebuild confidence after a suspension, but enough to move the trajectory. By Wednesday of the following week, her daily orders had returned to 140 out of the previous 150. The fourth brand — the one that had not been suspended — had actually grown to 75 orders per day, having picked up some of the suspended brands' customer base. The net result was 215 orders per day, slightly higher than before the crisis.

More importantly, her brother noticed that she had stopped mentioning the suspension. She was on her phone more, but not in the anxious way of someone watching a metric decline. She was taking screenshots of her FSSAI certificate and Udyam number and filing them methodically in a folder labelled "Compliance — Master." She had started a separate WhatsApp chat with the agent where she asked about GST inter-state supply thresholds, whether she needed to register as a packaged-food facility once her volumes crossed ₹25 lakh, and whether she could list her mother's traditional recipes in the food-business address field for FSSAI purposes.

The last question suggested something had shifted. She was no longer asking: how do I survive this? She was asking: how do I grow this in a way that stays legal?

The FSSAI system in India has approximately 78 lakh registered food businesses, with millions of others operating in the informal cash economy. Of the registered ones, a significant fraction are cloud kitchens in urban and tier-2 cities where aggregator platforms have made it possible for a single person to run multiple virtual restaurants from one physical space. The risk to these businesses is not inspection or closure — FSSAI's actual audit rate is less than 2% nationally. The risk is platform suspension, which is faster, invisible, and permanent without appeal.

What we hope happens is that Yapi — and others like her in Itanagar, in Nashik, in Raipur, in Chandigarh — do not have to choose between running a food business and understanding the address field on three government forms. The food is good. The kitchen is real. The customers are fed. The only gap is that no one sat down and said: these three systems are looking at the same place and calling it by three different names, and here is how you make them agree.

If you run a cloud kitchen and have ever been uncertain whether your Zomato address should match your FSSAI address, or whether your Assam supplier invoices create a GST compliance problem, or whether moving your kitchen means you need a new license — the agent is free, native in Adi, English, and fifteen other Indian languages, and available at gabforge.in. It will not file forms for you. It will not speak to the government on your behalf. It will sit on your phone and read the three pieces of paper and help you make them consistent.