Maharashtra Wants Swiggy, Zomato, Blinkit and Zepto Licensed Like Bike Taxis

On 8 August 2026, The Indian Express reported that Maharashtra's transport department has proposed amendments to the Maharashtra Bike-Taxi Rules, 2025 that would bring Swiggy, Zomato, Blinkit and Zepto inside a state transport framework, with the draft sent to the State Law and Judiciary Department. Business Standard carried the same development the same day. ABP Live's follow-up on 9 August 2026 summarised the package as a 2 per cent welfare levy, an insurance obligation and an electric fleet requirement.

Three obligations sit in the reporting, each landing on a different line of a platform's risk register:

1. Licensing of delivery aggregators under a state transport rule rather than a labour or commerce statute.
2. An electric-only fleet mandate for the two-wheelers doing the delivering.
3. A rider welfare levy of 2 per cent per ride, plus an obligation to provide insurance cover to riders.

The important word in that list is licensing. A state transport authority issuing a permit to a delivery platform asserts that the platform runs a transport service. Every other clause follows from that assertion, including the insurance one, and so does the question of whether the vehicles doing the work are validly insured today.

Delivery-platform regulation is discussed at the level of the platform. Insurance is priced at the level of the vehicle and the rider, and the gap between those two units is where the cost sits.

Moneycontrol reported on 22 July 2026 that Blinkit was running over 2,400 dark stores and 36 lakh daily orders in Q1 FY27. That is one platform nationally, and Maharashtra is one of its largest slices. Whatever share of those orders is fulfilled from Mumbai, Pune, Nagpur, Thane and Nashik, the rider count behind it runs into five figures in the state alone, and the same arithmetic repeats for Swiggy Instamart, Zomato and Zepto.

A transport licence attaches to vehicles and to the permit holder. Three procurement consequences follow:

• Vehicle-level record keeping becomes an insurance input. A licensing authority that registers vehicles under a platform permit creates a state-verified list of which two-wheelers are doing platform work. Underwriters have not had that list before, having priced delivery fleets off platform-supplied schedules.
• The insurable population becomes countable. A 2 per cent per-ride levy is computed from ride counts the state can audit. Once ride counts are auditable, so is exposure.
• The 3PL layer becomes the compliance layer. Most quick commerce riders in Maharashtra are engaged through third-party logistics vendors and fleet partners, and those vendors hold the contracts with riders and often with vehicle lessors.

The corpus post on quick commerce rider fleet insurance sets out how the motor, personal accident and liability layers already stack for these fleets. What the Maharashtra draft changes is who the counterparty is on the top layer.

The first argument platforms will make against a transport licence is definitional, and it is not a weak one. Swiggy, Zomato, Blinkit and Zepto do not own, register, insure or maintain the two-wheelers, and in most engagement structures they do not employ the rider either. The vehicle belongs to the rider or to a fleet partner, and the rider is contracted through an intermediary.

A transport rule licensing "aggregators" of delivery services has to define the licensable activity so that it reaches an entity owning none of the assets. The state has a workable answer, since aggregator definitions already exist in the Motor Vehicles (Amendment) Act, 2019, which brought digital intermediaries connecting passengers with drivers into the licensing perimeter without requiring them to own vehicles. Extending the same logic from passengers to parcels is a short step in drafting and a long step in consequence.

Risk managers should plan for the version where the escape hatch fails. Three positions worth taking before notification:

• Map which entity would hold the licence. If the permit sits with a 3PL vendor, the insurance obligation and the levy sit there too, and the platform's exposure converts into a contractual indemnity and a vendor-solvency question.
• Read the existing 3PL contracts for who bears a new statutory cost. Most delivery-vendor agreements are priced per order and are silent on levies introduced mid-term. A 2 per cent per-ride charge with no allocation clause becomes a renegotiation, or a dispute.
• Check whether vendor-held cover names the platform. A rider-side policy bought by a fleet partner does nothing for the platform's own vicarious exposure unless the platform is an additional insured or the wording extends to its liability.

The national coverage reported the insurance clause and moved on. The identity of the issuing authority changes what the obligation is.

Under the Code on Social Security, 2020, an aggregator's obligation to gig workers is a contribution obligation. The aggregator pays a percentage into a fund and the fund provides benefits. The platform buys nothing and holds no policy, and compliance is demonstrated by a remittance receipt.

A transport rule works differently. A licensing authority conditions a permit on the holder maintaining cover and verifies compliance by inspecting a policy document at issue and at renewal. That converts a fiscal obligation into a procurement obligation, and raises four questions the reporting does not answer:

1. Whose life and limb is covered? Rider personal accident, third-party liability arising from the rider's riding, or both. These are different policies with different insurers and different claims paths.
2. What minimum sum insured? A permit condition without a stated figure is unenforceable in practice, and a stated figure sets the market price overnight.
3. Who is the policyholder and who is the beneficiary? A master policy held by the platform covering riders it does not employ is a group personal accident construct that needs an insurable-interest basis the insurer is comfortable defending.
4. Does the cover run with the rider or with the vehicle? Riders in this sector work across platforms in a single day. Cover attached to a rider is portable and duplicative. Cover attached to a licensed vehicle is neither.

The third question is the one that decides whether a claim gets paid. Group personal accident wordings written for employees carry an employment nexus in the definition of an insured person and an insurable interest basis that follows from it. Adapting them to independent riders engaged through a 3PL requires an endorsement naming the engagement structure precisely.

The draft revives a question the Indian delivery sector has left unresolved for a decade.

