Insurance for Startups & New Economy

Swish Go and the Shift From Own Kitchens to Third-Party Restaurants: Food-Safety Liability When a Quick-Delivery Food App Becomes a Marketplace

Swish is piloting Swish Go, delivering from third-party restaurants and cloud kitchens instead of only its own kitchens. That shift from manufacturer to marketplace changes the platform's product liability, recall and vendor-indemnity position, and the insurance programme has to be rebuilt to match.

Sarvada Editorial TeamInsurance Intelligence
9 min read

Listen to this article

Audio version • 9 min read

food deliveryfood safety liabilitycloud kitchensmarketplace modelproduct liability

Last reviewed: October 2026

What Swish Go changes about who cooks the food

Swish built its brand on a full-stack model: it cooks in its own kitchens and promises fast delivery from them. That model gives the company direct control over ingredients, storage temperatures, kitchen hygiene and packaging. It also makes Swish, in plain terms, the manufacturer of every meal it sells.

According to Inc42 (7 October 2026), Swish is now piloting Swish Go in select Bengaluru pincodes. Swish Go delivers from external restaurants and cloud kitchens, with no packaging and platform fees charged to the customer. The core business runs in nearly 50 pincodes across Bengaluru, Gurugram, Noida, Delhi and Ghaziabad, and the company has raised $78 million, most recently a $24 million round led by Bertelsmann India Investments.

The commercial logic of a marketplace layer is easy to see: broader menus without capex on new kitchens, and more orders through the same rider fleet. The insurance logic is less obvious and runs the other way. Once the food comes from someone else's kitchen, the platform gives up control over the hygiene that its brand still promises. The customer opening a Swish app does not distinguish between a dish cooked in a Swish kitchen and one picked up from a partner restaurant two streets away.

Manufacturer versus marketplace: how the liability position shifts

When a platform cooks its own food, the liability chain is short. A contaminated meal is the platform's product, made in its kitchen by its staff. The product liability policy names the platform as the manufacturer, the underwriter rates the kitchens it has surveyed, and a claim is answered by one insurer on one wording.

In a marketplace model the chain gets longer and the questions get harder:

  • Who is the manufacturer? The partner restaurant or cloud kitchen prepared the food, so it is the primary party for preparation defects such as undercooking, cross-contamination or spoiled ingredients.
  • Who is the seller? The Consumer Protection Act, 2019 created a statutory product-liability action that reaches product sellers, not only manufacturers. A platform that controls the listing, the price and the customer relationship will be argued to be a seller, especially where it markets the food under its own brand.
  • Who handled the food last? Delivery time, temperature in transit and packaging integrity sit with the platform's rider network. A claimant's lawyer will look at that leg first if the restaurant shows clean records.

The Consumer Protection (E-Commerce) Rules, 2020 also place duties on e-commerce entities around seller information and grievance handling. A platform that cannot quickly identify which kitchen cooked an order, and when it left the pass, will struggle to push liability back to that kitchen.

The practical point: a full-stack operator's liability is concentrated and controllable. A hybrid operator, running own kitchens and a marketplace side by side, carries both the manufacturer exposure on its own food and a contested seller and distributor exposure on everyone else's.

Why the brand stays exposed even when the kitchen is not yours

Swish Go's pitch is that customers pay no packaging or platform fee. That is a pricing decision, but it has a liability side effect. If the platform does not supply the packaging, then packaging quality, tamper evidence and labelling depend on each partner kitchen. If the platform does supply branded packaging to partners, it draws itself further into the product.

Either way, the consumer complaint, the social-media post and the regulator's first call will usually name the app. A food-poisoning cluster traced to one partner kitchen is reported as a problem with the platform. This is reputational exposure first, but it quickly becomes financial: refunds, goodwill payments, crisis communications and lost order volume in the affected pincodes.

Three features make the exposure sharper for quick food delivery than for conventional aggregators:

  1. Tight radius. A short delivery promise means a small number of nearby kitchens serve a dense cluster of customers. One bad batch reaches many households in the same pincode quickly.
  2. Speed over checks. Very short delivery promises leave little room for receiving checks such as temperature probes or seal verification at handover.
  3. Brand continuity. Running Swish Go under the Swish name blurs the line between food the company cooked and food it only delivered.

