India gig worker platform rights

India's Platform Worker Registry Hits Its Deadline—Now the Harder Work of Delivering Benefits Begins

Fifteen aggregators completed eShram API integration by June 21, 2026, making millions of gig workers visible to the state for the first time—but registration is not yet benefits.

India's Gig Worker Registry at a Glance People of Internet Research · India 15 Platforms API-integrated Major aggregators completed eShram… ~23.5M Projected workers by 2030 NITI Aayog projects India's platfo… 1-2% Aggregator welfare levy Of annual turnover paid to Social … 90 days Eligibility threshold Minimum engagement for a worker to… peopleofinternet.com

Key Takeaways

The Deadline That Held

When India's Ministry of Labour set June 21, 2026 as the cutoff for digital aggregators to integrate with the eShram portal, the betting in policy circles was that platforms would miss it or seek extensions. Neither happened. Fifteen major aggregators—including Swiggy, Zomato, Uber, Ola, Rapido, Amazon, Zepto, Urban Company, Porter, and Blinkit—completed API integration ahead of the deadline, creating what is likely the largest national database of platform workers anywhere in Asia. For a workforce NITI Aayog counted at 7.7 million in 2020-21 and the ILO projects will reach 23.5 million by 2029-30, it is the first moment the Indian state can say with any precision who its gig workers are.

The legal vehicle is the Code on Social Security, 2020, passed by Parliament on September 22–23, 2020, and notified into force on November 21, 2025—a five-year gap that reflects India's chronic distance between legislative ambition and executive implementation. The Code's gig worker provisions were further operationalized through Social Security Rules 2026, effective May 8, 2026. Rules 48 and 49 require aggregators to share worker data electronically within 45 days of the rules taking effect, making June 21 the hard deadline. Non-compliance attracts penalties under Section 133 of the Code.

What the Registry Actually Creates

The eShram integration does not reclassify gig workers as employees. It creates an identity layer: each registered worker receives a Universal Account Number that, once linked to benefit schemes, is meant to unlock life insurance, accident cover, health benefits, and old-age protection. This is a deliberate design choice, not an oversight.

Under Section 114 of the Code, aggregators must contribute 1–2% of their annual turnover to a Social Security Fund, capped at 5% of what they pay their gig and platform workers. The fund is intended to finance government-designed welfare schemes rather than employment entitlements. Workers qualify for benefits only after 90 days of engagement with a single aggregator, or 120 days distributed across multiple platforms in a year—thresholds calibrated to cover regular platform workers while excluding genuinely casual participants.

The Case for Mandatory Registration

Before the Code, India's gig workforce operated in a legal vacuum. Delivery riders, cab drivers, and freelance logistics workers bore occupational risk with no collective safety net and no legal identity within the labour framework. Rajasthan's Platform Based Gig Workers (Registration and Welfare) Act, 2023—the first state-level gig worker law in India—demonstrated that demand for protection exists and that states would act unilaterally if the Centre moved too slowly.

The strongest argument for mandatory API integration, rather than voluntary self-declaration, is that it removes the incentive for underreporting. A delivery platform that manually registers only its highest-earning riders can claim compliance while leaving the most precarious workers uncovered. Forcing data flows through a standardized API closes that loophole. The 1–2% turnover levy is also modest enough that even venture-backed platforms with thin margins can absorb it without restructuring their models—a proportionality standard that regimes in the EU, which have pushed harder toward full employee reclassification, have struggled to maintain.

Where the Model Falls Short

The registration milestone is real but should not be confused with benefit delivery. Three structural gaps persist.

The portability problem. A delivery worker cycling between Swiggy, Zomato, and Zepto accumulates platform-specific engagement records that must be aggregated under a single UAN to count toward the 120-day multi-platform threshold. The eShram portal is designed to handle this, but it depends on data standards being adopted uniformly across all fifteen integrated platforms—a technical coordination task that the API deadline alone does not resolve.

The multi-registration burden. India now runs overlapping frameworks: the central eShram portal, Rajasthan's state welfare board, and aggregator-specific grievance systems. Workers navigating all three face what labour researchers describe as a "digital procedural maze"—high transaction costs in time and documentation that systematically screen out the most precarious workers, who are paradoxically most in need of coverage.

The identity-without-status gap. The Code explicitly excludes gig workers from protections available under the Industrial Relations Code, 2020: minimum wage guarantees, occupational safety provisions, and the right to collective bargaining. The social security layer therefore addresses risk-pooling without addressing the underlying legal asymmetry between platforms and workers. Worker rights organisations argue, with some force, that benefit access without employment status locks workers into an arrangement where platforms control the eligibility data while facing limited accountability under labour law.

The Proportionality Verdict

The eShram mandate is proportionate as a first step precisely because it does not attempt to resolve the misclassification question. Forcing reclassification of gig workers as employees—the direction several EU member states have pursued following the 2024 Platform Work Directive—would likely formalize a fraction of India's platform workforce while pushing the rest into informal sub-contracting arrangements. India's approach of building an identity and data layer first, then designing benefit schemes on top of it, is architecturally sound even if it has moved slowly.

The real test is whether the database translates into functioning benefit claims. The 2020 Code gave the government six years to operationalize its gig worker provisions; June 21 closed only the data-onboarding phase. Phase two—scheme notification, fund management, contribution collection, and actual benefit disbursement—remains underspecified. If the Social Security Fund fills with aggregator contributions but claims processing lags by years, the registry will be remembered as a compliance milestone rather than a social policy achievement.

India has built the foundation. An estimated 15–23 million gig workers are now visible to the state in a way they were not six months ago. Whether that visibility translates into security depends on administrative and fiscal decisions that will be made in the next budget cycle—not the last legislative one.

Sources & Citations

  1. PRS India: Code on Social Security 2020
  2. ILO: Expansion of India's Gig and Platform Economy
  3. SCC Online: eShram Aggregator Deadline
  4. India Briefing: Gig Workers eShram Registration
  5. Asanify: EOR & Compliance Digest, June 2026
  6. The Leaflet: Identity and Social Security for Gig Workers