For digital platforms, quick‑commerce operators, and ride‑hailing networks across India, logistics management is an absolute core business function. However, with the formal enforcement of the Code on Social Security, 2020 and the Social Security (Central) Rules, 2026 (notified on 8 May 2026), platform governance faces an immediate, high‑stakes structural shift.
Following the central notification, all aggregators face a strict June 22, 2026 deadline to link their active worker databases directly with the government’s e‑Shram portal via live API connections.
Right alongside this technical migration sits a significant commercial and legal question: The law mandates that every aggregator contribute between 1% to 2% of its annual turnover (excluding taxes, levy and cess) to a centralised Social Security Fund. Can platforms simply lower their baseline per‑order pay or dynamic tariffs to absorb these new costs, and what are the exact legal boundaries preventing this cost‑shifting strategy?
Let’s unpack the statutory walls, the emerging state‑level protections, and the compliance guardrails that platforms must navigate.
The Executive Context: The 5% Statutory Protection Cap
When news of the mandatory 1–2% annual turnover levy first swept through boardrooms, many finance teams treated it as a simple variable cost that could be neutralised by trimming delivery partner incentives or lowering the base fare per delivery. The assumption was that since gig workers operate outside a traditional employer‑employee relationship, their task‑based tariffs could be modified at will.
However, the Code on Social Security introduces a critical double‑lock financial guardrail designed specifically to prevent arbitrary cost‑shifting.
Under Section 114(4), the aggregator’s turnover‑based contribution is subject to a strict statutory cap: the total annual contribution payable can never exceed 5% of the total amount paid or payable by the aggregator to its gig and platform workers during that financial year.
This means the levy is mathematically bound to your fleet payouts. If a platform attempts to drastically reduce its total payout pool to save costs, it simultaneously restricts its statutory contribution parameters.
Conversational Breakdown: Is Tariff Reduction Legally Permissible?
Here lies the legal gap at the heart of the blog: the central Code on Social Security does not explicitly prohibit an aggregator from lowering per‑order pay. Gig workers are not “employees” under the Code; their compensation is governed by commercial contracts, not minimum wage statutes (except where state‑specific laws apply).
Therefore, a platform could, in theory, re‑calibrate its algorithms to reduce the base fare per delivery, thereby reducing its total payout pool and by extension; the 5% cap ceiling, while still remitting the correct 1–2% of turnover.
But two layers of legal restriction make this risky in practice:
1. State‑Level Transparency and Anti‑Deduction Laws
Because labour is a Concurrent Subject under the Indian Constitution, individual states have layered additional operational restrictions on top of the central framework.
Karnataka has enacted the Karnataka Platform‑Based Gig Workers (Social Security and Welfare) Act, 2025. Key provisions include:
- Welfare fee of 1–5% per transaction deducted from worker payouts (unlike the central levy, which is borne by aggregators from turnover).
- Termination restrictions: Aggregators cannot terminate a gig worker without 14 days’ prior notice and written reasons.
- Payment and Welfare Fee Verification System (PWFVS): A dedicated software system to monitor payments and provide gig‑by‑gig payout data to the Welfare Board, making algorithmic opacity much harder to sustain.
- Two‑tier grievance redressal: Internal committee → Welfare Board, for challenging unexplained payout variations.
Rajasthan passed the Rajasthan Platform‑Based Gig Workers (Registration and Welfare) Act in July 2023, requiring a welfare fee calculated as a percentage of the value of each transaction involving a platform worker.
Telangana has approved its draft Telangana Gig and Platform Workers Act, expected to cover over 3 lakh gig workers in transport, delivery, domestic services and logistics.
2. The Prohibition of “Arbitrary Deductions”
While the central Code does not forbid tariff adjustments, state rules explicitly state that any welfare fees or turnover levies mandated by the state or central governments must be borne entirely by the platform’s corporate treasury, prohibiting any direct or indirect impact on the baseline payout rate of the gig worker. Karnataka’s Payment and Welfare Fee Verification System (PWFVS) enables real‑time detection of such cost‑shifting.
Dual‑Regime Analysis: The Evolving Aggregator Framework
| Compliance Aspect | Legacy Regime (Pre‑Code) | Modern Code Regime (2026) |
| Legal definition | No formal definitions for gig/platform workers. | Formal recognition under Section 2(35) of Social Security Code. |
| Aggregator contribution | Zero statutory liability. | 1–2% of annual turnover (taxes excluded), capped at 5% of worker payouts. |
| Exact rate | – | Rate yet to be notified by Central Government per aggregator category under Seventh Schedule. |
| State‑level welfare fee | None. | Karnataka: 1–5% per transaction (from worker payouts). Rajasthan: transaction‑based levy. Telangana: draft Act approved. |
| Tariff regulation | Purely commercial contract. | State‑level transparency mandates; PWFVS (Karnataka) for gig‑by‑gig payout monitoring; prohibition of arbitrary deductions. |
| Penalty for delayed central contribution | – | 12% annual interest (1% per month) on delayed amounts. |
2026 Core Impact Filters for Platform Restructuring
When auditing your platform’s cost structures this year, map your financial models against these filters:
Separation from Traditional Salary Rules
Gig workers are exempt from the 50% Wage Rule and the 48‑Hour Exit Rule that govern standard company payrolls. This means platforms do not face complex statutory gratuity or retrenchment overheads during routine delivery partner exits. However, this separation means any attempt to blur the lines by executing regular salary deductions will be used by tribunals to re‑classify your delivery fleet as direct, permanent employees.
Real‑Time e‑Shram API Validation
Every partner onboarding sequence must be linked directly via API to the central e‑Shram portal. If an aggregator reduces per‑order rates and triggers a mass fleet log‑off, any sudden, un‑synchronised drop in active partner volumes will be immediately flagged in the government’s unified electronic compliance returns, triggering prompt inspection calls from the Labour Commissioner’s desk.
The Independent Fleet Vendor Loophole
The central rules explicitly cover any worker engaged by an aggregator directly or through an associate company, subsidiary, or third‑party logistics intermediary. If a platform attempts to route deliveries through sub‑contracted local fleet operators and instructs those vendors to suppress rider pay to absorb the 1–2% levy, the parent aggregator remains directly liable under the Code for any systemic compliance failures.
Core Compliance Checklist for Platform Executives – FREE
To protect your organisation against interest penalties, class‑action disputes, and regulatory audits:
- Isolate the Social Security Fund Reserves: Configure your financial ledger systems to separate the mandatory 1–2% annual turnover contribution as a pure corporate operational expense, ensuring it is never factored into worker payout algorithm deductions.
- Enforce the 5% Payout Cap Audit: Conduct a quarterly internal audit comparing your top‑line turnover contribution liabilities against your total delivery fleet payout volumes, ensuring the total levy consistently stays within the statutory 5% cap.
- Implement Algorithmic Transparency Modules: Update your user‑facing partner application to display a clear, step‑by‑step breakdown of every trip payout, explicitly proving that no corporate welfare levies are being deducted from the rider’s net earnings. In Karnataka, the PWFVS will audit this data.
- Verify Aadhaar‑Seeded UAN Collections: Ensure your engineering desk maintains continuous API synchronisation with the e‑Shram portal, linking every single delivery transaction back to a verified, active Universal Account Number (UAN).
- Monitor State‑Level Notifications: Karnataka, Rajasthan and Telangana have active or proposed welfare fee regimes. Platforms operating across states must track state‑specific contribution rates and transparency mandates.
Financial and Operational Risk Analysis
| Risk Category | Operational Impact | Legal & Financial Fallout |
| Delayed Central Contribution | Failing to calculate or deposit the turnover levy within prescribed timelines. | Mandatory 12% annual interest penalty (1% per month) under the Social Security (Central) Rules, 2026. |
| Algorithmic Cost‑Shifting (Karnataka) | Modifying delivery tariffs to indirectly claw back the corporate levy. | Class‑action disputes before State Welfare Board; PWFVS can detect payout variations; potential orders for restitution of back‑earnings. |
| Vendor Non‑Compliance | Third‑party logistics intermediaries lowering rider pay to absorb corporate costs. | The parent aggregator is held directly responsible for all indirect fleet compliance breaches under the extended definition of “aggregator”. |
| Data Synchronisation Errors | Failing to maintain live data sync with e‑Shram portal. | Automated flags in unified digital compliance returns, leading to unexpected corporate audits. Workers may lose benefit eligibility. |
| Concerted Tariff Reduction | Multiple platforms simultaneously reducing per‑order pay. | Potential scrutiny under the Competition Act, 2002 for anti‑competitive concerted practice. |
Furthermore, if an aggregator experiences widespread operational friction due to unannounced rate cuts, the ensuing disruption can cause immediate delivery delays, heavy partner churn, and significant damage to corporate brand equity during key consumer demand cycles.
Conclusion
The central Code on Social Security does not explicitly prohibit an aggregator from adjusting per‑order pay to offset its 1–2% turnover contribution. Gig workers are not employees, and their compensation is governed by commercial contracts.
But three realities make cost‑shifting a risky strategy:
- State‑level transparency laws (Karnataka’s PWFVS, Rajasthan’s transaction levy, Telangana’s draft Act) create real‑time payout visibility and grievance mechanisms.
- The 5% cap mathematically links the levy to your payout pool; aggressive rate cuts reduce the cap, but do not eliminate the 1–2% turnover obligation.
- Reputational and regulatory risk – unexplained, unilateral tariff reductions invite class‑action disputes, Welfare Board inquiries, and potential Competition Commission scrutiny.
Smart platforms will:
- Fund the 1–2% central contribution from corporate treasury, not worker payouts.
- Monitor state‑level welfare fee notifications in Karnataka, Rajasthan, Telangana and other states.
- Maintain algorithmic transparency and documented justifications for any tariff changes.
- Ensure third‑party fleet vendors are contractually bound to comply with all data reporting and payout transparency obligations.
Disclaimer: This publication is provided for general informational and educational purposes only and does not constitute legal advice. The information contained herein may not reflect the most current legal developments and is not guaranteed to be complete, accurate, or up‑to‑date. Nothing in this publication creates a lawyer‑client relationship between the reader and the author or publisher. Laws, regulations, and judicial interpretations vary by jurisdiction and may change over time. Readers should not act or refrain from acting on the basis of any information contained in this publication without first seeking independent legal counsel from a qualified lawyer licensed to practice in the relevant jurisdiction. The author and publisher expressly disclaim all liability in respect of any actions taken or not taken based on any or all of the contents of this publication. Case citations and statutory references are provided for illustrative purposes only and do not constitute a guarantee of any particular outcome. Always consult a qualified legal professional for advice tailored to your specific circumstances.