For the comparison with a full-stack setup, see our earlier post on dark kitchen and cloud kitchen insurance, which deals with the operator that owns the kitchen. The marketplace transition is a different problem because the platform's risk now depends on kitchens it does not run.

Rebuilding the product liability programme

An existing product liability policy written for a full-stack food operator is usually rated on the insured's own kitchens, turnover from food it produces and the hygiene controls the underwriter saw at survey. Adding a marketplace layer without telling the insurer creates a disclosure problem under the duty of utmost good faith and a scope problem in the wording.

The rebuild should address five points:

  • Declare the new revenue stream. Marketplace gross order value and the number of partner kitchens are material facts. Declare them at inception or by mid-term endorsement, not at renewal.
  • Check the insured capacity. Many food-business wordings define the insured as a manufacturer or processor. The schedule should also cover the platform as seller, distributor and vendor of third-party food.
  • Vendor's liability extension. The platform needs cover for claims made against it as the seller of products manufactured by others, with clarity on whether it applies only where the manufacturer is itself insured.
  • Batch and series clause. A contamination incident at one partner kitchen can produce dozens of claims. The aggregation clause decides whether that is one occurrence with one deductible or many. For a dense delivery radius, a batch clause usually works in the platform's favour.
  • Defence costs. Consumer commission proceedings can be numerous and small. Confirm whether defence costs sit inside or outside the limit.

Where the platform's own kitchens and the marketplace operate under the same legal entity, a single programme with both capacities is usually cleaner than two policies that can each point at the other.

Contamination and recall cover when the food is someone else's

Product liability pays third-party bodily injury and property damage. It does not pay the platform's own costs of pulling food off the menu, refunding orders, notifying customers or rebuilding trust after a contamination event. That is the job of contamination and recall cover, which is underwritten separately.

For a full-stack operator, a recall wording responds to contamination in the insured's own products. For a marketplace, the question is whether a contamination event at a partner kitchen triggers the platform's policy at all. Points to negotiate:

  • Trigger definition. Accidental contamination, government-ordered withdrawal and malicious tampering should each be addressed, including where the contaminated food was prepared by a listed third party.
  • First-party costs. Delisting and order-cancellation costs, customer refunds, notification and crisis-consultant fees.
  • Loss of gross profit. The order volume lost in affected pincodes after an incident, for a defined indemnity period.
  • Rehabilitation costs. Marketing spend to restore the brand after a publicised incident.

Our post on quick-commerce dark-store food-safety and recall liability covers the inventory-led version of this problem. The marketplace version differs because the platform cannot inspect the partner's storage directly, so the underwriter will price heavily on the onboarding and audit controls the platform can show.

Vendor indemnity: rewriting the partner kitchen agreement

Insurance sits behind contracts, not in place of them. When a platform onboards third-party restaurants and cloud kitchens, the partner agreement decides how much of a contamination loss the platform can recover from the kitchen that caused it. Many standard aggregator agreements are short on this point.

A workable partner agreement for a quick-delivery food marketplace should include:

  1. Food-safety warranties. A valid FSSAI licence or registration matched to the outlet address, compliance with Schedule 4 hygiene requirements under the Food Safety and Standards (Licensing and Registration of Food Businesses) Regulations, 2011, and an obligation to notify the platform of any inspection finding or suspension.
  2. Indemnity scope. An indemnity from the kitchen for claims, regulator penalties, refunds and recall costs arising from food it prepared, with carve-outs for loss caused by the platform's delivery leg.
  3. Insurance requirements. A minimum product or public liability limit carried by the kitchen, the platform added as an additional insured or indemnity to principal, and a certificate of insurance checked at onboarding and renewal.
  4. Audit rights. The right to inspect kitchens, review pest-control and temperature logs, and suspend listings without notice on a food-safety concern.
  5. Traceability. Order-level records of preparation and handover time so liability can be allocated.

