Digital Competition Bill 2024: India's Ex-Ante Framework for Big Tech

Executive Summary

Key Takeaways:

• The Digital Competition Bill 2024 (DCB) introduces India's first ex-ante regulatory framework for regulating Big Tech platforms before anti-competitive conduct occurs
• Targets Systemically Significant Digital Enterprises (SSDEs) - large digital platforms with significant market power and gatekeeping capabilities
• Identifies 10 Core Digital Services including search engines, social networking, online marketplaces, cloud computing, and digital advertising
• Uses user-based thresholds: 1 crore (10 million) end-users OR 10,000 business users in India during any calendar year
• Prohibits specific anti-competitive practices including self-preferencing, tying, data exploitation, and ecosystem lock-in
• Establishes a new Competition Commission of India (Digital Markets) Division with specialized expertise
• Represents a paradigm shift from ex-post enforcement (punishing past violations) to ex-ante regulation (preventing violations before they occur)
• Aligns India with global regulatory trends: EU's Digital Markets Act (DMA), UK's Digital Markets Competition Regime, and proposed US regulations

Introduction

The rapid digitalization of the Indian economy has created unprecedented challenges for traditional competition law enforcement. Digital platforms—with their network effects, data advantages, and multi-sided market structures—have accumulated market power that conventional ex-post regulatory mechanisms struggle to address effectively. By the time the Competition Commission of India (CCI) investigates and penalizes anti-competitive conduct, significant consumer and competitive harm has already occurred.

The Digital Competition Bill 2024 (DCB) represents India's legislative response to this enforcement gap. Introduced in Parliament in early 2024, the DCB proposes a comprehensive ex-ante regulatory framework specifically designed for digital markets. Unlike the Competition Act 2002, which intervenes after anti-competitive conduct has occurred, the DCB seeks to prevent anti-competitive behavior before it happens through clear, bright-line rules applicable to the largest digital platforms.

This article provides a comprehensive analysis of the DCB 2024, examining its scope, designation criteria, prohibited practices, enforcement mechanisms, and practical implications for digital enterprises operating in India.

The Shift from Ex-Post to Ex-Ante Regulation

Understanding Ex-Post vs. Ex-Ante Frameworks

Ex-Post Regulation (Competition Act 2002):

• Investigates and penalizes conduct after it has occurred
• Requires establishing dominance, market definition, and appreciable adverse effect on competition (AAEC)
• Lengthy investigation and adjudication process (often 2-5 years)
• Reactive: harm has already occurred by the time enforcement action is taken
• Case-specific remedies that may not address systemic issues

Ex-Ante Regulation (Digital Competition Bill 2024):

• Imposes obligations before anti-competitive conduct can occur
• Applies automatically to designated platforms meeting specific criteria
• Bright-line rules with limited discretion
• Proactive: prevents harm before it manifests
• Structural remedies that address market dynamics systematically

Why Digital Markets Require Ex-Ante Regulation

The WhatsApp-Facebook privacy policy case (decided by Delhi High Court in 2021) illustrates the limitations of ex-post enforcement. By the time the CCI directed an investigation under Section 26(1) of the Competition Act, WhatsApp's updated privacy policy had already been implemented, affecting over 400 million Indian users. The Delhi High Court upheld the CCI's jurisdiction but noted that privacy and competition concerns were deeply intertwined—an issue better addressed through ex-ante regulation.

Case Reference:

• WhatsApp LLC v. Competition Commission of India (2021) - Delhi High Court, W.P.(C) 4378/2021
• Holding: CCI has jurisdiction to investigate WhatsApp's privacy policy update under Section 26(1) even when privacy matters are pending before the Supreme Court
• Significance: Demonstrates CCI's proactive investigative powers but also highlights the time lag inherent in ex-post enforcement

Scope and Applicability: The 10 Core Digital Services

What Constitutes a "Core Digital Service"?

The DCB 2024 identifies 10 specific categories of digital services that, when provided at scale, warrant ex-ante regulation:

