Tying and Bundling

A tie is familiar in ordinary commerce. “You can buy A only if you also take B.” Bundling is broader and sometimes softer. Two products may be sold together because it is cheaper, more convenient, or technically better to do so that way. Most bundles are not competition problems. A printer sold with software, a phone sold with a charger, or a software suite sold as an integrated package may save costs and improve user experience. Indian competition law therefore does not condemn every commercial package. It asks whether distinct products are being linked in a way that forecloses choice or leverages market power.

The statutory hooks appear in more than one place. Section 3(4) treats a tie-in arrangement as a vertical restraint that becomes unlawful if it causes or is likely to cause an appreciable adverse effect on competition. Section 4 also matters where the tying firm is dominant. A dominant firm may abuse its position by making contracts subject to supplementary obligations unrelated to the subject of the contract, or by using dominance in one market to enter into or protect another. In practice, the same pattern can therefore be examined both as a vertical restraint and as abuse of dominance, depending on the facts.

The key commercial question is whether the tied products are truly distinct and whether the customer has a meaningful choice. If the products are naturally integrated, the law is usually cautious. If, however, the seller enjoys power in a must-have product and uses that power to push a separate product that customers would otherwise choose independently, the analysis changes. Concern rises where the tie changes not just what the customer buys, but what rival sellers can no longer realistically supply. That is why tying cases often turn on foreclosure, not only on compulsion.

The most important Indian example is the Android mobile devices matter against Google. The Commission found anti-competitive conduct linked to compulsory pre-installation of Google’s app suite, tying of the Play Store with other Google applications, and restrictions that protected Google’s ecosystem position. What makes the case so important is that the tie was not conceptual or theoretical. It operated through product design, default architecture, OEM contracts, and the commercial centrality of the Play Store. Once a product is a gateway that OEMs feel they must take, tying adjacent applications can materially shape market outcomes.

The Android orders also show why tying is not just about one forced purchase. It can become a way of protecting an ecosystem. If a powerful gateway product is licensed on terms that require or strongly induce use of affiliated products, rivals may lose distribution at the decisive point where user choice is formed. That is especially significant in digital markets because defaults, pre-installation, and app position can influence user behaviour long before any explicit choice is made. The NCLAT’s decision to uphold the penalty and a substantial part of the remedial directions confirms that these concerns were not treated as merely speculative.

At the same time, Indian law has not treated every closed ecosystem as a final violation. In the Apple App Store matter, the Commission in 2021 ordered an investigation into alleged restrictions on app distribution and compulsory use of Apple’s in-app purchase system, but that order was only a prima facie Section 26(1) step. It should not be cited as a final finding. Its relevance is narrower. It shows the kind of questions the Commission now asks about tying, self-preferencing, and access control in app ecosystems.

The practical way to think about tying is this. Integration is common and often beneficial. The legal problem begins when a firm with real market power links a must-have product to a second product in a way that customers cannot realistically avoid and rivals cannot realistically overcome. Businesses should therefore be clear about why the products are linked. Is the linkage technical, security-driven, quality-driven, or simply strategic. The stronger the power in the tying product, the stronger the need for a credible efficiency story.

For readers trying to make the concept intuitive, the simplest example is a landlord who says you may rent the only viable office premises in the district, but only if you also buy his internet service, his security service, and his furniture package. If the premises are genuinely unavoidable, and the added products are distinct, the concern is obvious. The same intuition travels into operating systems, app stores, insurance channels, and consumer devices. Indian law is asking a version of the same question each time. Is the bundle efficient, or is it a way of carrying power from one product into another?