A two-wheeler registered for private use, carrying an ordinary private-car-and-two-wheeler package policy, is being used to carry goods for hire and reward. Section 66 of the Motor Vehicles Act, 1988 requires a permit for a transport vehicle used in a public place for hire or reward, and registration category determines whether a vehicle is a transport vehicle. Insurers have long argued in claims that goods-carriage use on a private registration is a breach of the limitations-as-to-use clause in the policy schedule.

Section 149 of the Motor Vehicles Act, 1988 obliges the insurer to satisfy a third-party award notwithstanding most policy breaches and then recover from the insured. The injured third party is generally paid. The rider, and behind the rider the fleet partner and the platform, carries the recovery. Own damage on the rider's own vehicle sits outside that protection entirely.

A state transport rule removes the ambiguity this arrangement has depended on. Once a state defines platform delivery as a licensable transport activity, a private-registration vehicle doing it is visibly in the wrong category, and an insurer pursuing a recovery has a rule to point at rather than an inference to argue.

The consequences run in a sequence risk managers should trace now:

• Riders migrating to commercial goods-carriage registration face motor insurance premiums several multiples of the private-use rate, and that cost lands in rider economics first.
• Fleet partners running leased two-wheelers can convert to a fleet policy and price it into the per-order rate. Riders on their own vehicles cannot.
• The third-party liability recovery risk against riders, which platforms have generally not indemnified, becomes a foreseeable exposure rather than a theoretical one, which is exactly the point at which a court or a consumer forum starts asking why the platform did not cover it.

Treat this as unsettled, not decided. The draft forces the question into the open in one large state. A platform that has never audited the registration category of the vehicles doing its Maharashtra deliveries has no basis to estimate the exposure, and that audit takes months across a five-figure fleet.

The coverage treats an electric-only fleet requirement as a climate measure. On a motor account of this size it is a re-rating event. Electric two-wheelers change the own damage side of the book in ways well understood in pricing and poorly reflected in most delivery-fleet programmes:

• The battery pack is a large share of vehicle value. Repair economics shift toward total loss at lower impact severity, because a damaged pack is frequently replaced rather than repaired. Claims frequency may not move. Average claim cost does.
• Thermal events are a distinct peril. Fire following battery damage, charging-related fire, and fire while parked at a dark store or a charging hub raise a question no petrol fleet asks: whether a rider's vehicle fire at a platform-operated charging point is a motor claim, a property insurance claim on the dark store, or a liability claim.
• Battery ownership is often separate from vehicle ownership. Battery-as-a-service and swap models put the pack on a third party's balance sheet. The motor policy insures the vehicle. Who insures the pack, and who is the loss payee when it burns, is a contract question, not a policy question.
• Charging infrastructure concentrates value. Dark stores with charging banks carry a fire load the premises policy was probably not rated for, and an unnotified material change in risk is an exclusion argument waiting for a claim.

The procurement instruction is straightforward. If the rule is notified with an EV mandate on a defined timeline, requote motor own damage on the affected fleet on an electric basis before the conversion, and review dark-store fire declarations for charging load in the same cycle.

The levy design deserves scrutiny, because a percentage without a cap behaves differently from a percentage with one.

Reporting on Maharashtra's July 2026 bike-taxi plan set a fee of Rs 5 per day per bike taxi alongside the 2 per cent levy now proposed for delivery platforms. The two instruments are not comparable. A flat daily fee per vehicle is a known number that scales with fleet size and can be budgeted a year out. A 2 per cent charge on each ride scales with order volume, and without a stated ceiling in what has been reported.

Karnataka's approach to the same problem used a capped structure, which is examined in the corpus post on the Karnataka gig welfare fee. The relevant contrast is not the rate. It is the shape:

• A capped percentage has a computable worst case, so it can be provisioned, priced into unit economics and disclosed.
• An uncapped per-ride percentage grows with the exact metric a quick commerce platform is trying to grow. At 36 lakh daily orders on one platform nationally, that difference is not a rounding item.

A levy is not insurance and should not be recorded as though it were. It is a statutory charge funding a welfare board. Whether that board's benefits reduce the platform's own claims exposure depends on whether its scheme, once framed, displaces a claim the platform would otherwise have faced. Until a scheme exists, assume no displacement.

Plan for the multi-state version. Maharashtra, Karnataka, Rajasthan and Telangana are each building a separate rate, base and collection mechanic, and a national platform will reconcile several of them against one order ledger.

The draft is with the State Law and Judiciary Department. That is the window.

In the next quarter

1. Audit vehicle registration categories across the Maharashtra rider base, split by rider-owned, fleet-partner-leased and platform-arranged. Without this, no exposure estimate is credible.
2. Pull every 3PL contract and find the clause allocating a new statutory levy introduced mid-term. Where there is none, open the conversation before the rule lands.
3. Ask motor and personal accident insurers for an indicative electric-two-wheeler own damage rate on the affected fleet, and for their position on charging-related fire at dark stores.
4. Check whether vendor-bought rider cover names the platform and whether the wording responds to the platform's vicarious exposure or only to rider injury.

At renewal

• Rebuild the fire declaration for Maharashtra dark stores to reflect charging installations and battery storage as a separate risk item.
• Negotiate a permit-condition clause in the motor and personal accident programme, so a certificate satisfying a transport authority can be issued without a mid-term restructure.
• Model the levy on the Maharashtra order base at current and 12-month forward volume, and carry the forward figure, since the structure is uncapped.

The substantive point for a broker or a risk manager is that this draft reads as a labour measure and behaves as a motor and liability one. The parts that will cost the most, the registration-category question and the electric fleet conversion, are the parts the headlines did not cover.