1. **Online Search Engines**

• Definition: Platforms allowing users to search across indexed internet content
• Examples: Google Search, Bing, DuckDuckGo (if designated)
• Key Concerns: Self-preferencing in search results, favoring own services over competitors

2. **Social Networking Services**

• Definition: Platforms enabling users to connect, share, and communicate
• Examples: Facebook, Instagram, Twitter/X, LinkedIn
• Key Concerns: Data portability restrictions, interoperability barriers, predatory acquisitions

3. **Video-Sharing Platform Services**

• Definition: Platforms for uploading, sharing, and viewing video content
• Examples: YouTube, Instagram Reels, TikTok (if operating)
• Key Concerns: Preferencing own content, discriminatory recommendation algorithms

4. **Interpersonal Communication Services**

• Definition: End-to-end communication platforms (messaging, voice, video)
• Examples: WhatsApp, Telegram, Signal, Google Meet, Zoom
• Key Concerns: Interoperability restrictions, bundling with other services

5. **Online Intermediation Services (Marketplaces)**

• Definition: Platforms connecting third-party sellers/service providers with consumers
• Examples: Amazon, Flipkart, Swiggy, Zomato, Ola, Uber
• Key Concerns: Self-preferencing of private label products, unfair contract terms, data exploitation

6. **Cloud Computing Services**

• Definition: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), Software-as-a-Service (SaaS)
• Examples: Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform
• Key Concerns: Bundling of services, interoperability restrictions, lock-in through proprietary standards

7. **Operating Systems**

• Definition: Software managing computer hardware and software resources
• Examples: Android, iOS, Windows, macOS
• Key Concerns: Pre-installation of apps, default settings favoring own services, API restrictions

8. **Web Browsers**

• Definition: Software applications for accessing information on the World Wide Web
• Examples: Google Chrome, Safari, Microsoft Edge, Firefox
• Key Concerns: Default search engine agreements, preferencing own services in browser features

9. **Virtual Assistants**

• Definition: AI-powered software providing voice/text-based assistance
• Examples: Google Assistant, Siri, Alexa, Cortana
• Key Concerns: Preferencing integrated services, voice commerce manipulation

10. **Online Advertising Services**

• Definition: Platforms providing advertising technology stack (ad networks, ad exchanges, demand/supply-side platforms)
• Examples: Google Ads, Facebook Ads, Amazon Advertising
• Key Concerns: Self-preferencing in ad auctions, opaque pricing, data advantage exploitation

Convergence and Multi-Service Platforms

Many digital platforms provide multiple core digital services simultaneously. The DCB recognizes this service convergence and can designate a single entity as an SSDE across multiple service categories.

Example: Google's Multi-Service Ecosystem

• Online Search Engine (Google Search)
• Video-Sharing Platform (YouTube)
• Web Browser (Chrome)
• Operating System (Android)
• Virtual Assistant (Google Assistant)
• Online Advertising (Google Ads)
• Cloud Computing (Google Cloud)

This interconnected ecosystem creates cross-market leveraging opportunities, where dominance in one service (e.g., search) can be leveraged to foreclose competition in adjacent markets (e.g., online advertising, cloud services). The DCB's ex-ante framework addresses this through holistic designation and service-specific obligations.

Designation Criteria: Who Qualifies as an SSDE?

Quantitative Thresholds

An enterprise qualifies for designation as a Systemically Significant Digital Enterprise (SSDE) if it meets EITHER of the following user thresholds:

Threshold 1: End-User Base

• ≥ 1 crore (10 million) end-users in India
• Measured during any calendar year in the preceding three financial years
• Includes active and registered users (specific measurement methodology to be prescribed)

Threshold 2: Business User Base

• ≥ 10,000 business users in India
• Business users are enterprises/individuals using the platform for commercial purposes
• Examples: Sellers on Amazon/Flipkart, advertisers on Google/Facebook, app developers on iOS/Android

Qualitative Assessment Factors

Beyond numerical thresholds, the CCI will consider:

