In brief
The dealer management system (DMS) handles a dealership's business transactions: vehicle stock, orders, workshop, parts and invoices. The CRM manages the relationship with the customer: enquiries, conversations, offers and next steps. Problems arise when nobody has defined which system owns which data and customer data is maintained in several places.
What is a DMS, what is a CRM?
The DMS is the commercial backbone of the dealership. It has its roots in inventory management and accounting and thinks in transactions: one vehicle, one order, one invoice.
The CRM thinks in relationships: a person or a company with all their contacts, interests and vehicles over the years. It starts long before the first order and does not end with the invoice.
| DMS | CRM | |
|---|---|---|
| Core task | Handling business transactions | Managing customer relationships |
| Thinks in terms of | Vehicle, order, invoice | Person, contact, next step |
| Starts | With the offer or order | With the first sign of interest |
| Typical users | Vehicle logistics, workshop, accounting, sales | Sales, customer care, marketing, management |
| Typical data | Stock, prices, orders, workshop history | Enquiries, conversations, consents, tasks |
Simplified view. Many systems cover parts of both tasks.
Which system owns which data?
For each type of data, exactly one system should be the leading system. The other systems read this data or receive a copy, but do not change it on their own.
- Customer master data
Name, address and contact details need one leading source. Which one that is depends on the system landscape. What matters is that there is only one.
- Vehicle and order
Owned by the DMS or, in direct sales, by the manufacturer's system.
- Enquiries and contacts
Owned by the CRM, including conversation notes and follow-up reminders.
- Workshop history
Owned by the DMS. The CRM displays it so that sales knows what has happened with the vehicle.
- Consents
Who may be contacted for what has to be recorded in one place and apply in all systems.
An example: one customer's path through both systems
How the systems work together is best shown by the path of a single customer from first contact through to the workshop.
- 1. Enquiry
The customer enquires about a used car via a vehicle marketplace. A lead is created in the CRM with the vehicle, contact channel and person responsible. The DMS does not know about it yet.
- 2. Conversation and test drive
Notes, appointment and next step are recorded in the CRM. Vehicle data, such as location and price, comes from the DMS.
- 3. Offer and order
With the order, the transaction is created in the DMS. The customer master data is taken over from the leading system and not created again.
- 4. Vehicle handover and invoice
The DMS handles delivery and invoicing and reports the completed sale back to the CRM. The lead is closed there as won.
- 5. Workshop
The first service is recorded in the DMS. The CRM shows it in the customer profile and reminds sales when a contract or warranty is about to expire.
Which interfaces are typically needed?
| Direction | What to watch out for | |
|---|---|---|
| Customer master data | From the leading system to the other | One rule for duplicates and for changes to address and contact details |
| Vehicle stock and prices | From the DMS to the CRM | Up-to-date data, so that no vehicle that has already been sold is offered |
| Order status | From the DMS to the CRM | The completed sale must close the lead in the CRM |
| Workshop history | From the DMS to the CRM | Display only, no changes in the CRM |
| Consents | From the leading source to all systems | A withdrawal of consent must reach every system |
Which interfaces are technically possible depends on the systems in use.
Why are interfaces the real work?
The systems themselves are rarely the problem. The effort lies in connecting them: which data flows in which direction, how often, and what happens when there is a conflict? Without answers to these questions, duplicates arise and nobody knows which version is valid.
In multi-brand dealer groups, there is the added factor that every brand brings its own portals and requirements. A group-wide CRM can bring these worlds together if the data flows have been clarified beforehand.
Who may access customer data: manufacturer or dealer?
In the dealer model, the dealership is the customer's contractual partner and collects their data in this role. In the agency model, the customer concludes the contract with the manufacturer, and the dealership's access is governed by the agency agreement.
Regardless of the model, what may be done with customer data is determined by data protection law and the customer's consents. How manufacturer and dealer share data should therefore be settled contractually and technically before systems are connected. This section does not constitute legal advice.
How do you go about it?
Four steps create order before a new system is added. What a CRM has to deliver beyond this is described in the article CRM at the dealership.
- 1. List the systems
Write down every system that holds customer data, including manufacturer portals, marketplaces and spreadsheets.
- 2. Define the leading system
Decide for each type of data where it is maintained.
- 3. Map the data flows
Record what is transferred where and who is responsible when errors occur.
- 4. Clean up the data
Remove duplicates and outdated contacts before connecting the systems, not afterwards.
Frequently asked questions
What is a DMS at a dealership?
DMS stands for dealer management system. It is the system a dealership uses to handle vehicle stock, orders, workshop, parts and invoices.
Can a DMS replace a CRM?
For smaller single-brand dealerships, the CRM functions of the DMS may be sufficient. As soon as several brands, locations or channels come together, this reaches its limits, because the DMS thinks in transactions rather than in customer relationships.
What does leading system mean?
The leading system is the place where a particular type of data is maintained. All other systems take this data from there. This way, there is exactly one valid version for every question.


