Loop, LLC v. CDK Global, LLC (In re Dealer Mgmt. Sys. Antitrust Litig.)

362 F. Supp. 3d 477
CourtDistrict Court, E.D. Illinois
DecidedJanuary 25, 2019
DocketCase No. 18-cv-864
StatusPublished
Cited by3 cases

This text of 362 F. Supp. 3d 477 (Loop, LLC v. CDK Global, LLC (In re Dealer Mgmt. Sys. Antitrust Litig.)) is published on Counsel Stack Legal Research, covering District Court, E.D. Illinois primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Loop, LLC v. CDK Global, LLC (In re Dealer Mgmt. Sys. Antitrust Litig.), 362 F. Supp. 3d 477 (illinoised 2019).

Opinion

Robert M. Dow, Jr., United States District Judge

Before the Court is Defendant CDK Global, LLC's motion to dismiss [259] the amended complaint filed by Plaintiff Loop, LLC. For the reasons set forth below, the motion is denied.

I. Background1

Plaintiff Loop, LLC ("AutoLoop" or "Plaintiff") brings this action on behalf of itself and other automotive software application vendors to remedy and enjoin purported ongoing antitrust and state law violations by Defendant CDK Global, LLC ("CDK" or "Defendant"). [194 (Am. Compl.), at ¶ 1.] Plaintiff alleges that CDK and its non-party co-conspirator The Reynolds and Reynolds Company ("Reynolds") have committed antitrust violations and inflicted widespread harm on automotive dealers, vendors of software products and services (like Plaintiff), and the automotive industry by conspiring to eliminate competition for providing data integration services for dealer data. [Id. at ¶ 2.] Plaintiff is an automotive software products and services company, providing integrated *483software solutions to more than 2,000 car dealers across the country. [Id. at ¶ 6.] Plaintiff offers three suites of software: sales, service, and marketing. [Id. at ¶ 7.] Each suite includes multiple software applications that dealers can select to enhance their ability to sell cars and serve customers. [Id. ] Vendors like Plaintiff need access to dealer data for their products and services to function. [Id. at ¶ 8.] This dealer data includes vehicle and parts inventory, customer name and contact information, customer leads, completed and pending sales information, vehicle financing and insurance ("F & I") information, vehicle pricing information, and service and repair information. [Id. ]

A. The DMS Market

Dealers traditionally have stored a significant portion of their data on a database within their data management system ("DMS"), which is software that dealers use to help manage their businesses (e.g. , accounting, sales, service, and human resources). [Id. at ¶ 9.] Defendant and non-party Reynolds both have significant market power in the DMS market. [Id. at ¶ 10.] Together, they control approximately 75% of the United States market by number of dealers and approximately 90% when measured by number of vehicles sold. [Id. ] Defendant controls approximately 45% of the DMS market, and Reynolds controls approximately 30%. [Id. ] Switching DMS providers presents significant logistical challenges and is highly disruptive to business operations. [Id. at ¶ 48.] It can take a dealership more than a year of preparation, staff training, and testing before a new DMS can be put into operation, resulting in significant training and implementation costs. [Id. ] The average DMS client tenure is more than 20 years. [Id. at 68.] Defendant's own CEO publicly has recognized that dealers are hesitant to switch DMSs because the process can take time and can be very difficult. [Id. at ¶ 49.]

In addition to their DMSs, Defendant and Reynolds offer standalone software applications that compete directly with applications offered by Plaintiff and other third-party vendors. [Id. at ¶ 11.] DMS providers (including Defendant and Reynolds) historically have allowed dealers to provide third parties (including vendors like Plaintiff) automated access to the dealer data stored on their DMSs through data integration service providers, which collect and standardize the data to provide it to the dealer's chosen third-party vendors. [Id. at ¶ 12.] Plaintiff sells automotive software products and services to dealers, including applications that help dealers market, sell, and service cars. [Id. at ¶¶ 6-7.] Plaintiff's applications, like those of other vendors, require access to dealer data stored on a dealers' DMSs. [Id. at ¶ 8.]

B. The Dealer Data Integration Market

The Data Integration Services ("DIS") market consists of services that provide access to dealer data on their respective DMSs. [Id. at ¶ 56.] Data integrators (i.e. , DIS providers) also may provide value-enhancing services, such as putting data from different DMSs in a uniform format, data hygiene (i.e. , error correction), and granular control by dealers over which vendors receive which data. [Id. ] Defendant and Reynolds each provide data integration services for their respective DMSs. [Id. at ¶ 13.] Defendant's data integration service is known as Third Party Access ("3PA"), and Reynolds's data integration service is known as the Reynolds Certified Interface ("RCI"). [Id. ] Third parties also have provided competing data integration services. [Id. ] Indeed, Defendant owns two such third-party data integrators-Digital Motorworks, Inc. ("DMI") and IntegraLink. [Id. ] Other third-party data integrators have included Authenticom, Inc. ("Authenticom") and Superior Integrated *484Solutions, Inc. ("SIS"). [Id. ] At one time, both CDK and Reynolds had "open" DMSs, meaning that neither took steps to prevent dealer clients from authorizing third-party access to the dealers' data. [Id. at ¶ 14.] During this time, the competition between data integration services made access to dealer data cost effective. For example, an application vendor could pay a data integrator $ 50 per dealer per month. [Id. ] With dealers in control of access to and use of their data, vendors created an array of innovative software products and services to help dealerships market, sell, lease, and service cars. [Id. ]

Over time, Reynolds began to "close" its DMS by selectively blocking third-party data integrators from accessing dealer data stored on the Reynolds DMS. [Id. at ¶ 15.] As Reynolds reduced competition for DIS through its blocking activities, Reynolds increased the fees it charged for data integration through RCI. [Id. ] Defendant continued to differentiate its product as an "open" DMS. [Id. ] At the same time, Defendant's own data integration businesses provided vendors with access to dealer data on the Reynolds DMS. [Id. ] Defendant's open-access policy allowed it to gain (albeit very slowly) DMS customers at Reynolds's expense and to enter long-term contracts with those dealers. [Id. ] Defendant marketed its "open" system directly to dealers and issued press releases stressing that it "believes in the fair competitive environment and does not use its leverage through supply of the dealer management system to reduce competition through the restriction of data access." [Id. at ¶ 86.]

C. Alleged Agreement

That competition between Defendant and Reynolds halted in early 2015 when Defendant began blocking dealers from granting third-party access to dealer data and, at the same time, agreed to shut down its data integration business for dealers using a Reynolds DMS. [Id. at ¶ 16.] Plaintiff alleges that these changes were the result of horizontal agreements with Reynolds. [Id .] Effective February 18, 2015, Defendant and Reynolds entered into three written agreements. [Id.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
362 F. Supp. 3d 477, Counsel Stack Legal Research, https://law.counselstack.com/opinion/loop-llc-v-cdk-global-llc-in-re-dealer-mgmt-sys-antitrust-litig-illinoised-2019.