DMS vs. CRM vs. CDP: what each system holds, and which one feeds your website
The average dealership runs more than 40 software systems. Three of them hold the data that matters, and only one of them produces something a buyer who has never been in the store will ever see.
The average dealership relies on more than 40 different software systems, according to Cox Automotive's 2025 survey of 537 dealership leaders. Three of them hold the data that matters: the DMS, the CRM and, at a growing number of groups, a CDP. Most of what is written about the three is written by a vendor of one of them. This is written by a firm that sells none.
VulcanAX handles search visibility. The reason to write about the dealership tech stack anyway is narrow and specific: two of these three systems produce the data that decides what a search engine or an AI assistant can say about the store, and one of them produces the only output a buyer who has never been in the building will ever see. Sorting the three by what each one holds is useful. Sorting them by what each one sends outside is the point.
What a DMS is, and what it holds
A dealer management system is the system of record. Accounting and payroll. The deal and its F&I products. Parts inventory. Repair orders. And the inventory ledger: every unit the store owns, by VIN, with its cost, its age and its status. Every department writes to it and every other piece of software in the building reads from it, directly or through a certified integration. The major vendors are CDK Global, Reynolds and Reynolds, Tekion, Dealertrack from Cox Automotive, and Auto/Mate.
The clearest demonstration of what a system of record is came on June 18, 2024, when a ransomware attack took CDK Global's DMS offline. Roughly 15,000 dealerships in the United States and Canada wrote deals and repair orders by hand for the better part of two weeks. Anderson Economic Group put direct dealer losses at $1.02 billion over the three weeks that included June 19 through July 5: lost earnings on about 56,200 new-vehicle sales, lost used and fixed ops earnings, extra staffing and IT costs, and additional floor plan interest on inventory that could not be sold. Not a vendor going down. The store going down, because the ledger did.
What a CRM is, and what it holds
A customer relationship management system is the system of engagement: who the store is talking to, about what, and when it last did. Leads and their sources. Response times. Customer contacts, tasks and follow-up cadences. The sales conversation and, in stores that run it there, the service conversation. VinSolutions, DealerSocket, Elead, DriveCentric and Tekion's CRM are the names most stores are choosing between.
The CRM is where a dealership's marketing lives, and it is only as good as its match to the DMS. A CRM that cannot see the DMS cannot tell a lead from a sale, so the sales report stops at the lead and every campaign is judged on a count of people who filled out a form. The dealership analytics post covers why that is the most common measurement failure in the store; the short version is that it is an integration failure wearing a reporting costume.
Cox Automotive's 2025 study of what dealers want from AI is, read closely, a description of what they want from the CRM: 52% named engaging with customers around the clock by automated text, chat or email, 48% named personalised emails and texts, and 39% named predicting which consumers are ready to buy. Every one of those runs on CRM data, and 60% of the same dealers cited concerns with data and algorithms. They are describing the same problem from both ends.
What a CDP is, and whether a dealership needs one
The CDP Institute's definition is short: software that creates and maintains a persistent, unified customer record that is accessible to other systems. In a dealership that means ingesting the DMS, the CRM, website behaviour, service history and ad exposure, deduplicating all of it into one profile per household, and pushing audiences out to the ad platforms and back into the CRM. Fullpath, automotiveMastermind and Orbee are the automotive names.
Two things are worth saying that the category's marketing does not. The first is that a CDP holds nothing the other two systems do not already have. Its job is unification, so it is exactly as good as the match between the DMS and the CRM underneath it, and a store that buys one to fix a bad match has bought a third copy of the disagreement.
The second is that the urgency case has changed. Much of the CDP pitch from 2020 onward was built on third-party cookies disappearing from Chrome and first-party data becoming the only targeting left. On April 22, 2025, Google announced it would maintain its current approach to third-party cookies in Chrome and would not roll out a new standalone prompt. First-party data is still the better asset. It is no longer the only one, and a purchase justified on the deadline should be re-justified on the merits.
The merits are real for a specific store: a group with several rooftops, several CRMs and a marketing team that buys audiences, where nobody else in the stack can produce one profile per household across stores. A single rooftop with a clean DMS-to-CRM match usually does not need one; the CRM's segmentation does the work.
DMS vs. CRM vs. CDP, side by side
| DMS | CRM | CDP | |
|---|---|---|---|
| Role | System of record | System of engagement | System of unification |
| Holds | Accounting, payroll, deals and F&I, parts, repair orders, the inventory ledger by VIN | Leads, sources, response times, contacts, tasks, conversations | One persistent profile per household, stitched from the other two plus web and ad data |
| Who lives in it | Accounting, F&I, parts, service, the used car manager | Sales, BDC, service advisors in some stores | Marketing, usually at the group level |
| Sends outside the store | The inventory feed: website VDPs, structured data, Google Vehicle Ads, Meta inventory ads, marketplace listings, what AI assistants can read | Messages to people the store already knows | Audiences to ad platforms; segments back to the CRM |
| Vendors, as of 2026 | CDK Global, Reynolds and Reynolds, Tekion, Dealertrack, Auto/Mate | VinSolutions, DealerSocket, Elead, DriveCentric, Tekion | Fullpath, automotiveMastermind, Orbee |
| Failure mode | Everything stops; June 2024 cost dealers $1.02 billion in three weeks | Attribution stops at the lead; duplicate customers | A third copy of a DMS-to-CRM disagreement |
| Who sees its output | Every stranger searching for a unit | Existing customers | Ad platforms and the store |
Where the three break against each other
Every store with all three has the same four seams, and the cost of each shows up in a department that did not cause it.
The sold-unit match. A lead in the CRM and a deal in the DMS describe the same event, and if the integration cannot join them, the CRM never learns the lead sold. The consequence is that marketing is judged on leads and finance on units, and the two reports cannot be reconciled. This is the single most expensive seam because it decides where next year's budget goes.
The retype. Without a certified integration, the deal is entered in the CRM and again in the DMS, the repair order is keyed into the service tool by hand, and inventory changes reach the website when someone pushes them. Each retype is a chance for a VIN, a price or a customer name to disagree between systems, and the disagreement surfaces later as a wrong price on a live page or a customer who receives two versions of the same reminder.
The duplicate household. A customer who bought at one rooftop and services at another is two records until something unifies them. This is the problem CDPs exist to solve and the reason they are a group product more than a single-store one.
Feed latency. The inventory ledger changes the moment a unit is stocked or sold. The website changes when the feed runs. The gap between the two is the period during which the store advertises cars it no longer has and hides cars it just landed, and on a lot that turns in 46 days, as the market currently does, a daily feed is losing a measurable share of every unit's selling window. The inventory velocity post treats that gap as the lever nobody owns.
Which one feeds your website
This is where the sort by output earns its place. The CRM sends messages to people the store already knows. The CDP sends audiences to ad platforms. Neither produces anything a stranger will see. The DMS does, and it does it through one artefact: the inventory feed.
The units in the DMS ledger flow, usually through an inventory management or merchandising tool that adds photos and descriptions, to the website provider, which builds a vehicle detail page for each one. The same feed or a copy of it goes to Google Merchant Center for Vehicle Ads, to Meta for inventory ads, to the marketplaces, and, through the structured data on each VDP, to whatever a search engine or an AI assistant can read about the unit. Google's vehicle ads policy requires the price in the data source and the structured data to exactly match the price on the landing page, which is a rule about the feed dressed as a rule about ads.
So a question that sounds like an IT question is a marketing question. How often does the feed run. Which fields does it carry: trim, options, mileage, price, photos, or a subset. Does the website vendor render price from the feed or through a script that engines cannot read. Does the structured data on the VDP say what the feed says. Every buyer who has not chosen a store yet, and every AI assistant asked to name one, is reading the answer to those questions. Nobody in the store is measured on them, which is the recurring finding across this whole subject. The paid search post makes the same point from the ad side: the vehicle ad and the organic result are reading the same page.
How to evaluate the stack without sitting through a demo
Six questions, none of which requires a login. Who owns the data and can the store export all of it, in a usable format, on the day it leaves the vendor. Which integrations are certified, by the DMS vendor and by the OEM, because an uncertified integration is a retype waiting to happen. How often the inventory feed runs and what triggers it. Whether the sold-unit match exists, and whether the CRM can show a lead-to-sale rate by source without a spreadsheet. Whether the price on a live VDP is in the page's structured data, which anyone can check with view source. And what happened to the vendor's customers in June 2024, because every vendor has an answer now and the answers differ.
The Cox study's 74% of dealers worried about AI accuracy and 60% worried about data are, in the end, the same worry. A model reading a store's data can only be as accurate as the data, and the data is as accurate as the seams between these three systems allow.
What VulcanAX does and does not touch here
VulcanAX does not sell, implement or integrate a DMS, a CRM or a CDP, and the vendor names on this page are here for orientation rather than recommendation; confirm current ownership and certification before shortlisting any of them.
What VulcanAX handles begins where the feed leaves the building: whether each unit's VDP is indexed, whether its structured data carries the price, trim and mileage the feed does, and whether a search engine or an AI assistant can read the unit at all. That is technical SEO for dealerships and VDP and SRP work, and it is the only part of the stack a stranger interacts with. The three systems upstream stay with the store and the vendors that run them, where they belong.
FAQ
What is a DMS in automotive?
A dealer management system is the dealership’s system of record: the software that holds accounting, payroll, deals and F&I, parts, repair orders and the inventory ledger by VIN. Every department writes to it and every other system in the store reads from it. The major vendors are CDK Global, Reynolds and Reynolds, Tekion, Dealertrack (Cox Automotive) and Auto/Mate. When it stops, the store stops: the June 2024 ransomware attack on CDK took roughly 15,000 dealerships back to paper for the better part of two weeks, and Anderson Economic Group estimated direct dealer losses at $1.02 billion over three weeks, including about 56,200 lost new-vehicle sales.
What is the difference between a DMS and a CRM at a dealership?
The DMS records what the store owns and owes; the CRM manages who the store is talking to. A CRM holds leads, their sources and response times, customer contacts, tasks and the sales and service conversations, and it is where follow-up lives. The DMS holds the deal once it is written, the repair order once it is opened, and the unit itself. The line between them is the sold-unit match: a CRM that cannot see the DMS cannot tell a lead from a sale, which is why attribution at most stores stops at the lead. The main automotive CRMs are VinSolutions, DealerSocket, Elead, DriveCentric and Tekion’s CRM.
What is an automotive CDP?
A customer data platform, in the CDP Institute’s definition, is software that creates and maintains a persistent, unified customer record that is accessible to other systems. In a dealership it ingests the DMS, the CRM, website behaviour, service history and ad exposure, deduplicates them into one profile per household, and pushes audiences out to ad platforms and back into the CRM. Automotive CDPs include Fullpath, automotiveMastermind and Orbee. Its job is unification; it holds nothing the other systems do not already have, and it is only as good as the match between them.
Does a dealership need a CDP?
A single rooftop with a clean DMS-to-CRM match usually does not; the CRM’s segmentation does the work and a CDP would be a third copy of the same records. A group with several rooftops, several CRMs and a marketing team that buys audiences does, because nobody else in the stack can produce one profile per household across stores. Two cautions. The urgency case for CDPs was built on third-party cookies disappearing, and Google announced on April 22, 2025 that Chrome would keep them and not roll out a standalone opt-out prompt. And a CDP does not fix bad source data; it unifies it. Clean the DMS-to-CRM match first.
Which dealership system feeds the website?
The DMS, through the inventory feed. The units in the DMS inventory ledger flow, usually through an inventory management or merchandising tool that adds photos and descriptions, to the website provider, which builds a vehicle detail page for each one. That same feed, or a copy of it, goes to Google Merchant Center for Vehicle Ads, to Meta for inventory ads, to the marketplaces, and, through the structured data on each VDP, to whatever a search engine or an AI assistant can read about the unit. The CRM and the CDP feed nothing a stranger sees. The DMS feed is the only output of the stack that faces the public.
What happened when CDK went down in 2024?
On June 18 and 19, 2024, a ransomware attack on CDK Global took its dealer management system offline for roughly 15,000 dealerships in the United States and Canada. Stores wrote deals and repair orders by hand for the better part of two weeks while the system was restored. Anderson Economic Group estimated direct losses to franchised dealers at $1.02 billion over the three weeks that included June 19 through July 5, including lost earnings on about 56,200 new-vehicle sales, lost used-vehicle and fixed ops earnings, extra staffing and IT costs, and additional floor plan interest. It is the clearest demonstration on record of what a system of record is.
How do DMS integrations reduce manual data entry in dealerships?
By letting the other systems read the record instead of retyping it. Without a certified integration, a lead that becomes a deal is entered once in the CRM and again in the DMS, a repair order is keyed into the service CRM by hand, and inventory changes reach the website when someone remembers to push them. Each retype is a chance for a price, a VIN or a customer record to disagree between systems. An integration replaces the retype with a read, so the deal closes in the DMS and the CRM marks the lead sold on its own, the repair order opens once, and the feed updates the website when the ledger changes. The cost of not having it shows up as duplicate customers, mismatched prices and attribution that stops at the lead.
Who are the main DMS, CRM and CDP vendors for car dealerships?
DMS: CDK Global, Reynolds and Reynolds, Tekion, Dealertrack (Cox Automotive), Auto/Mate (DealerSocket). CRM: VinSolutions (Cox Automotive), DealerSocket, Elead (CDK), DriveCentric, Tekion. CDP and customer data: Fullpath, automotiveMastermind (S&P Global Mobility), Orbee. The category consolidates constantly, several vendors now sell in two of the three columns, and OEM certification requirements decide much of the shortlist before a store gets a vote, so confirm the current ownership and certification of any name before shortlisting it.
What is CRM in service, or a service CRM?
The service-department half of the CRM: appointment scheduling, reminders, declined-work follow-up, recall outreach and the service conversation history, tied to the repair orders in the DMS. Some stores run it inside the sales CRM, some in a separate fixed ops tool from the same vendor, and some in the scheduling product their website vendor supplies. The failure mode is the same as on the sales side: if the service CRM cannot read the DMS repair order, it cannot tell what was declined, and declined-work follow-up becomes a seasonal offer to everyone.
What does VulcanAX handle here?
The public-facing end of the DMS feed, and nothing upstream of it. VulcanAX does not sell, implement or integrate a DMS, a CRM or a CDP. What it handles is what happens to the inventory feed once it leaves the building: whether each unit’s vehicle detail page is indexed, whether the structured data on it carries the same price, trim and mileage the feed does, and whether a search engine or an AI assistant can read the unit at all. Those are the questions the stack vendors do not answer because the feed, from their side, is a file that left.