Gig Delivery Workforce Compliance In India

If your brand runs its own riders, or is thinking about it, the legal position is not the one printed on the contract. It is the one a labour inspector or a court would find by looking at how the work actually happens.

This matters more now than it did two years ago. The four labour codes were brought into force on 21 November 2025, gig and platform workers are named in central law for the first time, and at least two states have live welfare levies. The rollout has been staggered and incomplete, which is exactly the condition in which brands make expensive assumptions.

Before anything else: delivery partners are people doing physically demanding work in traffic, heat and rain, with income that swings week to week. Design the engagement for that reality and most of the compliance follows.

Contractor or employee is decided by substance

Indian tribunals apply a control and integration test. The contract label is evidence, not proof. The questions that decide it:

• Do you control how the work is done, not just what the outcome is? Fixed shift timings, mandated routes, a uniform and a reporting manager all point to employment.
• Is the person integrated into your business, doing work that is core and continuous rather than project based?
• Do you supply the tools, meaning vehicle, phone, fuel card or insulated bag?
• Can they work for someone else at the same time, or is exclusivity enforced in practice?
• Do you run disciplinary processes, approve leave, and pay something that behaves like a monthly wage?

If most answers point to employment, the downstream obligations follow whether or not the paperwork says independent contractor. That means provident fund contributions once you cross the establishment threshold, ESI where applicable with the wage ceiling at Rs 21,000 a month, gratuity on five years of service, minimum wages, and state shops and establishments registration. Reclassification is usually retrospective, which is what makes it painful.

What the Code on Social Security 2020 sets up

The Code was the first central legislation to define gig worker, platform worker and aggregator as distinct categories. The core mechanics:

• Aggregators in the listed categories, which include ecommerce, delivery and logistics services, owe a contribution of one to two percent of annual turnover, capped at five percent of the total amount payable by the aggregator to gig and platform workers in that financial year.
• The contribution funds a social security fund covering life and disability cover, accident insurance, health and maternity benefit, old age protection and creche support.
• Draft central rules circulated from December 2025 proposed eligibility thresholds of around 90 days of engagement with a single aggregator, or 120 days across multiple aggregators, in a financial year.
• Registration on the central portal is the gateway for a worker to access anything, so registration support is effectively part of the obligation.

The important caveat is that this is a staggered rollout. Not all schemes under the Code have been notified, benefit delivery is still being built, and the stated government target is to bring around 2.35 crore gig and platform workers under coverage by 2029-30. Treat the framework as directionally certain and operationally unsettled, and confirm current applicability for your specific structure with employment counsel. Nothing here is legal advice.

States are moving faster than the centre

Rajasthan passed the first state law in 2023, creating a welfare fund and a transaction level cess on aggregators. Karnataka followed with an ordinance and then a platform based gig workers Bill in 2025, allowing a welfare fee of one to five percent of the payout on each transaction, set by category. Karnataka notified one percent with per transaction caps, in the region of 50 paise on a two wheeler ride, 75 paise on a three wheeler and one rupee on a four wheeler, with a one percent levy on food and grocery deliveries. The Karnataka High Court declined to stay the Act in July 2026 and directed platforms to deposit the fee. Telangana has a draft bill in the same shape.

If you operate across cities, that means different registration, different levies and different reporting per state. Build the state map before you build the rider app.

What changes when you engage riders directly

Routing deliveries through an established aggregator moves most of this exposure onto them. Engaging riders yourself moves it onto you, and you may not even qualify as an aggregator under the Code, which means you get judged on ordinary employment law instead.

• Contract labour. If you engage riders through a manpower contractor and cross the threshold, the Contract Labour Act applies and you sit as principal employer, liable for wages and statutory dues if the contractor defaults. Audit the contractor challans monthly.
• Motor vehicle compliance. Riders need a valid licence, valid registration, and appropriate insurance where the vehicle carries goods. Third party cover is mandatory. Verify at onboarding and re-verify on expiry.
• Accident and health cover. Aggregators usually carry group personal accident cover. Direct engagement means you buy it, and it should be genuinely claimable rather than a certificate in a folder.
• Vicarious liability. If a rider on your task injures someone, you are in the claim. Your liability policy needs to contemplate that.
• Safety and grievance. Night shift protocols, rest guidance in heat waves, and a grievance channel a rider can actually use.

The practical answer for most brands: use an aggregator or a 3PL for volume, and keep direct rider engagement small, documented and deliberately structured. If you do engage directly, pay a base per hour rather than only per drop, cover insurance without being asked, and have a labour lawyer review the working arrangement rather than the template contract. The paperwork is cheap. The reclassification is not.