1. Market Position and Market Power

   • Market share in relevant digital service markets
   • Ability to act independently of competitive pressures
   • Barriers to entry and expansion faced by competitors

2. Network Effects

   • Direct network effects (value increases with more users of same type)
   • Indirect network effects (multi-sided platforms benefiting from cross-group externalities)
   • Data network effects (data accumulation creating competitive advantages)

3. Data Advantages

   • Volume, variety, and velocity of data collected
   • Non-replicability of datasets by competitors
   • Use of data for market foreclosure or self-preferencing

4. Ecosystem Lock-In

   • Switching costs faced by users
   • Multi-homing costs (cost of using multiple platforms simultaneously)
   • Proprietary standards and interoperability restrictions

5. Size and Scale

   • Global and India-specific turnover
   • User base growth trajectory
   • Geographic coverage and penetration

6. Integration Across Services

   • Number of core digital services provided
   • Degree of integration and bundling
   • Cross-subsidization and zero-pricing strategies

Designation Process

Step 1: Preliminary Assessment

• CCI initiates suo motu or on receipt of information
• Enterprise may self-notify if it meets thresholds

Step 2: Consultation

• CCI issues notice to the enterprise
• Enterprise submits representations and data
• Stakeholder consultations (competitors, users, civil society)

Step 3: Designation Order

• CCI issues final designation order specifying:
  • Core digital services covered
  • Specific obligations applicable
  • Compliance timelines
  • Effective date of designation

Step 4: Review and De-Designation

• Annual review of designation status
• De-designation if thresholds no longer met or market conditions change
• Appeals to Competition Appellate Tribunal (COMPAT)

Expected Designations in India

Based on publicly available data, the following platforms are likely to be designated as SSDEs under the DCB 2024:

Prohibited Practices: Core Obligations for SSDEs

Category 1: Self-Preferencing Prohibitions

Definition: Favoring one's own products, services, or business users over competitors in ways that distort competition.

Prohibited Conduct:

1. Search Result Manipulation

   • Ranking own services higher than competitors' services of equal or superior quality
   • Displaying own services more prominently (visual prominence, placement)
   • Example: Google preferencing Google Shopping over competing comparison shopping services

2. App Store Self-Preferencing

   • Pre-installing own apps with uninstall restrictions
   • Granting own apps privileged API access unavailable to third-party developers
   • Preferencing own apps in search rankings and recommendations
   • Example: Android pre-installing Google apps (Search, Chrome, Maps, YouTube) with preferential treatment

3. Marketplace Private Label Preferencing

   • Using non-public marketplace data to launch competing private label products
   • Preferencing private label products in search results and recommendations
   • Offering better placement, promotions, or terms to private label products
   • Example: Amazon using seller data to develop AmazonBasics competing products

4. Advertising Self-Preferencing

   • Favoring own advertising services over competitors in ad auctions
   • Bundling advertising services with other core digital services
   • Example: Google favoring Google Ads inventory over competing ad networks

Compliance Requirements:

• Non-Discrimination: Treat own products/services and third-party offerings equally in rankings, recommendations, and access
• Transparency: Disclose ranking criteria and any differential treatment
• Data Firewalls: Separate non-public third-party data from own product/service development teams

Category 2: Tying and Bundling Restrictions

Definition: Conditioning the sale/access of one product/service on the purchase/use of another product/service.

Prohibited Conduct:

1. Technological Tying

   • Making functionality of one service dependent on use of another service
   • Example: Microsoft bundling Internet Explorer with Windows (historical EU case)

2. Contractual Tying

   • Requiring business users to use specific services as condition for platform access
   • Example: Requiring app developers to use in-app payment systems exclusively

3. Default Settings Tying

   • Pre-setting defaults that favor own services with barriers to changing defaults
   • Example: Android setting Google Search as default search engine with complex opt-out process

4. Ecosystem Bundling

   • Creating seamless integration only within own ecosystem while restricting interoperability
   • Example: Apple's ecosystem integration (iMessage, FaceTime, AirDrop) that works only on Apple devices