The insurance requirements clause matters most in practice. An indemnity from a small cloud kitchen with no insurance and thin capital is worth little after a serious incident. Requiring partner cover, and preserving the platform insurer's subrogation rights against the kitchen and its insurer, is what turns the indemnity into recoverable money.

What FSSAI enforcement on misleading claims signals for platforms

Regulatory pressure on digital sellers of food is rising. Asia Insurance Post reported on 8 October 2026 that FSSAI issued notices to Dr Reddy's, Nestle Health Science, Amazon and Flipkart over misleading claims. The inclusion of two large e-commerce marketplaces alongside the product makers is the signal: the regulator is prepared to name the platform, not only the brand that made the claim.

For a food-delivery marketplace, the read-across is direct. Menu descriptions such as "healthy", "fresh", "homestyle", "no preservatives" or protein and calorie counts are claims. If the platform writes or edits partner menus, standardises descriptions, or promotes dishes under its own banners, it becomes harder to argue it is a neutral intermediary.

The insurance angle has two parts. First, most product liability policies exclude fines and penalties, and many exclude claims arising from advertising content. Regulatory defence costs may be available under a management liability or directors and officers policy, depending on the wording. Second, the same quick-commerce sector is still drawing capital, as shown by fulfilment startup Blitz raising Rs 28.7 crore in a pre-Series B led by IvyCap Ventures (Entrackr weekly report, 3 October 2026). Funded platforms are visible targets for both consumers and regulators, and investors may ask how a model change has been reflected in the risk programme.

A practical step: keep a log of who authored each menu claim. If partner kitchens supply their own descriptions under a contractual warranty, the platform's position on misleading-claim notices is much stronger.

A transition checklist for founders and brokers

A full-stack food startup moving to a hybrid or marketplace model should treat the change as a fresh underwriting event. A practical sequence:

  1. Map the flows. Separate own-kitchen orders from marketplace orders by revenue, pincode and kitchen count. Underwriters will ask for both.
  2. Notify current insurers before launch. A pilot in a few Bengaluru pincodes is still a material change in operations. Notify by endorsement rather than waiting for renewal.
  3. Extend the product liability wording. Add seller and vendor capacity, a batch clause and clarity on defence costs.
  4. Buy or extend contamination and recall cover so that a partner-kitchen event can trigger it.
  5. Rewrite the partner agreement with warranties, indemnity, minimum partner insurance and audit rights.
  6. Review the D&O and management liability programme for regulatory investigation cover.
  7. Test the scenario. Walk through one incident: a partner kitchen's batch makes 40 customers ill in one pincode. Who pays refunds, medical claims, defence, regulator response and lost orders, and under which policy?

The last step usually exposes the gaps. For broader context on how recall cover is built for food manufacturers, see our guide to food processing product recall insurance, and talk to your broker about structuring liability insurance for a hybrid model before the marketplace moves beyond its pilot.

Frequently Asked Questions

Does a food delivery platform carry product liability for meals cooked by partner restaurants?
It can. The Consumer Protection Act, 2019 allows product-liability claims against product sellers as well as manufacturers. A platform that controls the listing, pricing and customer relationship, or sells under its own brand, is likely to be pursued alongside the partner kitchen. The platform's policy should cover it in seller and vendor capacity, not only as a manufacturer.
Will our existing product liability policy cover Swish Go-style marketplace orders automatically?
Not reliably. Policies written for a full-stack food operator are usually rated on the insured's own kitchens and may define the insured as a manufacturer. Launching a marketplace is a material change that should be disclosed to the insurer and endorsed onto the policy, with a vendor's liability extension and a review of the batch clause.
What should a partner kitchen agreement require on insurance?
At minimum, a valid FSSAI licence or registration for the outlet, a product or public liability policy at a stated minimum limit, the platform added as additional insured or indemnity to principal where available, a certificate of insurance at onboarding and renewal, and an indemnity for claims and recall costs arising from food the kitchen prepared.
Does product liability insurance pay FSSAI penalties for misleading menu claims?
Usually not. Most product liability wordings exclude fines and penalties and often exclude claims arising from advertising content. Defence costs for a regulatory notice may fall under a D&O or management liability policy depending on its wording, so the platform should check that cover and keep records of who authored each menu claim.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform