E-Commerce & Gig Economy
Platform Aggregator Obligations, Gig Worker Social Security & Delivery Worker Protections
Overview
India's e-commerce and gig economy sector operates at the intersection of four Labour Codes and rapidly evolving state legislation. Platforms connecting buyers with service providers (whether food delivery, ride-hailing, home services, or hyperlocal logistics) face a layered compliance structure that is more complex than traditional employer-employee frameworks. The Code on Social Security, 2020 introduces "gig worker" and "platform worker" as distinct legal categories for the first time in Indian law, and imposes direct contribution obligations on aggregators to a national social security fund. Simultaneously, Karnataka has enacted India's first comprehensive state-level gig worker legislation, with Rajasthan following suit, and several other states in active deliberation. The Code on Wages requires platforms that exercise sufficient control over workers to treat them as employees for minimum wage purposes. The Industrial Relations Code's thresholds for standing orders and retrenchment procedures may apply where platforms engage large numbers of workers classified as employees. The OSH Code imposes health and safety obligations on establishments of qualifying size and, critically, on employers of contract labour, a category many platforms may inadvertently fall into. For delivery workers specifically, road accident risks, heat exposure, and physical strain create OSH obligations that go beyond office-based compliance. Getting the classification question right is the single most important compliance decision for any gig platform, and data-driven ongoing monitoring is essential as engagement patterns evolve.
Code on Wages, 2019
- Minimum wage applies to all employees. Platforms exercising control over gig workers risk them being reclassified as employees, triggering retrospective minimum wage liability.
- The 50% basic wage rule applies to any worker found to be an employee; distorted CTC structures using allowances to suppress basic pay will be unwound.
- Payment of wages obligations (timely, in full, via digital means) apply to employees. Delivery workers paid per trip may not satisfy minimum earnings thresholds, creating legal exposure.
- Bonus provisions under the Payment of Bonus Act (subsumed by Code on Wages) apply to establishments employing 20 or more employees; platform workers classified as employees would trigger this.
- Equal remuneration provisions require no wage discrimination on grounds of gender for the same or similar work, which is relevant where platforms have gendered pay differentials in their algorithm outputs.
For platforms that employ delivery or service workers directly (or are found to do so in substance), all Code on Wages provisions apply in full. The 50% basic wage rule and minimum wage requirements are the highest-impact items and must be modelled against current per-trip and incentive-based pay structures.
A single adverse classification ruling by a labour court or the EPFO can retrospectively apply minimum wage, bonus, and 50% basic wage rules to your entire gig workforce, potentially spanning 5–7 years of back-payments.
Industrial Relations Code, 2020
- Standing Orders under Chapter IV apply to industrial establishments with 300 or more workers. E-commerce platforms with large fulfilment centre workforces must have certified standing orders covering service conditions.
- The threshold for retrenchment permission (prior government approval) is raised to 300 workers under the IR Code from the earlier 100-worker threshold under the Industrial Disputes Act, providing relief for mid-sized platforms.
- Gig workers are currently outside the definition of "workman" under the IR Code; however, if classified as employees, all IR protections apply, including unfair labour practices, retrenchment compensation, and layoff provisions.
- Fixed-term employment contracts (FTEs), introduced by the IR Code, offer platforms a route to engage delivery workers on defined terms without creating permanent employment, but FTE workers accrue the same benefits as permanent workers on a pro-rata basis.
- Grievance redressal committees (mandatory for establishments of 20+ workers) must be established for employee workforces at fulfilment centres and warehouses.
The IR Code's raised threshold to 300 workers for retrenchment permission provides operational flexibility to larger platforms. The introduction of fixed-term employment is a useful tool for seasonal or project-based delivery workforce surges. Classification of gig workers as workmen remains the primary IR risk.
Fixed-term employment under the IR Code can legitimately engage delivery workers for peak seasons (Diwali, Big Billion Day) without creating permanent employment, provided contracts are properly structured with equal pro-rata benefits.
Code on Social Security, 2020
- Section 114 requires aggregators to contribute 1–2% of annual turnover to the social security fund for gig and platform workers, subject to a cap of 5% of total payments made to such workers.
- Aggregators must register with the designated authority and maintain a comprehensive database of all gig and platform workers, including Aadhaar linkage, for scheme administration.
- Platform workers are entitled to social security schemes covering life and disability insurance, health and maternity benefits, and old age protection, once the Central Government notifies the specific schemes.
- Karnataka's Act supplements this with a welfare fee of 1–2% of each booking value (per-transaction, not annual turnover) deposited into a state welfare fund, creating a dual contribution obligation in that state.
- Gig workers registered on the e-Shram portal (unorganised worker database) gain access to certain social security entitlements; platforms operating in Karnataka and Rajasthan must facilitate this registration.
- Under EPF and ESI provisions (subsumed by the Social Security Code), workers classified as employees at qualifying establishments (10+ for ESI, 20+ for EPF) are compulsorily covered. Classification therefore drives contribution obligations.
The Social Security Code creates the most direct and quantifiable compliance obligation for aggregators: the turnover-based contribution to the social security fund. This is currently pending notification of the central rules but Karnataka's state-level fee is already operational. Platforms must build contribution calculation engines that can handle both turnover-based (central) and booking-value-based (Karnataka) calculations.
KSK regularly advises gig platforms on structuring social security contribution systems and defending classification positions before the EPFO and labour courts. Early structuring significantly reduces retrospective exposure.
OSH Code, 2020
- The OSH Code applies to factories, mines, docks, and establishments of qualifying size; fulfilment centres and large warehouses of e-commerce platforms qualify as factories or establishments.
- Contract labour provisions of the OSH Code apply where platforms engage workers through contractors for fulfilment, packing, or last-mile logistics. The principal employer (platform) bears joint liability for compliance.
- Delivery workers face elevated OSH risks: road accident exposure, heat stress, physical strain from parcel handling, and dog bites. Platforms have a duty to provide adequate safety training, safety equipment (helmets, rainwear), and accident insurance.
- Women workers engaged in warehouses or on delivery routes are entitled to OSH protections including adequate sanitation facilities, creche facilities at establishments of qualifying size, and no night-shift deployment without adequate safety measures.
- OSH record-keeping requirements include accident registers, health surveillance records, and inspection reports, all of which must be maintained at each fulfilment centre and made available to inspectors.
Fulfilment centres and large warehouses face the full weight of the OSH Code's factory-equivalent provisions. For delivery workers, even those classified as independent contractors, platforms bear a practical duty of care that is increasingly being enforced through accident liability claims and state-level enforcement actions.
Delivery worker road accidents are the highest-frequency OSH event for e-commerce platforms. Inadequate safety training and equipment are regularly cited in fatal accident inquiries, and platforms face both civil liability and potential criminal prosecution under OSH Code provisions.
Compliance Checklist
Register as an aggregator with the designated Central Government authority upon notification of Social Security Code rules
Register with the Karnataka Platform-Based Gig Workers Welfare Board within 60 days of Act commencement (if operating in Karnataka)
Build a contribution calculation system covering both central (turnover-based) and Karnataka (booking-value-based) social security fee computations
Conduct a worker classification risk assessment for all gig/contractor categories: map engagement criteria against the Supreme Court's control and integration tests
Implement the 50% basic wage rule for any workers classified or at risk of classification as employees to avoid retrospective CTC adjustment liability
Establish a grievance redressal mechanism for gig workers that meets Karnataka Act requirements (defined timelines, escalation, appellate authority)
Disclose algorithmic work allocation, pricing, and performance assessment criteria to gig workers as required by Karnataka's Act
Provide safety training, helmets, rainwear, and accident insurance to delivery workers; maintain OSH accident registers at all operating hubs
Certify Standing Orders for fulfilment centre operations if employing 300 or more workers at a single establishment
Maintain Aadhaar-linked gig worker database with quarterly data returns to the National Social Security Board once central rules are notified
Common Pitfalls
Treating social security contribution as a future obligation
Platforms delay building contribution infrastructure on the assumption that central rules have not yet been notified. Karnataka's Act is already operational, and central rules are imminent. Delayed implementation creates an unmanageable backlog of contributions and potential penalties.
Treat the contribution obligation as live now for Karnataka operations, and build the central contribution engine in parallel so it can be activated on notification date. Run shadow calculations quarterly.
Using contractual labels to defeat classification claims
Platforms frequently use engagement agreements labelled "independent contractor" or "service agreement" to avoid employment status. Indian courts look beyond labels to substance: control over work methods, economic dependence, and integration into the business. Adverse rulings have imposed 7–10 years of retrospective PF, ESI, and gratuity liability.
Audit the actual working relationship against classification criteria. Where the relationship resembles employment in substance, restructure it or register workers as employees. Do not rely solely on contractual language.
Ignoring the per-booking-value vs per-turnover distinction
Karnataka's welfare fee is calculated on each booking value (per transaction), not annual turnover. Platforms that import the central Code's turnover-based formula to their Karnataka calculations will systematically under-contribute, creating a liability for arrears.
Implement separate calculation engines for central (turnover) and Karnataka (booking value) contributions. Maintain separate ledgers and audit each quarter against platform transaction data.
Deactivating gig workers without notice or reason
Under Karnataka's Act, deactivating a gig worker without 14 days' notice and stated reasons is a breach of the Act and grounds for the worker to approach the Welfare Board. Platforms that use algorithmic deactivation without human review and documentation face regulatory action and reputational damage.
Implement a deactivation protocol requiring a documented reason, a 14-day notice period (or contemporaneous notice with right of appeal), and a record of the decision in the gig worker's file. Integrate the protocol into the platform's operations system.
Overlooking OSH obligations for fulfilment centre contract workers
Platforms engaging packing, sorting, and logistics workers through contractors assume the contractor bears all OSH liability. The OSH Code imposes joint and several liability on the principal employer for OSH compliance for contract labour. A contractor's failure to provide safety equipment or conduct safety training is the platform's liability too.
Include OSH compliance warranties and audit rights in all contractor agreements. Conduct quarterly audits of contractor OSH compliance at fulfilment centres. Maintain joint accident registers and ensure contractor workers are covered under the platform's group accident insurance policy.
Frequently Asked Questions
Need E-Commerce & Gig Economy Compliance Help?
KSK's Labour & Employment practice team can help you navigate the new labour codes and ensure full compliance across all states.