Compliance Requirements:

• Unbundling: Offer core digital services separately without mandatory bundles
• User Choice: Allow users to easily select and switch to competing services
• Interoperability: Ensure third-party services can integrate as seamlessly as own services

Category 3: Data Exploitation Prohibitions

Definition: Using data collected from business users or competitors to gain unfair competitive advantages.

Prohibited Conduct:

1. Data Misappropriation

   • Using non-public data from business users to develop competing products/services
   • Example: Food delivery platform using restaurant sales data to launch own cloud kitchen

2. Data Combination Without Consent

   • Combining user data across services without explicit, informed consent
   • Example: Combining search history with email content for targeted advertising

3. Exclusivity in Data Access

   • Restricting business users' access to their own data or user data
   • Limiting data portability to competing platforms

4. Discriminatory Data Sharing

   • Sharing data with own services while denying equivalent access to competitors

Compliance Requirements:

• Data Separation: Maintain technical and organizational firewalls between data from different services
• Consent Requirements: Obtain explicit consent for cross-service data combination
• Data Portability: Provide users and business users with easy data export in machine-readable formats
• Equal Access: Grant third parties equivalent data access as provided to own services

Category 4: Interoperability and Data Portability Obligations

Definition: Ensuring users and business users can switch platforms and use competing services without undue friction.

Affirmative Obligations:

1. Messaging Interoperability

   • Allow messaging services to interoperate with competing messaging platforms
   • Example: WhatsApp users should be able to message Signal/Telegram users

2. Social Network Data Portability

   • Enable users to export their social graph, posts, and content to competing platforms
   • Maintain connections across platforms (cross-platform friend lists)

3. API Access Parity

   • Provide third-party developers with same API access quality and functionality as own services
   • Publish API documentation with advance notice of changes

4. Number Portability and Identity Portability

   • Allow users to retain identifiers (phone numbers, usernames) when switching platforms
   • Facilitate single sign-on (SSO) without requiring continued use of original platform

Compliance Requirements:

• Technical Standards: Adopt open, industry-standard protocols for interoperability
• Real-Time Data Portability: Provide continuous data synchronization, not just one-time export
• No Degradation: Ensure interoperability does not degrade user experience or security

Category 5: Transparency and Fairness in Business User Relations

Definition: Ensuring fair, transparent, and non-discriminatory treatment of business users (sellers, advertisers, app developers).

Prohibited Conduct:

1. Opaque Ranking Algorithms

   • Using undisclosed criteria to rank products, services, or content
   • Changing ranking algorithms without notice to business users

2. Unfair Contract Terms

   • Imposing most-favored-nation (MFN) clauses preventing business users from offering better terms elsewhere
   • Unilateral contract modifications without reasonable notice
   • Excessive revenue sharing or commission rates

3. Access Restriction and De-Platforming

   • Suspending or terminating business users without clear justification or due process
   • Discriminatory enforcement of platform policies

4. Data and Analytics Withholding

   • Denying business users access to performance metrics, sales data, or customer insights

Compliance Requirements:

• Transparency Reports: Publish ranking criteria, algorithm changes, and performance metrics
• Fair Contracts: Provide reasonable notice for contract changes; allow negotiation for large business users
• Grievance Redressal: Establish independent dispute resolution mechanisms for business users
• Equal Treatment: Apply platform policies consistently without discrimination

Enforcement and Compliance Mechanisms

The Digital Markets Division of CCI

The DCB establishes a specialized Competition Commission of India (Digital Markets) Division with:

• Dedicated Expertise: Economists, data scientists, and technologists specializing in digital markets
• Proactive Monitoring: Continuous compliance monitoring through algorithmic audits and data analysis
• Investigation Powers: Authority to conduct dawn raids, demand data/documents, and interview personnel
• Penalty Authority: Power to impose penalties up to 10% of global turnover for non-compliance

Compliance Obligations for SSDEs

1. **Annual Compliance Reporting**

