For millions of consumers navigating India’s hyperlocal food delivery ecosystems, the rating system is the ultimate shield against a bad meal. If a restaurant delivers cold food, uses poor ingredients, or messes up an order, a scathing 1-star review serves as both a penalty to the merchant and a warning to the community.<\/p>\n\n\n\n
However, an eye-opening investigative report has pulled back the curtain on a massive loophole in the platform economy. As it turns out, a bad restaurant never actually has to fix its food or watch its business die.<\/sup> It just needs a new name.<\/p>\n\n\n\n An in-depth analysis by tech publication Entrackr<\/em> has detailed how single cloud kitchen operators are successfully exploiting onboarding vulnerabilities to stream identical operations under entirely different restaurant storefronts simultaneously, effectively turning the platform’s review architecture completely useless.<\/sup><\/p>\n\n\n\n The investigation caught a single physical kitchen operating up to five distinct storefront identities at the exact same time on the app.<\/sup> To the average user scrolling through their feed in search of variety, these appear to be separate, competing establishments. In reality, the backend logistics tell a deeply deceptive story.<\/p>\n\n\n\n Consider a consumer who orders from a local Chinese storefront, receives a subpar, unhygienic meal, and leaves a well-deserved 1-star warning. The next week, consciously avoiding that specific spot, the consumer spots a fresh listing with a catchy name like “Crispy Crunch Momos”\u2014complete with a flawless, reset rating profile and zero negative history.<\/sup><\/p>\n\n\n\n They place the order, only for the food to be cooked in the exact same kitchen, by the exact same staff, using the exact same ingredients.<\/sup> The user\u2019s primary consumer protection tool\u2014their review\u2014has effectively been launderd out of existence by a simple cosmetic rebrand.<\/p>\n\n\n\n The most alarming aspect of this duplicate storefront phenomenon is that it occurs right under the nose of regulatory compliance protocols. To list a food business on any major delivery platform in India, a merchant must provide a valid Food Safety and Standards Authority of India (FSSAI) registration number.<\/p>\n\n\n\n Because the FSSAI number is a completely unique institutional identifier, a basic automated de-duplication check should instantly flag any attempt to register a second, third, or fourth storefront using identical credentials at the same geographical coordinate.<\/sup> Yet, these copycat profiles continue to clear verification and go live simultaneously.<\/p>\n\n\n\n Industry experts point out two troubling possibilities for how this happens:<\/p>\n\n\n\n The financial motivations for cloud kitchens to multiply their digital identities are directly tied to how delivery algorithms operate. When a kitchen is buried under a wave of negative 1-star reviews, its aggregate rating plummets, causing the platform\u2019s recommendation engine to suppress its organic visibility.<\/p>\n\n\n\n By spinning out a completely fresh, duplicate storefront, the operator accesses a highly lucrative “reputation reset.”<\/sup><\/p>\n\n\n\n While food aggregators continue to post robust structural volume gains\u2014with Swiggy’s recent financial reports showcasing an impressive 22.6% year-on-year jump in its Food Gross Order Value\u2014this listing vulnerability poses a significant long-term threat to consumer trust. If the gatekeepers of the digital food economy cannot guarantee that different names represent different kitchens, the entire rating framework risks becoming a cosmetic illusion.<\/p>\n","protected":false},"excerpt":{"rendered":" For millions of consumers navigating India’s hyperlocal food delivery ecosystems, the rating system is the ultimate shield against a bad meal. If a restaurant delivers cold food, uses poor ingredients, or messes up an order, a scathing 1-star review serves as both a penalty to the merchant and a warning to the community. However, an […]<\/p>\n","protected":false},"author":2,"featured_media":202,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-412","post","type-post","status-publish","format-standard","has-post-thumbnail","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/posts\/412","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=412"}],"version-history":[{"count":1,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/posts\/412\/revisions"}],"predecessor-version":[{"id":413,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/posts\/412\/revisions\/413"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=\/wp\/v2\/media\/202"}],"wp:attachment":[{"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=412"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=412"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/voice.lapaas.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The Ghost Mirror: One Kitchen, Five Identities<\/h2>\n\n\n\n
How the Onboarding Loophole Bypasses Security<\/h2>\n\n\n\n
\n
The Algorithmic Incentive of a Reputation Reset<\/h2>\n\n\n\n
\n