• Submit detailed compliance reports to CCI annually
• Disclose business practices, algorithm changes, data usage policies, and self-assessment of compliance

2. **Independent Audits**

• Conduct third-party audits of algorithms, data practices, and interoperability implementations
• Submit audit reports to CCI with remediation plans for identified gaps

3. **Compliance Officers**

• Appoint dedicated Chief Compliance Officers resident in India
• Compliance officers directly accountable to CCI for SSDE's adherence to DCB obligations

4. **Real-Time Data Sharing**

• Provide CCI with API access to monitor compliance in real-time
• Share algorithmic decision-making logs for transparency

Penalties for Non-Compliance

Global Turnover Calculation: Based on worldwide revenue across all services, not limited to India operations. This ensures meaningful deterrence even for globally dominant platforms with smaller India-specific revenue.

Appeals and Judicial Review

• First Appeal: Competition Appellate Tribunal (COMPAT)
• Second Appeal: Supreme Court of India on substantial questions of law
• Interim Relief: COMPAT may grant stay on penalty payment (typically 10-25% deposit required)
• Expedited Timelines: DCB mandates time-bound adjudication (COMPAT must decide within 6 months)

Judicial Precedent on CCI's Investigative Powers:

• Mahindra Electric Mobility v. CCI (2019, Delhi HC) - Upheld constitutionality of Competition Act; CCI's investigative and penalty powers do not violate separation of powers
• WhatsApp LLC v. CCI (2021, Delhi HC) - CCI can exercise Section 26(1) powers independently even when related matters pending before higher courts

Comparative Analysis: Global Ex-Ante Regulatory Frameworks

EU Digital Markets Act (DMA)

Similarities with DCB 2024:

• Ex-ante framework targeting "gatekeepers" (equivalent to SSDEs)
• Quantitative designation thresholds (€7.5 billion EU turnover, 45 million monthly active end-users)
• Prohibits self-preferencing, tying, and data combination
• Mandates interoperability and data portability

Differences:

• Scope: DMA covers broader "core platform services" (16 categories vs. DCB's 10)
• Designation: DMA uses higher turnover thresholds; DCB more inclusive with lower user thresholds
• Enforcement: DMA penalties up to 10% of global turnover initially, 20% for repeated violations; DCB caps at 10%
• Interoperability: DMA has more detailed interoperability mandates for messaging and social networks

UK Digital Markets, Competition and Consumers Act 2024

Similarities:

• Strategic Market Status (SMS) designation similar to SSDE designation
• Focus on preventing leveraging of market power across ecosystems
• Conduct requirements tailored to specific markets

Differences:

• Regulator: Digital Markets Unit (DMU) within Competition and Markets Authority (CMA) vs. CCI Digital Markets Division
• Flexibility: UK regime more flexible with case-by-case conduct requirements; DCB has standardized obligations
• Consumer Focus: UK regime emphasizes consumer welfare more explicitly

Proposed US Regulations (American Innovation and Choice Online Act - AICOA)

Similarities:

• Targets "covered platforms" with self-preferencing and tying prohibitions
• User thresholds similar to DCB (50 million monthly US users)
• Penalty structure based on US revenue

Differences:

• Status: Still legislative proposal; not yet enacted
• Private Right of Action: US proposal allows private litigation; DCB enforcement only by CCI
• Antitrust Integration: US approach integrates with existing Sherman Act and Clayton Act enforcement

Lessons for India from Global Precedents

1. Calibrated Enforcement: EU's experience shows need for clear guidance and grace periods for initial compliance
2. Stakeholder Engagement: UK's consultation-heavy approach ensures buy-in and reduces litigation
3. Technical Expertise: EU's reliance on technical experts for algorithmic audits should inform CCI's capacity building
4. Interoperability Standards: Learning from EU's messaging interoperability challenges to define realistic technical standards

Practical Implications for Digital Enterprises

For Designated SSDEs

Immediate Actions Required (Within 6 Months of Designation)

1. Compliance Gap Assessment

   • Conduct comprehensive audit of current practices against DCB obligations
   • Identify areas of non-compliance (self-preferencing, tying, data practices)

2. Governance Structure

   • Appoint Chief Compliance Officer resident in India
   • Establish cross-functional compliance committee (legal, product, engineering, data science)

3. Policy Overhaul

   • Revise terms of service for business users to ensure fairness and transparency
   • Update privacy policies to reflect data separation and portability obligations

4. Technical Implementation

   • Develop APIs for data portability and interoperability
   • Implement data firewalls between different services
   • Modify algorithms to eliminate self-preferencing

Medium-Term Strategic Adjustments (6-18 Months)

1. Business Model Recalibration

   • Assess revenue impact of unbundling and non-discrimination obligations
   • Develop pricing strategies for previously subsidized/bundled services

2. Ecosystem Openness

   • Design third-party integrations and partnerships to comply with interoperability mandates
   • Consider open-sourcing certain protocols to facilitate compliance

3. Regulatory Engagement

   • Proactive engagement with CCI Digital Markets Division
   • Participate in industry consultations on technical standards

4. Litigation Preparedness

   • Anticipate challenges to designation or specific obligations
   • Build evidentiary record of compliance efforts

For Competitors and New Entrants

Leveraging the DCB for Competitive Advantage

1. Market Entry Opportunities

   • Interoperability mandates reduce network effect barriers
   • Data portability lowers switching costs, enabling user acquisition

2. Business User Advocacy

   • Represent business user interests in CCI proceedings
   • Document SSDE discriminatory practices for CCI investigations

3. Innovation Enablement

   • API access parity allows development of complementary services
   • Reduced fear of exclusionary conduct encourages R&D investment

For Business Users (Sellers, Advertisers, Developers)

Asserting Rights Under DCB

1. Transparency Demands

   • Request detailed explanations of ranking algorithms and changes
   • Demand access to performance data and analytics

2. Contractual Fairness

   • Challenge unfair MFN clauses and unilateral contract modifications
   • Negotiate better revenue-sharing terms leveraging DCB protections

3. Grievance Mechanisms

   • Utilize SSDE's internal dispute resolution processes
   • Escalate complaints to CCI Digital Markets Division if unresolved

4. Multi-Homing Strategies

   • Use interoperability and data portability to diversify platform presence
   • Reduce dependency on single SSDE platform

For Investors and M&A Advisors

Due Diligence Considerations

1. SSDE Designation Risk

   • Assess likelihood of target being designated as SSDE
   • Model financial impact of compliance costs and business model changes

2. Compliance Liabilities

   • Evaluate existing compliance gaps as contingent liabilities
   • Factor potential penalties into valuation

3. Regulatory Approval

   • DCB designation may trigger additional scrutiny for mergers and acquisitions
   • CCI may impose structural/behavioral remedies as merger conditions

Challenges and Criticisms of the DCB Framework

1. **Over-Broad Designation Criteria**

Concern: Low user thresholds (10 million end-users) may capture mid-sized platforms without genuine systemic significance.

Response: CCI has discretion to consider qualitative factors (market power, network effects) alongside quantitative thresholds. Designation is not automatic upon crossing thresholds.

2. **Compliance Costs and Innovation Chilling**

Concern: Stringent obligations may impose disproportionate compliance costs, diverting resources from innovation.

Response: Ex-ante regulation prevents costly ex-post litigation and creates level playing field, ultimately fostering innovation by reducing entry barriers for competitors.

3. **Technical Feasibility of Interoperability**

Concern: Mandating interoperability (especially for messaging and social networks) poses significant technical and security challenges.

Response: Phased implementation with technical standard-setting consultations can address feasibility concerns while preserving user privacy and security.

4. **Extraterritorial Overreach**

Concern: Applying obligations to global platforms based on India-specific user base may conflict with other jurisdictions' regulations.

Response: India's approach aligns with EU DMA and UK regime; global harmonization through multilateral cooperation can reduce regulatory fragmentation.

5. **Regulatory Capture Risk**

Concern: Powerful SSDEs may influence CCI's enforcement priorities and interpretations, leading to regulatory capture.

Response: Institutional safeguards (independent audits, transparency in decision-making, stakeholder consultations) and judicial oversight mitigate capture risk.

Judicial Precedents Informing DCB Enforcement

1. WhatsApp LLC v. Competition Commission of India (2021)

Court: Delhi High Court Case No: W.P.(C) 4378/2021 Judges: Justice Navin Chawla

Facts: WhatsApp and Facebook challenged CCI's suo motu investigation into WhatsApp's 2021 privacy policy update, which allegedly enabled data sharing with Facebook without user opt-out.

Issue: Whether CCI had jurisdiction to investigate under Section 26(1) when privacy issues were pending before Supreme Court.

Holding: CCI has autonomous jurisdiction to issue prima facie opinion and direct investigation under Section 26(1), even when related constitutional matters are pending elsewhere.

Significance for DCB:

• Establishes CCI's proactive investigative authority over digital platforms
• Confirms that privacy and competition concerns are interconnected but distinct
• CCI need not await resolution of parallel proceedings before acting
• Reinforces ex-ante approach: CCI can act on potential anti-competitive conduct before consummation

2. Telefonaktiebolaget LM Ericsson v. CCI (2023)

Court: Delhi High Court Case No: LPA 246/2016 Judges: Justice Najmi Waziri, Justice Vikas Mahajan

Facts: Ericsson challenged CCI's jurisdiction to investigate FRAND (Fair, Reasonable, and Non-Discriminatory) patent licensing terms, arguing that the Patents Act provided exclusive remedy.

Issue: Whether CCI can investigate anti-competitive conduct arising from patent licensing or whether the Patents Act ousts CCI's jurisdiction.

Holding: CCI has no jurisdiction to inquire into exercise of patent-licensing rights; the Patents Act provides a complete code with the Controller of Patents as exclusive authority.

Significance for DCB:

• Clarifies boundaries of CCI's jurisdiction: exclusive statutory regimes may oust Competition Act
• DCB must carefully delineate its scope to avoid conflicts with sectoral regulators (e.g., TRAI for telecom, RBI for fintech)
• Suggests that DCB should explicitly state its supremacy over other laws concerning designated SSDEs

3. Mahindra Electric Mobility Limited v. CCI (2019)

Court: Delhi High Court Case No: W.P.(C) 11467/2018 Judges: Justice S. Ravindra Bhat, Justice Prateek Jalan

Facts: Mahindra challenged the constitutional validity of the Competition Act 2002, arguing that CCI's composition and penalty powers violated separation of powers.

Issue: Whether the Competition Act and CCI's structure are constitutionally valid; whether Section 22(3) (casting vote) is ultra vires.

Holding:

• Competition Act is constitutionally valid
• CCI performs administrative, investigative, and quasi-judicial functions; not a pure tribunal
• Section 22(3) (casting vote) is unconstitutional
• CCI must ensure judicial member presence during final hearings

Significance for DCB:

• Affirms CCI's constitutional legitimacy to impose penalties and exercise quasi-judicial powers
• DCB's reliance on CCI as enforcer is constitutionally sound
• Procedural safeguards (judicial member presence) must be maintained in DCB enforcement
• Penalty provisions under DCB (up to 10% global turnover) are constitutionally permissible

Compliance Checklist for SSDEs

Phase 1: Pre-Designation Preparedness (Ongoing)

• Monitor user base growth (end-users and business users) to anticipate designation
• Conduct preliminary compliance audit against DCB obligations
• Identify high-risk practices (self-preferencing, tying, data combination)
• Establish internal compliance task force with legal, product, engineering, and data teams
• Engage external competition law advisors with digital markets expertise

Phase 2: Post-Designation Immediate Actions (0-6 Months)

• File representations with CCI if contesting designation
• Appoint Chief Compliance Officer resident in India
• Conduct comprehensive compliance gap analysis
• Develop detailed compliance roadmap with timelines
• Implement data firewalls and access controls
• Revise terms of service for business users
• Publish transparency reports on ranking algorithms and policies

Phase 3: Technical Implementation (6-18 Months)

• Develop and deploy data portability APIs
• Implement interoperability protocols (especially for messaging/social networks)
• Modify algorithms to eliminate self-preferencing
• Unbundle tied/bundled services
• Establish independent audit mechanisms
• Deploy real-time compliance monitoring tools
• Create grievance redressal platform for business users

Phase 4: Ongoing Compliance (Annual)

• Submit annual compliance report to CCI
• Conduct third-party compliance audits
• Update compliance practices based on CCI guidance and enforcement actions
• Monitor algorithm changes for compliance implications
• Engage with industry working groups on technical standards
• Train employees on DCB obligations and compliance protocols

Conclusion

The Digital Competition Bill 2024 represents a historic shift in India's approach to regulating digital markets. By embracing ex-ante regulation, India joins the global movement toward proactive, preventative oversight of systemically significant platforms. The DCB's focus on clear, enforceable obligations—rather than protracted post-violation investigations—promises more effective protection of competition and consumer welfare in fast-moving digital ecosystems.

For designated SSDEs, the DCB demands fundamental recalibration of business models, data practices, and ecosystem strategies. Compliance will require significant investment in technical infrastructure, governance processes, and cultural transformation. However, the alternative—costly ex-post enforcement actions with unpredictable penalties and reputational damage—makes proactive compliance the prudent strategic choice.

For competitors, new entrants, and business users, the DCB creates unprecedented opportunities. Lower barriers to entry, mandated interoperability, and protection against discriminatory practices level the playing field. Startups and SMEs can now compete on merit rather than being foreclosed by incumbent gatekeepers.

For regulators and policymakers, the DCB's success will depend on three critical factors:

1. Institutional Capacity: CCI must rapidly build technical expertise in algorithm auditing, data science, and digital platform economics
2. Stakeholder Collaboration: Effective standard-setting for interoperability and data portability requires industry, civil society, and academic input
3. Adaptive Enforcement: Digital markets evolve rapidly; CCI must remain agile, updating guidance and obligations as technologies and business models change

As India's digital economy continues its exponential growth trajectory—projected to reach $1 trillion by 2030—the DCB 2024 provides the regulatory foundation for ensuring that this growth is competitive, innovative, and equitable. The next decade will test whether India's ex-ante framework can deliver on this promise, setting a potential model for other emerging digital economies worldwide.

Sources

Judicial Precedents

1. WhatsApp LLC v. Competition Commission of India, Delhi High Court, W.P.(C) 4378/2021, dated 22 April 2021

   • Relevance: CCI's proactive investigative jurisdiction over digital platforms

2. Telefonaktiebolaget LM Ericsson v. Competition Commission of India, Delhi High Court, LPA 246/2016, dated 13 July 2023

   • Relevance: Boundaries of CCI jurisdiction vis-à-vis sectoral regulators

3. Mahindra Electric Mobility Limited v. CCI, Delhi High Court, W.P.(C) 11467/2018, dated 10 April 2019

   • Relevance: Constitutional validity of Competition Act and CCI's powers

Legislative and Regulatory References

4. Digital Competition Bill 2024 (Draft as introduced in Parliament)
5. Competition Act 2002 (as amended through 2023)
6. Competition Commission of India (Procedure in regard to the transaction of business relating to combinations) Regulations 2011
7. EU Digital Markets Act (Regulation 2022/1925)
8. UK Digital Markets, Competition and Consumers Act 2024

Reports and Policy Documents

9. Competition Commission of India, Annual Report 2023-24
10. NITI Aayog, Discussion Paper on Digital Competition Law (2023)
11. European Commission, Digital Markets Act: Ensuring Fair and Open Digital Markets (2020)
12. UK Competition and Markets Authority, A New Pro-Competition Regime for Digital Markets (2021)